Systems-of-Systems Engineering (SoSE) addresses the design of multiple systems that, working together, generate capabilities that none can offer separately. Its main challenge is managing the interactions, interoperability, and continuous evolution of an increasingly connected and complex set.
When the whole does something the parts cannot do
The fundamental idea can be understood with a simple example.
An aircraft has navigation, communications, propulsion, sensor, and control systems. Each has its own requirements and objectives. However, the aircraft's mission depends on how they all work together.
In a System of Systems, this relationship reaches a new dimension.
The systems that make up the whole may have different owners, different life cycles, independent architectures, and even objectives that do not fully align. Even so, they need to collaborate to achieve a common capability.
INCOSE precisely defines Systems of Systems as complex environments in which emergent capabilities arise from the interaction between constituent systems that maintain varying degrees of independence.
The key word is emergence.
The value of the whole does not lie solely in adding up individual capabilities. It appears as a consequence of their interactions.
The complexity is no longer only inside the system
Traditional systems engineering has developed very powerful tools for managing requirements, architecture, interfaces, verification, and validation.
But when working with a System of Systems, an additional problem appears: many of the important variables are outside the engineer's direct control.
A constituent system can evolve without all the others doing so at the same time. It can change an interface, update a technology, modify its operating cycle, or even stop being available.
That is why designing the whole as if it were a single closed system can lead to solutions that are technically correct but operationally fragile.
Systems-of-Systems Engineering forces us to broaden our perspective.
It is not enough to ask whether each system works correctly. We must also ask:
What happens when they all work together?
Interfaces: where much of the problem begins
In complex projects, interfaces often receive less attention than they deserve.
An interface is not just a physical connector or an API. It can define how information is exchanged, who makes a decision, which system has authority over a given function, or what happens when two systems interpret the same piece of data differently.
In an SoS, these relationships can multiply quickly.
That is why architecture takes on a central role. The goal is not only to define the components, but to understand the dependencies and exchanges that allow the whole to fulfill its mission.
The INCOSE community itself identifies interfaces, systems thinking, and complexity as fundamental areas within the specific work of SoS Engineering.
Architecture thus stops being a static drawing of the system. It becomes a representation of relationships, responsibilities, and behaviors.
From requirements to emergent behavior
Another challenge is validation.
In a conventional system, we can check whether a function meets a given requirement. In an SoS, some of the most important capabilities do not belong to a single component.
An intelligent transportation system can combine connected vehicles, traffic lights, urban sensors, control centers, navigation systems, and data platforms. None of them, on its own, provides intelligent mobility.
The capability emerges from the interaction.
This means testing must also evolve. It is no longer enough to verify components in isolation. It is necessary to analyze scenarios, collective behaviors, edge conditions, and possible changes during operation.
The specialized literature notes precisely that Systems of Systems require recurring adaptation during operation due to the uncertainty and variability of the environment.
The human factor is also part of the architecture
There is a tendency to interpret Systems of Systems as a purely technological problem.
It is not.
When different organizations, independent operators, suppliers, regulators, or end users are involved, human decisions become part of the overall behavior.
A technically flawless architecture can fail if the actors who must operate it do not share objectives, information, or courses of action.
That is why governance, interface management, and coordination between organizations are inseparable elements of engineering.
Digital transformation is making this phenomenon increasingly visible. Many organizations are integrating existing systems to create new capabilities without necessarily replacing all the components they already had. Research in Systems Engineering itself identifies this type of transformation as a natural scenario for the System of Systems approach.
Engineering for systems that will keep changing
Perhaps the main difference compared to other approaches is this: a System of Systems should not be designed assuming it will remain stable.
Its components will evolve. New technologies will appear. Operational requirements will change. Some systems will be replaced and others added.
The architecture must be able to absorb that evolution without losing the overall mission.
That requires thinking about interoperability, modularity, interface evolution, traceability, and resilience from the earliest phases of the life cycle.
Systems Engineering is now defined as a cross-cutting, integrative discipline that accompanies systems from conception through operation and retirement. In a System of Systems, this life-cycle view becomes even more important because the evolution of one component can change the behavior of the whole.
Thinking beyond boundaries
The relevance of Systems-of-Systems Engineering will grow as interconnection between infrastructures, platforms, and devices increases.
Connected cities, autonomous mobility, smart energy grids, aerospace systems, defense, telecommunications, and industrial environments share one characteristic: it is increasingly difficult to define where one system ends and another begins.
The answer is not to eliminate that complexity. It is to learn to design it.
And that is where the true value of systems thinking lies: understanding that, in certain environments, the unit of engineering is no longer the component, or even the system, but the network of relationships that allows all of them to function as a whole.
