In simpler terms, verification answers the question "have we built the product right", i.e. is it correct and free from errors, does it meet the specification whereas
Validation asks the question" is this the right product?" have the users got what they wanted. To help you remember this use the following:
Verification
Is it error free, does it do what was specified?
Validation
Is it valid, is this what you really, really want?
Verification requires several types of reviews, including requirements reviews, design reviews,code walkthroughs, code inspections, and test reviews. The system user should be involved in these reviews to find defects before they are built into the system.E.g are Shown in the given below table.
Validation is accomplished simply by executing a real-life function (if you wanted to check to see if your mechanic had fixed the starter on your car, you’d try to start the car).Examples of validation are shown
Saturday, 9 January 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment