DocumentCode
1345417
Title
What makes inspections work?
Author
Porter, Adam ; Votta, Lawrence
Author_Institution
Dept. of Comput. Sci., Maryland Univ., MD, USA
Volume
14
Issue
6
fYear
1997
Firstpage
99
Lastpage
102
Abstract
Software inspections are considered a cheap and effective way to detect and remove defects from software. Still, many people believe that the process can be improved and have thus proposed alternative methods. We reviewed many of these proposals and detected a disturbing pattern: too often competing methods are based on conflicting arguments. The existence of these competing views indicates a serious problem: we have yet to identify the fundamental drivers of inspection costs and benefits. We first built a taxonomy of the potential drivers of inspection costs and benefits. Then we conducted a family of experiments to evaluate their effects. We chose effort and interval, measured as calendar time to completion, as our primary measures of cost. Defects discovered per thousand lines of code served as our primary measure of inspection benefits
Keywords
cost-benefit analysis; inspection; program debugging; program testing; software cost estimation; software quality; cost benefit analysis; cost measures; experiments; inspection effort; inspection interval; program debugging; software defect detection; software inspections; software quality; time; Bibliographies; Calendars; Collaborative software; Collaborative work; Costs; Inspection; Proposals; Radio access networks; Taxonomy; Time measurement;
fLanguage
English
Journal_Title
Software, IEEE
Publisher
ieee
ISSN
0740-7459
Type
jour
DOI
10.1109/52.636690
Filename
636690
Link To Document