Tracing software developers' eyes and interactions for change tasks
Open accessThe DOI matches its Crossref record; 17 of the 17 references it cites were found in a registry or an index.
Abstract
What are software developers doing during a change task? While an answer to this question opens countless opportunities to support developers in their work, only little is known about developers' detailed navigation behavior for realistic change tasks. Most empirical studies on developers performing change tasks are limited to very small code snippets or are limited by the granularity or the detail of the data collected for the study. In our research, we try to overcome these limitations by combining user interaction monitoring with very fine granular eye-tracking data that is automatically linked to the underlying source code entities in the IDE. In a study with 12 professional and 10 student developers working on three change tasks from an open source system, we used our approach to investigate the detailed navigation of developers for realistic change tasks. The results of our study show, amongst others, that the eye tracking data does indeed capture different aspects than user interaction data and that developers focus on only small parts of methods that are often related by data flow. We discuss our findings and their implications for better developer tool support.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Eye movements in reading and information processing: 20 years of research
Rayner, K. (1998) · Psychological Bulletin · doi:10.1037/0033-2909.124.3.372 · Cited by 7,979
A theory of reading: From eye fixations to comprehension.
Just, M. A., & Carpenter, P. A. (1980) · Psychological Review · doi:10.1037/0033-295x.87.4.329 · Cited by 5,220
Towards a theory of the comprehension of computer programs
Brooks, R. (1983) · International Journal of Man-Machine Studies · doi:10.1016/s0020-7373(83)80031-5 · Cited by 756
Ko, A. J., Myers, B. A., Coblenz, M. J., & Aung, H. H. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.116 · Cited by 685 · cited 1×
“In order to successfully complete these tasks, they have to read, navigate and edit the relevant pieces of code [22, 16].”
BackgroundUsing task context to improve programmer productivity
Kersten, M., & Murphy, G. C. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181777 · Cited by 452
How are Java software developers using the Eclipse IDE?
Murphy, G. C., Kersten, M., & Findlater, L. (2006) · IEEE Software · doi:10.1109/ms.2006.105 · Cited by 413
On the Use of Automated Text Summarization Techniques for Summarizing Source Code
Haiduc, S., Aponte, J., Moreno, L., & Marcus, A. (2010) · 2010 17th Working Conference on Reverse Engineering · doi:10.1109/wcre.2010.13 · Cited by 408
Supporting program comprehension with source code summarization
Haiduc, S., Aponte, J., & Marcus, A. (2010) · Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2 · doi:10.1145/1810295.1810335 · Cited by 291 · cited 1×
“Existing techniques to summarize code have mainly focused on summarizing whole methods [17, 18] rather than only summarizing the parts relevant for a given task.”
MethodUsing psycho-physiological measures to assess task difficulty in software development
Fritz, T., Begel, A., Müller, S. C., Yigit-Elliott, S., & Züger, M. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568266 · Cited by 262 · cited 2×
“Studies with sensors for tracking biometric features, such as eye gaze, have generated new insights on developers’ work on small code tasks, such as perceptions of difficulty [15], brain activation patterns [42], the scanning patterns of code [36] or the ease of comprehending different representations of code [40, 6].”
BackgroundSelf-citationMining StackOverflow to turn the IDE into a self-confident programming prompter
Ponzanelli, L., Bavota, G., Di Penta, M., Oliveto, R., & Lanza, M. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597077 · Cited by 240 · cited 2×
“By using eye-tracking to capture a more fine-grained task context while a developer is working, we are also able to better determine what a developer is currently interested in and complement existing approaches to recommend relevant artifacts to the developer, such as Hipikat [46] or Prompter [30].”
MethodUnderstanding understanding source code with functional magnetic resonance imaging
Siegmund, J., Kästner, C., Apel, S., Parnin, C., Bethmann, A., Leich, T., Saake, G., & Brechmann, A. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568252 · Cited by 219 · cited 2×
“Studies with sensors for tracking biometric features, such as eye gaze, have generated new insights on developers’ work on small code tasks, such as perceptions of difficulty [15], brain activation patterns [42], the scanning patterns of code [36] or the ease of comprehending different representations of code [40, 6].”
BackgroundImproving automated source code summarization via an eye-tracking study of programmers
Rodeghero, P., McMillan, C., McBurney, P. W., Bosch, N., & D'Mello, S. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568247 · Cited by 198 · cited 2×
“[34] focused on using eye-tracking to summarize whole methods.”
BackgroundMethodCode bubbles: a working set-based interface for code understanding and maintenance
Bragdon, A., Zeleznik, R., Reiss, S. P., Karumuri, S., Cheung, W., Kaplan, J., Coleman, C., Adeputra, F., & LaViola, J. J. (2010) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753706 · Cited by 174 · cited 1×
“Most prominently, editors of common IDEs, such as Visual Studio or Eclipse, display whole classes, but even the recently suggested new bubble metaphor for IDEs displays full methods [9].”
Background(2015) · doi:10.5555/2818754.2818838 · Cited by 111
Self-citationInterruptibility of Software Developers and its Prediction Using Psycho-Physiological Sensors
Züger, M., & Fritz, T. (2015) · Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems · doi:10.1145/2702123.2702593 · Cited by 96 · cited 1×
“Most of this research focuses on eye-tracking [31, 19], while only few studies have been conducted so far that also use other signals, such as an fMRI to identify brain activation patterns for small comprehension tasks [42], or a combination of eye-tracking, EDA, and EEG sensors to measure aspects such as task difficu…”
BackgroundSelf-citationTowards understanding programs through wear-based filtering
DeLine, R., Khella, A., Czerwinski, M., & Robertson, G. (2005) · Proceedings of the 2005 ACM symposium on Software visualization · doi:10.1145/1056018.1056044 · Cited by 91 · cited 2×
“The more we know about a developer’s work, the better we are able to support her, for instance, by reducing information overload [21], improving defect prediction [24], or providing automatic navigation recommendations [13, 29].”
BackgroundMethodDevelopers' code context models for change tasks
Fritz, T., Shepherd, D. C., Kevic, K., Snipes, W., & Bräunlich, C. (2014) · Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2635868.2635905 · Cited by 45
Self-citation
Cited by
An eye tracking study assessing source code readability rules for program comprehension
Park, K.-I., Johnson, J., Peterson, C. S., Yedla, N., Baysinger, I., Aponte, J., & Sharif, B. (2024) · Empirical Software Engineering · doi:10.1007/s10664-024-10532-x · Cited by 9
Self-citationComputing Education Research Today
Fincher, S. A., Tenenberg, J., Dorn, B., Hundhausen, C., McCartney, R., & Murphy, L. (2019) · The Cambridge Handbook of Computing Education Research · doi:10.1017/9781108654555.003 · Cited by 7
Towards Activity-Aware Tool Support for Change Tasks
Kevic, K., & Fritz, T. (2017) · 2017 IEEE International Conference on Software Maintenance and Evolution (ICSME) · doi:10.1109/icsme.2017.48 · Cited by 5
“These studies vary in the granularity of the developer activities they focus on, ranging from very abstract and high-level activities, such as understanding and editing code [2], [3], [7], [8], [12]–[15], and the high-level questions developers ask (”To move this feature into this code what else needs to be moved?“ [4…”
BackgroundSelf-citation(2025) · doi:10.1145/3723010.3723018 · Cited by 3
Self-citation
Metadata
- Authors
- Kevic, K., Walters, B. M., Shaffer, T. R., Sharif, B., Shepherd, D. C., & Fritz, T.
- Venue
- Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2015-08-30
- Pages
- 202-213
- OpenAlex
- W1999331443
- Cited by
- 106
- References
- 17
- FWCI
- 7.31
- Type
- conference paper
- Language
- en
- Open access
- green
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
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.