Managing code inspection information
- 1 March 1994
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 11 (2) , 59-69
- https://doi.org/10.1109/52.268958
Abstract
Inspection data is difficult to gather and interpret. At AT&T Bell Laboratories, the authors have defined nine key metrics that software project managers can use to plan, monitor, and improve inspections. Graphs of these metrics expose problems early and can help managers evaluate the inspection process itself. The nine metrics are: total noncomment lines of source code inspected in thousands (KLOC); average lines of code inspected; average preparation rate; average inspection rate; average effort per KLOC; average effort per fault detected; average faults detected per KLOC; percentage of reinspections; defect-removal efficiency.Keywords
This publication has 5 references indexed in Scilit:
- Lessons from three years of inspection data (software development)IEEE Software, 1993
- Evaluating the effectiveness of reliability-assurance techniquesJournal of Systems and Software, 1989
- The TAME project: towards improvement-oriented software environmentsIEEE Transactions on Software Engineering, 1988
- Estimating the Number of Faults in CodeIEEE Transactions on Software Engineering, 1984
- Design and code inspections to reduce errors in program developmentIBM Systems Journal, 1976