[Review] What is a System of Systems and Why Should I Care?

SoS and SoS Engineering (SoSE) are becoming important while living in complex and diverse systems. Systems are ubiquitous. SoS is used in many places such as home, business, disaster response, defense, space exploration system.


Key characteristics of SoS

How So is Different from a System?
SoS is that many systems belong to various people and organizations, and there are emergent behaviors and common purpose.
What is still controversial is whether emergent behaviors should be planned and managed. Also, someone needs to create an integrated protocol that makes it easy to get in and out of the SoS. And it is said that someone should be well planned, tested and managed to avoid undesirable behaviors.
What is unique about SoS is that each CS is Operationally independent and Managerially independent.
Types of SoS
Virtual: There is no central management authority and no obvious SoS goal. For example,
Collaborative: There is no SoS engineering team, CS collaborates voluntarily for central goals.
Acknowledged: At SoS level there are goals, managers and resources. However, the SoSE team does not have complete authority over CS.
Directed: There is a jungle management, and it achieves a certain goal. Evolution is managed by a SoS management organization.

Key Ways in Which SoSE Differs from Traditional Single Systems Engineering

Most SE standards are for a single system development. Therefore, the existing SE process should enable both the evolution of SoS and CS.
Seven SoSE activities
1. Translating capability objectives: The requirements of SoS should be expressed as requirements.
2. Understanding systems and relationships: Understand which systems can contribute to SoS and their relationships and boundaries.
3. SoS evaluation criteria
4. Developing, evolving, and maintaining an SoS architecture / design: a framework to support the evolution of SoS to meet user's needs
5. Monitoring and assessing changes: CS change monitoring, impact prediction
6. Addressing new requirements and options: priorities
7. Orchestrating upgrades to SoS: planning, coordinating, integrating, testing changes

Key SoSE Challenges

Focusing constituent-systems on SoS needs and capabilities: As CSs are upgraded individually, they must coordinate for the needs of each stakeholder and SoS.
CS may have to work with previous versions because the CS may be individually upgraded and the environment may be different, and the CS may belong to several SoSs and may have to take one of several criteria.
Maintaining SoS performance: SoS becomes larger and more complicated.
Testing soS capabilities in an asynchronous development environment: Testing the ability of SoS because the pieces of functionality belong to multiple systems is a performance test in those various environments.
Identifying and managing unplanned SoS emergent behaviors: Unexpected functions and usage appear at the time of development, and it is not reasonable to stop and fix the entire SoS because one thing is wrong.
SoSE capability cost and schedule analysis:

Current research area

SoSE cost modeling and estimation
Constituent-system interoperability
SoSE and lean principles
Kanban scheduling to improve visibility and work flow within SoS development environment
SysML tailored for SoSE
SoS capability engineering

References
Lane, Jo Ann, and D. Epstein. "What is a system of systems and why should i care?" University of Southern California, available at http: // csse. usc. edu / TECHRPTS / 2013 / reports / usc-csse-2013-500. pdf (2013).

Comments

Popular posts from this blog

[Review] Architecting Principles for Systems-of-Systems

[Review] Systems of Systems Engineering: Basic Concepts, Model-Based Techniques, and Research Directions

[Review] System-of-Systems Engineering Management