|
Explain different types of Verification.Verification is static type of s/w testing. It means code is not executed. The product is evaluated by going through the code. Types of verification are:
i. Walkthrough
ii. Inspection
iii. Reviews
Walkthroughs are informal, initiated by the author of the s/w product to a colleague for assistance in locating defects or suggestions for improvements. They are usually unplanned. Author explains the product; colleague comes out with observations and author notes down relevant points and takes corrective actions.
Inspection is a thorough word-by-word checking of a software product with the intention of:
- Locating defects
- Confirming traceability of relevant requirements
- Checking for conformance to relevant standards and conventions
Inspections are more formal than walkthroughs. It involves 5 major roles:
- Author: person who originally created the work product.
- Moderator: Person responsible to ensure the discussions proceed on the productive lines.
- Reader: Person responsible for reading aloud small logical units of the work product
- Recorder: Person who records/documents all the defects that arise from the inspection team.
- Inspector: All of the inspection team members who analyze and detect the defects within the work product.
Review is a subsequent examination of a product for the purpose of monitoring earlier changes. It is a process in which one or more persons check the changed documents or data to determine if the changes are correct. It is also an analysis undertaken at a fixed point in time to determine the degree to which stated objectives have been reached.
There are four levels of verification:
1. Component Testing: Verifying the design implementation for one software element like unit / module or a group of software elements
2. Integration Testing: Testing with orderly progression which involves the integration of various software and / or hardware elements together and tested. It continuous until the complete system has been integrated.
3. System Testing: A type of testing which tests integrated software and hardware system verification whether the system meets the specified requirements.
4. Acceptance Testing: A testing process that determines whether a system satisfies the acceptance criterion and for enabling the customer for determining whether or not to accept the system.
Division of verfication can also be understood as:
- Inspection: Typical walkthroughs, software reviews, technical reviews, and formal inspections.
- Analysis: It is about estimation of execution times and estimation of system resources.
- Testing: Verification phase is about white box testing. Techniques include statement coverage, condition coverage, and decision coverage.
- Demonstration: It is about black box testing. Techniques include error guessing, boundary-value analysis, and equivalence partitioning.
|
