V-model
Definition
The V-model is a software development framework that extends waterfall by pairing each development phase on the left side of the 'V' with a corresponding testing and verification phase on the right side, ensuring every requirement is traceable to a test.
The V-model emerged in the 1980s and 1990s in German and European defense and aerospace software development contexts, the term 'V-Modell' comes from the German government's IT project standard. It became influential in safety-critical software development where traceability between requirements and tests is mandatory.
The V shape represents the relationship between development and testing phases. Reading down the left side of the V: user requirements → system requirements → architecture design → module design → coding. Reading up the right side: unit testing ← integration testing ← system testing ← acceptance testing. Each level on the right corresponds to a level on the left, acceptance testing verifies user requirements, system testing verifies system requirements, and so on.
The key improvement over pure waterfall is that test planning begins at the same time as requirements, you don't wait until coding is done to think about how to test. This means test cases are written against requirements when they're specified, creating explicit traceability.
The V-model is used in automotive (ISO 26262 functional safety), aerospace (DO-178C for avionics software), medical devices (IEC 62304), and defense. Outside regulated industries, agile and DevOps approaches have replaced it for most product development.
V-model diagrams appear on whiteboards during project planning and architecture sessions in regulated industries. The 'V' shape is unmistakable, boarding in a whiteboard photo immediately signals the regulatory context.
Examples
- Medical device: user needs → system requirements → software architecture → detailed design → code, then unit test → integration test → system test → clinical validation
- Automotive ADAS: vehicle requirements → system design → software design → module code, verified by module tests → integration tests → system tests → vehicle tests
- Defense avionics: DO-178C-compliant V-model with formal reviews at each phase gate and traceability matrix linking every requirement to test cases
- Industrial control system: process requirements → safety requirements → PLC logic design → ladder code, paired with SIL verification at each level
Related terms
Snap a v-model. Ship its actions.
BoardSnap turns any whiteboard, including this one, into a summary and action plan.