The DOI matches its Crossref record; 8 of the 8 references it cites were found in a registry or an index.
Software reconnaissance: Mapping program features to code
Abstract
Maintainers of old code often need to discover where particular program features are implemented. This paper presents a method, called ‘software reconnaissance’ for answering this question through an analysis of the execution of different test cases. The method is quite easy to implement, requiring only a test coverage monitor, some simple tools, and a surprisingly small number of test cases. A statistical case study is presented that shows the kind of results that can be obtained on a typical medium‐sized program. The method seems to be effective in identifying a small number of code components that are unique to a particular program feature, though it may not find all components that make up the feature's delocalized plan. A small protocol case study shows that professional programmers can learn to use the method quickly and can use the information that it produces. Software reconnaissance may be a simple but useful addition to the maintainer's tool kit in that it provides starting points for understanding a large program and a way of recovering some requirements traceability information from old code. For the researcher, it also provides a novel functionality ‘view’ of software that maps features to program components at different levels of precision.
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
Programmers use slices when debugging
Weiser, M. (1982) · Communications of the ACM · doi:10.1145/358557.358577 · Cited by 761
Delocalized Plans and Program Comprehension
Letovsky, S., & Soloway, E. (1986) · IEEE Software · doi:10.1109/ms.1986.233414 · Cited by 245
A formal evaluation of data flow path selection criteria
Clarke, L. A., Podgurski, A., Richardson, D. J., & Zeil, S. J. (1989) · IEEE Transactions on Software Engineering · doi:10.1109/32.41326 · Cited by 222
Designing documentation to compensate for delocalized plans
Soloway, E. M., Lampert, R., Letovsky, S., Littman, D., & Pinto, J. (1988) · Communications of the ACM · doi:10.1145/50087.50088 · Cited by 192
Mental models and software maintenance
Littman, D., Pinto, J., Letovsky, S. I., & Soloway, E. M. (1986) · Cited by 163
From program comprehension to tool requirements for an industrial environment
von Mayrhauser, A., & Vans, A. M. (2002) · IEEE International Conference on Program Comprehension (ICPC) · doi:10.1109/wpc.1993.263903 · Cited by 95
Control flow and data structure documentation
Shneiderman, B. (1982) · Communications of the ACM · doi:10.1145/358315.358391 · Cited by 54
Software debugging with dynamic instrumentation and test-based knowledge
Pan, H. (1993) · Cited by 13
Cited by
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
Locating features in source code
Eisenbarth, T., Koschke, R., & Simon, D. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1183929 · Cited by 554
An information retrieval approach to concept location in source code
Marcus, A., Sergeyev, A., Rajlich, V., & Maletic, J. I. (2005) · 11th Working Conference on Reverse Engineering · doi:10.1109/wcre.2004.10 · Cited by 455
A Systematic Survey of Program Comprehension through Dynamic Analysis
Cornelissen, B., Zaidman, A., van Deursen, A., Moonen, L., & Koschke, R. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.28 · Cited by 420
Software Architecture Reconstruction: A Process-Oriented Taxonomy
Ducasse, S., & Pollet, D. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.19 · Cited by 360
Metadata
- Authors
- Wilde, N., & Scully, M. C.
- Venue
- Journal of Software Maintenance: Research and Practice
- Publisher
- Wiley
- Published
- 1995-01
- Volume
- 7
- Issue
- 1
- Pages
- 49-62
- ISSN
- 1040-550X (ISSN-L)
- 1096-908X
- OpenAlex
- W2121234902
- Cited by
- 373
- References
- 8
- FWCI
- 5.23
- 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.