Pages

Saturday, August 20, 2011

Difference between Verification and Validation

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, 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.

Difference between Verification and Validation:

Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements, and specifications. Validation, on the other hand, evaluates the product itself. 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. 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.

2 comments:

  1. Verification can be considered similar to the quality and quantity checks which is performed during the assembly line of a product - design and development cycle in vlsi world. It involves both peripheral and internal functionality or properties testing; usually done by the development team themselves.more information

    ReplyDelete
  2. Review on documents are called Verfication (or) documents testing.
    validaton means combination of unit testing,intigration testing,sofware testing,acceptance testing,release testing and test changes in sofware(maintainance)

    ReplyDelete