163
Foundations in Systems Integration
• Functional representations
• Performance representations
• Quality representations
• Hardware representations
• Software representations
• Usability and user interface representations
• Maintenance representations
• Support representations
• Logistics representations
• Operational reliability
• Manufacturability and assembly representations
• Affordability representations
• Reliability representations
• Behavioral representations
As with abstract integration, the domains of the model class of integration
span objects and process, the attributes of things objective and subjective.
A product (e.g., a deck of cards) that is manufactured has an intended use.
The cards come packaged in a box or wrapper. One of the functions of the
physical wrapper is to contain the physical extent to which the deck can be
separated into individual cards. Some functions of a deck of cards include ‘to
entertain’ (play games), ‘to act as building tiles to construct structures’ (build
houses made of cards), ‘glide’ (when ‘pitched’ in an atmosphere), ‘to shim’
(act as a jack for leveling uneven supports), ‘pick teeth’ (flossing), ‘jimmy’
(open doors, disengage locks), ‘act as a paperweight,’ ‘act as a combustible to
start or sustain a fire,’ ‘cover an eye,’ ‘to symbolize an abstract or corporeal
concept,’ and ‘act as an injurious projectile.’ All these functions of a manufactured deck of cards are determined by the needs and wants of the user. The
process domain characterizes the human activities that result in the representations. These processes span the set of acts that when concatenated into
like-kind or singularly related activities result in the formation and enactment of a process.
The combination of the abstraction, social, and model classes constitutes
the whole of the integration description. These classes link the common set
of limitations, the constraints allocated within the project and temporal constraints that synchronize the interpersonal relations, intellectual discussions, and the various corporeal representations for the product or service.
Newton, as observer and subsequently as communicator, was separated
from his experiment with the motions of an apple and therefore used the
physical domain in which to describe that motion. Carrying out his methods
and approach to the experiments falls into the model class (his organization
and enactment of tasks or activities fall into the process domain, his
Foundations in Systems Integration
• Functional representations
• Performance representations
• Quality representations
• Hardware representations
• Software representations
• Usability and user interface representations
• Maintenance representations
• Support representations
• Logistics representations
• Operational reliability
• Manufacturability and assembly representations
• Affordability representations
• Reliability representations
• Behavioral representations
As with abstract integration, the domains of the model class of integration
span objects and process, the attributes of things objective and subjective.
A product (e.g., a deck of cards) that is manufactured has an intended use.
The cards come packaged in a box or wrapper. One of the functions of the
physical wrapper is to contain the physical extent to which the deck can be
separated into individual cards. Some functions of a deck of cards include ‘to
entertain’ (play games), ‘to act as building tiles to construct structures’ (build
houses made of cards), ‘glide’ (when ‘pitched’ in an atmosphere), ‘to shim’
(act as a jack for leveling uneven supports), ‘pick teeth’ (flossing), ‘jimmy’
(open doors, disengage locks), ‘act as a paperweight,’ ‘act as a combustible to
start or sustain a fire,’ ‘cover an eye,’ ‘to symbolize an abstract or corporeal
concept,’ and ‘act as an injurious projectile.’ All these functions of a manufactured deck of cards are determined by the needs and wants of the user. The
process domain characterizes the human activities that result in the representations. These processes span the set of acts that when concatenated into
like-kind or singularly related activities result in the formation and enactment of a process.
The combination of the abstraction, social, and model classes constitutes
the whole of the integration description. These classes link the common set
of limitations, the constraints allocated within the project and temporal constraints that synchronize the interpersonal relations, intellectual discussions, and the various corporeal representations for the product or service.
Newton, as observer and subsequently as communicator, was separated
from his experiment with the motions of an apple and therefore used the
physical domain in which to describe that motion. Carrying out his methods
and approach to the experiments falls into the model class (his organization
and enactment of tasks or activities fall into the process domain, his