For a better experience on dSPACE.com, enable JavaScript in your browser. Thank you!

Use Case: Modeling AUTOSAR System Architectures

Modeling AUTOSAR architectures and systems can be a quite complex task because the whole structure of the ECU software has to be defined and designed. With SystemDesk®, dSPACE offers a dedicated AUTOSAR authoring tool for software architects.

Intuitive Work Environment

Different overviews that concentrate on different system aspects, simplify working with large and complex systems.

SystemDesk provides a graphical working environment that gives you a clear overview of the components and their connections at all times.

You can, for example, create different composition diagrams for one software composition that display selected software components and the connections between them. Thus, you can always concentrate on the task ahead, and you are able to work efficiently, especially in large series projects.

SystemDesk provides support for error-prone and time-consuming tasks, such as automatically selecting the correct implementation data types for the used application data types. 

dSPACE Support for Modeling AUTOSAR Systems

  • Reliable model quality due to a comprehensive set of validation rules
  • Close coupling with TargetLink to include function code
  • Easy integration into company-specific processes with fully documented API
  • Reliable data exchange with partners and project members based on adaptive data exchange options
  • Complete AUTOSAR schema support for all current AUTOSAR 4.x releases

Developing AUTOSAR Architectures

The first step is to plan or develop the new functions, for example with MATLAB®/Simulink®. You then decide which functions are to be included into one software component (SWC) and the overall structure of your ECU software. Creating your architecture with your SWCs is done graphically in SystemDesk. If SWCs are already available, you can start with them by reusing and adapting them.

All throughout the development process, SystemDesk offers comprehensive dialogs and editors that guide you through the necessary steps, for example for importing and assigning the bus communication for your SWCs.

Additionally, SystemDesk comes with a large set of validation rules that continuously let you check whether the design complies with the AUTOSAR constraints and is consistent. This way, you can be sure to develop a system that meets the requirements of the AUTOSAR standard. You can also add your own validation rules and build your own rule set so that it fits your specific needs best.

Reliable Data Exchange

Using the AUTOSAR description file between different tools allows for an easy and reliable data exchange.

Exchanging data between tools, e.g., function code or basic software, or between partners, e.g., suppliers and OEM, plays an important part in ECU software development. As an AUTOSAR authoring tool, SystemDesk supports various options for the import and export of AUTOSAR description files (arxml), and for including function code and basic software.

SystemDesk offers different options for the arxml file exchange to best support the different use cases. Examples for this are, if you are working in a team and you want to exchange data between an OEM and a supplier, or if you want to transfer the architecture to a basic software configuration tool.

To include function code into the SWC, SystemDesk works closely together with TargetLink®, the production code generator from dSPACE. The two tools exchange SWC containers that hold not only ARXML files but also source files for implementing A2L files, and other helpful meta information. This is a reliable, transparent way to perform AUTOSAR round trips with minimum user intervention. 

Further Information