| Definition |
The process of evaluating work-products (not the actual final product) of a development phase to determine whether they meet the specified requirements for that phase. |
The process of evaluating software during or at the end of the development process to determine whether it satisfies specified business requirements. |
| Objective |
To ensure that the product is being built according to the requirements and design specifications.,In other words, to ensure that work products meet their specified requirements. |
To ensure that the product actually meets the user’s needs, and that the specifications were correct in the first place.,In other words, to demonstrate that the product fulfils its intended use when placed in its intended environment. |
| Question |
Are we building the product right? |
Are we building the right product? |
| Evaluation Items |
Plans, Requirement Specs, Design Specs, Code, Test Cases |
The actual product/software. |
| Execution of code |
Execution of code is not comes under Verification |
Execution of code is comes under Validation |
| Cost of Errors |
Cost of errors caught in Verification,is less than errors found in Validation. |
Cost of errors caught in Validation is more than errors found in Verification. |
| Method |
It is basically manually checking the of documents and files like requirement specifications etc. |
It is basically checking of developed program based on the requirement specifications documents & files |
| When Carried Out |
Verification is carried out before the Validation. |
Validation activity is carried out just after the Verification. |
| Process |
Verification process explains whether the outputs are according to inputs or not. |
Validation process describes whether the software is accepted by the user or not. |
| Activities |
Reviews Walkthroughs Inspections |
White box testing Black box testing |
and 2 others joined a min ago.
teamques10
★ 68k