About System Mapping Diagram

The system mapping diagram shows you the mapping between the functional and the hardware or between the software and the hardware.

This page discusses:

System Mapping Diagram Structure

A system mapping diagram is created in a view and is linked to the system mapping tree.

To create a diagram, click Create View from the tree.

A system mapping can be attached to several diagrams.

In the system mapping diagram, you can show elements from the associated topology and either from the associated function or the software component.

Functions and subfunctions are represented by boxes, with attached In and Out ports.

EE components and software components are represented by boxes. Each EE component and software component has its own color.

Each component can be either of the following:

You can quickly identify the state of an element of a system mapping by its color:


Components	Representation of Mapped Elements	Representation of Unmapped Elements
Actuator
ECU
Electrical device
Sensor
Subsystem	-
Function
Software Architecture
Atomic Software Component
Application
Partition
Configuration Table

Note: With the Avionics Architect (AVARA) role, you can work with applications, partitions, and configuration tables.

EE component ports, functions/subfunctions ports, and software ports have the following representations depending on their type:


Port	Representation	Color Code
Functional port	In: Out:	Mapped port. Unmapped port. Unmapped port with some, but not all, of its subflows mapped. Local port. This port does not need to be mapped. Unknown status. Waiting for the mapping of the functional. Partially mapped port. The bus is referenced but the signal is not yet identified.
Software: Sender-receiver port	Read: Write:	Mapped port. Unmapped port. Unmapped port with some, but not all, of its subflows mapped. Local port. This port does not need to be mapped. Unknown status. Waiting for the mapping of the functional. Partially mapped port. The bus is referenced but the signal is not yet identified.
Software: Client-server port	Read: Write:
Hardware	Wired In: Wired Out: Wired InOut: Other ports:

EE channels are represented by an extended box or by a line:

Connections have the following representation:


Connections	Representation
Connection between ports
Computed path of connections for functions and software components: When a data passes through a few levels of an object hierarchy, the whole pathway is displayed by a green dotted line. This line is displayed between allocated objects or most inner objects, when no allocated objects are involved in the path.

You can temporarily or permanently display the links between mapped elements.

For example, if you select an ECU, the links from the ECU to the allocated functions are displayed.

The representation of links depends on the selection:


Links	Representation
Links between mapped ECUs and mapped functions or between mapped ECUs and mapped software components. This mode is temporarily or permanent. Note: If an ECU, function, or software component is filtered, the allocation is displayed in gray instead of red.	or
All links from buses, ECU ports, functional ports, or software ports. This mode is only temporarily.
All links from gateways or to gateways. This mode is only temporarily.

You can display signals, flows, and frames in automatically computed I/O notes. You can select the notes but you cannot edit them.

For each ECU port, you can display the functional information or the communication information, which passes through.

I/O notes are represented by the following elements:


Notes	Representation
Incoming information
Outgoing information

Notes:

If you select a signal or a flow in a note, all the occurrences of this signal or flow are highlighted.
If you CTRL + click a signal or a flow in a note, all the occurrences of this signal or flow are highlighted with a color background. Each new action of this type is highlighted with another color.