| systemConnectionType Complex Type |
Connection
Namespace: Empty
Schema: Empty
Base Type
UsagesChildren| 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 | Source of the connection | |
| target | Target of the connection |
Attributes| Name | Type | Required | Description |
|---|---|---|---|
 externalDataDirectory |  string | Directory of the external data file | |
| externalDataNodePath | string | Path of the node inside the external data file | |
| externalFileName | string | Name of the external data file | |
| uID | ID | Yes | UID |
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 classifies the primary nature of the connection, such as electric, pneumatic, hydraulic, mechanical, fluid, or data.
The fluid type denotes the transport of a fluid medium as a consumable or resource, such as fuel, water, or oxygen. In contrast, hydraulic and pneumatic denote the transmission or conditioning of power via a pressurized liquid or gas, respectively.