81
Essences of Interaction
The model for objective causalities must deal with objective behavioral
issues and objects as well as their mechanical properties (the objective component), and the processes to provide the objective component through cognition or rules, procedures or activities, and models or representations of
cognition or procedures (the subjective part). The model for objective causalities is rationally consistent with a core interpretation (Luhmann 1982) of the
Luhmannian perspective of systems theory (Luhmann 1995a, b).* These two
parts form the model from which a framework is devised to guide thinking
and management of relations. The objective part encapsulates the resultant
product or service that is built by the systems engineer while the subjective
part is describable as the management process used by the system engineer
to satisfy the requirements of the new product or service (i.e., perhaps a
system). The objective part can also be construed as nature’s objects interacting with EMMI, with the subject part construed as the set of allowable interaction, the procedures of those interactions, and the manner of representing
those means that are recognizable by the objects to be integrated.
Objective Causalities Framework
A framework for objective causalities applicable to interaction and integration
must reconcile the sociological aspects of systems integration, integration
method, processes, activities, and acts (referred to as the subjective factors)
with the physical and functional aspects of the product and service during
development (and integration) and when operational (referred to as the objective factors). The blending of these social and engineering aspects results in a
nexus of cognitive and literal activities that build products and services.
Figure 2.8 depicts a diagram showing events (customer, developer’s enterprise, and developer’s project). The causal events that impact on the project
(the customer and the enterprise) are initiated in the past. The modal causalities reflect these historical modes from which near-term events are resultant.
Budgets and schedules are limited during the modal causality phase by the
source of funding for a capability. The customer determines a set of requirements that are consistent with the limited funding and schedule, then begins
the processes to either purchase the product or service or have the requisite
requirements satisfied by a custom development and integration. A contract
* Within the ongoing debates of sociological theory, two basic views have emerged—the view
of social processes as systemic or as consensual decision making. Since systems engineering
is as much a social science as it is an engineering discipline, the debate is relevant to the discussion of integration. Systems engineering is about building products and services. The
social aspect of management, economics, and team activities are important and germane.
The engineering aspects of bringing technologies and structures together in a meaningful
way reveal the efficacy of the resultant product or service (Bausch 1997).
Essences of Interaction
The model for objective causalities must deal with objective behavioral
issues and objects as well as their mechanical properties (the objective component), and the processes to provide the objective component through cognition or rules, procedures or activities, and models or representations of
cognition or procedures (the subjective part). The model for objective causalities is rationally consistent with a core interpretation (Luhmann 1982) of the
Luhmannian perspective of systems theory (Luhmann 1995a, b).* These two
parts form the model from which a framework is devised to guide thinking
and management of relations. The objective part encapsulates the resultant
product or service that is built by the systems engineer while the subjective
part is describable as the management process used by the system engineer
to satisfy the requirements of the new product or service (i.e., perhaps a
system). The objective part can also be construed as nature’s objects interacting with EMMI, with the subject part construed as the set of allowable interaction, the procedures of those interactions, and the manner of representing
those means that are recognizable by the objects to be integrated.
Objective Causalities Framework
A framework for objective causalities applicable to interaction and integration
must reconcile the sociological aspects of systems integration, integration
method, processes, activities, and acts (referred to as the subjective factors)
with the physical and functional aspects of the product and service during
development (and integration) and when operational (referred to as the objective factors). The blending of these social and engineering aspects results in a
nexus of cognitive and literal activities that build products and services.
Figure 2.8 depicts a diagram showing events (customer, developer’s enterprise, and developer’s project). The causal events that impact on the project
(the customer and the enterprise) are initiated in the past. The modal causalities reflect these historical modes from which near-term events are resultant.
Budgets and schedules are limited during the modal causality phase by the
source of funding for a capability. The customer determines a set of requirements that are consistent with the limited funding and schedule, then begins
the processes to either purchase the product or service or have the requisite
requirements satisfied by a custom development and integration. A contract
* Within the ongoing debates of sociological theory, two basic views have emerged—the view
of social processes as systemic or as consensual decision making. Since systems engineering
is as much a social science as it is an engineering discipline, the debate is relevant to the discussion of integration. Systems engineering is about building products and services. The
social aspect of management, economics, and team activities are important and germane.
The engineering aspects of bringing technologies and structures together in a meaningful
way reveal the efficacy of the resultant product or service (Bausch 1997).