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 D: Implementation Strategies
  3. Hardware vs Software Engineering

Agile V-Model, anybody?

PreviousThe Traditional V-Model in Automotive DevelopmentNextKey: Loosely Coupled, Automated Development Pipelines

Last updated 6 months ago

In the era of software-defined vehicles, OEMs are aiming to decouple mechanical, electrical/electronic (E/E), and digital (software and AI) workstreams to enable multi-speed development. As shown in the diagram, this decoupling ensures that each stream operates at its own optimal pace. The digital workstreams must support rapid iteration cycles, often measured in hours or days, enabling frequent updates, feature improvements, and testing. In contrast, E/E workstreams require a medium-term focus, typically spanning weeks, to ensure robust system integration and validation. Finally, the mechanical workstreams follow a long-term development cadence measured in months, driven by extensive physical testing, safety requirements, and production timelines.

To achieve this multi-speed approach, OEMs must establish clearly defined technical and organizational interfaces. On the technical side, key enablers include loose coupling between the layers of development, supported by hardware abstraction layers (HAL) and vehicle hardware abstraction layers (VHAL). This abstraction allows software and digital innovation to advance independently of hardware constraints. The concept of "Shift North" further supports this, enabling non-safety-critical software functions to reside in higher-level compute environments where rapid changes can occur without impacting lower-level systems.

Organizationally, this decoupling requires well-defined workflows, tools, and responsibilities across teams. By creating interfaces that align development priorities and testing processes, OEMs ensure seamless collaboration while maintaining the integrity of long-term physical systems and fast-moving digital innovation.

Additionally, this approach aligns with the Shift Left strategy, which emphasizes early-stage digital validation through simulation, virtualization, and continuous testing. This minimizes costly late-stage errors and ensures that the digital, E/E, and mechanical streams can efficiently converge during system integration, verification, and production.

Ultimately, this multi-speed, decoupled development approach provides OEMs with the agility to innovate quickly in the digital space while maintaining the reliability and safety of the physical vehicle systems.