
In this paper we present accumulated results from two years of experience with a teaching unit on debugging Java programs. With this special teaching unit, we strive to foster the debugging skills of our students. Students were asked to find different defects in given code, to analyze these and finally to fix them. As well, students were requested to document their approach in writing. The achieved results ranged from “all bugs found and fixed” to “completely lost in the code”. When analyzing these results, we discovered that the debugging skills of our students seem to correlate with some non-technical skills that are essential base competencies in software engineering, such as the ability to work in a systematic way. This implies that for improving our students' debugging skills, it is helpful to address not only the technical aspects of debugging, but to foster the required base competencies as well.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 13 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Top 10% | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Top 10% |
