The Significance of Participant Experience when Evaluating Software Inspection Techniques
Authors:
- David A. McMeekinDMDavid A. McMeekin
- Brian R. von KonskyBKBrian R. von Konsky
- Michael RobeyMRMichael Robey
- David J. A. CooperDCDavid J. A. Cooper
- 1 April 2009
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15300803,p. 200-209
Abstract
Software inspections have been used to improve software quality for 30 years. The checklist based reading strategy has traditionally been the most prevalent reading strategy. Increased object oriented usage has raised questions regarding this technique's efficacy, given issues such as delocalisation. This study compared two OO inspection techniques: use-case reading and usage-based reading, with checklist based reading. Students and industry professionals were recruited to participate in the study. The effectiveness of each reading strategy was analysed, and the effect experience had on inspection efficacy. The results showed no significant difference between inspection techniques, whether used by student or professional developers but a significant difference was identified between student and professional developers in applying the different techniques. Qualitative results highlighted the differences in ability between industry and students with respect to what each group considered important when inspecting and writing code. These results highlight the differences between student and industry professionals when applying inspections. Therefore, when selecting participants for empirical software engineering studies, participant experience level must be accounted for within the reporting of results.Keywords
This publication has 27 references indexed in Scilit:
- Investigating the effect of expert ranking of use cases for design inspection2004
- Using Students as Subjects—A Comparative Study of Students and Professionals in Lead-Time Impact AssessmentEmpirical Software Engineering, 2000
- An encompassing life cycle centric survey of software inspectionJournal of Systems and Software, 2000
- By the way, has anyone studied any real programmers, yet? [software development process]1995
- The software-research crisisIEEE Software, 1994
- Maintaining object-oriented softwareIEEE Software, 1993
- Maintenance support for object-oriented programsIEEE Transactions on Software Engineering, 1992
- Support for maintaining object-oriented programsIEEE Transactions on Software Engineering, 1992
- Advances in software inspectionsIEEE Transactions on Software Engineering, 1986
- Design and code inspections to reduce errors in program developmentIBM Systems Journal, 1976