9
Importance of Integration
Approximately half of the first demonstrable software objects pass their
unit tests, while the failed units undergo rework. However, nearly half of
all software units that eventually pass this early testing fail their integration and system test (Mishler et al. 2007). Given the “design–build–test–fix”
approach, integration for the Hubble Space Telescope probably began as early
as possible to use the success and failures from testing as valuable feedback
to help guide planning and to indicate progress. As such, integration and
testing was used as part of developing the subsystem, blurring the distinction between development, integration, and testing.
Principles
Beginning the discussion on systems integration with principles may seem a
bit stilted, as it seems to weigh toward an academic discussion away from
any practical value. However, when the range of phenomena is very broad,
the subject complicated, the practice encumbered with lore, legends, and
superstitions, principles help defeat the viciousness of myths. The “bird’seye view” enables us to distill the exactitudes without “losing our bearings”
(Ashby 1962).
A principle is a means of organizing thoughts to articulate a pattern of
behavior that frames or structures action. In essence, a principle represents
both the context and concepts* that enable us to classify and interpret a situation in terms of previous situations. A situation is a sequence of events
where an event describes an activity that relates an input EMMI to an output
EMMI through a causal mechanism. An event is something that happens, an
action that takes place, or an occurrence. An event is a change in an object
due to the transformation of input EMMI into output EMMI. Changes in an
object may be causal to changes in other objects. In this manner, events can
be identified as precipitating or triggering other events. Events can result in
interactions or integrations. Events have structure, can be sequenced through
mechanistic transformations of EMMI, and are distinctively recognizable as
objects (i.e., physical or intellectual).
The framework in which a principle is described has both observation and
measurement, that is, both subjectivity and objectivity. The scope (or in this
case, the applicability) of a framework determines the completeness for a
given event or sequence of events. For systems integration, the events are
grouped or evaluated by principle, each underpinned with a fundamental or
undisputed law, doctrine, or assumption that is justifiable on the basis of
another principle (e.g., treat others as you would like to be treated); a rule;
* Including interactions and integrations of the concepts.
Importance of Integration
Approximately half of the first demonstrable software objects pass their
unit tests, while the failed units undergo rework. However, nearly half of
all software units that eventually pass this early testing fail their integration and system test (Mishler et al. 2007). Given the “design–build–test–fix”
approach, integration for the Hubble Space Telescope probably began as early
as possible to use the success and failures from testing as valuable feedback
to help guide planning and to indicate progress. As such, integration and
testing was used as part of developing the subsystem, blurring the distinction between development, integration, and testing.
Principles
Beginning the discussion on systems integration with principles may seem a
bit stilted, as it seems to weigh toward an academic discussion away from
any practical value. However, when the range of phenomena is very broad,
the subject complicated, the practice encumbered with lore, legends, and
superstitions, principles help defeat the viciousness of myths. The “bird’seye view” enables us to distill the exactitudes without “losing our bearings”
(Ashby 1962).
A principle is a means of organizing thoughts to articulate a pattern of
behavior that frames or structures action. In essence, a principle represents
both the context and concepts* that enable us to classify and interpret a situation in terms of previous situations. A situation is a sequence of events
where an event describes an activity that relates an input EMMI to an output
EMMI through a causal mechanism. An event is something that happens, an
action that takes place, or an occurrence. An event is a change in an object
due to the transformation of input EMMI into output EMMI. Changes in an
object may be causal to changes in other objects. In this manner, events can
be identified as precipitating or triggering other events. Events can result in
interactions or integrations. Events have structure, can be sequenced through
mechanistic transformations of EMMI, and are distinctively recognizable as
objects (i.e., physical or intellectual).
The framework in which a principle is described has both observation and
measurement, that is, both subjectivity and objectivity. The scope (or in this
case, the applicability) of a framework determines the completeness for a
given event or sequence of events. For systems integration, the events are
grouped or evaluated by principle, each underpinned with a fundamental or
undisputed law, doctrine, or assumption that is justifiable on the basis of
another principle (e.g., treat others as you would like to be treated); a rule;
* Including interactions and integrations of the concepts.