The DOI matches its Crossref record; 36 of the 36 references it cites were found in a registry or an index.
How effective developers investigate source code: an exploratory study
Abstract
Prior to performing a software change task, developers must discover and understand the subset of the system relevant to the task. Since the behavior exhibited by individual developers when investigating a software system is influenced by intuition, experience, and skill, there is often significant variability in developer effectiveness. To understand the factors that contribute to effective program investigation behavior, we conducted a study of five developers performing a change task on a medium-size open source system. We isolated the factors related to effective program investigation behavior by performing a detailed qualitative analysis of the program investigation behavior of successful and unsuccessful developers. We report on these factors as a set of detailed observations, such as evidence of the phenomenon of inattention blindness by developers skimming source code. In general, our results support the intuitive notion that a methodical and structured approach to program investigation is the most effective.
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
(1984) · Cited by 81,983
Case study research: design and methods
Phelan, S. (2011) · Evaluation & Research in Education · doi:10.1080/09500790.2011.582317 · Cited by 21,763
Hartley, J. (2004) · Essential Guide to Qualitative Methods in Organizational Research · doi:10.4135/9781446280119.n26 · Cited by 15,461
Mack, A., & Rock, I. (1998) · The MIT Press eBooks · doi:10.7551/mitpress/3707.001.0001 · Cited by 1,593
Qualitative methods in empirical studies of software engineering
Seaman, C. B. (1999) · IEEE Transactions on Software Engineering · doi:10.1109/32.799955 · Cited by 1,493
Program Evolution: Processes of Software Change
Lehman, M. M., & Belady, L. A. (1985) · CERN Document Server (European Organization for Nuclear Research) · Cited by 809
SMALLTALK-80: the interactive programming environment
Goldberg, A. (1984) · HAL (Le Centre pour la Communication Scientifique Directe) · Cited by 718
Parnas, D. L. (1994) · doi:10.5555/257734.257788 · Cited by 655
Does code decay? Assessing the evidence from change management data
Eick, S. G., Graves, T. L., Karr, A. F., Marron, J. S., & Mockus, A. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895984 · Cited by 636
Experimentation in software engineering
Basili, V. R., Selby, R. W., & Hutchens, D. H. (1986) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1986.6312975 · Cited by 553
Cited by
Ko, A. J., Myers, B. A., Coblenz, M. J., & Aung, H. H. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.116 · Cited by 685
The state of the art in end-user software engineering
Ko, A. J., Abraham, R., Beckwith, L., Blackwell, A., Burnett, M., Erwig, M., Scaffidi, C., Lawrance, J., Lieberman, H., Myers, B., et al. (2011) · ACM Computing Surveys · doi:10.1145/1922649.1922658 · Cited by 633
Feature location in source code: a taxonomy and survey
Dit, B., Revelle, M., Gethers, M., & Poshyvanyk, D. (2013) · Journal of Software: Evolution and Process · doi:10.1002/smr.567 · Cited by 583
Poshyvanyk, D., Gueheneuc, Y.-G., Marcus, A., Antoniol, G., & Rajlich, V. (2007) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.1016 · Cited by 469
How are Java software developers using the Eclipse IDE?
Murphy, G. C., Kersten, M., & Findlater, L. (2006) · IEEE Software · doi:10.1109/ms.2006.105 · Cited by 413
Self-citationCataldo, M., Wagstrom, P. A., Herbsleb, J. D., & Carley, K. M. (2006) · Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work · doi:10.1145/1180875.1180929 · Cited by 400
Automatic generation of natural language summaries for Java classes
Moreno, L., Aponte, J., Sridhara, G., Marcus, A., Pollock, L., & Vijay-Shanker, K. (2013) · 2013 21st International Conference on Program Comprehension (ICPC) · doi:10.1109/icpc.2013.6613830 · Cited by 331
Asking and Answering Questions during a Programming Change Task
Sillito, J., Murphy, G. C., & De Volder, K. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2008.26 · Cited by 319
Self-citationQuestions programmers ask during software evolution tasks
Sillito, J., Murphy, G. C., & De Volder, K. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181779 · Cited by 270
Self-citationProgramming, Problem Solving, and Self-Awareness: Effects of Explicit Guidance
Loksa, D., Ko, A. J., Jernigan, W., Oleson, A., Mendez, C. J., & Burnett, M. M. (2016) · Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems · doi:10.1145/2858036.2858252 · Cited by 223
On the Comprehension of Program Comprehension
Maalej, W., Tiarks, R., Roehm, T., & Koschke, R. (2014) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2622669 · Cited by 180
Subjective evaluation of software evolvability using code smells: An empirical study
Mäntylä, M. V., & Lassenius, C. (2007) · Empirical Software Engineering · doi:10.1007/s10664-006-9002-8 · Cited by 171
Code bubbles: a working set-based interface for code understanding and maintenance
Bragdon, A., Zeleznik, R., Reiss, S. P., Karumuri, S., Cheung, W., Kaplan, J., Coleman, C., Adeputra, F., & LaViola, J. J. (2010) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753706 · Cited by 174
How Programmers Debug, Revisited: An Information Foraging Theory Perspective
Lawrance, J., Bogart, C., Burnett, M., Bellamy, R., Rector, K., & Fleming, S. D. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.111 · Cited by 142
An 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
Using information scent to model the dynamic foraging behavior of programmers in maintenance tasks
Lawrance, J., Bellamy, R., Burnett, M., & Rector, K. (2008) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1357054.1357261 · Cited by 76
“For example, Robillard et al. studied navigation qualitatively with a controlled experiment of 5 graduate student developers [24], from which they derived a descriptive theory.”
BackgroundMethodThe Emergent Structure of Development Tasks
Murphy, G. C., Kersten, M., Robillard, M. P., & Čubranić, D. (2005) · Lecture Notes in Computer Science · doi:10.1007/11531142_2 · Cited by 69
“In our work, we have found that this crosscutting structure emerges from how a developer works with the code base [19, 10].”
BackgroundSelf-citationWhat distinguishes great software engineers
Li, P. L., Ko, A. J., & Begel, A. (2020) · Empirical Software Engineering · doi:10.1007/s10664-019-09773-y · Cited by 48
Stacksplorer: call graph navigation helps increasing code maintenance efficiency
Karrer, T., Krämer, J.-P., Diehl, J., Hartmann, B., & Borchers, J. (2011) · Proceedings of the 24th annual ACM symposium on User interface software and technology · doi:10.1145/2047196.2047225 · Cited by 48
Developers' code context models for change tasks
Fritz, T., Shepherd, D. C., Kevic, K., Snipes, W., & Bräunlich, C. (2014) · Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2635868.2635905 · Cited by 45
The Influence of the Task on Programmer Behaviour
Ying, A. T. T., & Robillard, M. P. (2011) · 2011 IEEE 19th International Conference on Program Comprehension · doi:10.1109/icpc.2011.35 · Cited by 41
Self-citationForaging and navigations, fundamentally: developers' predictions of value and cost
Piorkowski, D., Henley, A. Z., Nabi, T., Fleming, S. D., Scaffidi, C., & Burnett, M. (2016) · Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2950290.2950302 · Cited by 38
Navigating software development in the ChatGPT and GitHub copilot era
France, S. L. (2024) · Business Horizons · doi:10.1016/j.bushor.2024.05.009 · Cited by 38
Focus-shifting patterns of OSS developers and their congruence with call graphs
Xuan, Q., Okano, A., Devanbu, P., & Filkov, V. (2014) · Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2635868.2635914 · Cited by 27
Inference of development activities from interaction with uninstrumented applications
Bao, L., Xing, Z., Xia, X., Lo, D., & Hassan, A. E. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9547-8 · Cited by 25
Borrowing from the Crowd: A Study of Recombination in Software Design Competitions
LaToza, T. D., Chen, M., Jiang, L., Zhao, M., & Hoek, A. V. D. (2015) · 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering · doi:10.1109/icse.2015.72 · Cited by 23
A Practical Guide to Analyzing IDE Usage Data
Snipes, W., Murphy-Hill, E., Fritz, T., Vakilian, M., Damevski, K., Nair, A. R., & Shepherd, D. (2015) · The Art and Science of Analyzing Software Data · doi:10.1016/b978-0-12-411519-4.00005-7 · Cited by 14
Metadata
- Authors
- Robillard, M. P., Coelho, W., & Murphy, G. C.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2004-12
- Volume
- 30
- Issue
- 12
- Pages
- 889-903
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2099571428
- Cited by
- 260
- References
- 36
- FWCI
- 35.29
- Type
- journal article
- 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.