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. Implementing the Shift Left

De-Coupled, Multi-Speed System Evolution

PreviousPhysical test systemNextContinuous Homologation

Last updated 6 months ago

Coming back to our goal of establishing a shift-left approach in combination with multi-speed development, we have now looked at the evolution along the V-Model. In this context, it is important to understand that testing evolves independently north and south of the Vehicle Hardware Abstraction Layer (VHAL). North of the VHAL, algorithms and software are developed and validated without direct dependency on the underlying hardware, enabling rapid prototyping and iterative testing. Applications here are agnostic to whether they interact with lightweight simulations, virtual ECUs, or physical test hardware, supporting agile, continuous improvement.

South of the VHAL, the test environments progress in complexity – starting with basic models, moving to high-fidelity simulations, virtual ECUs, and ultimately hardware-in-the-loop (HIL) and physical systems. This layered approach ensures embedded systems, often safety-critical (ASIL), are rigorously validated under realistic conditions. By decoupling development speeds, engineers can iterate quickly on software north of the VHAL while gradually increasing hardware realism south of the VHAL. This multi-speed strategy accelerates testing cycles and supports robust, end-to-end validation across the V-Model.

The multi-speed, shift-left approach combined with the VHAL separation offers several key benefits:

  1. Accelerated Development: Algorithms north of the VHAL iterate quickly, decoupled from hardware readiness.

  2. Scalable Testing: Enables testing progression from lightweight virtual prototypes to realistic hardware environments.

  3. Cost Efficiency: Reduces dependency on physical prototypes early in development.

  4. Enhanced Flexibility: Software remains agnostic to test environments, fostering reusability across simulations and hardware.

  5. Improved Validation: Gradual complexity south of the VHAL ensures robust, safety-critical validation without stalling software development.

These benefits are enabled by the de-coupled, multi-speed system evolution approach.