SOAR

Acknowledged System-of-Systems (SoS)

1. Introduction
2. Contents
   1. Essential content
   2. Described by
   3. Related alphas
3. States
   1. Analyzed
   2. Designed
   3. Valid Architecture
   4. Operational and Evolving
   5. Retired
4. References
   1. Templates and tools
   2. Examples

Introduction

Acknowledged System-of-Systems (SoS): A complex system resulted from the interoperation of other independent and heterogeneous systems (i.e., Constituent Systems (CSs). The collaborative work of CSs yields emergent functionalities in order to accomplish the SoS goals/mission.

SoS are typically complex, large-scale systems whose functionalities and purposes can change and dynamically evolve, i.e., they present an evolutionary development. In Acknowledged SoS, goals, resources, and authority are all recognized at SoS level, but the constituent systems retain their independent management and the behavior is not subordinated to the central managed purpose ¹ .

The architecture of SoS is dynamic and reactive since it must evolve according to the dynamic collaboration of constituent systems that are also changing. In this context, the construction process of SoS is complex demanding new strategies not considered in already existent processes conceived for monolithic systems and this alpha embodies the key concept of SoS as a system class.

Contents

Essential content

N/A

Described by

N/A

Related alphas

• Software System (Parent)

• Constituent Systems (CSs) form Acknowledged System-of-Systems (SoS)
• Software Architecture exhibits Acknowledged System-of-Systems (SoS)

States

Analyzed

The Context of SoS and potential CSs are known.

Checkpoints

The alpha is in this state when:

• Desired SoS boundary is known.
• SoS and CSs missions are known.

Designed

New CASs were proposed and a new architectural version must be validated.

Checkpoints

The alpha is in this state when:

• Other architectures (e.g., physical and organitational) have been identified.
• New architectural decisions have been proposed as CASs.

Valid Architecture

The new proposed architectural version is validated.

Checkpoints

The alpha is in this state when:

• Evaluation strategies were planned and executed.
• The new CASs were approved to satify the ASRs dealt in the iteration.
• The relevant stakeholders agree that the demonstrated architecture is appropriate.

Operational and Evolving

The last validated architectural version is implemented and the SoS is operational.

Checkpoints

The alpha is in this state when:

• The SoS has been made available to the stakeholders intended to use it.
• At least one SoS function is fully operational.
• The stakeholders accept the SoS as fit-for-purpose.
• Operational support is in place.
• The performance of the system is acceptable to the stakeholders.
• Changes that affect the SoS architecture have been monitored.

Retired

The SoS is no longer in operation.

Checkpoints

The alpha is in this state when:

• The SoS has been replaced or discontinued.
• The SoS is no longer supported.
• There are no stakeholders who still use the SoS.
• Updates to the SoS will no longer be produced.

References

¹ Departament of Defense (DoD): Systems Engineering Guide for Systems of Systems, 2008

Templates and tools

N/A.

Examples

N/A.

Copyright © 2014 ICMC Instituto de Ciências Matemáticas e de Computação, University of São Paulo (USP), Brasil - IRISA Institut de Recherche en Informatique et Systèmes Aléatoires, Université de Bretagne-Sud (UBS), France, ver. beta 1.0