SDV Guide
digital.auto
  • Welcome
  • SDV101
    • Part A: Essentials
      • Smart Phone? No: Habitat on Wheels!
      • Basics: What is a Software-defined Vehicle
      • MHP: Expert Opinion
      • Challenges: What sets automotive software development apart?
      • SDV Domains and Two-Speed Delivery
    • Part B: Lessons Learned
      • Learnings from the Internet Folks
        • Innovation Management
        • Cloud Native Principles
          • DevOps and Continuous Delivery
          • Loose Coupling
            • Microservices & APIs
            • Containerization
            • Building Robust and Resilient Systems
      • Learnings from the Smart Phone Folks
    • Part C: Building Blocks
      • Foundation: E/E Architecture
        • Today`s E/E Architectures
        • Evolving Trends in E/E Architectur
        • Case Study: Rivian
      • Standards for Software-Defined Vehicles and E/E Architectures
      • Building Blocks of an SDV
        • Service-Oriented Architecture
          • The SOA Framework for SDVs
          • Container Runtimes
          • Vehicle APIs
          • Example: Real-World Application of SDV Concepts
          • Ensuring Functional Safety
          • Event Chains in Vehicle SOAs
          • Vehicle SOA Tech Stack
        • Over-the-Air Updates: The Backbone of Software-Defined Vehicles
        • Vehicle App Store: The Holy Grail of Software-Defined Vehicles
      • Summary: Building Blocks for Software-Defined Vehicles
    • Part D: Implementation Strategies
      • #DigitalFirst
      • Hardware vs Software Engineering
        • The Traditional V-Model in Automotive Development
        • Agile V-Model, anybody?
        • Key: Loosely Coupled, Automated Development Pipelines
        • The SDV Software Factory
      • Implementing the Shift Left
        • Simulation and Digital Prototyping
          • Early Validation: Cloud-based SDV Prototyping
          • Detailed Validation: SDVs and Simulation
        • Towards the Virtual Vehicle
          • Case Study: Multi-Supplier Collaboration on Virtual Platform
          • Long-Term Vision
        • Physical test system
        • De-Coupled, Multi-Speed System Evolution
        • Continuous Homologation
        • Summary and Outlook
      • Enterprise Topics
        • Variant Management
        • Engineering Intelligence
        • Enterprise Organization, Processes, and Architecture
        • Incumbent OEMs vs EV Start-ups
  • SDV201
  • ./pulse
    • SDV Culture
    • Lean Sourcing
      • LeanRM
        • Why so many Requirements?
      • SCM for SDVs
    • SDV Systems Engineering
      • LeanSE
      • SDVxMBSE
    • Digital First
    • Loose Coupling
      • API-first
      • Freeze Points
    • Automation and Engineering Intelligence
    • Continuous Homologation
    • Build / Measure / Learn
  • Glossary
Powered by GitBook

SDV Guide

  • Legal Notice
  • Disclaimer
  • Privacy Policy

(c) 2025 Dirk Slama

On this page
  1. SDV101
  2. Part C: Building Blocks

Summary: Building Blocks for Software-Defined Vehicles

PreviousVehicle App Store: The Holy Grail of Software-Defined VehiclesNextPart D: Implementation Strategies

Last updated 6 months ago

In Part C of SDV 101: Building Blocks, we explored the foundational elements enabling modern software-defined vehicles (SDVs). At the core of SDVs lies the evolution of E/E architectures, which transition from legacy designs into either domain-centralized architectures or cutting-edge zonal architectures with high-performance compute (HPC) capabilities. These advancements provide the structural backbone for SDVs.

Building on E/E architectures, SDVs implement service-oriented architectures (SOAs) that leverage container runtimes and vehicle APIs to ensure modularity, scalability, and integration with external ecosystems. Critical to this framework is the focus on functional safety, especially when operating in mixed-criticality environments, supported by modern tech stacks and industry standards such as AUTOSAR, COVESA VSS, and SOAFEE.

We also examined over-the-air (OTA) updates, a critical enabler for dynamic updates of software, AI models, and other digital artifacts, paving the way for continuous innovation. Finally, we looked at the concept of the Vehicle App Store, a transformative vision integrating secure environments, controlled API access, and cross-platform services to deliver new digital experiences to automotive customers.

Together, these building blocks represent the future of automotive innovation, where modular architectures, advanced software integration, and seamless updates redefine the vehicle experience.