systemArchitectureType

A system architecture represents the logical and functional view of an aircraft system. It complements the physical and geometric description provided by genericSystems by defining the connections between instantiated components and their interfaces to other systems.

In accordance with the CPACS top-down approach, a system architecture may initially be specified only by its systemType. The systemType can be used to classify the architecture by a predefined ATA chapter or by the keyword generic.

The optional controlDevices can be used to describe operating states by assigning abstract control parameters. The optional connections define the source and target of interactions within the architecture. These references may point to components or sub-components, or alternatively to external elements (ambient | passengers), ATA chapters, or other system architectures.

Attributes

Name	Type	Use	Description
`@externalDataDirectory`	`xsd:string`	optional	Directory of the external data file
`@externalDataNodePath`	`xsd:string`	optional	Path of the node inside the external data file
`@externalFileName`	`xsd:string`	optional	Name of the external data file
`@uID`	`xsd:ID`	optional	UID

Child elements

Name	Type	Constraints	OccurrenceHow often the element may appear at this place. The schema writes it as minOccurs and maxOccurs on the declaration.	Description
allThe children below may appear in any order. Each may appear at most once.
`name`	`stringBaseType`		[1..1] required	Name
`description`	`stringBaseType`		[0..1] optional	Description
`systemType`	`systemTypeType`	one of 2 types	[0..1] optional	ATA Chapter \| generic
`controlDevices`	`systemControlDevicesType`		[0..1] optional	Control devices
`connections`	`systemConnectionsType`		[0..1] optional	Connections between the system elements

systemArchitectureType

Attributes

Child elements

Used by

In a dataset · 2 paths

In the schema · 1 declaration