Difference between Verification and Validation

Verification and Validation are the basic ingredients of Software Quality Assurance (SQA) activities.

“Verification” checks whether we are building the right system, and
“Validation” checks whether we are building the system right.

Verification Strategies

Verification Strategies comprise of the following:

1. Requirements Review.
2. Design Review.
3. Code Walkthrough.
4. Code Inspections.

Validation Strategies

Validation Strategies comprise of the following:

1. Unit Testing.
2. Integration Testing.
3. System Testing.
4. Performance Testing.
5. Alpha Testing.
6. User Acceptance Testing (UAT).
7. Installation Testing.
8. Beta Testing.

Now lets see the Verification Strategies in detail:



Validation Strategies in detail:





When Testing should occur?

Testing can and should occur throughout the phases of a project.

Requirements Phase

* Determine the test strategy.
* Determine adequacy of requirements.
* Generate functional test conditions.

Design Phase

* Determine consistency of design with requirements.
* Determine adequacy of design.
* Generate structural and functional test conditions.

Program (Build) Phase

* Determine consistency with design.
* Determine adequacy of implementation.
* Generate structural and functional test conditions for programs/units.

Test Phase

* Determine adequacy of the test plan.
* Test application system.

Installation Phase

* Place tested system into production.

Maintenance Phase

* Modify and retest.