By Topic

Investigating the effect of a second software inspection cycle. Cost-benefit data from a large-scale experiment on reinspection of a software requirements document

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

3 Author(s)
S. Biffl ; Inst. of Software Technol., Tech. Univ., Vienna, Austria ; M. Halling ; M. Kohle

The goal of software inspection is to identify defects and to measure the product and inspection process quality. Software development products that are suspected to contain a substantial number of defects after inspection may be subject to a second inspection cycle (re-inspection). So far, very few empirical results can be found on re-inspections. This paper reports on a controlled experiment that compares the effect of two inspection cycles. A software requirements document was re-inspected by 31 teams, after defects found during the initial inspection had been removed. We present data on the effectiveness, efficiency, net gain and return-on-investment from a second inspection cycle, and compare these results with data from the initial inspection. Models in the literature suggest decision criteria with regard to when to re-inspect, based on assumptions on the relationships of variables between the two inspection cycles. With experimental data, we evaluate these assumptions and the correctness of their decision criteria. The results of the experiment strongly support considering re-inspection as an option to improve product quality

Published in:

Quality Software, 2000. Proceedings. First Asia-Pacific Conference on

Date of Conference: