Describe to me the difference between validation and verification.


Answer posted by Radhika on 2005-05-24 08:29:43: Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements and specifications. Validation evaluates the product itself. The input of verification are checklists, issue lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation is the actual testing of an actual product. The output of verification is a nearly perfect set of documents, plans, specifications and requirements
  • Interview Candidate
  • 43
  • 8408

Showing Answers 1 - 43 of 43 Answers

Radhika

  • May 24th, 2005
 

Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements and specifications. Validation evaluates the product itself. The input of verification are checklists, issue lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation is the actual testing of an actual product. The output of verification is a nearly perfect set of documents, plans, specifications and requirements

Amith

  • Jun 19th, 2005
 

Verification: is done to ensure that it meets the specifications. 
Validation: is done to ensure that it meets the customer requirements.

  Was this answer useful?  Yes

choudary

  • Jul 5th, 2005
 

Vefication: Checks consistency of the application with the i/p 
Validation:Checks Consistency of the aplication with the User Requirements. 
 
as told by the radhika Verification takes place before the validation.  
 
veification done on all the documents produced during development, and on plans. 
i/p for verification:  
1 checklists 
2.issue lists 
3.walkthroughs 
4.inspections 
5.reviews and meetings 
 
Validation is actual testing 
i/p for validation: 
1.test cases based on user requirements. 
2.test data. 
etc; 

  Was this answer useful?  Yes

tinu

  • Jul 6th, 2005
 

Verification : Are we building the product right. 
 
Validation : Are we building the right product. 
 
Verfication comes after the validation.

C.Chitra Naidu

  • Jul 15th, 2005
 

Verification is examination of process and validation is execution of process.

Andrews Wilson

  • Jul 19th, 2005
 

Verification is nothing but the Static Testing and Validation is nothing but the Dynamic Testing

  Was this answer useful?  Yes

Kalpana Naidu

  • Aug 2nd, 2005
 

Verification : Typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications. This can be done with checklists,issues lists, walk-throughs and inspection meetings. 
 
Validation : Typically involves actual testing and takes place after verifications are completed.

  Was this answer useful?  Yes

giri

  • Aug 14th, 2005
 

verification is a process to define pre-define activity i.e.,( before testing process starts, check whether all relavent documents are prepared and ensure that standard which we create to meet the requirement) to prepare a application. 
 
validation: its a process to test the apllication and deliver error free application

  Was this answer useful?  Yes

sreeram

  • Sep 22nd, 2005
 

Hi Radhika,u gave an suitable answerf or above question. i apperciate u.ThanksSriramRadhika Wrote:Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements and specifications. Validation evaluates the product itself. The input of verification are checklists, issue lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation is the actual testing of an actual product. The output of verification is a nearly perfect set of documents, plans, specifications and requirements

  Was this answer useful?  Yes

Aniyan Remo

  • Feb 17th, 2006
 

Verification: To check the application with respect to software requirement documents (S/wRS, Design Documents)

Validation: To check whether the application meets customer requirements and expectations or not.

  Was this answer useful?  Yes

Bijay Kumar from MIT

  • Aug 22nd, 2006
 

Verifications refers to the set of activities that ensure that software correctly implements a specific function.

While  Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements.

  Was this answer useful?  Yes

sunilkumarnanda

  • Sep 15th, 2006
 

Validation: The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

Verification: The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

  Was this answer useful?  Yes

Kunju

  • Mar 16th, 2007
 

you are wrong. Validation comes after verification

  Was this answer useful?  Yes

Barham Ahlawat

  • Mar 26th, 2007
 

Validation: Are we building the right product(what customer's desired)?

Verification: Are we building the product right(using correct approach to to attain customer's specifications)?

Validation starts after completion of Verification, however vice-versa is not true.

  Was this answer useful?  Yes

kishore

  • Apr 26th, 2007
 

Example:
              There is a one full glass of milk is ready
verification :*It desires how much sugar is added
                    *how much millilitres of milk is added
                    *how much water is included in that milk
                   
validation   :It describes about
                   taste of milk is sweet or sour or salty
                      

  Was this answer useful?  Yes

Pawan Kumar

  • Jul 1st, 2007
 

Verfication: ofcourse this is the process before validation. It means to check whether a given software is having all the features as written in the specification document. say I am building a MP3 player, so features may be like play, pause, forward, reverse. So if all the four features are there then my verfication is complete.

Validation: validation is to check whether those features work as supposed to work. as in above given example whether Play is working correctly. when I press reverse whether song reverses??? so in nut shell to check whether features are working correctly.

I hope I m clear...
Regards,
Pawan

  Was this answer useful?  Yes

sweetlee

  • Aug 9th, 2007
 

Verification: Ensure that product IS BEING BUILT as per specification
Validation: Ensure that product HAS BEEN BUILT as per specification

Verification: Development
Validation: Testing

Consequently
Verification: Quality Assurance
Validation: Quality Control

  Was this answer useful?  Yes

shivak141

  • Oct 23rd, 2007
 

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

  Was this answer useful?  Yes

kurtz182

  • Dec 29th, 2009
 

Here are some easy ways to remember the difference between verification and validation:

First you verify what a customer wants,
then you validate whether or not you have delivered it. 

Verification is all about process, whereas
Validation is all about product. 

Verification is all about the customer, whereas
Validation is all about the product.
 
Verification is about "doing the right thing," while
Validation is about "doing the thing right."

The input of verification is communication with clients and/or customers to determine what they want.  The input of validation is the actual product.

The output of verification are requirements, specifications, and plans.  The output of validation is a product that has been tested to ensure the requirements, specifications and plans have been met.



  Was this answer useful?  Yes

kurtz182

  • Dec 29th, 2009
 

Here are some easy ways to remember the difference between verification and validation:

First you verify what a customer wants,
then you validate whether or not you have delivered it.
 

Verification is all about process, whereas
Validation is all about product.
 

Verification is all about the customer, whereas
Validation is all about the product.
 
Verification is about "doing the right thing," while
Validation is about "doing the thing right."

The input of verification is communication with clients and/or customers to determine what they want.  The input of validation is the actual product.

The output of verification are requirements, specifications, and plans.  The output of validation is a product that has been tested to ensure the requirements, specifications and plans have been met.

  Was this answer useful?  Yes

mail2vass

  • Jan 17th, 2011
 

verification:it is a process of verifying are we developing the right system or not that means , checking the srs , brs documents. and verification does not involve in code execution.


Validation:it involves in code execution, and it is followed  by unit, integ, and system testing

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions