40
Engineering Systems Integration
boundaries that are important to integration relate to the physical object,
they represent the extent of the uses of that object by other objects, and they
relate to the behaviors of those users of the functions of the objects. How the
boundaries interact is not always straightforward from the perspective taken
by the observer. Different observers may perceive boundaries differently
and in conflict with other observers.
From an integration perspective, the physical boundaries are the primary
focus from which the functional and behavioral aspects are realized.
Analysis and evaluation of boundaries should and can be performed before
finalizing requirements for a product or service. Bringing together two
objects exposes the functions of a product or service, whereas operating (or
testing) those objects makes observable the behaviors of users (and other
stakeholders). Any interaction that has a significant impact on the product or
service needs to be considered and accommodated in the design, architecture, operation, and disposal. The lifecycle issues need to be considered in
systems engineering and in systems integration. Each of these boundaries
extends the EMMI transformed by the object’s mechanism(s). From the perspective of an observer who is focused on establishing boundaries from an
object (an object-centric boundary perspective) the most limiting of these boundaries is likely the physical boundary—the matter that comprises the object.
That the physical boundary is considered limiting is meant to imply that the
object minimum extent is deemed physical, and the functional and behavioral impacts carry on far beyond the physical boundary. The object’s physical boundary (i.e., the physical boundary of the product or service) is most
often extended by the user behaviors due to the object’s functions. The functional boundaries are determined by the temporal and spatial relations
between a “user” (object) and a product or service (object). The behaviors that
result because of the objects or their function(s) (or in anticipation of same)
are similarly bounded by the lifecycle of these kindred behaviors.
Scope
Products and services have scope; projects have scope. For many engineering projects, the scope of the product or service is defined spatially by a
physical boundary. And in turn, sometimes the physical boundary is stated
as the spatial extent of the product or service. For example, a hardback book
is often considered spatially to be the extent of its physical dimensions (i.e.,
length, width, and depth). When the book is shipped, its weight is considered in addition to its physical dimensions. When the book is transported,
its physical characteristics usually dominate the important boundary consideration. When the book is read, its physical dimensions play a role in the
boundary considerations, as the book may need to be held and the pages
Engineering Systems Integration
boundaries that are important to integration relate to the physical object,
they represent the extent of the uses of that object by other objects, and they
relate to the behaviors of those users of the functions of the objects. How the
boundaries interact is not always straightforward from the perspective taken
by the observer. Different observers may perceive boundaries differently
and in conflict with other observers.
From an integration perspective, the physical boundaries are the primary
focus from which the functional and behavioral aspects are realized.
Analysis and evaluation of boundaries should and can be performed before
finalizing requirements for a product or service. Bringing together two
objects exposes the functions of a product or service, whereas operating (or
testing) those objects makes observable the behaviors of users (and other
stakeholders). Any interaction that has a significant impact on the product or
service needs to be considered and accommodated in the design, architecture, operation, and disposal. The lifecycle issues need to be considered in
systems engineering and in systems integration. Each of these boundaries
extends the EMMI transformed by the object’s mechanism(s). From the perspective of an observer who is focused on establishing boundaries from an
object (an object-centric boundary perspective) the most limiting of these boundaries is likely the physical boundary—the matter that comprises the object.
That the physical boundary is considered limiting is meant to imply that the
object minimum extent is deemed physical, and the functional and behavioral impacts carry on far beyond the physical boundary. The object’s physical boundary (i.e., the physical boundary of the product or service) is most
often extended by the user behaviors due to the object’s functions. The functional boundaries are determined by the temporal and spatial relations
between a “user” (object) and a product or service (object). The behaviors that
result because of the objects or their function(s) (or in anticipation of same)
are similarly bounded by the lifecycle of these kindred behaviors.
Scope
Products and services have scope; projects have scope. For many engineering projects, the scope of the product or service is defined spatially by a
physical boundary. And in turn, sometimes the physical boundary is stated
as the spatial extent of the product or service. For example, a hardback book
is often considered spatially to be the extent of its physical dimensions (i.e.,
length, width, and depth). When the book is shipped, its weight is considered in addition to its physical dimensions. When the book is transported,
its physical characteristics usually dominate the important boundary consideration. When the book is read, its physical dimensions play a role in the
boundary considerations, as the book may need to be held and the pages