Difference between Verification and Validation in Software Testing

What is the difference between Validation & Verification in Software Testing ?

No.	VERIFICATION	VALIDATION
1	Verification is a static practice of verifying documents, design, code and program.	Validation is a dynamic mechanism of validating and testing the actual product.
2	It does not involve executing the code.	It always involves executing the code.
3	It is human based checking of documents and files.	It is computer based execution of program.
4	Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.	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.	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.	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.	Target is actual product-a unit, a module, a bent of integrated modules, and effective final product.
8	Verification is done by development team to provide that the software is as per the specifications in the SRS document.	Validation is carried out with the involvement of client and testing team.
9	It, generally, comes first-done before validation.	It generally follows after verification.
10	Question Are we building the product right?	Question Are we building the right product?
11	Evaluation Items Plans, Requirement Specs, Design Specs, Code, Test Cases	Evaluation Items The actual product/software.
12	Activities Reviews Walkthroughs Inspections	Activities Testing