System Architecture

Developing Complex ECU Software Architectures
  • Developing and modeling ECU software
  • Visualizing software architectures
  • Generating virtual ECUs for early testing without an ECU prototype
  • Support of AUTOSAR R3.x and R4.0
  • Easy access to TargetLink® for developing software component functions
  • Connection to tools for configuring basic software
  • Process support for importing and exporting AUTOSAR files
  • Automating individual actions
The software in one of today's electronic control units comprises a large number of interacting components. These are joined by numerous distributed functions that are not confined to just one single ECU, but are spread across several interacting ECUs. The resulting system architectures are extremely complex, and to keep things under control when developing them, well-structured procedures and extensive tool support are essential. dSPACE provides the solution: the software architecture tool SystemDesk®.
Comprehensive AUTOSAR Support
Not all ECU software has to be developed from scratch. Tested software components (SWCs) are often already available and can be reused. Because ECU software is usually not developed by one team alone, but by several groups within a company or even in different companies, it is important to be able to integrate SWCs from different sources. This was the motivation for the AUTOSAR standard, which defines interfaces and data transfer methods to ensure that individual functions and components can work together without errors.
Support for the AUTOSAR standard is a central element in SystemDesk, making it easier and safer to reuse existing SWCs that have already been tested. SystemDesk enables users to efficiently create high-quality AUTOSAR description files that guarantee smooth data exchange between OEMs and their suppliers.
Graphical Software Architecture Modeling
SystemDesk visualizes the individual software components and the communication connections between them to make the task of creating a software architecture clear and intuitive. Even with very complex systems, the interactions between components can be seen at a glance. All the software architect has to do is drag components and interfaces to the architecture and connect them. Special configuration dialogs facilitate component definition by displaying only the settings that are actually required at each point in the process. And you can save time and effort by using scripts to automate a wide range of actions.