Formal Inspection
Overview
Formal Inspection is a static testing type. A visual examination of the software product to detect and identify software anomalies, including errors and deviations from standards and specifications.
Formal Inspection
Inspection typically consists of 3-8 people, including a moderator, a reader, and a recorder to take notes. Inspections are peer examinations led by impartial facilitators trained in inspection techniques. Formal inspection of system development products is a very effective means of reducing errors in software development.
Inspections at each exit point. Key inspections to be carried out:
- Design Architecture
- Test Plan
- Test Cases
- Code
Goal
The goal is to remove errors, hence reducing rework costs. The result of postponing the inspection is usually a lengthening of the overall schedule and increased product cost.
Inspections are more formal than a walkthrough. A walkthrough is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required. It is also a static analysis technique in which a designer or programmer leads members of the development team and other interested parties through a Software product, and the participants ask questions and comment about possible errors, violations of the development standards, and other problems.
—
Software Testing Tutorials:
