Cited by 685Software Engineering ResearchSoftware Engineering Techniques and PracticesUsability and User Interface Design

An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks

Ko, Amy J., Myers, Brad A., Coblenz, Michael J., Aung, Htet Htet·2006·IEEE Transactions on Software Engineering

Abstract

Much of software developers' time is spent understanding unfamiliar code. To better understand how developers gain this understanding and how software development environments might be involved, a study was performed in which developers were given an unfamiliar program and asked to work on two debugging tasks and three enhancement tasks for 70 minutes. The study found that developers interleaved three activities. They began by searching for relevant code both manually and using search tools; however, they based their searches on limited and misrepresentative cues in the code, environment, and executing program, often leading to failed searches. When developers found relevant code, they followed its incoming and outgoing dependencies, often returning to it and navigating its other dependencies; while doing so, however, Eclipse's navigational tools caused significant overhead. Developers collected code and other information that they believed would be necessary to edit, duplicate, or otherwise refer to later by encoding it in the interactive state of Eclipse's package explorer, file tabs, and scroll bars. However, developers lost track of relevant code as these interfaces were used for other tasks, and developers were forced to find it again. These issues caused developers to spend, on average, 35 percent of their time performing the mechanics of navigation within and between source files. These observations suggest a new model of program understanding grounded in theories of information foraging and suggest ideas for tools that help developers seek, relate, and collect information in a more effective and explicit manner.

Integrity signals

Registry

Crossref · 10.1109/tse.2006.116

Cites

50 of 50 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Developers spend 35%-50% of their time navigating through source code during development activities.

    “Empirical studies have revealed that software developers spend 35%-50% of their time navigating through source code during development activities”
  • Searches in code frequently failed to turn up desired results, and developers spent substantial time organizing and reorganizing files and bookmarks in the IDE.

    “This result was consistent with an earlier study into the challenges of information foraging by developers, such as the fact that searches in code frequently failed to turn up desired results, and that developers spent substantial time organizing and reorganizing files and bookmarks in the IDE [21].”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Ko, A. J., Myers, B. A., Coblenz, M. J., & Aung, H. H.
Affiliations
  • Human-Computer Interaction Institute, School of Computer Science, Carnegie Mellon University, 5000 Forbes Ave., Pittsburgh, PA 15213
  • Carnegie Mellon University (US)
Venue
IEEE Transactions on Software Engineering
Published
2006-12
Volume
32
Issue
12
Pages
971-987
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
  • 2326-3881
OpenAlex
W2151996389
Cited by
685
References
50
Citations by year
2026: 22 · 2025: 30 · 2024: 75 · 2023: 27 · 2022: 35 · 2021: 24 · 2020: 27 · 2019: 41 · 2018: 31 · 2017: 48 · 2016: 48 · 2015: 52 · 2014: 47 · 2013: 49 · 2012: 31
FWCI
52.51
Type
journal article
Language
en
Open access
closed
Locations
IEEE Transactions on Software Engineering (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
Keywords
software maintenance, program comprehension, debugging, code navigation, Eclipse IDE, information foraging, information gathering, software development environment

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