VERIFICATION & VALIDATION
Verification is the process of confirming that software meets its specification. It involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings..
Validation is the process of confirming that it meets the user’s requirements. Validation typically involves actual testing and takes place after verifications are completed.
For Example: - The Hubble space telescope was launched into the orbit around the earth, and it uses the large mirror to magnify the objects. Extreme precision and accuracy was the major concern for the construction of the mirror, but actually testing the mirror was not feasible. Therefore, the only means to check it was to carefully measure all its attributes and compare the measurements with the specifications.
After the measurements, as soon as it was launched, the images it returned was out of focus. The reason for this was improper manufacturing of the mirror. This confirmed that the mirror met the specifications but not the requirements i.e. Verification was fine, but it was not validated. Therefore, the difference in Verification and Validation is:
Verification : Are we building the product right?
Validation : Are we building the right product?
Comments