inspection
A formal, systematic method for finding errors in
specifications and code by visual examination of development work
products by subject matter experts other than the authors.
The objectives of the inspection process are:
- Uncover and document defects, omissions and
inconsistencies in a work product
- Verify that work products satisfy their specifications
- Verify that work products conform to applicable standards
- Ensure the technical correctness and consistency of
project deliverables
- Quantitative analysis of the quality of a work product
through collection of defect statistics
- Improve software development processes through
application of causal
analysis techniques
Note that the objectives of an inspection contrast with those
of a walkthrough in the following areas:
- Inspections are confined to defect detection and do not
include discussions on how the work product may be
improved as in a walkthrough
- Only completed work products are inspected. Walkthroughs
may be conducted at any time in the development of a
deliverable
- It is not mandatory that the author be present in an
inspection while walkthroughs are commonly conducted by
authors
- All parties to an inspection must have thoroughly
reviewed the work product prior to the inspection. A
walkthrough may be used to educate participants on the
content of the work product.
Contrast with: walkthrough
See also: causal
analysis