By Topic

What makes inspections work?

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
A. Porter ; Dept. of Comput. Sci., Maryland Univ., MD, USA ; L. Votta

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

Published in:

IEEE Software  (Volume:14 ,  Issue: 6 )