277
Integration in Systems Engineering Context
Architecting focuses on the major elements—the elements that are structurally important to achieve the end-to-end functionality desired by the
system solution. Architecting is choosing the small set of mechanisms, patterns of behavior and operations, and styles that are consistent with the
needs (and desires) of stakeholders. Architecture is a tool that allows us to
tame complexity. Architecting is not the whole design, but architecting is
design. (Design is not architecting.) Architecting is infrastructure, the foundation of being able to move data. Moving data require paths (connectivity)
and interfaces that link the path to various nodes of processes or mechanisms. The architecture consists of the network of connections, and the
movement of data (energy, material, money) through the network. Good
architectures are usually formed by a team of people who are committed to a
solving an agreed-upon problem, who embrace the same performance goals,
and who hold the same approach to resolving the vexing issues confronting
the characterization of the solution.
System architecture precedes hardware and software architecture. At the
system’s level, architecture reveals its relations outside the boundaries of
the product or service. Inside, architecture is an end-to-end (boundary-toboundary) solution. Integration is the key issue that distinguishes architecture from design. Integration requires the forethought to prepare the
structures so that data can flow to and from nodes where it is needed at the
appropriate time. Architecture can and must be validated.
Much like designing, architecting brings order to misleading, ill-fitting,
and confounding data; at-odds opinions; differing values; and problematic
convergences. Designs that are not well defined, problems that are misstated, and needs that are unspoken merely frustrate the architect, but do
not deter the search for more than one set of solutions that satisfy the problem. The system architecture views show how multiple systems link and
interoperate. Additionally, the system architecture describes the internal
construction and operations. These descriptions include the physical connections, location and identification of the key nodes (or points of interaction), and the object performance parameters. Architecting focuses on the
major objects—the objects that are important to achieve the structurally
supported end-to-end functionality envisioned by the system solution.
Architecting is choosing the key set of mechanisms, the desired patterns of
behavior and operations, and the styles that are consistent with the needs
(and desires) of stakeholders. Architecture is a tool that allows us to tame
complexity. Architecting is infrastructure, the foundation of being able to
move data. Moving EMMI requires pathways (connectivity) and interfaces
that link the path to various nodes of processes or mechanisms. The architecture consists of the network of connections, the movement of EMMI
through the connections of objects.
Integration is the key issue that distinguishes architecture from design.
Integration requires the forethought to prepare the structures so that EMMI
can flow between objects where it is needed at the appropriate time.