Towards an eye-tracking enabled IDE for software traceability tasks

Walters, Braden; Falcone, Michael; Shibble, Alexander; Sharif, Bonita

doi:10.1109/tefse.2013.6620154

Cited by 14 publications

(14 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To understand the impact of multiple representations on debugging [Jermann and Nüssli, 2012] To study the impact of sharing selection among collaborators in a pairprogramming task [Sharafi et al, 2012] To investigate the impact of gender on developers' effectiveness for source code reading and identifier recalling [Sharif et al, 2012] To study the impact of scan Time in detecting source code defects [Soh et al, 2012] To analyze the impact of expertise on developers' speed and accuracy [Binkley et al, 2013] To analyze the impact of identifier style on program comprehension [Cagiltay et al, 2013] To propose measures to enhance understanding of ERD diagrams [Duru et al, 2013] To study the impact of software visualization in program comprehension [Petrusel and Mendling, 2012] To understand the impact of multiple representations in debugging [Sharafi et al, 2013] To study the relations between the type of requirement representations (graphical vs. textual) and developers efficiency [Sharif et al, 2013] To analyze the impact of SeeIT 3D on software engineering tasks [Sharma et al, 2013] To study the interaction of developers in a pair programming task [58] To recover traceability links from eye-movements data [Busjahn et al, 2014] To present a method to recover traceability links from eye-gaze data [Fritz et al, 2014] To use psycho-physiological measures to calculate task difficulty [Rodeghero et al, 2014]…”

Section: Slr Articlesmentioning

confidence: 99%

A systematic literature review on the usage of eye-tracking in software engineering

Sharafi

Soh

Guéhéneuc

2015

Information and Software Technology

177

105

View full text Add to dashboard Cite

Section: Slr Articlesmentioning

confidence: 99%

A systematic literature review on the usage of eye-tracking in software engineering

Sharafi

Soh

Guéhéneuc

2015

Information and Software Technology

177

105

View full text Add to dashboard Cite

“…Other researchers examined different strategies novice and expert developers employ in program comprehension and debugging [7,6], as well as where developers spend most time when reading a method to devise a better method summarization technique [34]. Finally, researchers have also used eye-tracking to evaluate its potential for detecting software traceability links [38,48,49]. All of these studies are limited to very small, toy applications or single page code tasks.…”

Section: Biometric Sensingmentioning

confidence: 99%

Tracing software developers' eyes and interactions for change tasks

Kevic

Walters

Shaffer

et al. 2015

Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering

Self Cite

View full text Add to dashboard Cite

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.

show abstract

“…They first proposed this idea of moving towards an eye aware IDE in [28]. In 2014, they conducted a pilot study [4] to determine if it was feasible to generate traceability links from eye gaze alone.…”

Section: Eye Tracking As Informing Software Tasksmentioning

confidence: 99%

The Use of Eye Tracking in Software Development

Sharif

Shaffer

2015

Foundations of Augmented Cognition

Self Cite

View full text Add to dashboard Cite

Abstract. Eye trackers have been routinely used in psychology reading experiments and in website usability studies for many years. However, it is only recently that they have been used by more researchers in the software engineering community. In this paper, we categorize two broad areas in which eye tracking technology can benefit software development in a practical way. The first area includes using the eye tracker as an assessment tool for software artifacts, tools, and techniques. The second area deals with using eye tracking data from developers to inform certain software tools and software development tasks such as providing developer recommendations and software traceability tasks. Examples of experiments and studies done in each of these broad areas is presented and discussed along with future work. The results point towards many benefits that eye trackers provide to augment the daily lives of programmers during software development.

show abstract

Towards an eye-tracking enabled IDE for software traceability tasks

Cited by 14 publications

References 8 publications

A systematic literature review on the usage of eye-tracking in software engineering

A systematic literature review on the usage of eye-tracking in software engineering

Tracing software developers' eyes and interactions for change tasks

The Use of Eye Tracking in Software Development

Contact Info

Product

Resources

About