The DOI matches its Crossref record; 80 of the 80 references it cites were found in a registry or an index.
Asking and Answering Questions during a Programming Change Task
Open accessAbstract
Little is known about the specific kinds of questions programmers ask when evolving a code base and how well existing tools support those questions. To better support the activity of programming, answers are needed to three broad research questions: 1) What does a programmer need to know about a code base when evolving a software system? 2) How does a programmer go about finding that information? 3) How well do existing tools support programmers in answering those questions? We undertook two qualitative studies of programmers performing change tasks to provide answers to these questions. In this paper, we report on an analysis of the data from these two user studies. This paper makes three key contributions. The first contribution is a catalog of 44 types of questions programmers ask during software evolution tasks. The second contribution is a description of the observed behavior around answering those questions. The third contribution is a description of how existing deployed and proposed tools do, and do not, support answering programmers' questions.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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?
In the citing paper
“Software developers, like all humans, are cognitively diverse (e.g., they differ in attitudes toward risk, information-processing and learning preferences, motivations for using a technology), which impacts how they problem-solve, manage uncertainty in work, or even engage with genAI [7, 19, 79, 83, 101, 126].”
From What Needs Attention? Prioritizing Drivers of Developers' Trust and Adoption of Generative AI (2025) · cites this paper as [126]
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
The Discovery of Grounded Theory: Strategies for Qualitative Research.
Wagner, H. R., Glaser, B. G., & Strauss, A. L. (1968) · Social Forces · doi:10.2307/2575405 · Cited by 46,361
The Discovery of Grounded Theory; Strategies for Qualitative Research
Glaser, B. G., Strauss, A. L., & Strutzel, E. (1968) · Nursing Research · doi:10.1097/00006199-196807000-00014 · Cited by 39,449
(1998) · Sage eBooks · Cited by 38,631
The magical number seven, plus or minus two: Some limits on our capacity for processing information.
Miller, G. A. (1994) · Psychological Review · doi:10.1037/0033-295x.101.2.343 · Cited by 17,161
Stroustrup, B. (1985) · Cited by 3,940
The Java Language Specification
Gosling, J., Joy, B., & Steele, G. L. (1996) · Cited by 3,924
Weiser, M. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010248 · Cited by 3,204
No Silver Bullet Essence and Accidents of Software Engineering
Brooks (1987) · Computer · doi:10.1109/mc.1987.1663532 · Cited by 3,186
Kernighan, B. W., & Ritchie, D. M. (1978) · Cited by 1,857
CCFinder: a multilinguistic token-based code clone detection system for large scale source code
Kamiya, T., Kusumoto, S., & Inoue, K. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.1019480 · Cited by 1,711
Cited by
Using an LLM to Help With Code Understanding
Nam, D., Macvean, A., Hellendoorn, V., Vasilescu, B., & Myers, B. (2024) · Proceedings of the IEEE/ACM 46th International Conference on Software Engineering · doi:10.1145/3597503.3639187 · Cited by 487
“Therefore, researchers have studied to understand how developers learn and comprehend unfamiliar code and domains [30, 38, 51, 62], especially how they search for and acquire information, as developers need a variety of kinds of knowledge [43, 66, 68, 77].”
BackgroundA field study of API learning obstacles
Robillard, M. P., & DeLine, R. (2011) · Empirical Software Engineering · doi:10.1007/s10664-010-9150-8 · Cited by 352
Portfolio: finding relevant functions and their usage
McMillan, C., Grechanik, M., Poshyvanyk, D., Xie, Q., & Fu, C. (2011) · Proceedings of the 33rd International Conference on Software Engineering · doi:10.1145/1985793.1985809 · Cited by 313
Abbes, M., Khomh, F., Gueheneuc, Y.-G., & Antoniol, G. (2011) · 2011 15th European Conference on Software Maintenance and Reengineering · doi:10.1109/csmr.2011.24 · Cited by 309
Improving 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
Metadata
- Authors
- Sillito, J., Murphy, G. C., & De Volder, K.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2008-07
- Volume
- 34
- Issue
- 4
- Pages
- 434-451
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2097750323
- Cited by
- 319
- References
- 80
- FWCI
- 40.41
- Type
- journal article
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Asking and Answering Questions during a Programming Change Task. https://app.cochat.ai/papers/10.1109/tse.2008.26
- The paper
- Sillito, J., Murphy, G. C., & De Volder, K. (2008). Asking and Answering Questions during a Programming Change Task. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2008.26
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.