Answer
# 1 |
"Verification" ensures the product is designed to deliver
all the functionalities to the customer. It 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" ensures that functionality, as defined in
requirements, is the intended behavior of the product;
validation typically involves actual testing and takes place
after verifications are completed. Validation takes place
during or at the end of the development process.
So to the BEST of my Knowledge, the difference between
Verification and Validation is:
1) Verification takes place before validation, and not vice
versa.
2) verification evaluates documents, plans, code,
requirements, and specifications. Validation, on the other
hand, evaluates the product itself.
3) 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.
4) 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.
|
| Jtatavarti |
Answer
# 4 |
Verification ensures the product is designed to deliver all
functionality to the customer; it typically involves
reviews and meetings to evaluate documents, plans, code,
requirements and specifications; this can be done with
checklists, issues lists, and walkthroughs and inspection
meetings.
Validation ensures that functionality, as defined in
requirements, is the intended behavior of the product;
validation typically involves actual testing and takes
place after verifications are completed.
|
| Hitesh T Patel |