Catalog
concept#Governance#Software Engineering#Delivery#Quality Assurance

V-Model

Phase-oriented development model for managing development and acceptance processes with integrated testing and quality focus.

The V-Model is a phase-oriented development model for planning, implementing and accepting technical systems.
Established
Medium

Classification

  • Medium
  • Organizational
  • Organizational
  • Intermediate

Technical context

Configuration management tools (e.g., Git, SVN)Test management tools (e.g., Jenkins, TestRail)Requirements and issue trackers (e.g., JIRA)

Principles & goals

Clear phase separation with defined handover pointsEarly and continuous verification across the lifecycleDocumentation as basis for acceptance and compliance
Build
Enterprise, Domain

Use cases & scenarios

Compromises

  • Delays due to late defect discovery
  • Excessive bureaucracy if not adapted to project size
  • Misunderstandings from unclear acceptance criteria
  • Scale rather than adopt blindly: tailor the model to project size
  • Integrate testing early into planning and design
  • Define clear, verifiable acceptance criteria

I/O & resources

  • Requirements specification
  • Project plan and resource allocation
  • Regulatory mandates and standards
  • Acceptance protocols and test reports
  • Release documentation and release packages
  • Traceable verification matrix

Description

The V-Model is a phase-oriented development model for planning, implementing and accepting technical systems. It emphasizes defined roles, comprehensive documentation and integrated verification/validation along a V-shaped lifecycle. Implementation requires coordinated processes, clear decision gates and governance for complex software and systems projects.

✔

  • Clear responsibilities and traceability
  • Well-suited for regulated and safety-critical projects
  • Structured linkage between development and testing

✖

  • Low flexibility for late requirement changes
  • High documentation overhead
  • Relatively heavyweight for small agile teams

  • Defect find rate per phase

    Number of defects found relative to phase; measures early defect detection.

  • Number of acceptance deviations

    Number of deviations from requirements discovered at acceptance.

  • Documentation effort hours

    Hours spent creating and maintaining required artifacts.

Use in public IT procurements

Municipal procurement projects use the V-Model to manage and accept complex deliveries.

Product development in medical technology

Medical device manufacturers use the V-Model for traceable testing and regulatory documentation.

Verification of embedded vehicle software

Automotive suppliers apply the model to align software and system tests.

1

Analyze project size and adapt the V-Model

2

Define roles, milestones and acceptance criteria

3

Establish verification and test activities per phase

⚠️ Technical debt & bottlenecks

  • Unmaintained verification artifacts hinder later changes
  • Outdated documents lead to inconsistencies
  • Rigid process setup blocks modernization efforts
Documentation overheadLate defect detectionRole clarification
  • Small product team imposes rigid V-Model and loses velocity
  • Lack of adaptation to agile delivery cycles causes conflicts
  • Only documentation is produced while tests remain superficial
  • Believing the V-Model eliminates all risks
  • Late involvement of test owners
  • Insufficient scaling to project scope
Project experience with phase-oriented processesAbility to create test and verification plansKnowledge of regulatory requirements (if relevant)
Regulatory requirements and demonstrabilitySafety and quality objectivesNeed for clear acceptance and handover points
  • • Requires defined roles and processes
  • • Dependence on stable requirements
  • • Not every project type is equally suitable