266
Engineering Systems Integration
this is there are a great number of things and issues that appear complex
scaled from the atomic level to the universe. There seems no limit as to what
can be complex. Complexity is omnipresent, commonplace, almost to the
point of being pointless because it is ordinary by its nature. But in the ordinary, the humdrum of existence, the exceptional transpires. As phrased by
Klir, “Complexity (in the epistemological and methodological sense) is
thus associated with systems, that is, some abstractions distinguished on
objects that reflect the way in which the objects are interacted with” (Klir
2001). Complexity is the result of interactions between objects. Yet, more
interactions do not necessarily increase complexity. Complexity can increase
and decrease. Complexity can be seen as relative to the level of abstraction in
which one views two objects. For an atom, the constituent parts of protons
and neutrons may not be complex at that level of abstraction. But examine
the constituent parts of the proton and reveal details that are as yet unexplained. Scale up from an atom to molecules and then subsequently to a
human-built system that interacts with other systems. Regardless of scale,
we find complexity. Interaction is the defining process of complexity.
Interaction is the catalyst that results in integration. Integration is the process
of systems and of systems interacting with other systems. The fundamental
mechanism that drives complexity is interaction across the three types of
boundaries that lead to integration of the elements.
Process Models
In a simple and inaccurate form, systems engineering process models relate
work that needs to be done to a set of stages that map to the systems engineering progression of defining the problem; designing and architecting
solutions; developing and integrating objects; and testing, verifying, and
validating to satisfy requirements. Again in a simple and inaccurate form,
process models indicate what should be done next, and how long it should
take. In addition to process models, maturity models have been developed to
describe various aspects of systems through the development process. These
maturity models include parameters such as capability and integration. Each
model is specialized to deal with perceived risk, verification of specifications
or requirements, domain interactions, or a catch-all of multiple factors.
Process models help to orchestrate the work as well as communicate what
type of work should be performed to reach the next milestone. Selection of
the process model for a systems engineering effort depends in part on the
preference of the acquirer, the skills of the developer, and the particular key
limitation (e.g., cost, budget, or performance) that is to drive the work.
Process models differ from acquirer to acquirer. Within the U.S. government, multiple process models are used. Within industry, home-grown
Engineering Systems Integration
this is there are a great number of things and issues that appear complex
scaled from the atomic level to the universe. There seems no limit as to what
can be complex. Complexity is omnipresent, commonplace, almost to the
point of being pointless because it is ordinary by its nature. But in the ordinary, the humdrum of existence, the exceptional transpires. As phrased by
Klir, “Complexity (in the epistemological and methodological sense) is
thus associated with systems, that is, some abstractions distinguished on
objects that reflect the way in which the objects are interacted with” (Klir
2001). Complexity is the result of interactions between objects. Yet, more
interactions do not necessarily increase complexity. Complexity can increase
and decrease. Complexity can be seen as relative to the level of abstraction in
which one views two objects. For an atom, the constituent parts of protons
and neutrons may not be complex at that level of abstraction. But examine
the constituent parts of the proton and reveal details that are as yet unexplained. Scale up from an atom to molecules and then subsequently to a
human-built system that interacts with other systems. Regardless of scale,
we find complexity. Interaction is the defining process of complexity.
Interaction is the catalyst that results in integration. Integration is the process
of systems and of systems interacting with other systems. The fundamental
mechanism that drives complexity is interaction across the three types of
boundaries that lead to integration of the elements.
Process Models
In a simple and inaccurate form, systems engineering process models relate
work that needs to be done to a set of stages that map to the systems engineering progression of defining the problem; designing and architecting
solutions; developing and integrating objects; and testing, verifying, and
validating to satisfy requirements. Again in a simple and inaccurate form,
process models indicate what should be done next, and how long it should
take. In addition to process models, maturity models have been developed to
describe various aspects of systems through the development process. These
maturity models include parameters such as capability and integration. Each
model is specialized to deal with perceived risk, verification of specifications
or requirements, domain interactions, or a catch-all of multiple factors.
Process models help to orchestrate the work as well as communicate what
type of work should be performed to reach the next milestone. Selection of
the process model for a systems engineering effort depends in part on the
preference of the acquirer, the skills of the developer, and the particular key
limitation (e.g., cost, budget, or performance) that is to drive the work.
Process models differ from acquirer to acquirer. Within the U.S. government, multiple process models are used. Within industry, home-grown