309
Systems Integration Management
behavior (order and schedules of objects). The Bayesian interpretation of scenario development leads to the defining of object order, start time, and duration as probabilistic measures of the stakeholder beliefs that the pattern will
occur, given all that is relevant, known, and included by the stakeholders. In
this interpretation, the probability of an event occurring in the sequence
specified, at the starting time indicated, and having duration stipulated is
dependent on both the event and the stakeholder’s knowledge of the event
(Poh 1993). By this means, various scenarios can be scripted and evaluated,
using the variables of object pattern, start time, and duration to represent the
stakeholder knowledge.
There are four techniques for determining the pattern and behavior: expert
opinion (including engineers, financial analysts, systems engineers, and managers); estimates of the work duration by similar types of tasks (e.g., by index
lines of code in the case of software, standard part or off-the-shelf part delivery
or manufacturing times); estimates of work by functions (e.g., using function
points for software estimation or applying functional analysis to compare like
functions with previous projects); and algorithmic comparisons with like-kind
work packages or work sequences. While today these techniques are heralded
as the best, they do not separate planning and scheduling using reverse view
perspectives. Scheduling moves temporally into the future, whereas planning
moves from the most future event (delivery of the product or service to the
events of present day—the reverse view perspective). A promising approach is
the use of augmented Lagrangian optimization (Guignard 1995; Li and
Ierapetritou 2010). The last 20 years have shown promising results and this
relatively unexplored approach deserves attention.
Integration Plan
An integration plan should include the strategy for bringing objects together
to demonstrate functionality. The integration plan is based on the system
design and the system architecture. Commensurate with the strategy and
sequencing for joining objects is the preparation of integration resources and
make-up of the integration teams. The integration plan also covers approach,
testing, and verification of the integrated subsystems, as well as laying out
the validation for the integrated system. The integration plan is the management guide for integration, followed by both the systems engineers and
engineers. Integration is so important with large, complex, and expensive
systems that in 2005, the U.S. Government Accountability Office that reports
to the Subcommittee on Oversight of Government Management, The Federal
Workforce, and the District of Columbia, Committee on Homeland Security
and Governmental Affairs, United States Senate, recommended that the
Senior Executive Service within the Department of Homeland Security have
Systems Integration Management
behavior (order and schedules of objects). The Bayesian interpretation of scenario development leads to the defining of object order, start time, and duration as probabilistic measures of the stakeholder beliefs that the pattern will
occur, given all that is relevant, known, and included by the stakeholders. In
this interpretation, the probability of an event occurring in the sequence
specified, at the starting time indicated, and having duration stipulated is
dependent on both the event and the stakeholder’s knowledge of the event
(Poh 1993). By this means, various scenarios can be scripted and evaluated,
using the variables of object pattern, start time, and duration to represent the
stakeholder knowledge.
There are four techniques for determining the pattern and behavior: expert
opinion (including engineers, financial analysts, systems engineers, and managers); estimates of the work duration by similar types of tasks (e.g., by index
lines of code in the case of software, standard part or off-the-shelf part delivery
or manufacturing times); estimates of work by functions (e.g., using function
points for software estimation or applying functional analysis to compare like
functions with previous projects); and algorithmic comparisons with like-kind
work packages or work sequences. While today these techniques are heralded
as the best, they do not separate planning and scheduling using reverse view
perspectives. Scheduling moves temporally into the future, whereas planning
moves from the most future event (delivery of the product or service to the
events of present day—the reverse view perspective). A promising approach is
the use of augmented Lagrangian optimization (Guignard 1995; Li and
Ierapetritou 2010). The last 20 years have shown promising results and this
relatively unexplored approach deserves attention.
Integration Plan
An integration plan should include the strategy for bringing objects together
to demonstrate functionality. The integration plan is based on the system
design and the system architecture. Commensurate with the strategy and
sequencing for joining objects is the preparation of integration resources and
make-up of the integration teams. The integration plan also covers approach,
testing, and verification of the integrated subsystems, as well as laying out
the validation for the integrated system. The integration plan is the management guide for integration, followed by both the systems engineers and
engineers. Integration is so important with large, complex, and expensive
systems that in 2005, the U.S. Government Accountability Office that reports
to the Subcommittee on Oversight of Government Management, The Federal
Workforce, and the District of Columbia, Committee on Homeland Security
and Governmental Affairs, United States Senate, recommended that the
Senior Executive Service within the Department of Homeland Security have