View Item 

Checklist based reading's influence on a developer's understanding

Access Status
Open access
Authors
McMeekin, David
Von Konsky, Brian
Chang, Elizabeth
Cooper, David
Date
2008
Type
Conference Paper

Metadata
Show full item record
Citation
McMeekin, David and Von Konsky, Brian and Chang, Elizabeth and Cooper, David. 2008. Checklist based reading's influence on a developer's understanding, in Hussain, F. and Chang, E. (ed), 19th Australian Conference on Software Engineering, Mar 26 2008, pp. 489-496. Perth, WA: Institute of Electrical and Electronics Engineers (IEEE) Computer Society.
Source Title
Proceedings of the 19th Australian software engineering conference (ASWEC 2008)
Source Conference
19th Australian Software Engineering Conference (ASWEC 2008)
DOI
ISSN
Faculty
Curtin Business School
School of Economics and Finance
School
Centre for Extended Enterprises and Business Intelligence
Remarks

Copyright © 2008 IEEE. This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder.

URI
Collection
Abstract

This paper addresses the influence the Checklist Based Reading inspection technique has on a developer's ability to modify inspected code. Traditionally, inspections have been used to detect defects within the development life cycle. This research identified a correlation between the number of defects detected and the successful code extensions for new functionality unrelated to the defects. Participants reported that having completed a checklist inspection, modifying the code was easier because the inspection had given them an understanding of the code that would not have existed otherwise. The results also showed a significant difference in how developers systematically modified code after completing a checklist inspection when compared to those who had not performed a checklist inspection. This study has shown that applying software inspections for purposesother than defect detection include software understanding and comprehension.