Workflows for AUTOSAR

To develop AUTOSAR software components in Simulink^®, you create a Simulink representation of an AUTOSAR software component. AUTOSAR component creation can start from an existing Simulink design or from an AUTOSAR XML (ARXML) component description created in another development environment.

In a Simulink originated (bottom-up) workflow, you take an existing Simulink design or algorithm and map it into an AUTOSAR software component model.

In a round-trip workflow, you import an AUTOSAR component description created by an authoring tool in another development environment. Importing the component specification into Simulink creates an AUTOSAR software component model.

Simulink Originated (Bottom-Up) Workflow

In a Simulink originated, or bottom-up, workflow, you take a design or algorithm that originated in Simulink and configure it into an AUTOSAR software component model. To get started, use the AUTOSAR Component Quick Start or AUTOSAR model templates on the Simulink Start Page. For more information, see Create AUTOSAR Software Component in Simulink.

You develop the component design and behavior in Simulink. For example, you configure AUTOSAR software component elements, map Simulink model elements to AUTOSAR software component elements, develop component behavior algorithms, and simulate the component behavior.

Using Simulink Coder™ and Embedded Coder^®, you can generate AUTOSAR-compliant XML descriptions and C or C++ code from the component model. You can test the code in Simulink or integrate the descriptions and code in an AUTOSAR run-time environment.

Round-Trip Workflow

In a round-trip workflow, you import an AUTOSAR software component description created in another development environment into Simulink. Simulink can import AUTOSAR-compliant XML descriptions exported by common AUTOSAR authoring tools (AATs). Importing the XML description of an AUTOSAR software component creates a Simulink model representation of the component. For more information, see Import AUTOSAR XML Descriptions Into Simulink or Import AUTOSAR Adaptive Software Descriptions.

As with a Simulink originated design, you develop the component design and behavior in Simulink. For example, you configure AUTOSAR software component elements, map Simulink model elements to AUTOSAR software component elements, develop component behavior algorithms, and simulate the component behavior.

Using Simulink Coder and Embedded Coder, you can generate AUTOSAR-compliant XML descriptions and C or C++ code from the component model for testing or integration.

In a round-trip workflow, you deliver the generated description files and code back to the originating AAT. Using the AAT, merge your Simulink design work with other components and systems. If you further modify the component in the other development environment, use the AAT to export updated XML specifications. In your Simulink environment, import the new descriptions and update your component model to reflect the changes. For more information, see Import AUTOSAR Software Component Updates.

To support the round trip of AUTOSAR elements between an AAT and Simulink, ARXML import preserves imported AUTOSAR XML file structure and content for ARXML export. For more information, see Round-Trip Preservation of AUTOSAR XML File Structure and Element Information.