Modern product development often generates systems of high complexity that are prone to emergent behavior. The industry has a need to establish better practices to detect inherent emergent behavior when engineering such systems. Philosophers and researchers have debated emergence throughout history, tracing to the time of the Greek philosopher Aristotle (384–322 B.C.) and current literature has both philosophical and practical examples of emergence in modern systems. In this review paper, we investigate the phenomenon of emergent behavior in engineered systems. Our aim is to describe emergence in engineered systems and propose methods to detect it, based on literature. Emergence is in general explained as dynamic behavior seen at macro level that cannot be traced back to the micro level. Emergence can be known or unknown in combination with positive or negative. We find that best practices to engineer complicated systems should contain a sensible suite of traditional approaches and methods, while best practices to engineer complex systems need extensions to this considering a new paradigm using incentives to guide system behavior rather than testing it up‐front.
A major responsibility of architecting and integration is ensuring that desired dynamic behavior and desired qualities emerge from the interaction of components within the systems, between systems, and between the users and environment of the systems. A challenge is that organizational attention tends to be on the parts structure, which is determining organization, logistics, manufacturing, and servicing. At the same time, many developers lack the competence to capture dynamic behavior and the way qualities emerge. This paper explores the role of Systems of Systems (SoS) architecting in relation to the impact on integration and looks at alternative ways to visualize dynamic behavior. Three different Systems of Systems, both Directed and Acknowledged SoS, are studied. The visualizations in this paper aid in conceptualizing the system of interest to a larger stakeholder community. Visualizing dynamic behavior allows us to think and reason about potential changes and improvements of Systems of Systems. We encourage use of visualizing dynamic behavior from early conceptual phase and recommend that the developed visualizations are maintained and in active use throughout the SoS life cycle.