Intended learning outcomes: Explain the association hierarchy, or determination hierarchy.
Continuation from previous subsection (20.2.3)
In an association hierarchy, or determination hierarchy, all elements G1, G2, G3, … that jointly define or determine a subordinate element A, or due to whose association an element A comes into existence or is generated, are placed superior to A.
In other words, to exist, element A needs all elements G1, G2, G3,… jointly. We can also say that A belongs to the elements G1, G2, G3, … together, or that A comes into existence because of their association. In reverse order, the hierarchically superior elements G1, G2, G3,… jointly “generate,” “determine,” or “possess” a subordinate element A. Figure 20.2.3.3 illustrates the semantics.
Fig. 20.2.3.3 Association hierarchy, or determination hierarchy.
Examples of association hierarchies, or determination hierarchies, are:
- To exist, a child needs a father and a mother. Or the child comes into existence by their association.
- A taxpayer is defined by a person and a political unit (municipality)
- A customer order is determined by a customer and a date.
- Sales and distribution are determined by marketing (which is strategically superior) and long-term corporate planning.
Examples of association hierarchies in the modeling of information systems are:
- To exist, an object needs various other objects
- A process is determined by several other processes
The different verbs used to describe the semantics of the association hierarchy, point up different possible degrees of intensity of determination: from generation to possession. However, what they all always share is that the subordinate element cannot exist without the elements that determine it. The most intensive form is a “parent/child” relationship.
The least binding form of the association hierarchy can be expressed by the verb “to have,” or in reverse order “belongs to.” However, the semantics are too general to characterize the association hierarchy, as it can also be used for the component hierarchy or for another hierarchical or nonhierarchical relationship.
The various semantic constructs of creating hierarchies are recursive. Thus, multilevel constructs can be built:
- Each component itself can in turn be composed of subordinate elements.
- Each specialized element itself can in turn be specialized into further elements, possibly according to another criterion.
- Each element defined through a superior element can in turn, possibly together with further elements, determine a subordinate element.
Familiar examples:
- A bill of material or nomenclature is the structured list of components making up a product. It is a multilevel component hierarchy. See here also Section 1.2.2.
- A classification system is a multilevel specialization hierarchy. An example of this is the German DIN 4000 standard, a standardized classification guide aiding the work of the designer, enabling the designer to systematically trace items — typically semiprocessed items and single parts. See here also Section 17.5.3.
- The classical chain of command in a company or another human or mechanical organization is a multilevel determination hierarchy in which in each instance only one determining element has an influence on one subordinate element.
Course section 20.2: Subsections and their intended learning outcomes
20.2 Modeling Enterprise Information Systems
Intended learning outcomes: Present basic principles of modeling. Differentiate various dimensions in the modeling of information systems for business processes. Describe the dimension of hierarchy creation and the dimension of various views in modeling.
20.2.1 Basic Principles of Modeling
Intended learning outcomes: Describe, as a basic problem in modeling, how the quality of a system image is affected by the person who designs the model.
20.2.2 Various Dimensions in the Modeling of Information Systems for Business Processes and the ARIS Tool Set
Intended learning outcomes: Present the various dimensions of the ARIS tool set for modeling information systems for business processes. Explain the dimension of four views and the dimension of three descriptive levels.
20.2.3 Whole-Part Hierarchy, and Specialization Hierarchy
Intended learning outcomes: Differentiate between the component hierarchy, or whole-part hierarchy, and the specialization hierarchy.
20.2.3b Association Hierarchy, or Determination Hierarchy
Intended learning outcomes: Explain the association hierarchy, or determination hierarchy.
20.2.4 Dimension: Various Views in Modeling Enterprise Information Systems
Intended learning outcomes: Explain the four views of information systems for business processes. Differentiate between process-oriented modeling, function-oriented modeling, object-oriented modeling, and task-oriented modeling.
