 | Additional relationships are introduced between the elements listed above. These are realized as references. The following table contains a listing of all types of references to be considered in this context and includes those already in existence.
Types of references
No.
|
Designation
|
Source element
|
Target element
|
Meaning
|
1
|
|
<requirements>, <product-spec>
|
|
Defines the top-level part type (exactly one) for each of the two views.
|
2
|
|
|
|
Assigns the specific part type (exactly one) to a part.
|
3
|
|
|
|
Allocates software functions to the software of a part type ( none, one or several), that are described within the software of another part type, e.g. multiple use of such functions as operating system or network management functions.
|
4
|
|
|
|
Allocates software functions to a software function (none, one or several) within the same software description, that constitute the decomposition of the first.
|
5
|
|
Part, SW function
|
Function
|
Allocates those (behavioral) functions to a part or a software function (none, one or several) that it realizes.
|
6
|
|
Function
|
Function
|
Allocates the (behavioral) function in the view requirement, to a specified (behavioral) function in the view consent, that is realized by the first.
|
The following diagram illustrates the types of references as an example (no. 6 excepted).
Figure 21: Extended structure with references
|