167
Foundations in Systems Integration
of having no impact is satisfied and the releasing object is static. It is arguable
that something always happens to the acted on object, but that reaction may
not be observable, that is, below the threshold of detectability or causality. If
it is determined by reasoning or experimentation, the acted on object should
have a reaction, but nothing is observed, the reaction is determined to be
unknown. If the reaction is observable then we need both a perspective from
which to consider the observable in the context of patterns in addition to a
framework in which to make measurements according to that context. If the
functionality of the acted on object is degraded or destroyed, then the capacity* of the acted on object ‘to manage’ the release was exceeded. Now, if one
object’s release(s) invokes the receiving object to release(s), the two objects are
said to be interacting. If the two objects begin to interact in a cause/effect
manner, the two objects are said to be interacting and exchanging (termed
exchanging) releases.
Strategy of Integration
To develop an overall strategy for integration, we need to accommodate the
types of systems (NotaSystem, ProtaSystem, System, and System of Systems)
and bring together the classes of integration (abstract, social, and model) so
that the attributes and parameters within the domains (objects and processes) can be related to provide for the causal factors that result in products
and services.
At this point, we should be beyond the initial stages of thinking about
integration and are now willing to appreciate the nature of integration. What
does it mean to not be integrated? It is not integration to know how to configure or test the interfaces between objects and processes. Are the objects necessary, and insufficient? If there is no interaction (direct or otherwise)
between two objects, then neither of these objects can be integrated. Without
action there is no mechanism to facilitate integration.
Differentiation is determined as a need for integration (Bernstein 2001). If
the desire for the whole is to have increased differential value over that of its
constituent parts, then the strategy for integration formally identifies the
starting and ending structures of integration while recognizing the goal is to
increase value (Chapter 2) of the product or service. The value of systems
engineering is predicated on its ability to integrate disparate components
and a wide range of fields and disciplines. This effort is exacerbated by contradicting requirements constituted at the beginning of the work and then
* The maximum power, ability, and extent of storing, containing, absorbing, or grasping.
Foundations in Systems Integration
of having no impact is satisfied and the releasing object is static. It is arguable
that something always happens to the acted on object, but that reaction may
not be observable, that is, below the threshold of detectability or causality. If
it is determined by reasoning or experimentation, the acted on object should
have a reaction, but nothing is observed, the reaction is determined to be
unknown. If the reaction is observable then we need both a perspective from
which to consider the observable in the context of patterns in addition to a
framework in which to make measurements according to that context. If the
functionality of the acted on object is degraded or destroyed, then the capacity* of the acted on object ‘to manage’ the release was exceeded. Now, if one
object’s release(s) invokes the receiving object to release(s), the two objects are
said to be interacting. If the two objects begin to interact in a cause/effect
manner, the two objects are said to be interacting and exchanging (termed
exchanging) releases.
Strategy of Integration
To develop an overall strategy for integration, we need to accommodate the
types of systems (NotaSystem, ProtaSystem, System, and System of Systems)
and bring together the classes of integration (abstract, social, and model) so
that the attributes and parameters within the domains (objects and processes) can be related to provide for the causal factors that result in products
and services.
At this point, we should be beyond the initial stages of thinking about
integration and are now willing to appreciate the nature of integration. What
does it mean to not be integrated? It is not integration to know how to configure or test the interfaces between objects and processes. Are the objects necessary, and insufficient? If there is no interaction (direct or otherwise)
between two objects, then neither of these objects can be integrated. Without
action there is no mechanism to facilitate integration.
Differentiation is determined as a need for integration (Bernstein 2001). If
the desire for the whole is to have increased differential value over that of its
constituent parts, then the strategy for integration formally identifies the
starting and ending structures of integration while recognizing the goal is to
increase value (Chapter 2) of the product or service. The value of systems
engineering is predicated on its ability to integrate disparate components
and a wide range of fields and disciplines. This effort is exacerbated by contradicting requirements constituted at the beginning of the work and then
* The maximum power, ability, and extent of storing, containing, absorbing, or grasping.