What is V & V? Difference between V & V...

Verification ensures the product –
is designed to deliver all functionality to the customer; it involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; and it can be done with checklists, issues lists, walkthroughs and inspection meetings.

Validation ensures –
that functionality, as defined in requirements, is the intended behavior of the product; and
validation typically involves actual testing and takes place after verifications are completed.

Verification
It takes place before validation, and not vice versa.
evaluates documents, plans, code, requirements, and specifications.
The inputs of verification are checklists, issues lists, walkthroughs and inspection meetings, reviews and meetings.
The output of verification is a nearly perfect set of documents, plans, specifications, and requirements document.

Validation
It evaluates the product itself.
The input of validation, is the actual testing of an actual product.
The output of validation, is a nearly perfect, actual product.

In short, Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements, and specifications. Validation, on the other hand, evaluates the product itself. The inputs of verification are checklists, issues lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation, on the other hand, is the actual testing of an actual product. The output of verification is a nearly perfect set of documents, plans, specifications, and requirements document. The output of validation, on the other hand, is a nearly perfect, actual product.