Cited by 270Software Engineering ResearchSoftware Engineering Techniques and PracticesAdvanced Software Engineering Methodologies

Questions programmers ask during software evolution tasks

Sillito, Jonathan, Murphy, Gail C., De Volder, Kris·2006·Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering

Abstract

Though many tools are available to help programmers working on change tasks, and several studies have been conducted to understand how programmers comprehend systems, little is known about the specific kinds of questions programmers ask when evolving a code base. To fill this gap we conducted two qualitative studies of programmers performing change tasks to medium to large sized programs. One study involved newcomers working on assigned change tasks to a medium-sized code base. The other study involved industrial programmers working on their own change tasks on code with which they had experience. The focus of our analysis has been on what information a programmer needs to know about a code base while performing a change task and also on howthey go about discovering that information. Based on this analysis we catalog and categorize 44 different kinds of questions asked by our participants. We also describe important context for how those questions were answered by our participants, including their use of tools.

Integrity signals

Registry

Crossref · 10.1145/1181775.1181779

Cites

22 of 22 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?

  • Little is known at the foundational level about how well developers can predict the value and cost of their navigations, and SE research has not systematically considered this.

    “Despite these gains, however, little is known at the foundational level of developer navigation-how well developers go about choosing where to navigate.”
  • Developers seek information to answer specific questions, test mental hypotheses, develop context, or follow leads.

    “These studies have also revealed that developers seek this information to answer specific questions that they have [23,42], to test mental hypotheses about how an existing program works [4], to develop an overall sense of context [13], or to follow leads that simply look relevant to their current task [26].”

Cites

Flagged first, then by citations

Research works printed but not linked: 10

  1. 10.5555/521138.786884 · DOI
  2. 10.5555/580914.858205 · DOI
  3. Flor N. V., 1991, Proceedings of the Empirical Studies of Programmers: Fourth Workshop, 36
  4. Glaser B. G., 1967, Aldine Publishing
  5. 10.5555/164632.260021 · DOI
  6. 10.5555/788007.788157 · DOI
  7. Letovsky S., 1986, Proceedings of Conference on Empirical Studies of Programmers, 80
  8. Strauss A. L., 1998, Sage Publications
  9. van Someren M. W., 1994, Academic Press
  10. Wilde N., 1996, Proceedings of WCRE, 270

Cited by

Sorted by citations

Authors
Sillito, J., Murphy, G. C., & De Volder, K.
Affiliations
  • University of British Columbia (CA)
  • University of British Columbia, Vancouver, B.C. Canada
Venue
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Publisher
ACM
Published
2006-11-05
Pages
23-34
OpenAlex
W2080534028
Cited by
270
References
22
Citations by year
2026: 6 · 2025: 14 · 2024: 9 · 2023: 1 · 2022: 10 · 2021: 11 · 2020: 9 · 2019: 10 · 2018: 12 · 2017: 18 · 2016: 16 · 2015: 20 · 2014: 20 · 2013: 25 · 2012: 23
FWCI
9.47
Type
conference paper
Language
en
Open access
closed
Locations
ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) (publishedVersion)
Funders
Natural Sciences and Engineering Research Council of Canada
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 › Artificial Intelligence › Advanced Software Engineering Methodologies
Keywords
software evolution, information needs, novice programmers, software tools

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