A Review of AMADEOS:

Topics

• SoS Modeling Challenges
• The AMADEOS Profile
• Viewpoints
• Pacakges

SoS Challenges: Maier

• Operational Independence:each system within the System of Systems is fully capable of independent operation
• Managerial Independence: each system within the System of Systems is fully capable of independent management of its own tasks, and does in fact manage itself

SoS Challenges: Maier

• Geographic Distribution: each system within the System of Systems is located some physical distance from the other systems and as such they do not share power but information
• Evolutionary Development: The System of Systems is always subject to change; individual systems can be added or removed at will

SoS Challenges: Maier

• Emergent Behavior: The System of Systems provides services/behaviors that are possible due to the collaboration of the individual system contained therein

The AMADEOS Profile

• Conceptual model for Systems of Systems (SoSs)
• Separates the description of basic SoS concepts into different perspectives/characteristics they call "Viewpoints"

Viewpoints

• Structure: It represents architectural concerns of an SoS.
• Dynamicity: represents variations to the operation of SoS that have been considered at design-time to reconfigure the SoS in specific situations

Viewpoints

• Evolution: represents changes that have been introduced later to accommodate modified or new requirements by means of including, removing or modifying system functions
• Dependability and security: Consists of non-functional critical requirements such as availability, reliability, safety, privacy or confidentiality.

Viewpoints

• Time: Necessary to design responsive SoSs able to achieve reliably time-dependent requirements
• Multi-criticality: Integrating together subsystems that provide services with different levels of criticality corresponding to different dependability and security requirements

Viewpoints

• Emergence: The appearance of novel phenomena at the SoS level that are not observable at Constituient System (CS) level; managing emergence is essential to avoid undesired, possibly unexpected, situations generated from CSs interactions and to realize desired emergent phenomena

SysML Packages

• Architecture: extends SysML Block Definition Diagram (BDD) in order to model the topology and the relations of an SoS
• Communications: composed of CSs that exchange information with other elements.

SysML Packages

• Interface: can be an “internal_interface” a “physical_interface”, a “message_ based_interface” and an “external_interface”
• Evolution: represents changes that have been introduced after initial production to accommodate modified or new requirements

SysML Packages

• Dynamicity: objective is to (1) identify which parts of an SoS are dynamic to a certain extent and (2) to represent the dynamic behavior through the interactions among CSs

SysML Packages

• Scenario-Based Reasoning: supports the generation, evaluation, and management of different scenarios thus supporting decision-making in an SoS

SysML Packages

• Dependability: provides details of dependability -sensitive CSs within the SoS and what they rely on
• Security: focused on Crypto and Access Control

SysML Packages

• Time: used for enabling the interpretation of timestamps in the different CSs, limiting the validity of real-time control data, synchronizing input and output actions across nodes, providing conflict-free resource allocation, and performing prompt error detection

SysML Packages

• Emergence: uses two different types of representation that a system designer can choose: a Block Definition Diagram or a Sequence Diagram; attempts to capture operational aspects related to emergence by considering an SoS in action

AMADEOS in use

• Project performed trial through modeling a Smart Grid household