Since 2003, some of the world’s largest Automotive OEMs have joined the AUTOSAR global development partnership with an objective to establish open and standardized software architecture for Automotive electronic control units (ECUs).

Today, the automotive industry is being disrupted by OEMs, Tier-1s, tool vendors, semiconductor suppliers, and integrators are making significant technological investments in ECUs, Zone Control Units (ZCUs), Domain Control Units (DCUs), Vehicle Central Computing Units (VCCUs), and Collaborative Cognitive Control Units (CCCUs). Some of the possibilities enabled by Sasken in realizing AUTOSAR are:

  • Enabling OEMs and Tier-1s to decouple vehicle functionality and features
  • Modularization of the hardware and software architecture needs
  • Helping partners remain profitable by enabling them to monetize the hardware, software and system integration solutions, services, and support
  • Simplifying audits, standards compliance, and quality
  • Creating newer business models in mobility
Trends Implications Challenges Sasken is Solving

Increase in adoption of AUTOSAR based architecture to reduce costs and time to market

Need to move to AUTOSAR based modular architecture for ECUs

Selection of AUTOSAR stack and components

Emergence of Adaptive AUTOSAR in Body Electronics domain

Migrate event driven ECUs architecture to Adaptive AUTOSAR architecture

Transformation of ECU architectures with non-critical features

Consolidation of ECUs to lower cost, simplifying OTA updates, and reducing power consumption and overall vehicle weight

Introduction of ECUs, DCUs, ZCUs, Gateways, Vehicle Central Computing Units (VCCUs) collaborating as cognitive control units with high degree of configurability and re-use

Virtual ECU development emulating peripherals

Emergence of new in-vehicle communication technologies

Need to implement CAN FD, SOME/IP, DDS, RESTful, IPC communication

Selecting right technology choice for inter ECU communications

New use cases in Body Electronics domain

Reducing Body Control module load and limited to critical functions

Using AI and Data Analytics to support new use cases, variant handling, and partial networking

Increase in Safety and Security concerns

Separation of critical and non-critical functionalities

AUTOSAR Conformance, Functional Safety as per Development Interface Agreement and Cyber Security Compliance

Stress on improving test coverage

Need to automate model-based development and testing

Finalizing test acceptance criteria



  • SW-C & RTE/SAL Design Methods
  • BSW/ECAL/MCAL Layers
  • CDD/Tooling/FOTA/OS/ V2X/E2E Activities
  • Performance, Timing, Statics and Dynamics
  • ISO 26262 Functional Safety
  • ICC1-ICC3 AUTOSAR Migration

Adaptive AUTOSAR

  • Application and Non-Platform services
  • Sensor Integration and Fusion
  • Back-end Infrastructure Integration and Fusion
  • AI/ML/DL/ IoT Training, Annotation, etc.
  • Action/Path Planning and Automation of Controls
  • ISO 21448 Functional Safety/SOTIF (safety of the intended functionality)
  • ADAS 1- 3 HAD 3+ - 5 based Adaptive AUTOSAR Migration

Platform Independent

  • Requirements Elicitation and Work Teardown
  • Bootloader/Reprogramming Primary Boot Loader, Secondary Boot Loader, Flash Boot Loader
  • Diagnostics Unified Diagnostic services/Keyword protocol/On-board diagnostics/Diagnostic over internet protocol
  • Automotive Cyber - Security Activities
  • Intra/Inter ECU COM, Domain High Performance Computing Gateways



Click to Enlarge

Adaptive AUTOSAR


Click to Enlarge


  • 15+ years of Automotive platform experience
  • Extensive experience in different domains of Automotive ECU software development such as Body Electronics, Telematics, ADAS, Infotainment, Instrument Cluster, Automotive Safety System, etc.
  • End-to-end development and delivery experience in multiple production programs on Automotive Body Electronics features such as Climate Control Module, Remote Keyless Entry, Remote Parking, etc.
  • Extensive experience in enabling Cognitive Content to the ECUs by connecting to the Cloud and making the necessary AI-based decisions utilizing Adaptive AUTOSAR platform
  • Sasken is a CMMI Dev V1.3 ML3, ISO/IEC 27001:2013 company and Sasken’s Quality Management System is compliant to TL9000, Functional Safety ISO 26262, and Automotive SPICE v2.5 (HIS model) framework



Testing of automotive components i.e., its verification and validation...

The goal of AUTOSAR is to not only introduce standardization in the de...

Growth of Data Science in Vehicles In recent times, the need for comfo...

Hardware and Software architecture in vehicles in recent decades Since...