236
Engineering Systems Integration
and compound in a way that is strictly in definite proportion to the total of
the constituent results. In other words, while the activities and results may
have intertwined, there is no synergy—no greater effect than the sum of
their individual effects. We term this process of interchange and interplay as
the interaction between elements. An element is an artifact or atomic unit
that is one of the individual parts that comprise an entity, a cognitive pro
cess, an operation, or an object within a system. It is the fundamental unit
which is perceived, known, or inferred to have existence (living or nonliv
ing). Elements that are interactional may be capable of acting on or influenc
ing each other under various conditions. However, these elements do not
have such undue influence so as to impart information, energy, material, or
wealth as part of their interaction. In other words, elements may interact, but
if they leave no imprint or lasting effect, their interaction is not causal.
Causality requires that another condition be met. The first enactments that
lead to success emphasize the aggregative effects, whereas the property of
emergence is embodied in the second portrayal of success. The interaction
between objects takes care to distinguish between interaction and integra
tion (which relies on emergence).
Lifecycle success is challenged by development and integration: (1) figuring
out what product to build; (2) determining which parts are required;
(3) deciding on which parts to make or buy; (4) putting the parts together;
(5) keeping the parts together so they perform as expected; and (6) then dis
posing of the parts when they no longer are useful to society.
Lifecycle Stages
Within the systems engineering parlance, lifecycle can be described as stages
that characterize the product as it transitions from a concept to its final dis
posal (and the last lawsuit). The stages are defined for an individual project
as agreed upon by the stakeholders. The stages represent work that moves
the product or service through milestones, each milestone showing progress
toward the delivery of the requisite product or service. Systems engineering
lifecycle models are specified, tailored, and used to pace the events leading
through development and operations. In a general sense, these stages can be
characterized as follows:
• Conceptualization: The first stage concentrates on two activities—
defining the problem faced by stakeholders and determining their
need; conceptualizing the concept of solutions (CONSOLS) and the
concept of operations (CONOPS). Conceptualization is done to attract
financing and set a preliminary course to explore the stakeholder’s
problem, need, and solution space. Conceptualization increases the
likelihood of appealing to the profit or opportunities that may inter
est investors. As more time is invested in conceptualization and
Engineering Systems Integration
and compound in a way that is strictly in definite proportion to the total of
the constituent results. In other words, while the activities and results may
have intertwined, there is no synergy—no greater effect than the sum of
their individual effects. We term this process of interchange and interplay as
the interaction between elements. An element is an artifact or atomic unit
that is one of the individual parts that comprise an entity, a cognitive pro
cess, an operation, or an object within a system. It is the fundamental unit
which is perceived, known, or inferred to have existence (living or nonliv
ing). Elements that are interactional may be capable of acting on or influenc
ing each other under various conditions. However, these elements do not
have such undue influence so as to impart information, energy, material, or
wealth as part of their interaction. In other words, elements may interact, but
if they leave no imprint or lasting effect, their interaction is not causal.
Causality requires that another condition be met. The first enactments that
lead to success emphasize the aggregative effects, whereas the property of
emergence is embodied in the second portrayal of success. The interaction
between objects takes care to distinguish between interaction and integra
tion (which relies on emergence).
Lifecycle success is challenged by development and integration: (1) figuring
out what product to build; (2) determining which parts are required;
(3) deciding on which parts to make or buy; (4) putting the parts together;
(5) keeping the parts together so they perform as expected; and (6) then dis
posing of the parts when they no longer are useful to society.
Lifecycle Stages
Within the systems engineering parlance, lifecycle can be described as stages
that characterize the product as it transitions from a concept to its final dis
posal (and the last lawsuit). The stages are defined for an individual project
as agreed upon by the stakeholders. The stages represent work that moves
the product or service through milestones, each milestone showing progress
toward the delivery of the requisite product or service. Systems engineering
lifecycle models are specified, tailored, and used to pace the events leading
through development and operations. In a general sense, these stages can be
characterized as follows:
• Conceptualization: The first stage concentrates on two activities—
defining the problem faced by stakeholders and determining their
need; conceptualizing the concept of solutions (CONSOLS) and the
concept of operations (CONOPS). Conceptualization is done to attract
financing and set a preliminary course to explore the stakeholder’s
problem, need, and solution space. Conceptualization increases the
likelihood of appealing to the profit or opportunities that may inter
est investors. As more time is invested in conceptualization and