{'fraction_non_alphanumeric': 0.027877055039313797, 'fraction_numerical': 0.0, 'mean_word_length': 5.1946902654867255, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Graphical User Interface definition processes in the frame of Systems-of-Systems

In the frame of naval forces, coordination means have always been in constant evolution through centuries, from marine flags to radio communications and more recently with tactical data links. Nowadays a naval ship is being considered as part of larger systemsof-systems, and could even be possibly a kind of systemof-systems itself. Through interactions anticipation within others existing and future contributing systems, that will possibly include some sub-systems to be integrated on board, and more surely crews to operate them, the design of next generation surface and submarine combat ships has to cope with the systemsof-systems issues. The question to be raised is thereby: How methods and tools that support graphical user interface definition and development process are facing the systems-of-systems issues? This article aims to first list the existing and emerging solutions for Graphical User Interface design in the frame of combat ship: (i) from a crew-centered approach point of view, (ii) for specification and modelling, in the frame of system engineering; (iii) for specification, prototyping and (iv) for development and testing. In a second time, we will discuss if those emerging solutions can handle the SoS specificities, and what are the ones they can't, trying to propose tracks for those.