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
  • Example: Airbags
  • 1. Functional Requirements
  • 2. Safety & Redundancy
  • 3. Regulatory & Compliance Requirements
  • 4. Hardware & Material Constraints
  • 5. Integration with Other Systems
  • 6. Software & Communication Protocols
  • 7. Testing & Validation
  1. ./pulse
  2. Lean Sourcing
  3. LeanRM

Why so many Requirements?

The number of requirements for a new vehicle product line varies widely based on complexity, regulatory needs, and market positioning. However, here are some general figures:

  1. Traditional Internal Combustion Engine (ICE) Vehicles

    • 50,000 to 100,000+ requirements

    • Covers mechanical, electrical, regulatory, and safety aspects

  2. Electric Vehicles (EVs)

    • 100,000 to 200,000+ requirements

    • Includes additional software, battery management, thermal management, and high-voltage safety

  3. Software-Defined Vehicles (SDVs)

    • 200,000 to 500,000+ requirements

    • Higher complexity due to over-the-air (OTA) updates, software-based functionalities, connectivity, ADAS, and autonomy

  4. Highly Automated / Autonomous Vehicles

    • 500,000 to 1,000,000+ requirements

    • Integrates AI-driven perception, sensor fusion, redundancy, fail-operational architectures, and extensive regulatory compliance

In modern vehicle development, 40-60% of requirements are software-related, and this share is increasing with SDVs. OEMs rely on requirement management tools (e.g., Polarion, DOORS, Codebeamer) to track and validate these requirements across product lines.

Example: Airbags

The Airbag sub-systems of a car can easily have 50,000-80,000 requirements associated with them. Here is why

1. Functional Requirements

  • Deployment Logic: When should the airbag deploy? (E.g., frontal impact > 25 km/h)

  • Multi-stage Deployment: Different force levels depending on crash severity.

  • Passenger Sensing: Detecting occupants (adult, child, empty seat).

  • Side Airbags & Curtain Airbags: Coordinated deployment in different crash scenarios.


2. Safety & Redundancy

  • Redundant Triggering Circuits: Prevent false positives/negatives.

  • Fail-Safe Mechanisms: System must self-diagnose failures.

  • Sensor Fusion: Integration with accelerometers, gyroscopes, and radar.


3. Regulatory & Compliance Requirements

  • FMVSS 208 (USA): Occupant crash protection standards.

  • UNECE R94/R95 (Europe): Frontal & lateral impact regulations.

  • China NCAP, Euro NCAP, IIHS: Different rating system compliance.


4. Hardware & Material Constraints

  • Inflator Chemistry: Must be stable under various temperatures.

  • Fabric Strength: Must resist wear and environmental degradation.

  • Connector Reliability: Must withstand vibration and corrosion.


5. Integration with Other Systems

  • Seatbelt Pretensioners: Airbag must coordinate with them.

  • ADAS (Advanced Driver Assistance Systems): Adjustments based on predicted impact.

  • Vehicle Architecture: Different requirements for SUVs vs. sedans.


6. Software & Communication Protocols

  • CAN Bus Messaging: Ensure proper timing of deployment signals.

  • OTA Updates: Requirements for software-based calibration.

  • Self-Diagnostics & Logging: Error codes, sensor failures, and remote monitoring.


7. Testing & Validation

  • Crash Test Scenarios: Dozens of crash speeds, angles, and occupant sizes.

  • Environmental Testing: Extreme heat/cold, humidity, aging simulation.

  • End-of-Line Testing: Every unit must pass factory quality control.


Why 80,000+ Requirements?

Each of these top-level requirements branches into hundreds of sub-requirements, covering:

  • Component-level details (e.g., inflator pressure curve specs).

  • Software constraints (e.g., real-time response deadlines).

  • Testing conditions (e.g., crash test dummies of different weights).

  • Country-specific compliance differences.

PreviousLeanRMNextSCM for SDVs

Last updated 4 months ago