This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion
January/February 2008 (vol. 25 no. 1)
pp. 88-90
ASCII Text
x 
 
Forrest Shull, Carolyn Seaman, "Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion," IEEE Software, vol. 25, no. 1, pp. 88-90, January/February, 2008.
 
 
BibTex
x
 
@article{ 10.1109/MS.2008.7,
author = {Forrest Shull and Carolyn Seaman},
title = {Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion},
journal ={IEEE Software},
volume = {25},
number = {1},
issn = {0740-7459},
year = {2008},
pages = {88-90},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.7},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion
IS - 1
SN - 0740-7459
SP88
EP90
EPD - 88-90
A1 - Forrest Shull,
A1 - Carolyn Seaman,
PY - 2008
KW - software inspections
VL - 25
JA - IEEE Software
ER -
 
Forrest Shull, Fraunhofer Center for Experimental Software Engineering
Carolyn Seaman, University of Maryland, Baltimore County and Fraunhofer Center for Experimental Software Engineering
Inspections are among the most mature and best-studied practices in software engineering. People, especially when they bring objective viewpoints, are among the most powerful tools for finding problems in systems. The inspection process mitigates the fact that, although the human brain is powerful, relying on it has drawbacks. It's interesting to look at how such a practice catches on among busy professionals.

1. M.E. Fagan, "Design and Code Inspection to Reduce Errors in Program Development," IBM Systems J., vol. 15, no. 3, 1976, pp. 182–211.
2. M.E. Fagan, "Advances in Software Inspections," IEEE Trans. Software Eng., vol. 12, no. 7, 1986, pp. 744–751.
3. G.W. Russell, "Experience with Inspection in Ultra Large-Scale Developments," IEEE Software, vol. 8, no. 1, 1991, pp. 25–31.
4. L. Harjumaa, I. Tervonen, and P. Vuorio, "Using Software Inspection as a Catalyst for SPI in a Small Company," Proc. 5th Int'l Conf. Product-Focused Software Process Improvement, LNCS 3009, Springer, 2004, pp. 62–75.
5. C. Denger and F. Shull, "A Practical Approach for Quality-Driven Inspections," IEEE Software, vol. 24, no. 2, 2007, pp. 79–86.
6. M. Conrad et al., "Using Model and Code Reviews in Model-Based Development of ECU Software," Proc. SAE World Congress, SAE doc. #2006-01-1240, 2006.
7. P. Jalote and M. Haragopal, "Overcoming the NAH Syndrome for Inspection Deployment," Proc. 20th Int'l Conf. Software Eng., IEEE CS Press, 1998, pp. 371–378.
8. C. Ebert et al, "Improving Validation Activities in a Global Software Development," Proc. 23rd Int'l Conf. Software Eng., IEEE CS Press, 2001, pp. 545–554.
9. R. Grady and T. Van Slack, "Key Lessons in Achieving Widespread Inspection Use," IEEE Software, vol. 11, no. 4, 1994, pp. 46–57.

Index Terms:
software inspections
Citation:
Forrest Shull, Carolyn Seaman, "Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion," IEEE Software, vol. 25, no. 1, pp. 88-90, Jan.-Feb. 2008, doi:10.1109/MS.2008.7
Usage of this product signifies your acceptance of the Terms of Use.