Verification & validation (V&V) in software testing– what is the difference?
What is the difference between verification and validation in software testing?
Verification answers the question, “Did we build the right software?*” while validations addresses, “Did we build the software right?*”
Verification versus validation (V&V) – definitions & objectives
Verification in software testing – a definition
Verification is the process the project deliverable is evaluated in the development phase to find out whether it meets identified and approved requirement specifications
Validation in software testing – a definition
Validation is the process in which the project deliverable is evaluated at the end of the development life cycle to determine whether it meets the stakeholder expectations and requirements or not.
Software testing
In software testing both Validation and Verification are the parts of V model in which the development & testing activity is started based on the identified and confirmed requirement specifications. The verification process always comes before the validation process.
Verification versus validation (V&V) – actions and deliverables explained
Verification |
Validation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
References:
* Barry Boehm, Software Engineering Economics, 1981