Monday, January 16, 2012

Difference Between Verification And Validation Explain It With Example?

Verification and Validation example is also given just below to this table. 

             Verification
             Validation
1. Verification is a static practice of verifying documents, design, code and program.
1. Validation is a dynamic mechanism of validating and testing the actual product.
2. It does not involve executing the code.
2. It always involves executing the code.
3. It is human based checking of documents and files.
3. It is computer based execution of program.
4. Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.
4. Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc.
5. Verification is to check whether the software conforms to specifications.
5. Validation is to check whether software meets the customer expectations and requirements.
6. It can catch errors that validation cannot catch. It is low level exercise.
6. It can catch errors that verification cannot catch. It is High Level Exercise.
7. Target is requirements specification, application and software architecture, high level, complete design, and database design etc.
7. Target is actual product-a unit, a module, a bent of integrated modules, and effective final product.
8. Verification is done by QA team to ensure that the software is as per the specifications in the SRS document.
8. Validation is carried out with the involvement of testing team.
9. It generally comes first-done before validation.
9. It generally follows after verification.

Example of verification and validation are explained below:-


Suppose we have the specifications related to the project than by checking that specifications without executing to see whether the specifications are up to the mark or not is what we have done in verification.

Similarly Validation of the software is done to make sure that the software always meets the requirements of the customer by executing the specifications of the project and product. 

Note that the customer and end users are concerned in validation of the software. 

It is also crucial to differentiate between end users, and customers. Considering example, if you are developing a library monitoring system, the librarian is the client and the person who issue the books, collect fines etc. are comes under the category of the end users.

Techniques or Methods of Verification and Validation


Methods of Verification

1. Walkthrough

2. Inspection
3. Review
Methods of Validation
1. Testing

2. End Users

Conclusion:

1) Verification and Validation both are necessary and complementary.
2) Both of them provides its own sets of Error Filters.
3) Each of them has its own way of detect out the errors left in the software.

Lots of people use verification and validation interchangeably but both have different meanings. 

Verification process describes whether the outputs are according to inputs or not, and 

Validation  process describes whether the software is accepted by the user or not.

Note:
If you remain have any problem regarding Difference between Verification and Validation than you can definitely discuss with me in comments section below. 

40 comments:

  1. It gives clear idea thank u

    ReplyDelete
  2. Excellent explanation... thanks a lot...:)

    ReplyDelete
  3. good one..!! It really Helps..!!! Thanks..!

    ReplyDelete
  4. At what stage of software engineering verification and validation takes place??

    ReplyDelete
    Replies
    1. Hi Nilkamal,
      I think verification is done at initial stages
      And validation at end of s/w launch to customer
      In b/w finding n fixing bugs it is not termed as validated

      Delete
  5. overall article is good, but the sentence "Verification process describes whether the outputs are according to inputs or not" is weak

    ReplyDelete
  6. It is also crucial to differentiate between end users and client/customer. more information

    ReplyDelete
  7. e dir moi 1 example de verification e validation

    ReplyDelete
  8. very useful information!!

    ReplyDelete
  9. Very useful... Thanks a lot :)

    ReplyDelete
  10. Could you please describe what 1. Walkthrough

    2. Inspection
    3. Review are... Thanks a lot for the useful info

    ReplyDelete
  11. Clearly described with example... :)

    ReplyDelete
  12. Got clear idea on these topics.

    thank you..

    ReplyDelete
  13. The information which you have provided is very good. It is very useful who is looking for basic interview questions.

    ReplyDelete
  14. can u relate verification and validation with STLC(software testing life cycle)..

    ReplyDelete
  15. can you please share some example? like considering some project specifications & what might be the verification/validation for that project.

    ReplyDelete
  16. Thank you so much for such a great article

    ReplyDelete
  17. This site helps a lot to learn.thank you.

    ReplyDelete
  18. THNAKS GOOD INFO

    ReplyDelete
  19. Is it right to say that Testing begins after coding in SDLC? or Please tell me when does Testing starts in testing life cycle?

    ReplyDelete
  20. Super Pots.. !!!

    ReplyDelete
  21. Sir how we can do verification and validation of core web engineering ? any published paper or help ?

    ReplyDelete
  22. I am preparing for the interview. I found this perfect site. Excellent information. Verification is "Are we building the home right?", Validation is "Are we building the right home?"

    Thanks.

    ReplyDelete
  23. thanks a ton.................

    ReplyDelete
  24. Rakesh has Explained very well.
    Just want to conclude it ,Verification is a Static testing and Validation is a Dynamic testing.

    ReplyDelete
  25. 4.Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.

    4. Validation uses methods like black box (functional) testing, gray box testing, and white box (structural) testing etc.

    Incorrect! Verification uses methods like Test, Analysis, Demonstration & Inspection and uses black box (functional testing), gray and white box testing. "Testing" is synonymous with "Verification". Validation involves running Monte Carlos and statistical analysis to validate that simulation performance with the actual fielded system that the simulation is supposed to represent.

    ReplyDelete
  26. thank u so much for this information

    ReplyDelete
  27. Is combination of Verification and Validation is called testing?

    ReplyDelete
  28. Verification and Validation both are independent type of testing. Obviously, If we look both of these activities as a whole, we can also call it testing.

    ReplyDelete