SOAR

Emergent Behaviors

1. Introduction
2. Contents
   1. Essential content
   2. Described by
   3. Related alphas
3. Essential Qualities
4. States
   1. Planned
   2. Predicted
   3. Checked
5. References

Introduction

The result from the collaborative work of constituent systems.

Constituent systems isolated working cannot provide the collaborative work for emergent behaviors.

Some emergent behaviors can be either foreseen, i.e., they can be determined by specifying interactions among constituent systems or representing interaction patterns (the ways in which they interact), or unforeseen, i.e., they dynamically appear in the context of the SoS.

Contents

Essential content

N/A

Described by

N/A

Related alphas

• Constituent Systems (CSs) yield Emergent Behaviors
• Emergent Behaviors satisfy Architecturally Significant Requirements (ASRs)

Essential Qualities

1. Both foreseen and unforeseen emergent behaviors may be desirable or even undesirable, so that the result of the interactions among constituent systems within an SoS can be respectively positive or negative over its operation ¹ . In general, predicted/desirable behaviors come from architectural solutions and must be maximized since they foster the accomplishment of SoS missions. On the other hand, undesirable behaviors must be minimized because they may negatively affect the accomplishment of SoS missions and/or important quality attributes such as performance, security, and reliability.

States

Planned

The strategies to identify emergent behaviors are planned.

Checkpoints

The alpha is in this state when:

• The architectural team agreed on a set of strategies to predict desired emergent behaviors related to the Sos software architecture.
• The architectural team agreed on a set of strategies to predict undesired emergent behaviors related to the Sos software architecture.
• A plan for prediction was established.

Predicted

Both desired and undesired emergent behaviors are predicted.

Checkpoints

The alpha is in this state when:

• The emergent behaviors were predicted by following the planned techniques.
• The architectural team agree with the reached predictions.

Checked

An introduction to the state.

Checkpoints

The alpha is in this state when:

• The architectural evaluation strategies were applied to the candidate software architecture and the emergent behaviors were confirmed.
• The emergent behaviors have been presented to the stakeholders and they agree that they can satisfy the ASRs.

References

¹ Holland, O. T.: Taxonomy for the modeling and simulation of emergent behavior systems 2007 Spring Simulation Multiconference, Society for Computer Simulation International, Vol. 2, P. 28-35, 2007

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

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