But before we preceding towards Exact Difference between Verification and Validation it is very important for us to first take a warm look at Verification and Validation means what it is all about.
Verification is the system of confirming that software meets
its specification. Verification involves reviews to evaluate documents, plans,
code, software requirements, and specifications. It can be fulfill with
checklists to involve, issues lists, and walkthroughs by people, and inspection
meetings. Verification= “Are we
building the project right”.
Validation is the system of confirming that software meets
the user’s requirements. Validation typically involves absolute testing and
takes place after verification is completed.
Validation means to executing the software to see it meets the client
requirements or not. Validation= “Are
we building the right Project/product”.
Difference between
Verification and Validation with Example – Tabular Form
Verification
|
Validation
|
1. Verification is a static practice of
verifying documents, design and code/program.
|
1.
Validation is a dynamic mechanism of validating / 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 / files.
|
3. It is computer based execution of
program.
|
4. Target is requirements specification,
application and software architecture, high level, complete design, and database design etc.
|
4. Target is actual product-a unit, a
module, a bent of integrated modules, and effective final product.
|
5.
Verification uses methods like inspections/review, walkthroughs, and Desk-checking etc.
|
5.
Validation uses methods like black box (functional) testing, gray box
testing, and white box (structural) testing etc.
|
6. Verification is done by development
team to provide that the software is as per the specifications in the SRS
document.
|
6. Validation is carried out with the
involvement of client.
|
7.
It can catch errors that validation cannot catch. It is low level exercise.
|
7. It can catch errors that verification
cannot catch. It is High Level Exercise.
|
8.
Verification is to check whether the software conforms to
specifications.
|
8. Validation is
to check whether software meets the customer expectations.
|
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
specification related to the project than by checking that specifications are
up to the blot or not is what we have done in verification.
Similarly Validation of the
software is done to make safe that the software always meets the requirements
of the customer. Note that the customer/end users are concerned in validation
of the software. It is also exigent to differentiate between end users and
client/customer. 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/Methods of Verification
1. Walkthrough
2. Inspection
3. Review
Techniques/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.
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 is 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. And you can also give feedback for further improving
the post Difference between Verification
and Validation.
