Mumbai University > Information Technology > Sem 8 > Software Testing and Quality Assurance

Marks: 10 Marks

Year: May 2016

i) Verification

1. Verification is a kind of activity that helps in evaluating a software system by determining whether the product of a given development phase satisfies the requirements established before the start of that phase.

2. Activities that check the correctness of a development phase are called verification activities.

3. Verification activities aim at confirming that one is "building the product correctly".

4. Verification activities are performed on interim products by applying mostly static analysis techniques, such as inspection, walkthrough, and reviews and using standards and checklists.

5. Verification is the process of evaluating products whether they meet the specified requirements.

6. It ensures that the software system meets all the functionality and mostly done by developers.

7. It is human based checking of documents and files and does not involve executing the code.

8. Verification is done by QA team to ensure that the software is as per the specifications in the SRS document.

9. Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.

10. Cost of errors caught in Verification is less than errors found in Validation.The need for verification is to ensure that the product is being built according to the requirements and design specifications. In other words, to ensure that work products meet their specified requirements.

ii) Validation:

1.Validation activities help us in confirming that a product meets its intended use.

2.Validation activities aim at confirming that a product meets its customer's expectation.

3.In other words, validation activities focus on the final product, which is extensively tested from the customer point of view.

4.It aims at confirming that one is "building the correct product".

5.For example, it is performed towards the end of system development to determine if the entire system meets the customer's needs and expectations.

6.Validation is the process of evaluating software at the end of the development process to determine whether software meets the customer expectations and requirements.

1. It ensures that the functionalities meet the intended behavior and mostly done by testers.

2. It is computer based execution of program and always involves executing the code.

3. Validation is carried out with the involvement of testing team.

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

5. Cost of errors caught in Validation is more than errors found in Verification.

6. The need for validation is to ensure that the product actually meets the user’s needs, and that the specifications were correct in the first place. In other words, to demonstrate that the product fulfills its intended use when placed in its intended environment.