Electronic development in the automobile industry has always been an iterative process—even long before the implementation of AUTOSAR. In the course of a project, requirements are amended or refined; decisions about design are revised and architectures adjusted. Through the standardization of specification formats of different design artifacts, AUTOSAR has explicitly defined how these process steps are carried out.
Meanwhile, thanks to advanced tool support, the AUTOSAR standard is being successfully utilized in many areas of product development. The challenge for these projects, however, is to ensure consistent data exchange between tools without loss of design information. Particular attention is being paid to the interaction of architecture and Model-Based Design tools for development of individual software components along with functional software with both top-down and bottom-up design approaches supported.
Using the examples of MATLAB, Simulink, and Embedded Coder by MathWorks, as well as the AUTOSAR authoring tool VSA from Mentor Graphics, we will demonstrate the interaction and interoperability of architecture- and Model-Based Design environments in five steps under consideration of the mechanisms defined by AUTOSAR.
For the complete article, including how software tools are vital in the exchange of AUTOSAR artifacts between OEMs and their suppliers, click here, courtesy of EE Times Europe. (Be aware: Complimentary registration may be required to view this feature in the September 2911 digital edition.)
Receive a weekly highlights update delivered directly to your inbox by signing up for our weekly automotive electronics newsletter here