The V-model connects the breakdown of requirements and design with the corresponding integration and evaluation work. Testing is considered while the system is being defined, rather than treated only as a final activity.
Typical Connections
•
User needs connect to validation of the delivered system in its intended use.
•
System requirements connect to system-level verification.
•
Architecture and interfaces connect to integration checks.
•
Component design connects to component-level tests.
The exact names and levels vary by organization. The useful part is traceability: each requirement should have an appropriate way to establish whether it has been met.
Verification and Validation
Verification checks compliance with specified requirements. Validation checks whether the system meets users’ needs in the intended environment. Passing component tests alone does not establish either the whole system’s behavior or its usefulness.
Things to Check
Review ambiguous requirements early and define observable acceptance criteria. A V-shaped diagram is not a guarantee of quality, and evidence may still require a design to change.
