Journal of Software Maintenance Research and Practice · 1995 · 376 citations · 13 references
ComputingComputer ScienceFeature EngineeringRequirements EngineeringSoftware EngineeringComponent-based Software EngineeringRequirements TraceabilitySoftware MaintenanceSoftware TestingStatic Code AnalysisAutomated Bug FindingCode TraceabilityReconnaissanceReconnaissance TechniquesSoftware TraceabilityTest CasesTest CoverageTraceability In Software Engineering
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.
13
Programmers use slices when debugging
Mark Weiser · Communications of the ACM · 1982 · 762 citations · Full text
Delocalized Plans and Program Comprehension
Stanley Letovsky, Elliot Soloway · IEEE Software · 1986 · 246 citations
A formal evaluation of data flow path selection criteria
Lori A. Clarke, Andy Podgurski, Debra J. Richardson et al. · IEEE Transactions on Software Engineering · 1989 · 225 citations · Full text
Designing documentation to compensate for delocalized plans
Elliot Soloway, Robin Lampert, Stan Letovsky et al. · Communications of the ACM · 1988 · 201 citations · Full text
Computing, Design, Documentation +9
Mental models and software maintenance
David Littman, Jeannine Pinto, Stanley Letovsky et al. · 1986 · 165 citations