V-model
The V-model is a software development lifecycle model that pairs each development activity with a corresponding testing activity, emphasizing early test planning and verification.
“A sequential software development lifecycle model describing a one-for-one relationship between major phases of software development from business requirements specification to delivery, and corresponding test levels from acceptance testing to component testing.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is V-model?
Testing activities are planned alongside development phases to improve quality and ensure systematic verification and validation.
Parallel planning: Testing is planned during development.
Traceability: Each development phase has a corresponding test level.
Structured lifecycle: Supports disciplined software engineering.
Real World Example
A regulated product team is preparing a release where V-model appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats V-model as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between V-model and similar ideas.
The page becomes useful in practice because V-model is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes V-model in the context of ISTQB terminology?
Question 2
A tester needs to explain V-model to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned V-model. Test your understanding with topic-specific questions in our Mock Exams.