Your shopping cart is empty!
The terms ‘Verification‘ and ‘Validation‘ are frequently used in the software testing world but the meaning of those terms are mostly vague and debatable. You will encounter (or have encountered) all kinds of usage and interpretations of those terms, and it is our humble attempt here to distinguish between them as clearly as possible.
It is entirely possible that a product passes when verified but fails when validated. This can happen when, say, a product is built as per the specifications but the specifications themselves fail to address the user’s needs.
An brief comparison between the both is as
1. Verification represents static testing techniques.
1. Validation represents dynamic testing techniques.
2. Verification ensures that the software documents comply with the organisations standards, it is static analysis technique.
2. Validation ensures that the software operates as planned in the requirements phase by executing it, running predefined test cases and measuring the output with expected results.
3. Verification answers the question “Is the Software build according to the specifications”.
3. Validation answers the question “Did we build the software fit for purpose and does it provides the solution to the problem”.