Expertise in Debugging Computer Programs: A Process Analysis

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Improving Robot Controller Transparency Through Autonomous Policy Explanation (2017, methodology): “We frame our approach to policy explanation in a manner that facilitates the four operational goals outlined in Vessey’s study on debugging processes [43]: problem identification, familiarity acquisition, program structure exploration, and error repair.”
A Survey on Software Fault Localization (2016, background): “, identifying the locations of faults, has historically been a manual task that has been recognized to be time consuming and tedious as well as prohibitively expensive [347], given the size and complexity of large-scale software systems today.”
Recovering Traceability Links between Code and Documentation (2002, background): “They also agree that programmers use different types of knowledge during program comprehension, ranging from domain specific knowledge to general programming knowledge [14], [50], [ 53 ].”
Debugging: finding, fixing and flailing, a multi-institutional study of novice debuggers (2008, background): “Vessey (1985) also investigated novice and expert diﬀerences.”