Scribd
Upload
55 views2 pages

What Is Verification?

Verification is a static process that evaluates software documents, design, code, and programs to determine if they meet requirements specified at the start of development. It uses methods like reviews and walkthroughs to check for errors. Validation is a dynamic process that evaluates the final software product through testing to ensure it meets customer expectations and requirements. Validation methods include testing the actual software. The key difference is that verification checks if the software meets its specifications, while validation checks if the right product was built by verifying it satisfies customer needs.

Uploaded by

maano
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
55 views2 pages

What Is Verification?

Verification is a static process that evaluates software documents, design, code, and programs to determine if they meet requirements specified at the start of development. It uses methods like reviews and walkthroughs to check for errors. Validation is a dynamic process that evaluates the final software product through testing to ensure it meets customer expectations and requirements. Validation methods include testing the actual software. The key difference is that verification checks if the software meets its specifications, while validation checks if the right product was built by verifying it satisfies customer needs.

Uploaded by

maano
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

What is Verification?

Definition : The process of evaluating software to determine whether the products of a given
development phase satisfy the conditions imposed at the start of that phase.
Verification is a static practice of verifying documents, design, code and program. It includes all
the activities associated with producing high quality software: inspection, design analysis and
specification analysis. It is a relatively objective process.
Verification will help to determine whether the software is of high quality, but it will not ensure
that the system is useful. Verification is concerned with whether the system is well-engineered
and error-free.
Methods of Verification : Static Testing
 Walkthrough
 Inspection
 Review

What is Validation?
Definition: The process of evaluating software during or at the end of the development process
to determine whether it satisfies specified requirements.
Validation is the process of evaluating the final product to check whether the software meets the
customer expectations and requirements. It is a dynamic mechanism of validating and testing the
actual product.
Methods of Validation : Dynamic Testing
 Testing
 End Users

Difference between Verification and Validation


The distinction between the two terms is largely to do with the role of specifications.
Validation is the process of checking whether the specification captures the customer’s
needs. “Did I build what I said I would?”
Verification is the process of checking that the software meets the specification. “Did I build
what I need?”
Verification Validation

1. Verification is a static practice of


1. Validation is a dynamic mechanism of
verifying documents, design, code and
validating and testing the actual product.
program.

2. It does not involve executing the code. 2. It always involves executing the code.

3. It is human based checking of 3. It is computer based execution of


documents and files. program.

4. Verification uses methods like 4. Validation uses methods like black box
inspections, reviews, walkthroughs, and (functional) testing, gray box testing, and
Desk-checking etc. white box (structural) testing etc.

5. Validation is to check whether software


5. Verification is to check whether the
meets the customer expectations and
software conforms to specifications.
requirements.

6. It can catch errors that validation cannot 6. It can catch errors that verification
catch. It is low level exercise. cannot catch. It is High Level Exercise.

7. Target is requirements specification,


7. Target is actual product-a unit, a module,
application and software architecture, high
a bent of integrated modules, and effective
level, complete design, and database
final product.
design etc.

8. Verification is done by QA team to


8. Validation is carried out with the
ensure that the software is as per the
involvement of testing team.
specifications in the SRS document.

9. It generally comes first-done before


9. It generally follows after verification.
validation.

You might also like