Analysis of the impact of reading technique and inspector capability on individual inspection performance

Proceedings - Asia-Pacific Software Engineering Conference, APSEC

Volumn 2000-January, Issue , 2000, Pages 136-145

  Biffl, S ^a  

^a VIENNA UNIVERSITY OF TECHNOLOGY   (Austria)

Author keywords

Data analysis; Fault diagnosis; Feedback; Inspection; Programming; Quality management; Software engineering; Software measurement; Software performance

Indexed keywords

DATA REDUCTION; DEFECTS; FAILURE ANALYSIS; FAULT DETECTION; FEEDBACK; MATHEMATICAL PROGRAMMING; PROGRAM DIAGNOSTICS; QUALITY ASSURANCE; QUALITY CONTROL; QUALITY MANAGEMENT; SOFTWARE DESIGN; SOFTWARE ENGINEERING;

CONTROLLED EXPERIMENT; READING TECHNIQUES; REQUIREMENTS SPECIFICATIONS; SOFTWARE MEASUREMENT; SOFTWARE PERFORMANCE; TIMELY FEEDBACK;

INSPECTION;

EID: 84949521057     PISSN: 15301362     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/APSEC.2000.896692     Document Type: Conference Paper

References (21)

1. V.R. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Soerumgaard, and M. Zelkowitz, "The Empirical Investigation of Perspective-Based Reading", Empirical Software Engineering Journal, vol. 1, no. 2, 1996, pp. 133-164.
2. R. Chillarege, I. Bhandari, J. Chaar, M. Halliday, D. Moebus, B. Ray, and W. Wong, "Orthogonal Defect Classification - A Concept for In-Process Measurements", IEEE Transactions on Software Engineering, vol. 18, no. 11, 1992, pp. 943-956.
3. M. Ciolkowski, C. Differding, O. Laitenberger, and J. Münch, "Empirical Investigation of Perspective-based Reading: A Replicated Experiment", Fraunhofer Institute for Experimental Software Engineering, Germany, Tech. Report Int. Software Engineering Research Network, 1997, ISERN-97-13.
4. T. Gilb, and D. Graham, Software Inspection, Addison-Wesley, 1993.
5. W. Humphrey, Introduction to the Team Software Process, Addison Wesley, 2000
6. P.M. Johnson, and D. Tjahjono, "Assessing Software Review Meetings: A Controlled Experimental Study Using CSRS", Technical Report 96-06, Dept. of Information and Computer Sciences, Univ. of Hawaii, 1996.
7. P.M. Johnson, "Reengineering Inspection," Comm. of the ACM, vol. 41, no. 2, February 1998.
8. P.M. Johnson, "Does Every Inspection Really Need a Meeting?", Empirical Software Engineering Journal, vol. 3, no. 3, 1998, pp. 9-35.
9. J.C. Knight, and A. Myers, "An Improved Inspection Technique", Comm. of the ACM, vol. 36, no. 11, 1993, pp. 51-61.
10. O. Laitenberger, and J.-M. DeBaud, "An encompassing life cycle centric survey of software inspection", Journal of Systems and Software, vol. 50, no.1, 2000, pp. 5-31.
11. J. Martin, and W. Tsai, "N-fold Inspection: A Requirements Analysis Technique", Comm. of the ACM, vol. 33, no. 2, February 1990, pp. 225-232.
12. J. Miller, M. Wood, and M. Roper; "Further experiences with scenarios and checklists", Empirical Software Engineering Journal, vol. 3, no. 1, 1998, pp. 37-64.
13. th Int. Conf. on Software Engineering, 1994, pp. 103-112.
14. A. Porter, and L. Votta, "Comparing Detection Methods for Software Requirements Inspections: a Replicated Experiment using professional subjects", Empirical Software Engineering Journal, vol. 3, no. 4, 1998, pp. 355-379.
15. F. Redmill, "Fagan's Inspection: Achieving Quality in Code and DocumentationM; Built-In Gauge of Effectiveness", Managing System Development, vol. 13, no. 3, Mar. 1993, pp. 1-5.
16. C. Sauer, D. Jeffery, L. Land, and P. Yetton, "The Effectiveness of Software Development Technical Reviews: A Behaviorally Motivated Program of Research"; IEEE Transactions on Software Engineering, vol. 26, no. 1, January 2000, pp. 11-14.
17. H.P. Siy, "Identifying the Mechanisms Driving Code Inspection Costs and Benefits", PhD thesis, Univ. of Maryland (unpublished), 1996.
18. R.G. Strauss, and R. Ebenau, Software Inspection Process, McGraw Hill, 1994.
19. G. Travassos, F. Shull, M. Fredericks, and V. Basili, "Detecting defects in object-oriented designs: Using reading techniques to increase software quality", Proc. Conf. on Object-oriented Programming Systems, Languages & Applications (OOPSLA), 1999.
20. L. Votta, "Does every Inspection need a Meeting?", ACM Software Eng. Notes vol. 18, no. 5, 1993, pp. 107-114.
21. E. F. Weller, "Lessons from Three Years of Inspection Data", IEEE Software, vol. 10, no. 5, Sept. 1993, pp. 38-45.