Verification - process describes whether the outputs are according to inputs or not
The process of evaluating work-products (not the actual final product) of a development phase to determine whether they meet the specified requirements for that phase.
- It makes sure that the product is designed to deliver all functionality to the customer.
- Verification is done at the starting of the development process. It includes reviews and meetings, walkthroughs, inspection, etc. to evaluate documents, plans, code, requirements and specifications.
- It answers the questions like: Am I building the product right?
- Am I accessing the data right (in the right place; in the right way).
- It is a Low level activity
- Performed during development on key artifacts, like walkthroughs, reviews and inspections, mentor feedback, training, checklists and standards.
- Demonstration of consistency, completeness, and correctness of the software at each stage and between each stage of the development life cycle.
Methods of Verification
1. Walkthrough
2. Inspection
3. Review
Validation - process describes whether the software is accepted by the user or not.
The process of evaluating software during or at the end of the development process to determine whether it satisfies specified business requirements.
- Determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs.
- Validation is done at the end of the development process and takes place after verifications are completed.
- It answers the question like: Am I building the right product?
- Am I accessing the right data (in terms of the data required to satisfy the requirement).
- It is a High level activity.
- Performed after a work product is produced against established criteria ensuring that the product integrates correctly into the environment.
- Determination of correctness of the final software product by a development project with respect to the user needs and requirements.
Methods of Validation
1. Testing
2. End Users
No.
|
VERIFICATION
|
VALIDATION
|
|---|---|---|
| 1 | Verification is a static practice of verifying documents, design, code and program. | Validation is a dynamic mechanism of validating and testing the actual product. |
| 2 | It does not involve executing the code. | It always involves executing the code. |
| 3 | It is human based checking of documents and files. | It is computer based execution of program. |
| 4 | Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. | 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. | 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. | 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. | Target is actual product-a unit, a module, a bent of integrated modules, and effective final product. |
| 8 | Verification is done by development team to provide that the software is as per the specifications in the SRS document. | Validation is carried out with the involvement of client and testing team. |
| 9 | It, generally, comes first-done before validation. | It generally follows after verification. |
| 10 | Question Are we building the product right? | Question Are we building the right product? |
| 11 | Evaluation Items Plans, Requirement Specs, Design Specs, Code, Test Cases | Evaluation Items The actual product/software. |
| 12 | Activities Reviews Walkthroughs Inspections | Activities Testing |
Hi....!!! I am a part time blogger.Here i shared some information which are collected from web.I hope you'll enjoy reading. Thank you!
ConversionConversion EmoticonEmoticon