How to avoid software inspection failure and achieve ongoing benefits

CrossTalk

Volumn 21, Issue 1, 2008, Pages 23-27

  Stewart, Roger ^a,b   Priven, Lew ^a,b  

^a Stewart Priven Group

^b Stewart Priven Group   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

INSPECTION FAILURE; SOFTWARE INSPECTIONS;

COMPUTER SOFTWARE; FAILURE ANALYSIS; PROBLEM SOLVING;

INSPECTION;

EID: 38349008582     PISSN: None     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (13)

1. NIST. "The Economic Impacts of Inadequate Infrastructure for Software Testing." NIST Planning Report 02-3. May 2002.
2. Bennett, Ted L., and Paul W. Wennberg. "Eliminating Eimbedded Software Defects Prior to Integration Test." CROSSTALK Dec. 2005.
3. McConnell, Steve. "Best Influences on Software Engineering Over Past 50 Years." IEEE Software Jan./Feb. 2000.
4. Wiegers, Karl. "The More Things Change." Better Software Oct. 2006.
5. Jones, Capers. "Interview." Computer Aid Inc. July 2005.
6. Radice, Ron. High Quality Low Cost Software Inspections. Andover, MA: Paradoxicon Publishing, 2002.
7. Weller, Ed. "Calculating the Economics of Inspections." StickyMinds Jan. 2002.
8. Priven, L.D "Managing the Programming Development Cycle." IBM Technical Report 21.463 Mar. 1972.
9. Fagan, Michael E. "Design and Code Inspections and Process Control in the Development of Programs." IBM Technical Report 21.572. Dec. 1974.
10. Priven, L. and F. Tsui. "Implementation of Quality Control in Software Development." AFIPS Conference Proceedings, 1976 National Computer Conference 45 (1976):443-449.
11. McGraw, Gary. Making Essential Software Work. Cigital, Inc. Mar. 2003 〈http://citigal.com/whitepapers〉.
12. Software Engineering Standards Committee of the IEEE Computer Society. "IEEE Standard for Software Reviews, Section 6. Inspections." IEEE Std. 1028-1997, 1997.
13. Humphrey, Watts. "Three Dimensions of Process Maturity." CROSSTALK Feb. 1998.