Building Usage Contexts During Program Comprehension
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
Software developers often work on multiple simultaneous projects. Even when only a single project is underway, everyday distractions interrupt the development effort. Consequently, developers spend significant effort pursuing recovery of their context. By context, we focus on the classes and methods within the code that are relevant to a specific bug being fixed or enhancement made. Context is reified by a program in terms of a set of presentations (windows a containing source code, command executions, and data files); however, it is not enough to save the latest context. Even when working on a single task, programmers flip between contexts as they extend their understanding, and when they decide on a change, they may have to visit several contexts in order to address all possible ripple effects. Consequently, we would like to record a history of contexts and be able to retrieve them as demanded by the current task. We introduce a novel technique to obtain a context, consisting of a set of methods relevant for the current task, from a programmer's interactions with an IDE. Using this context, we demonstrate how to improve the ability of a programmer to recover the mental state associated with tasks and to facilitate the exploration of software through recommendation systems
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
A diary study of task switching and interruptions
Czerwinski, M., Horvitz, E., & Wilhite, S. (2004) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/985692.985715 · Cited by 830
Towards understanding programs through wear-based filtering
DeLine, R., Khella, A., Czerwinski, M., & Robertson, G. (2005) · Proceedings of the 2005 ACM symposium on Software visualization · doi:10.1145/1056018.1056044 · Cited by 91 · cited 7×
“The DOI model used inFAN provides a global view of the source code; this approach has difficulty in assisting programmers working on elements not historically having high DOI.”
MethodInfluential
Research works printed but not linked: 16
- zayour, 2000, A cognitive and user centric based approach for reverse engineering tool design, CASCON '00 Proceedings of the 2000 conference of the Centre for Advanced Studies on Collaborative research, 16
- 10.1109/ICSE.2004.1317478 · DOI · Paper page
- 10.1109/WPC.1997.601257 · DOI
- ye, 2002, Supporting Reuse by Delivering Taskrelevant and Personalized Information
- 10.1109/ICSM.2005.66 · DOI · Paper page
- singer, 1997, An examination of software engineering work practices, CASCON '97 Proceedings of the 1997 Conference of the Centre for Advanced Studies on Collaborative Research, 21
- 10.1145/502933.502935 · DOI
- o'conaill, 1995, Timespace in the workplace: Dealing with interruptions, CHI '95 Conference companion on Human factors in computing systems, 262, 10.1145/223355.223665 · DOI · Paper page
- 10.1147/sj.52.0078 · DOI · Paper page
- 10.1145/170035.170072 · DOI · Paper page
- 10.1145/1052898.1052912 · DOI · Paper page
- 10.1145/142750.142751 · DOI · Paper page
- 10.1145/633292.633383 · DOI
- 10.1145/325737.325796 · DOI · Paper page
- 10.1145/502585.502607 · DOI · Paper page
- 10.1145/1101908.1101949 · DOI · Paper page
Cited by
Resumption strategies for interrupted programming tasks
Parnin, C., & Rugaber, S. (2011) · Software Quality Journal · doi:10.1007/s11219-010-9104-9 · Cited by 103
Self-citationAn Information Foraging Theory Perspective on Tools for Debugging, Refactoring, and Reuse Tasks
Fleming, S. D., Scaffidi, C., Piorkowski, D., Burnett, M., Bellamy, R., Lawrance, J., & Kwan, I. (2013) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2430545.2430551 · Cited by 79
Evaluating Cues for Resuming Interrupted Programming Tasks
Parnin, C., & DeLine, R. (2010) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753342 · Cited by 60
Self-citationCharacterizing and Understanding Development Sessions
Robbes, R., & Lanza, M. (2007) · 15th IEEE International Conference on Program Comprehension (ICPC '07) · doi:10.1109/icpc.2007.12 · Cited by 51
“[11] but it has not been implemented yet, and their later work in [10] only uses IDE interactions.”
BackgroundPiorkowski, D., Fleming, S., Scaffidi, C., Bogart, C., Burnett, M., John, B., Bellamy, R., & Swart, C. (2012) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/2207676.2208608 · Cited by 50
“Developers also frequently navi-gated between locations in code, revisiting places to learn about structural relationships [19, 26].”
BackgroundMethodInfluential
Metadata
- Authors
- Parnin, C., & Gorg, C.
- Venue
- 14th IEEE International Conference on Program Comprehension (ICPC'06)
- Publisher
- IEEE
- Published
- 2006-07-10
- Pages
- 13-22
- OpenAlex
- W2150601094
- Cited by
- 76
- References
- 2
- FWCI
- 3.33
- Type
- conference paper
- Language
- en
- Open access
- closed
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
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.