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

./pulse

The ./pulse driving the digital.auto [r]evolution

PreviousSDV201NextSDV Culture

Last updated 2 months ago

This is the beta version of the ./pulse framework. We are currently going through reviews and building up our ./pulse advisory board with international experts from the different domains.

In an era where the automotive industry is transforming into a software-driven ecosystem, the ./pulse framework introduces a pioneering multi-speed delivery model. This model is designed to bridge the gap between traditional automotive standards like ISO 26262 and ASPICE and the agile methodologies shaping modern software development, including SAFe, Scrum, and more.

The ./pulse framework ensures seamless integration of safety-critical systems with the iterative, fast-paced innovation cycles required for software-defined vehicles (SDVs). By harmonizing these two paradigms, the framework empowers organizations to adopt continuous delivery, real-time compliance, and collaborative engineering intelligence across mechanical, electrical/electronic (E/E), and digital domains.

The multi-speed delivery model of the ./pulse framework allows different value streams to progress at tailored speeds, aligning with their unique risk profiles and planning horizons. Mechanical systems, such as chassis and body components, move at a slower pace due to their reliance on physical prototyping, extensive validation, and regulatory requirements, often requiring months to complete development cycles. Electrical/Electronic (E/E) systems operate at a medium pace, balancing hardware and software integration, and progressing in weeks through iterative simulation and testing. Digital/software systems, such as infotainment and user experience features, are highly agile, moving in days or even hours, leveraging continuous deployment and rapid iteration.

The ./pulse framework is designed to harmonize traditional automotive development with agile principles, enabling faster, more efficient, and compliant delivery of complex systems. It introduces key elements to streamline requirements, systems engineering, and continuous improvement across mechanical, E/E, and software domains.

  • Lean Sourcing

    • LeanRM (Lean Requirement Management): Simplifies requirements management by focusing on value, reducing waste, and ensuring traceability at the speed of modern development.

    • Supply Chain Management for SDVs shifts from static, hardware-driven logistics to a modular, software-first ecosystem. It unbundles HW and SW, and enables agile contracts with fewer fixed requirements.

  • SDV Systems Engineering

    • LeanSE (Lean Systems Engineering): Integrates systems engineering into agile workflows, balancing cross-domain dependencies while ensuring safety and compliance.

    • Combined with SDVxMBSE, which enables co-existence of model- and code-centric development.

  • #DigitalFirst: Integrates Shift Left (early validation, simulation, and CI/CD) with Shift North (moving business logic out of deeply embedded environments and embracing cloud-native DevOps).

  • Loose coupling in SDVs enables agility through an API-first approach, allowing independent development while ensuring seamless integration. Freeze points are balancing flexibility with system-wide stability, accelerating innovation without breaking compatibility.

  • Intelligent Automation

    • CI/CD/CT Automation accelerates development through DevOps for SDVs and highly automated development pipelines

    • Engineering Intelligence provides AI-powered insights and automation

  • Continuous Homologation: Ensures dynamic compliance with regulations by integrating homologation processes directly into iterative workflows.

  • Build / Measure / Learn: Embeds feedback loops across all phases to optimize processes, identify bottlenecks, and continuously enhance product quality and delivery speed.

This framework empowers organizations to deliver safe, compliant, and innovative vehicles while adapting to the evolving demands of a software-driven world.

Page cover image