318
Engineering Systems Integration
the subfunction levels that concatenate to the highest-priority system-level
function (in its simplest form).
The third phase of the SysPMI covers the expansion of integration to the
prioritized top-level system functions and the critical independencies.
Phase III spans the test planning, test execution, and benchmarking of the
prioritized system-level functional threads. The culmination of the third
phase of the SysPMI is the demonstration of system-level functions in their
simplest forms based on their set(s) of subfunctions. To complete the third
phase, some object demonstrated in Phase I will need to have additional subfunctions built into their physical entities. As additional subfunctions are
completed they will be tested to demonstrate additional functionality as well
as to show improvement(s) in the end-to-end system-level functions. Should
a system-level function be degraded from its benchmark performance by
the addition of a new functionality, the objects that were modified will be
analyzed to improve their handling of EMMI through adjustments of their
mechanisms.
The fourth phase of the SysPMI is the overall improvement of performance(s)
for all system-level threads by improving subfunctions. Mechanisms are
tuned, enhanced, improved, or replaced with improved components or
objects. Should new technologies or modifications to existing objects be
necessary, they are performed in the fourth phase (after the system has been
shown to provide the system-level functions and the optimized level of
performance(s) associated with those performances). The culmination of the
fourth phase of SysPMI is system-level testing.
The fifth phase of the SysPMI is preparation of the final version of the
validation strategy, upgrade strategy, and maintenance strategy. Furthermore,
the validation strategy is carried out in the fifth phase. Note that verification
occurs during all phases of the systems engineering work, from conceptualization through development. Verification of the system design, architecture, concept of operations, and specifications must be completed before
integration of physical objects to assure that only those objects and functions
that satisfy the specifications and meet the requirements end up having time
spent on them by the integration teams.
Three Tests for Iterative Thinking versus recursive Thinking
As successive phases of the SysPMI are implemented and progress toward
their objectives, the type of work transitions from iterative-centric thinking
to recursive-centric thinking. To discern how much thinking needs to be
involved with work in a particular stage, there are three questions that
should be answered. The first question deals with the scalability of the
objects to deal with inputs and outputs (including losses to achieve those
outputs) through their mechanisms in the same fashion that is determinable
from a sampling of data points (taken by modeling, simulation, or testing).
The relation between successive domains of data, taken in various regions
Engineering Systems Integration
the subfunction levels that concatenate to the highest-priority system-level
function (in its simplest form).
The third phase of the SysPMI covers the expansion of integration to the
prioritized top-level system functions and the critical independencies.
Phase III spans the test planning, test execution, and benchmarking of the
prioritized system-level functional threads. The culmination of the third
phase of the SysPMI is the demonstration of system-level functions in their
simplest forms based on their set(s) of subfunctions. To complete the third
phase, some object demonstrated in Phase I will need to have additional subfunctions built into their physical entities. As additional subfunctions are
completed they will be tested to demonstrate additional functionality as well
as to show improvement(s) in the end-to-end system-level functions. Should
a system-level function be degraded from its benchmark performance by
the addition of a new functionality, the objects that were modified will be
analyzed to improve their handling of EMMI through adjustments of their
mechanisms.
The fourth phase of the SysPMI is the overall improvement of performance(s)
for all system-level threads by improving subfunctions. Mechanisms are
tuned, enhanced, improved, or replaced with improved components or
objects. Should new technologies or modifications to existing objects be
necessary, they are performed in the fourth phase (after the system has been
shown to provide the system-level functions and the optimized level of
performance(s) associated with those performances). The culmination of the
fourth phase of SysPMI is system-level testing.
The fifth phase of the SysPMI is preparation of the final version of the
validation strategy, upgrade strategy, and maintenance strategy. Furthermore,
the validation strategy is carried out in the fifth phase. Note that verification
occurs during all phases of the systems engineering work, from conceptualization through development. Verification of the system design, architecture, concept of operations, and specifications must be completed before
integration of physical objects to assure that only those objects and functions
that satisfy the specifications and meet the requirements end up having time
spent on them by the integration teams.
Three Tests for Iterative Thinking versus recursive Thinking
As successive phases of the SysPMI are implemented and progress toward
their objectives, the type of work transitions from iterative-centric thinking
to recursive-centric thinking. To discern how much thinking needs to be
involved with work in a particular stage, there are three questions that
should be answered. The first question deals with the scalability of the
objects to deal with inputs and outputs (including losses to achieve those
outputs) through their mechanisms in the same fashion that is determinable
from a sampling of data points (taken by modeling, simulation, or testing).
The relation between successive domains of data, taken in various regions