The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.02 - March/April (1994 vol.11)
pp: 59-69
ABSTRACT
<p>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.</p>
INDEX TERMS
software metrics; software reliability; inspection; project management; code inspection information; AT&T Bell Laboratories; metrics; software project managers; inspection process; total noncomment lines; source code; preparation rate; inspection rate; effort per fault; reinspections; defect-removal efficiency; software inspection
CITATION
Jack Barnard, Art Price, "Managing Code Inspection Information", IEEE Software, vol.11, no. 2, pp. 59-69, March/April 1994, doi:10.1109/52.268958
31 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool