Appendix C - Software Inspections
How to run and measure inspections
Learning Objectives
- Follow the inspection flow and roles
- Log defects and measure yields
- Use a quick checklist during meetings
Overview
Appendix C defines inspections: structured peer reviews with clear roles, logging, and follow-up to prevent defects early.
Inspection Process
- Entry check: artifact complete, standards available.
- Roles assigned; overview if needed.
- Readthrough and defect logging (INS/LOGD).
- Rework and optional reinspection.
- Record time, defects, yield.
Inspection Roles
| Role | Responsibility |
|---|---|
| Author | Provides artifact; answers questions |
| Moderator | Runs meeting, ensures process |
| Reader | Leads walkthrough |
| Recorder | Captures defects/time |
| Inspectors | Find defects; follow checklist |
Metrics & Yields
- Defects/KLOC or per page
- Yield = defects removed early / total found later
- Time per page; prep time vs. meeting time
Quick Checklist (Meeting Aid)
- Entry criteria met?
- Roles assigned?
- Defects logged with IDs?
- Action items captured?
- Metrics recorded?