Difference Between Verification and Validation

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 (Project Charters, BRDs, FSDs), plans, code, requirements and specifications; this can be done with checklists, issues lists, and walkthroughs and inspection meetings.

 Realize that verification is not just in the hands of QA.  It is a team effort.

Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verification is complete.

 Difference between Verification and Validation (Both are part of QA)

Verification Validation
Making sure that the requirements documents have captured the true essence of the product. Actual testing of software through test cases to make sure the product has been coded properly
Is done during the course of requirements, design and development.  This is done before code is developed. Is done after code has been completed and a product has been handed over to the QA team
Manual process Manual or can be automated.
Happens throughout the SDLC Happens only in the Acceptance Phase.
Makes sure that the correct product is being built Makes sure that the correct producthas been built.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s