The AUTOSAR Behavior Toolbox contains all elements required to model the internal behavior of AUTOSAR components (e.g. Runnables, Inter-Runnable-Variables etc.). Not all model elements are currently exported to ARXML.
| Name | Usage |
|---|---|
| AUTOSAR Artifact | Defines artifacts like .h and .c files in an enar autosar model. |
| AUTOSAR Behavior | Container used in a AUTOSAR component to contain all behavior elements. This element is based on the structured Activity and you can use the EA-functionality of the Composite Diagram to enable a double-click navigation to the sub-diagram. |
| AUTOSAR Control Flow | Connects AUTOSAR Events to AUTOSAR Runnables. |
| AUTOSAR Data Element | Currently unused and reserved for future extensions |
| AUTOSAR Dependency | Connector used to express dependencies to other model elements. |
| AUTOSAR Event | Defines AUTOSAR element events (e.g. time events to start a runnable) |
| AUTOSAR Inter Runnable Variable | Defines Inter-Runnable-Variables. |
| AUTOSAR Object Flow | This connection is used to connect Runnables and Inter Runnable Variables or Component Ports and AUTOSAR Runnable Ports. |
| AUTOSAR Realization | This connection is used to express a realization of a Runnable or a component. It is used to connect Runnables and/or components and AUTOSAR Artifacts. |
| AUTOSAR Runnable | Use this elements to define Runnables as part of the Component Behavior. |
| AUTOSAR Runnable Port | The Runnable Ports define an interface of a Runnable. They are connected by an AUTOSAR Object Flow connector with a AUTOSAR Component port. |
| AUTOSAR Software Component Implementation | This element is used to represent a SW Component Implementation. |
| AUTOSAR Initialization | This connector is used to specify complex data type initializations. |