Why AUTOSAR is Necessary for Realizing SDV 

The limits of conventional development, and the future opened up by standardization, reuse, and automation

The shift toward SDV, where the center of vehicle value moves to software, is accelerating, and automotive software development is reaching a major turning point in both scale and complexity.。

As the limits of conventional methods surface toward realizing SDV, from explosive code growth, to feature expansion dependent on adding ECUs, to individual development per vehicle model or ECU, one of the leading answers to these challenges is the industry standard AUTOSAR.

This document explains in detail the role and significance of AUTOSAR in supporting SDV development, along with key points for adoption and use.

• Challenges in software development toward realizing SDV
  ・What is SDV (Software Defined Vehicle)? Redefining vehicle value
  ・The limits of conventional (non-AUTOSAR) automotive software development
  ・Summary so far and requirements for a software platform
• Overview of AUTOSAR and its role in realizing SDV
  ・What is AUTOSAR
  ・Overview of AUTOSAR Classic Platform
  ・Overview of AUTOSAR Adaptive Platform
  ・The role AUTOSAR plays in realizing SDV:
  　－① Supporting division-of-labor development needed in the SDV era
  　－② Promoting a shift toward a development structure resilient to functional changes
  　－③ Providing a robust, highly extensible architectural foundation
  　－④ Enabling safe OTA and long-term maintenance
  　－⑤ Driving organizational development that can scale with SDV project size
  ・Challenges and countermeasures for AUTOSAR adoption
• eSOL's solutions supporting AUTOSAR adoption and development
• Closing: Summary of this document