{'fraction_non_alphanumeric': 0.01740139211136891, 'fraction_numerical': 0.0, 'mean_word_length': 4.831081081081081, '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}}
The design team as a "system of systems"

Systems of Systems (SoS) are defined - amongst other distinguishing features - as a collection of component systems that produce results not achievable by the individual systems alone. But SoS is more than just a higher level focus on factors that are primarily concerned with the mechanics of data handling. SoS deals with the process of work-in-progress and how the design drives the implementation. It seems reasonable to couch the teams and constituent people involved in developing those system of systems products as fitting the definitions equally well. This paper will build on earlier work that looked at the process, design and implementation issues that distinguish Systems of Systems, but take up themes from ensuing discussion and explore the team and people aspects of the System of Systems design process.