Skip to main content

Difference Between Verification And Validation 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. 

Comments

Anonymous said…
It gives clear idea thank u
Anonymous said…
Excellent explanation... thanks a lot...:)
Anonymous said…
good one..!! It really Helps..!!! Thanks..!
Unknown said…
At what stage of software engineering verification and validation takes place??
Anonymous said…
overall article is good, but the sentence "Verification process describes whether the outputs are according to inputs or not" is weak
Bikram said…
It is also crucial to differentiate between end users and client/customer. more information
Unknown said…
e dir moi 1 example de verification e validation
Anonymous said…
very useful information!!
Unknown said…
very useful and superb
Anonymous said…
Very useful... Thanks a lot :)
Anonymous said…
Could you please describe what 1. Walkthrough

2. Inspection
3. Review are... Thanks a lot for the useful info
Anonymous said…
Clearly described with example... :)
Unknown said…
Got clear idea on these topics.

thank you..
JobsOnClick said…
The information which you have provided is very good. It is very useful who is looking for basic interview questions.
Unknown said…
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
Unknown said…
now I got the clarification.
Unknown said…
can u relate verification and validation with STLC(software testing life cycle)..
Anonymous said…
can you please share some example? like considering some project specifications & what might be the verification/validation for that project.
Unknown said…
Thank you so much for such a great article
Anonymous said…
This site helps a lot to learn.thank you.
Anonymous said…
THNAKS GOOD INFO
Mukta said…
Is it right to say that Testing begins after coding in SDLC? or Please tell me when does Testing starts in testing life cycle?
Anonymous said…
Super Pots.. !!!
Unknown said…
Good Explanation.
Unknown said…
Sir how we can do verification and validation of core web engineering ? any published paper or help ?
Anonymous said…
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.
Rajkumar said…
Its very clear, thank u
chitra said…
thanks a ton.................
Unknown said…
Rakesh has Explained very well.
Just want to conclude it ,Verification is a Static testing and Validation is a Dynamic testing.
Anonymous said…
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.
kalaimathy said…
thank u so much for this information
Unknown said…
superb .. very nice!!!
Anonymous said…
Is combination of Verification and Validation is called testing?
Anonymous said…
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.
Unknown said…
I really like examining and also following ones write-up when i locate them incredibly beneficial and also fascinating. That write-up is usually just as beneficial along with fascinating. Thanks for facts you already been putting on doing your web site such an fascinating.Interview Preparation
Anonymous said…
Nice Explanation... Very Useful.
Unknown said…

Verification and Validation are the activities performed to improve the quality and reliability of the system and assure the product satisfies the customer needs.
Verification assures the product of each development phase meets their respective requirements.
Validation assures the final product meets the client requirements.



software validation
Anonymous said…
Good one.
Anonymous said…
Thank you very much it will helpful to us
Anonymous said…
Hello,
A check verification service provides businesses or individuals with either the ability to check the validity of the actual check or draft being presented, or the ability to verify the history of the account holder, or both.Click here
Unknown said…
thnks for the details.good work.
Anonymous said…
Very good!!!!!!!!!!!!!!!
Unknown said…
Thanks for sharing such a nice information.

Thanks again
report writing help
Unknown said…
Very informative..... thanks for providing..........
Unknown said…
Very informative.... thanks for providing.
Unknown said…
why we are saying SRS as black box document???
Anonymous said…
yes i m also agree with you...
SUJITH said…
Very helpful.....
Unknown said…
what systems need more v&V?
Orakzai said…
Informative :)
Unknown said…
thx..it helped a lot :)
Unknown said…
its superb...thanks
Anonymous said…
thanks
Anonymous said…
great explanation
I'm_Interested said…
can you please tell me which activity is tough and difficult in both of them?
Anonymous said…
give more example for validation of software product
Unknown said…
When we are performing verification and validation in Google account
Unknown said…
Give me one real time examples
Anonymous said…
thanks for the good explanation...even wiki is not stating the differences clearly!

Popular posts from this blog

Endurance Testing with Example, Meaning and Definition

Endurance Testing is a type of Performance Testing which is usually used to determine how much a system can sustain the continuous expected load. During the period of Endurance Testing memory utilization is always monitored to detect any potential leaks. In short we can say that judging/studying the memory leak of a server under the period of stability is known as Endurance Testing . Due to its judgment and study on memory leak that is the reason why Endurance Testing is also known by the name Soak Testing . As you know in Endurance Testing memory utilization is monitored so it very important for us to know about memory leak means what it is all about. When memory allocated to objects are not being freed by the system/application than definitely the memory leak occurs. Endurance Testing Example – Real Time Below is given the real time example of Endurance Testing and hope after seen these real time example your knowledge on Endurance Testing should definitely b...

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...