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
  • Key Goals and Focus
  • What SDV201 Will Cover
  • Project Timeline
  • Get Involved

SDV201

PreviousIncumbent OEMs vs EV Start-upsNext./pulse

Last updated 5 months ago

The SDV201 project is the successor to SDV101, offering a more advanced, hands-on exploration of Software-Defined Vehicles (SDVs). While SDV101 provides a general introduction to SDVs aimed at a broad audience, including non-technical readers, SDV201 targets individuals with a deeper interest in the technical aspects of SDV development.

Key Goals and Focus

The primary objective of SDV201 is to deliver a practical, project-based learning experience. Participants will engage in real-world SDV development tasks, requiring:

  • Basic Programming Skills: Some experience in coding (e.g., Python, C++) will be helpful.

  • Embedded Hardware Knowledge: Familiarity with basic hardware components and their integration.

What SDV201 Will Cover

SDV201 will provide a deep dive into the digital.auto Playground and the corresponding E/E Starter Kit developed by digital.auto. Participants will gain hands-on experience working with both hardware and software components of an SDV system.

Project Timeline

The SDV201 project is currently work in progress, with the goal of releasing a solid beta version by summer 2025. Content development, course structure, and supporting materials are actively being created by the digital.auto community.

Get Involved

If you are interested in contributing to SDV201 or want to stay informed about project updates, connect with us through our LinkedIn channel: šŸ‘‰

Subscribe to the channel for the latest news and updates regarding the SDV201 project.

Digital.auto LinkedIn
Page cover image