Testing - Verification and Validation
- What is the difference between Verification and Validation?
- "Verification" involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications to confirm whether items, processes, services, or documents conform to specified requirements or not.
- This can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings.
- The purpose of verification is to determine whether the products of a given phase of the software development cycle fulfill the requirements established during the previous phase or not.
- "Validation" is the actual testing
- Validation is the determination of the correctness of the final program or software product produced from a development project with respect to the user needs and requirements.
- This involves actual testing of the product and takes place after verifications are completed.
- "Software Verification" raises the question, "Are we building the Product Right?"; that is, does the software conform to its specification.
- "Software Validation" raises the question, "Are we building the Right Product?"; that is, is the software doing what the user really requires.
