| connection Element |
Connection
Namespace: Empty
Schema: Empty
Type
ParentsChildren| Name | Occurrences | Description |
|---|---|---|
 All | ||
 connectionType | [0, 1] | Optional classification of the connection type |
| controlDevices | [0, 1] | Optional control devices defining connection-specific operating states |
| description | [0, 1] | Description |
| name | Name | |
| source | Definition of the source of the connection | |
| target | Definition of the target of the connection |
Attributes| Name | Type | Required | Description |
|---|---|---|---|
 externalDataDirectory |  string | ||
| externalDataNodePath | string | ||
| externalFileName | string | ||
| uID | ID | Yes |
RemarksA connection represents a directed logical relation between a source and a target within a system architecture. It can be used to describe interactions, transfer paths, or dependencies between system components and their interfaces to other systems.
Depending on the selected modeling fidelity, source and target may reference components (or their sub-components) via uID. Alternatively, they may refer to external entities (such as ambient or passengers), ATA chapters, or other system architectures. Optional controlDevices can be used to describe connection-specific operating states. The optional connectionType can be used to classify the connection, for example as electric, pneumatic, hydraulic, mechanical, or data.
See Also