The Significance of Participant Experience when Evaluating Software Inspection Techniques

• Published in: 2009 Australian Software Engineering Conference pp. 200 - 209
• Main Authors: McMeekin, David A., von Konsky, Brian R., Robey, Michael, Cooper, David J. A.
• Format: Conference Proceeding
• Language: English
• Published: IEEE 01-04-2009
• Subjects: Australia; Dynamic programming; Ecosystems; Functional programming; industry participants; Inspection; participant experience level; Programming profession; Recruitment; Software engineering; Software inspections; Software quality; student participants; Writing
• ISBN: 9780769535999; 0769535992
• ISSN: 1530-0803; 2377-5408
• DOI: 10.1109/ASWEC.2009.13

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.