Design as the best differentiator of system-of-systems

Systems of Systems are defined as a collection of component systems that produce results not achievable by the individual systems alone. SoS serves to distinguish true multi-domain and multi-discipline systems from others who have taken up the systems mantle, most noticeably software and IT spaces. But SoS is more than just a higher level focus on configuration management (CM), requirements management (RM), data management strategies (CMS) and integrated logistics support (ILS). These factors 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. The design is the guiding element for the system or product. This paper will distill the process, design and implementation issues that distinguish Systems-of-Systems from subsystems and domain-specific systems. These differentiated factors will be illustrated in case studies that focus on safety-critical processes common in aviation, rail, road and automotive development. For example, one commonly required is the need to gauge process maturity as found in the CMMI, Automotive Spice, Aviation ARP4754A and, more recently, the automotive ISO-26262 “Fitfor-Purpose” certifications. All of these strive to measure the worthiness of hardware-software systems. All such systems are in fact assembled from other systems, thus creating true `system of systems' final implemented products. Without consideration of the system of systems aspects from the initial inception throughout the design flow, such systems inevitably experience numerous iterations, regulatory challenges and delivery delays. By paying appropriate attention to the full broader set of issues - through effectively applying systems engineering approaches and relevant standards from the concept through design and into implementation and delivery, critical improvements in process and product lead to successful results.