Pages

Saturday, March 20, 2010

Difference between Verification and Validation


Verification : Am I building the product right?
Validation : Am I building the right product?


Verification : The review of interim work steps and interim deliverables during a project to ensure they are acceptable. To determine if the system is consistent, adheres to standards, uses reliable techniques and prudent practices, and performs the selected functions in the correct manner.
Validation : Determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs. It is traditional and is performed at the end of the project.


Verification : Am I accessing the data right (in the right place; in the right way)?
Validation : Am I accessing the right data (in terms of the data required to satisfy the requirement)?


Verification : Low level activity
Validation : High level activity


Verification : Performed during development on key artifacts, like walkthroughs, reviews and inspections, mentor feedback, training, checklists and standards
Validation : Performed after a work product is produced against established criteria ensuring that the product integrates correctly into the environment


Verification : Demonstration of consistency, completeness, and correctness of the software at each stage and between each stage of the development life cycle.
Validation : Determination of correctness of the final software product by a development project with respect to the user needs and requirements.

No comments:

Post a Comment