Verification & Validation

Software Testing Tutorial


[fblike]

Software Verification and Validation : Introduction

  • Software verification and validation are the two hands around which a software product is built. 
  • Software verification is a process which ensures that the product has been built according to the requirement and design specifications.

  • It means, “Are we building the System/Product right?”.

  • Software validation is a process which ensures that the product meets the user’s requirement and fulfills the need of user.
  • It means, “Are we building the right System/Product?”.

Verification and Validation : The Difference

 

This image describes the comparison between Verification and Validation in software testing.

Verification and Validation : The Differences

Software Verification and Validation : The V-Model

  • The V-Model is a systematic approach with the help of which verification and validation process can be carried out simultaneously, where the left arm of the model describes the software verification process and right arm describes the software validation process.

  • Since, we want to carry out the development(software verification) and testing(software validation) process in parallel, this model helps us to do the same in order to save time and reduce the cost.

 

The V Model : Verification & Validation

The V Model : Verification & Validation

 

Software Verification and Validation : Verification Methods

  1. Walk-through: Walk-through is an informal way of verification which is initiated by the author of software product to their colleagues in order to locate defect or any suggestion for improvements. Walk-through is an unplanned process .

  2. Review: Reviews are more formal than walk-through but less formal than inspection process. It is done to check the change in data and to determine whether the changes are correct or not.

  3. InspectionInspection is a most formal verification process. It is done in a software product  in which every individual line of code is checked in order to:

    • Locate the defects in software programs.

    • Confirmation of standardization.

    • Check for relevant requirement.