A Review of Software Inspections

Adam Porter, Harvey Siy, Lawrence Votta

Research output: Contribution to journalArticle

26 Citations (Scopus)

Abstract

For two decades, software inspections have proven effective for detecting defects in software. We have reviewed the different ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost effectiveness of different methods. We detect a disturbing pattern in the evaluation of inspection methods. Although there is universal agreement on the effectiveness of software inspection, their economics are uncertain. Our examination of several empirical studies leads us to conclude that the benefits of inspections are often overstated and the costs (especially for large software development projects) are understated. Furthermore, some of the most influential studies establishing these costs and benefits are 20 years old now, which leads us to question their relevance to today's software development processes. Extensive work is needed to determine exactly how, why, and when software inspections work, and whether some defect detection techniques might be more cost effective than others. We ask some questions about measuring the effectiveness of software inspections and determining how much they really cost when their effect on the rest of the development process is considered. Finding answers to these questions will enable us to improve the efficiency of software development.

Original languageEnglish (US)
Pages (from-to)39-76
Number of pages38
JournalADVANCES IN COMPUTERS
Volume42
Issue numberC
DOIs
StatePublished - Dec 1 1996

Fingerprint

Inspection
Software engineering
Costs
Taxonomies
Cost effectiveness
Defects
Economics

ASJC Scopus subject areas

  • Computer Science(all)

Cite this

A Review of Software Inspections. / Porter, Adam; Siy, Harvey; Votta, Lawrence.

In: ADVANCES IN COMPUTERS, Vol. 42, No. C, 01.12.1996, p. 39-76.

Research output: Contribution to journalArticle

Porter, Adam ; Siy, Harvey ; Votta, Lawrence. / A Review of Software Inspections. In: ADVANCES IN COMPUTERS. 1996 ; Vol. 42, No. C. pp. 39-76.
@article{b97bd5c00cf94c38821b718179e696f7,
title = "A Review of Software Inspections",
abstract = "For two decades, software inspections have proven effective for detecting defects in software. We have reviewed the different ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost effectiveness of different methods. We detect a disturbing pattern in the evaluation of inspection methods. Although there is universal agreement on the effectiveness of software inspection, their economics are uncertain. Our examination of several empirical studies leads us to conclude that the benefits of inspections are often overstated and the costs (especially for large software development projects) are understated. Furthermore, some of the most influential studies establishing these costs and benefits are 20 years old now, which leads us to question their relevance to today's software development processes. Extensive work is needed to determine exactly how, why, and when software inspections work, and whether some defect detection techniques might be more cost effective than others. We ask some questions about measuring the effectiveness of software inspections and determining how much they really cost when their effect on the rest of the development process is considered. Finding answers to these questions will enable us to improve the efficiency of software development.",
author = "Adam Porter and Harvey Siy and Lawrence Votta",
year = "1996",
month = "12",
day = "1",
doi = "10.1016/S0065-2458(08)60484-2",
language = "English (US)",
volume = "42",
pages = "39--76",
journal = "Advances in Computers",
issn = "0065-2458",
publisher = "Academic Press Inc.",
number = "C",

}

TY - JOUR

T1 - A Review of Software Inspections

AU - Porter, Adam

AU - Siy, Harvey

AU - Votta, Lawrence

PY - 1996/12/1

Y1 - 1996/12/1

N2 - For two decades, software inspections have proven effective for detecting defects in software. We have reviewed the different ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost effectiveness of different methods. We detect a disturbing pattern in the evaluation of inspection methods. Although there is universal agreement on the effectiveness of software inspection, their economics are uncertain. Our examination of several empirical studies leads us to conclude that the benefits of inspections are often overstated and the costs (especially for large software development projects) are understated. Furthermore, some of the most influential studies establishing these costs and benefits are 20 years old now, which leads us to question their relevance to today's software development processes. Extensive work is needed to determine exactly how, why, and when software inspections work, and whether some defect detection techniques might be more cost effective than others. We ask some questions about measuring the effectiveness of software inspections and determining how much they really cost when their effect on the rest of the development process is considered. Finding answers to these questions will enable us to improve the efficiency of software development.

AB - For two decades, software inspections have proven effective for detecting defects in software. We have reviewed the different ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost effectiveness of different methods. We detect a disturbing pattern in the evaluation of inspection methods. Although there is universal agreement on the effectiveness of software inspection, their economics are uncertain. Our examination of several empirical studies leads us to conclude that the benefits of inspections are often overstated and the costs (especially for large software development projects) are understated. Furthermore, some of the most influential studies establishing these costs and benefits are 20 years old now, which leads us to question their relevance to today's software development processes. Extensive work is needed to determine exactly how, why, and when software inspections work, and whether some defect detection techniques might be more cost effective than others. We ask some questions about measuring the effectiveness of software inspections and determining how much they really cost when their effect on the rest of the development process is considered. Finding answers to these questions will enable us to improve the efficiency of software development.

UR - http://www.scopus.com/inward/record.url?scp=77956787802&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=77956787802&partnerID=8YFLogxK

U2 - 10.1016/S0065-2458(08)60484-2

DO - 10.1016/S0065-2458(08)60484-2

M3 - Article

AN - SCOPUS:77956787802

VL - 42

SP - 39

EP - 76

JO - Advances in Computers

JF - Advances in Computers

SN - 0065-2458

IS - C

ER -