Verification typically involves reviews and meetings to 
evaluate documents, plans, code, requirements, and 
specifications. This can be done with checklists, issues 
lists, walkthroughs, and inspection meetings. Validation 
typically involves actual testing and takes place after 
verifications are completed. The term 'IV & V' refers to 
Independent Verification and Validation.

verification:
*Beofore validation we have to do verification.
*comparing the customer document and our document to check 
wheather its correct or not.
*It won't talk about the functionality of the screen.
*wheather the screen is designed to the customer 
requirement or not.

Validation:
*Running the application and test the application
*Testing the s/w functionality wheather it is working or 
not.
*wheather the s/w is supporting the customer requirement or 
not.

verification and validation
     It is widely used model.  Here writing test plan’s and 
test cases starts at the initial phase i.e. during 
designing phase of SDLC and the test cases execution is 
done after coding.

       This is an up gradation of ‘V’ Model only, in this 
model at every stage a review is done. i.e the reason it is 
called as validation and verification Model.

umesh
tejasoft pvt ltd

verification:
--ARE WE BUILD PRODUCT RIGHT
--it is done by QA
--it is oriented towards preventive 
--it is done by walk throughs and inspections
--it is quality process , identifying the errors and 
suggesting improvements for the same
validation:
--ARE WE BUILD RIGHT PRODUCT
--it is done by qc
--it is oriented towards detection
--it is done by testing
--it is quality product ,identifying the errors 
and suggesting to improve

Verification:Are we build system Right
it is typically involves reiews,walkthroughs,inspections
it is done by QA

Validations: Are we build Right system 
it is typically involves actual testing and takes place 
after 
verifications are completed.
it is done by qc

Verification:  It is a process confirming that software 
meets its specification document. It basically involves 
walkthroughs, review and inspection. QA team members define 
the process as per the specification.

Validation:   It is a process confirming that software 
meets its user requirements. It basically involves testing. 
Validation technique done after verification process. QC 
team like testers they r going to implementing the process 
defined by QA team.

Verification is QA activity which ensures that the software 
product is designed to deliver all the functionality 
whatever mentioned in the requirement specification 
document. Reviews, walkthroughs and inspections are its 
techniques. It is a preventive phase.

Validation ensures that whatever mentioned in the 
requirement specification document should be the intended 
behavior of the software. Validation is actual testing. It 
is a corrective phase and is QC activity. 


Vimal 
Software Test Engineer

verification is the process of proving or demonstrating 
that the program correctly satisfies the specifications. 
“each step of the development process correctly echoes the 
intentions of the immediately preceding step.”

Validation: Validation is the process of evaluating 
software, at the end of the development process, to ensure 
compliance with requirements.
 that the verification community also uses the term 
validation to differentiate formal functional verification 
from extensive testing of a program against its 
specifications