MT - 39 - Verification and validation ( V &V ) or Static and dynamic testing

Used in software testing , validation and verification are two independent procedures that are used to check the product or any setup meets requirements and specifications or not.

Validation(Static testing):

Validation is the process of evaluating the final product to check whether the software meets the business needs. In simple words the test execution which we do in our day to day life are actually the validation activity which includes smoke testing, functional testing, regression testing, systems testing etc

Verification(Dynamic testing):

Verification is a process of evaluating the intermediary work products of a software development lifecycle to check if we are in the right track of creating the final product.


There are two aspects of V&V tasks

Confirms to requirements (Producer view of quality)
Fit for use (consumers view of quality)

Producer’s view of quality, in simpler terms means the developers perception of the final product.
Consumers view of quality means users perception of final product.
When we carry out the V&V tasks, we have to concentrate both of these view of quality.

Methods of Verification

1. Walkthrough
2. Inspection
3. Review

Methods of Validation

1. Different phases of testing
2. End Users


Difference : 

Verification	Validation
1. Verification is a static practice of verifying documents, design, code and program. Its done without executing the actual code.	1. Validation is a dynamic mechanism of validating and testing the actual product. Its done with t he execution of the code.
2. To ensure that the product is being built according to the requirements and design specifications. In other words, to ensure that work products meet their specified requirements.	2. To ensure that the product actually meets the user’s needs, and that the specifications were correct in the first place. In other words, to demonstrate that the product fulfils its intended use when placed in its intended environment.
3. Its discussion based checking of documents , code , RTM and files.	3. It is actual testing of system through execution of program.
4. Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.	4. Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc.
5. Verification is to check whether the software conforms to specifications.It makes sure that the product is designed to deliver all functionality to the customer.	5. Validation is to check whether software meets the customer expectations and requirements.
6. Checks “Are we building the product right”?	6. Checks “Are we building the right product”?
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.

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.