Managing code inspection information

Author

Barnard, Jack ; Price, Art

Author_Institution

AT&T Bell Labs., Denver, CO, USA

Volume

11

Issue

2

fYear

1994

fDate

3/1/1994 12:00:00 AM

Firstpage

59

Lastpage

69

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

inspection; project management; software metrics; software reliability; AT&T Bell Laboratories; code inspection information; defect-removal efficiency; effort per fault; inspection process; inspection rate; metrics; preparation rate; reinspections; software inspection; software project managers; source code; total noncomment lines; Fault detection; Information management; Inspection; Software measurement; Software testing;

fLanguage

English

Journal_Title

Software, IEEE

Publisher

ieee

ISSN

0740-7459

Type

jour

DOI

10.1109/52.268958

Filename

268958