Premium
7.6.0 How to Engineer the Emergent Behavior of a System of Systems
Author(s) -
Hsu J,
Axelband E,
Rouse B,
Madni A,
Sheard S
Publication year - 2008
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2008.tb00850.x
Subject(s) - systems modeling language , computer science , system of systems , interoperability , architecture , agency (philosophy) , risk analysis (engineering) , plan (archaeology) , unified modeling language , complex system , systems engineering , process management , knowledge management , engineering , software engineering , artificial intelligence , systems design , business , art , philosophy , archaeology , software , epistemology , visual arts , history , programming language , operating system
Emergent behaviors exist in biological systems, physical systems and human performance. Little is currently known about constructing an interoperable network of systems and the incorporation of known emergent behaviors. The purpose of this panel is to explore the methods and principles in developing an architecture including the emergent behavior. SoS displays a global complexity that cannot be adequately managed by hierarchical structures and central control; therefore, traditional systems engineering and management approaches are inadequate and insufficient for a SoS. The challenge is how to understand the initiation mechanisms of the emergent behaviors for a particular system architecture model so that the resident beneficial or harmful emergent behaviors can be enhanced or mitigated with selected changes in the current system architectural model. Is model‐based the only feasible approach to develop the architecture model with emergent behavior? If this is the answer, what kind of modeling methodology? Should it be solely based on agent‐based modeling? or combination of SysMl and agent‐based? Is SysML ready to deal with emergent behavior? For a non‐modeling consideration, can we plan for the beneficial or harmful emergent properties? How do we overcome development friction that is bound to arise when there are complex, independent, overlapping governances? We may need experiment with “guided” emergence that help produce the desired SoS capabilities and behaviors. The customer requirements for systems‐of‐systems evolve over time. There may only be system‐of‐system modeling at the level of the government agency, who actually procures but does not build, and not at the level of contractors who build the next generation of technologies. Even we have methodology to build SoS architecture, whether model‐base or non model‐base. How do we train systems engineers to understand the emergent behavior to be incorporated in a newly designed SoS?