> For the complete documentation index, see [llms.txt](https://www.sdv.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.sdv.guide/sdv101/part-d-implementation-strategies/hardware-vs-software-engineering/agile-v-model-anybody.md).
# Agile V-Model, anybody?
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.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://www.sdv.guide/sdv101/part-d-implementation-strategies/hardware-vs-software-engineering/agile-v-model-anybody.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.