Here we are going to learn about Verification and Validation along with their advantages and differences:
Verification is an act of testing checking and auditing that makes sure that the product is designed to deliver all functionality to the customer.
- Verification is done at the starting of the development process. It includes reviews and meetings, walk-throughs, inspection, etc. to evaluate documents, plans, code, requirements and specifications.
- It answers the questions like: Am I building the product right?
- It is a Low level activity.
- Demonstration of consistency, completeness, and correctness of the software at each stage and between each stage of the development life cycle.
Advantages of Software Verification:
- Verification helps in lowering down the count of the defect in the later stages of development.
- Verifying the product at the starting phase of the development will help in understanding the product in a better way.
- It reduces the chances of failures in the software application or product.
- It helps in building the product as per the customer specifications and needs.
Fig: Software verification and validation
Validation is determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs.
- Validation is done at the end of the development process and takes place after verifications are completed.
- It answers the question like: Am I building the right product?
- It is a High level activity.
- Performed after a work product is produced against established criteria ensuring that the product integrates correctly into the environment.
- Determination of correctness of the final software product by a development project with respect to the user needs and requirements.
- Validation is basically done by the testers during the testing.
Advantages of Validation
- During verification if some defects are missed then during validation process it can be caught as failures.
- If during verification some specification is misunderstood and development had happened then during validation process while executing that functionality the difference between the actual result and expected result can be understood.
- Validation is done during testing like feature testing, integration testing, system testing, load testing, compatibility testing, stress testing, etc.
- Validation helps in building the right product as per the customer’s requirement and helps in satisfying their needs.
Differences between Verification and Validation
|1. Verification is a static practice of verifying documents, design, code and program.||1. Validation is a dynamic mechanism of validating and testing the actual product.|
|2. It does not involve executing the code.||2. It always involves executing the code.|
|3. It is human based checking of documents and files.||3. It is computer based execution of program.|
|4. Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.||4. Validation uses methods like black box testing, gray box testing, and white box testing.|
|5. Verification is to check whether the software conforms to specifications.||5. Validation is to check whether software meets the customer expectations and requirements.|
|6. It can catch errors that validation cannot catch. It is low level exercise.||6. It can catch errors that verification cannot catch. It is High Level Exercise.|
|7. Target is requirements specification, application and software architecture, high level, complete design, and database design etc.||7. Target is actual product-a unit, a module, a bent of integrated modules, and effective final product.|
|8. Verification is done by QA team to ensure that the software is as per the specifications in the SRS document.||8. Validation is carried out with the involvement of testing team.|
|9. It generally comes first-done before validation.||9. It generally follows after verification.|
96 total views, 0 views today