Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

The DOI matches its Crossref record.

Student Debugging Practices and Their Relationships with Project Outcomes

Kazerouni, Ayaan M., Mansur, Riffat Sabbir, Edwards, Stephen H., Shaffer, Clifford A. · 2019 · Proceedings of the 50th ACM Technical Symposium on Computer Science Education

Abstract

Debugging is an important part of the software development process, studied by both the CS education and software engineering communities. Most prior work has focused either on novice or professional programmers. Intermediate-to-advanced students (such as those enrolled in post-CS2 Data Structures courses) who are working on large and complex projects have largely been ignored. We present results from an empirical observational study that examined junior-level undergraduate students' debugging practices on relatively large (4-week lifecycle) projects, using IDE clickstream data collected by a custom Eclipse plugin. Specifically, we hypothesize that there are differing debugging behaviors exhibited, and that differing behaviors lead to differing project out-comes. For example, how often do students use the symbolic debugger available in modern IDEs, versus how often do they use diagnostic print statements, or both? What triggers a debugging session? What follows a debugging session? Does it matter when in the project lifecycle that debugging takes place? We have a number of interesting preliminary results. When using the debugger, there was a negative relationship between step-over and step-into actions versus final course grades, indicating that when students "spin their wheels" while debugging, they tend to perform more poorly. Students also tend to perform better on the project when debugging takes place earlier in the overall project life-cycle. We developed an algorithm to identify diagnostic print statements in the students' projects. We found that over 90% used at least one diagnostic print statement, and about 75% used the symbolic debugger, at least once in any given project.

Overview

Integrity signals

Registry

Crossref · 10.1145/3287324.3293794

Cites

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Citations

Cited by

See all 5

Metadata

Authors
Kazerouni, A. M., Mansur, R. S., Edwards, S. H., & Shaffer, C. A.
Affiliations
  • Virginia Tech (US)
  • Virginia Tech, Blacksburg, VA, USA
Venue
Proceedings of the 50th ACM Technical Symposium on Computer Science Education
Publisher
ACM
Published
2019-02-22
Pages
1263-1263
OpenAlex
W2916903689
Cited by
4
References
0
Citations by year
2025: 1 · 2024: 1 · 2023: 1 · 2021: 1
Type
conference abstract
Language
en
Open access
closed
Locations
ACM Technical Symposium on Computer Science Education (SIGCSE) (publishedVersion)
Funders
National Science Foundation (DUE-1245334)
Topics
  • Physical Sciences › Computer Science › Computer Science Applications › Teaching and Learning Programming
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
Keywords
student programmers, Eclipse plug-in, project life cycle, course grades, data structures course, software engineering education

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Student Debugging Practices and Their Relationships with Project Outcomes. https://app.cochat.ai/papers/10.1145/3287324.3293794
The paper
Kazerouni, A. M., Mansur, R. S., Edwards, S. H., & Shaffer, C. A. (2019). Student Debugging Practices and Their Relationships with Project Outcomes. Proceedings of the 50th ACM Technical Symposium on Computer Science Education. https://doi.org/10.1145/3287324.3293794

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.