As a software tester, you have probably been asked at one time or another about whether you are doing “Verification” or “Validation”.
It is not always easy to explain the difference between these two terms. To make so, we have to ask the following questions:
- Validation: Are we building the right system?
- Verification: Are we building the system right?
In other words, validation is checking that the system will meet the customer’s needs while verification is checking whether the system is well-engineered, without error, etc.
Verification will help to determine whether the software is of high quality, but it will not ensure that the system is useful.
It is still confusing, isn’t it? OK, so let us get a little example to explain it:
You are testing an application. The system requirements say there are two fields with max Length of 64 characters and Save button. The Use case says that the User will fill in first and last name and save.
When checking the presence of the fields and the Save button, it is verification. When you follow the use case, it is validation.
CC : Welovebug.com
Here in after, you can find the definition of Validation and verification according to IEEE and ISO
IEEE standard in its 4th edition defines the two terms as follows:
- « Validation. The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers. Contrast with verification. »
- « Verification. The evaluation of whether or not a product, service, or system complies with a regulation, requirement, specification, or imposed condition. It is often an internal process. Contrast with validation. »
ISO 9001 standard defines them this way :
- Verification is the conformation that a product meets identified specifications.
- Validation is the conformation that a product appropriately meets its design function or the intended use
Author- Nizar BELKHATOUI