1.1 MOTIVATION
A little longer than a decade ago, the community of systems engineers started to seriously deal with a category of challenges: system of systems (SoS).
Systems Engineering (SE) is now better understood since its official birth as a discipline in the middle of the last century. It is widely understood to control the total systems life cycle process: definition, development, deployment, and retirement of a system. SE ensures that solutions are reliable, maintainable, and cost-effective. But its solutions focus on a system made up of components born from a common set of user requirements. Interactions with other systems was always possible, but these other systems were external and beyond the central systems boundaries.
In particular, the Internet showed the power of interconnectivity. Net-centric solutions were soon discussed that allowed the reuse of systems by loosely coupling them via information exchange. But this extended system was beyond traditional program, governance, and organization boundaries. New processes were needed to help synchronize activities, budgets, and schedules. Sage and Cuppan (2001) and Keating et al. (2003) contributed to the engineering managerial foundations to move toward System of Systems Engineering (SoSE) using the architecting principles identified by Maier (1998) only a couple of years earlier.
The technical challenges cannot be neglected. Designing interfaces and communications protocols to federate independently developed systems with each other without allowing for any significant redesign of the system is a huge challenge. However, the organizational challenges that had to be addressed by engineering managers were even bigger. For example, todayâs managers are not used to the task to bring systems together to fulfill a common task without having the power to establish common processes, a common administration, and a common governance.
In his work, which is actually summarized and continued in Chapter 2 of this handbook, Maier identified five criteria commonly recognized in SoSE literature:
- Operational independence of the individual systems: An SoS is composed of systems that are independent and useful in their own right. If an SoS is disassembled into the component systems, these component systems are capable of independently performing useful operations independently of one another.
- Managerial independence of the systems: The component systems not only can operate independently, but they generally do operate independently to achieve an intended purpose. The component systems are generally individually acquired and integrated, and they maintain a continuing operational existence that is independent of the SoS.
- Geographic distribution: Geographic dispersion of component systems is often large. Often, these systems can readily exchange only information and knowledge with one another and not substantial quantities of physical mass or energy.
- Emergent behavior: The SoS performs functions and carries out purposes that do not reside in any component system. These behaviors are emergent properties of the entire SoS and not the behavior of any component system. The principal purposes supporting engineering of these systems are fulfilled by these emergent behaviors.
- Evolutionary development: An SoS is never fully formed or complete. Development of these systems is evolutionary over time and with structure, function, and purpose added, removed, and modified as experience with the system grows and evolves over time.
Modeling and simulation (M&S) in general and agent-directed simulation (ADS) in particular already support SE successfully. Yilmaz and Ăren (2009) dedicated a whole book to the synergisms of ADS and SE. Simulated systems can be used to obtain, display, and evaluate operationally relevant data in agile contexts by executing models using operational data exploiting the full potential of M&S and producing numerical insight into the behavior of complex systems. ADS have been shown to have the ability to support the development of robust, fault-tolerant, adaptive, self-optimizing, learning, social-capable, autonomous, and agile solutions. ADS also expose emergent behavior similar to SoS, so that they can be used to better understand and utilize this criterion and enforce positive emergence while avoiding negative emergence.
The experts in the field invited to contribute chapters to this handbook were asked to utilize the five criteria provided above as a common foundation. However, the community is still very diverse when it comes to using M&S in support of SoSE applications so this book can merely provide a map of the landscape of approaches.
1.2 OBJECTIVE
Jamshidiâs books provided an overview on SoSE from the methodological perspective (Jamshidi, 2010) as well as from the application perspective (Jamshidi, 2011). He also invited experts to contribute chapters, but the focus was clearly on the SE processes.
This book has the objective to focus more on M&S support, providing the foundations for a better research agenda. This research agenda, however, cannot only focus on M&S support questions, but it needs to understand the SoSE application cases as well. As such, the objective of this book is to contribute to find answersâor identify required research to provide answersâto questions such as the following:
- What are the processes of SoSE?
- What steps in the processes are supported by M&S?
- What steps in the processes can be supported in the future by M&S, and what are the necessary constraints?
- How can M&S be used to better understand SoS?
The chapter of this book will start to address them and hopefully initiate more research to fill the gap in the body of knowledge.
1.3 STRUCTURE OF THE HANDBOOK
Despite the challenges mentioned in the last section, this text has the objective to demonstrate how M&S can provide academic augmentation to the relatively new term of SoS. To facilitate this discussion, this text is divided into four major sections. Section I is the âOverview and Introduction.â Its purpose is to provide the taxonomy and academic foundation for the rest of the text. Section II is the âTheoretical or Methodological Considerations.â The purpose of this section is to address, as the title implies, more theoretical or more generalized approaches to the subject. Section III is the âTheoretical or Methodological Considerations with Applications and Lessons Learned.â The purpose of this section is to identify specific cases where definitive applications can be abstracted and lessons learned drawn from the specific application. The final section of the text, Section IV, provides a review of what has been presented previously and draws major conclusions across both the theoretical and application spectrums.
1.3.1 Overview and Introduction
The main thrust of Section I is Chapter 2 âThe Role of Modeling and Simulation in System of Systems Development.â This chapter is the cornerstone to this text. In this chapter, Mark Maier defines SoS and identifies important systems and various categories of systems that the reader should be cognizant of. He also discusses M&S within the specific SoS category. He then moves ahead to address architecture, architecture description, and development. He closes his chapter with a summary and conclusions.
1.3.2 Theoretical or Methodological Considerations
Section II has five chapters that have been categorized as purely theoretical or methodological in nature.
In Chapter 3, Mike Jones addresses the M&S subject of âComposability.â He has taken the attributes of an SoS as defined by Mark Maier to lay a foundation for his chapter. He then examines the M&S topics of conceptual modeling separately and then composability, interoperability, and integratability as a unit. The levels of the Conceptual Interoperability Model are then addressed. Current standards and current research are then addressed from Maierâs SoS perspective. Mike finishes with his conclusions.
In Chapter 4, Adam Ross and Donna Rhodes discuss âAn Approach for System of Systems Tradespace Exploration (TE).â First, they provide the reader a background on the subject of TE. Then they identify SoS-specific considerations for TE. Next, a specific approach is provided for TE. Then, an illustrative case is considered. They close their discussion with a chapter summary.
Daniele Gianni, in Chapter 5, pursues âData Policy Definition and Verification for SoS Governance.â First, in his background, he addresses a methodology based upon the terminology and concepts from the Unified Modeling Language, enterprise architecture frameworks, SoS governance, and conceptual data modeling. In his next section, he identifies the role of data policy methodology in the context of SoS governance. Next, he addresses the topic of the design of the data policy method methodology. Finally, he provides an example application for the European Space Agency (ESA) space situational awareness preparatory program. Daniele completes his chapter with conclusions.
In Chapter 6, Stephen Johnson addresses the subject of âSystem Health Management (SHM).â He starts off by laying a foundation of definitions from which to draw upon later in his chapter. Then SHM is addressed for a system. He follows this topic with another that discusses SHM from the perspective of models, simulations, and their applications. Next, he draws a distinction between a system and an SoS. Finally, he illustrates how SHM would pertain to an SoS. He closes his chapter with a conclusion section.
In the last chapter of Section II, Chapter 7, R. William Maule describes a Model Methodology for a Department of Defense Architecture Design. This chapter is an examination of the Department of Defense Architecture Framework (DoDAF) as looked at through the lens of an SoS. The first few sections address a reference architecture, model tooling, and model workflow. The rest of the chapter addresses each individual view as currently portrayed in DoDAF. The chapter closes with a chapter conclusion.
1.3.3 Theoretical or Methodological Considerations with Applications and Lessons Learned
Section III constitutes the bulk of this text. It has 14 chapters assigned to it. These chapters are those that have been categorized as truly methodological consideration in nature as they have definitive applications from which lessons learned can be drawn.
The first in this section is Chapter 8 by Agostino Bruzzone, Marina Massei, Alfredo Garro, and Francesco Longo. It is entitled âAn Agent-Oriented Perspective on System of Systems for Multiple Domains.â In this chapter, the authors first address the spectrum that ranges from large-scale systems to SoS. Then they address M&S approaches for SoS. Next is an agent-oriented perspective for SoS. Then they turn the discussion to exploiting the agent-oriented perspective with application examples in multiple domains. They end their chapter with conclusions and future works.
Chapter 9 by Sanjay Jain, Charles Hutchings, and Y. Tina Lee is entitled âBuilding Analytical Support for Homeland Security.â The authors address the relationship between homeland security and SoS. Then they identify the need for M&S and analysis for homeland security. This discussion is followed by providing a knowledge sharing framework. The last consideration in their chapter is that of a prototype for an SoS application. Their chapter is completed with a chapter summar...