ACM Home Page
Please provide us with feedback. Feedback
Debugging: the good, the bad, and the quirky -- a qualitative analysis of novices' strategies
Full text PdfPdf (223 KB)
Source
Technical Symposium on Computer Science Education archive
Proceedings of the 39th SIGCSE technical symposium on Computer science education table of contents
Portland, OR, USA
SESSION: Debugging table of contents
Pages 163-167  
Year of Publication: 2008
ISBN:978-1-59593-799-5
Also published in ...
Authors
Laurie Murphy  Pacific Lutheran University, Tacoma, WA, USA
Gary Lewandowski  Xavier University, Cincinnati, OH, USA
Renée McCauley  College of Charleston, Charleston, SC, USA
Beth Simon  University of California, San Diego, La Jolla, CA, USA
Lynda Thomas  Universit of Aberystwyth, Aberystwyth, Wales Uk
Carol Zander  University of Washington, Bothell, Bothell, WA, USA
Sponsors
ACM: Association for Computing Machinery
SIGACCESS: ACM Special Interest Group on Accessible Computing
SIGCSE: ACM Special Interest Group on Computer Science Education
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 24,   Downloads (12 Months): 151,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1352135.1352191
What is a DOI?

ABSTRACT

A qualitative analysis of debugging strategies of novice Java programmers is presented. The study involved 21 CS2 students from seven universities in the U.S. and U.K. Subjects "warmed up" by coding a solution to a typical introductory problem. This was followed by an exercise debugging a syntactically correct version with logic errors. Many novices found and fixed bugs using strategies such as tracing, commenting out code, diagnostic print statements and methodical testing. Some competently used online resources and debuggers. Students also used pattern matching to detect errors in code that "just didn't look right". However, some used few strategies, applied them ineffectively, or engaged in other unproductive behaviors. This led to poor performance, frustration for some, and occasionally the introduction of new bugs. Pedagogical implications and suggestions for future research are discussed.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
3
 
4
S. Fitzgerald, G. Lewandowski, R. McCauley, L. Murphy, B. Simon, L. Thomas and C. Zander. Debugging: Finding, Fixing and Flailing -A multi-institutional study of novice debuggers. Forthcoming in Computer Science Education - Special Issue on Debugging, 18(2), June 2008.
 
5
Gould. Some psychological evidence on how people debug computer programs. International J. of Man-Machine Studies, 7(1), pp. 151--182, 1975.
6
 
7
I. Katz and J. Anderson. Debugging: An analysis of bug location strategies. Human-Computer Interaction, 3(4):351--399, 1987.
 
8
9
 
10
McCauley, S. Fitzgerald, G. Lewandowski, L. Murphy, B. Simon, L. Thomas and C. Zander. Debugging: A review of the literature from an educational perspective. Forthcoming in Computer Science Education -- Special Issue on Debugging, 18(2), June 2008.
 
11
 
12
 
13
Vessey. Expertise in debugging computer pro-grams: A process analysis. International J. of Man-Machine Studies, 23, pp. 459--494, 1985.


Collaborative Colleagues:
Laurie Murphy: colleagues
Gary Lewandowski: colleagues
Renée McCauley: colleagues
Beth Simon: colleagues
Lynda Thomas: colleagues
Carol Zander: colleagues