Dealing with automotive software complexity with virtual prototyping - Part 2: An AUTOSAR use case
Victor Reyes, Synopsys Inc.
embedded.com (May 25, 2014)
In 2003, OEM manufacturers and Tier 1 automotive suppliers founded the AUTOSAR3 consortium to address the technical and business challenges they all faced with the increase in software development and test costs. The premise of that conversation is the principle that guides the AUTOSAR alliance today: Cooperate on standards, compete on implementation. The net goal of the consortium is to drive the change in software development, moving from proprietary solutions to standardized, productized and predictable software products.
AUTOSAR focuses on three main areas: software architecture, methodology and application interfaces. In this document we will only discuss on the software architecture part.
The goal of the AUTOSAR software architecture [3] is to provide a clear separation from the application (differentiation) and the infrastructure (commodity) domain.
![]() |
E-mail This Article | ![]() |
![]() |
Printer-Friendly Page |
|
Synopsys, Inc. Hot IP
Related Articles
- Dealing with automotive software complexity with virtual prototyping - Part 1: Virtual HIL development basics
- Dealing with automotive software complexity with virtual prototyping - Part 3: Embedded software testing
- Automotive System & Software Development Challenges - Part 2
- How to make virtual prototyping better than designing with hardware: Part 2
- Virtual Prototyping Environment for Multi-core SoC Hardware and Software Development
New Articles
- How NoC architecture solves MCU design challenges
- Automating Hardware-Software Consistency in Complex SoCs
- Beyond Limits: Unleashing the 10.7 Gbps LPDDR5X Subsystem
- How to Design Secure SoCs: Essential Security Features for Digital Designers
- System level on-chip monitoring and analytics with Tessent Embedded Analytics