Thursday, 1 March 2012

Verification Vs Validation

Verification and Validation are independent procedures that are used together for checking that a product, service or system meets requirements and specifications and validation is performed by a third party.

Verification: 
  • It represents whether we are building the product right.
  • The review of interim wok steps and interim deliverable 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 selection functions in the correct manner.
  • It represents whether we are accessing the data right in the right place, in the right way.
  • Verification is a low level activity.
  • This process is performed during development on key artifacts, like walk through, reviews and inspections, mentoring feedback, checklists, training and standards.
  • It demonstrates the consistency, completeness and correctness of the system at each stage and between each stage of development life cycle of the system.
Validation:
  • It represents where we are developing the right product.
  • Used in determining if the software complies with the requirements and performs functions for which it is intended to meets the organization's goals and user requirements.
  • Validation is traditional and performed at the end of the project.
  • It represents whether we are acceding the right data in terms of the data required to satisfy the requirement.
  • Validation is a high level activity.
  • Validation is performed after a software is produced against the well established criteria ensuring that the product integrates correctly into the environment.
  • Mainly performed to determine the correctness of the final software product by a development project with respect to the requirements.

0 comments:

Post a Comment

 
Back To Top