221
Integration in Systems Engineering Context
extremely important when the focus is on designing an aircraft skin
that has a variable signature rather than a fixed signature. Stakeholder
analysis is not taught, defined, or detailed in any forum. This often
results in a set of requirements that are either missed or known but
not acted on.
• There are the inadequacies in the process of determining the minimum set of requirements needed to assure that the constraints of
budget and schedule are met. These inadequacies include poor
stakeholder analysis, subsequent steps involved in the logic, prototyping, modeling, simulation, and analysis that is often flawed.
Many requirements are discovered late in the development cycle,
resulting in significant losses caused by extensive modifications or
scrapping of the project. Integration will only be as good as what is
provided. If the objects do not encompass the requisite functionality,
then integration will do nothing to change that. The responsibility
for providing the essential subfunctions is solely that of development. Integration merely combines objects in such a way to highlight both the functionality and the performance(s) that result from
integration with other objects. Systems engineering is the domain of
producing a product or service, development provides the requisite
objects, and integration brings those objects together in such a way
and manner to realize the essences of the system design, the stakeholder preferences through the architecture, and the requirements
to satisfy the concept of operations.
• There are inherent difficulties when integrating cross-disciplinary
knowledge. Consider, for example, human systems integration and
the question of potential or actual losses incurred at the system level
for two design strategies for movement of information: just-in-time
versus on-demand. At issue is the timeliness and latency of flow of
information, that is, the losses incurred due to poor integration and
delaying a decision maker. The integration inefficiencies stem from
the concurrency of data within the system (e.g., correlation of one
data item with another data item representative of the best correlation of these two data items given that there may be a more relevant
data item in the system that is unavailable due to lack of access to it
or because it is unknown at the time of correlation). Integration
brings out the direct measures of coupling and cohesion between
objects and their relations through EMMI.
• Lifecycle issues are regarded as important when scoping work; however, initial budgetary constraints often restrict the efforts devoted
to lifecycle engineering and planning that can be considered or
designed into the system. The result is to sacrifice the long-term
interests of minimizing the total lifecycle cost for the expediency of
a lower up-front investment.
Integration in Systems Engineering Context
extremely important when the focus is on designing an aircraft skin
that has a variable signature rather than a fixed signature. Stakeholder
analysis is not taught, defined, or detailed in any forum. This often
results in a set of requirements that are either missed or known but
not acted on.
• There are the inadequacies in the process of determining the minimum set of requirements needed to assure that the constraints of
budget and schedule are met. These inadequacies include poor
stakeholder analysis, subsequent steps involved in the logic, prototyping, modeling, simulation, and analysis that is often flawed.
Many requirements are discovered late in the development cycle,
resulting in significant losses caused by extensive modifications or
scrapping of the project. Integration will only be as good as what is
provided. If the objects do not encompass the requisite functionality,
then integration will do nothing to change that. The responsibility
for providing the essential subfunctions is solely that of development. Integration merely combines objects in such a way to highlight both the functionality and the performance(s) that result from
integration with other objects. Systems engineering is the domain of
producing a product or service, development provides the requisite
objects, and integration brings those objects together in such a way
and manner to realize the essences of the system design, the stakeholder preferences through the architecture, and the requirements
to satisfy the concept of operations.
• There are inherent difficulties when integrating cross-disciplinary
knowledge. Consider, for example, human systems integration and
the question of potential or actual losses incurred at the system level
for two design strategies for movement of information: just-in-time
versus on-demand. At issue is the timeliness and latency of flow of
information, that is, the losses incurred due to poor integration and
delaying a decision maker. The integration inefficiencies stem from
the concurrency of data within the system (e.g., correlation of one
data item with another data item representative of the best correlation of these two data items given that there may be a more relevant
data item in the system that is unavailable due to lack of access to it
or because it is unknown at the time of correlation). Integration
brings out the direct measures of coupling and cohesion between
objects and their relations through EMMI.
• Lifecycle issues are regarded as important when scoping work; however, initial budgetary constraints often restrict the efforts devoted
to lifecycle engineering and planning that can be considered or
designed into the system. The result is to sacrifice the long-term
interests of minimizing the total lifecycle cost for the expediency of
a lower up-front investment.