go-v.orgdoi

Identifying Code Reading Strategies in Debugging using STA with a Tolerance Algorithm

Christine Lourrine S. Tablatin, Ma. Mercedes T. Rodrigo · APSIPA Transactions on Signal and Information Processing · 2022

  • DOI 10.1561/116.00000040
  • Publisher Cambridge University Press
  • Type article
  • Issued 2022

Not cached yet. This record was fetched live for this request and is stored after the lookup. Reopening the page should serve the cached copy.

APSIPA Transactions on Signal and Information Processing · Cambridge University Press · article · 2022

Abstract

The purpose of this study was to identify the common code reading strategies of the high and low performing students engaged in a debugging task. Using Scanpath Trend Analysis (STA) with a tolerance on eye tracking data, common scanpaths of high and low performing students were generated. The common scanpaths revealed differences in the code reading patterns and code reading strategies of high and low performing students. High performing students follow a bottom-up code reading strategy when debugging complex programs with logical and semantic errors.

A top-down code reading strategy is employed when debugging programs with simple control structures, few lines of code, and simple error types. These results imply that high performing students use flexible debugging strategies based on the program structure. The generated common scanpaths of the low performing students, on the other hand, showed erratic code reading patterns, implying that no obvious code reading strategy was applied. The identified code reading strategies of the high performing students could be explicitly taught to low performing students to help improve their debugging performance.

Open the resolved locator · 10.1561/116.00000040

Metadata licence: OpenAlex metadata (CC0)

Registry
OpenAlex DOI index + API
Fetched
2026-11-20 03:52 UTC
Cache state
not cached yet (bulk-index+openalex)
Locator
https://doi.org/10.1561/116.00000040
Metadata licence
OpenAlex metadata (CC0)
Scope
Metadata as returned by the resolver; abstracts are never generated here.