Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Braden Walters

dblp:145/4476 · also Braden M. Walters · DBLP profile ↗
← Back
4ranked-venue papers
1as first author
0since 2021 · last 2017
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Empirical software engineering · 71% Software maintenance and evolution · 29%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
developer studies
0.422015
iTrace: enabling eye tracking on software artifacts within the IDE to support software engineering tasks · ESEC/SIGSOFT FSE 2015
Tracing software developers' eyes and interactions for change tasks · ESEC/SIGSOFT FSE 2015
Software maintenance and evolution
program comprehension
0.322015
iTrace: enabling eye tracking on software artifacts within the IDE to support software engineering tasks · ESEC/SIGSOFT FSE 2015
Tracing software developers' eyes and interactions for change tasks · ESEC/SIGSOFT FSE 2015
Empirical software engineering › developer studies
eye tracking
0.212015
Tracing software developers' eyes and interactions for change tasks · ESEC/SIGSOFT FSE 2015
Empirical software engineering › human factors in software engineering
eye-tracking studies
0.212015
iTrace: enabling eye tracking on software artifacts within the IDE to support software engineering tasks · ESEC/SIGSOFT FSE 2015
Software maintenance and evolution
traceability
0.112015
iTrace: enabling eye tracking on software artifacts within the IDE to support software engineering tasks · ESEC/SIGSOFT FSE 2015

Methods — techniques the papers use, named apart from their topics

eye tracking · 0.4user interaction monitoring · 0.2IDE instrumentation · 0.2
YearPublicationVenuePosition
2017 Eye gaze and interaction contexts for change tasks - Observations and potential
Katja Kevic, Braden Walters, Timothy Shaffer, Bonita Sharif, David C. Shepherd, Thomas Fritz 0001
J. Syst. Softw.2
2015 Tracing software developers' eyes and interactions for change tasks
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.
Katja Kevic, Braden Walters, Timothy Shaffer, Bonita Sharif, David C. Shepherd, Thomas Fritz 0001
ESEC/SIGSOFT FSE2
2015 iTrace: enabling eye tracking on software artifacts within the IDE to support software engineering tasks
abstract
The paper presents iTrace, an Eclipse plugin that implicitly records developers' eye movements while they work on change tasks. iTrace is the first eye tracking environment that makes it possible for researchers to conduct eye tracking studies on large software systems. An overview of the design and architecture is presented along with features and usage scenarios. iTrace is designed to support a variety of eye trackers. The design is flexible enough to record eye movements on various types of software artifacts (Java code, text/html/xml documents, diagrams), as well as IDE user interface elements. The plugin has been successfully used for software traceability tasks and program comprehension tasks. iTrace is also applicable to other tasks such as code summarization and code recommendations based on developer eye movements. A short video demonstration is available at https://youtu.be/3OUnLCX4dXo.
Timothy Shaffer, Jenna DiVincenzo, Braden Walters, Sebastian C. Müller, Michael Falcone, Bonita Sharif
ESEC/SIGSOFT FSE3
2014 Capturing software traceability links from developers' eye gazes
abstract
The paper presents a novel approach for recovering software traceability links from developers' eye gazes. An eye tracker is used to capture eye gazes while developers perform software maintenance tasks within the Eclipse IDE. An algorithm is presented that establishes a set of traceability links from the eye-gaze data of several developer sessions. A preliminary study assesses the feasibility and validity of the approach. The links generated by the approach were validated by another set of developers. Results indicate that our algorithm achieves strong recall when developers accurately perform bug-localization tasks.
Braden Walters, Timothy Shaffer, Bonita Sharif, Huzefa H. Kagdi
ICPC1