by Spencer Rugaber, Kurt Stirewalt, Linda M. Wills, I B Le
Encyclopedia of Computer Science and Technology
http://users.ece.gatech.edu/~linda/papers/wcre95-interleaving.pdf
Add To MetaCart
Abstract:
One of the factors that can make a program di cult to understand is that code responsible for accomplishing more than one purpose may be woven together in a single section. We call this interleaving, and it may arise either intentionally { for example, in optimizing aprogram, a programmer may use some intermediate result for several purposes { or unintentionally, due to patches, quick xes, or other hasty maintenance practices. To understand this phenomenon, we have looked at a variety of interleaving instances in actual programs and have distilled characteristic features. If the characterization proves to be robust then it will enable the design of tools for detection of interleavings and the extraction of the individual strands of computation. 1 1
Citations
|
908
|
Program slicing
– Weiser
- 1984
|
|
112
|
The Programmer's Apprentice
– Rich, Waters
- 1990
|
|
111
|
Program understanding and the concept assignment problem
– Biggerstaff, Mitbander, et al.
- 1994
|
|
108
|
An Intelligent Tool for Reengineering Software Modularity
– Schwanke
|
|
95
|
Structured Design: Fundamentals of a Discipline of Computer
– Yourdon, Constantine
- 1979
|
|
86
|
System Structure Analysis: Clustering with Data Bindings
– Hutchens, Basili
- 1985
|
|
70
|
Design Maintenance Systems
– Baxter
- 1992
|
|
68
|
Computer Methods for Mathematical Computations
– Forsythe, Moler
- 1977
|
|
62
|
A memory-based approach to recognizing programming plans
– Quilici
- 1994
|
|
59
|
Automated support for legacy code understanding
– Ning, Engberts, et al.
- 1994
|
|
56
|
E.Soloway. Delocalized plans and program comprehension
– Letovsky
- 1986
|
|
52
|
Automated Program Recognition by Graph Parsing
– Wills
- 1992
|
|
46
|
Intention-Based Diagnosis of Novice Programming Errors
– Johnson
- 1986
|
|
35
|
Understanding and documenting programs
– Basili, Mills
- 1982
|
|
31
|
Reliable Software through Composite Design
– Myers
- 1975
|
|
28
|
Recognizing design decisions in programs
– Rugaber, Ornburn, et al.
- 1990
|
|
24
|
A method for analyzing loop programs
– Waters
- 1979
|
|
23
|
A reverse engineering method for identifying reusable abstract data types
– Canfora, Cimitile, et al.
- 1993
|
|
23
|
Discovering, visualizing, and controlling software structure
– Schwanke, Altucher, et al.
- 1989
|
|
21
|
Automated support for encapsulating abstract data types
– Bowdidge, Griswold
- 1994
|
|
20
|
Automated program understanding by concept recognition
– Kozaczynski, Ning
- 1994
|
|
20
|
Inspection methods in programming
– Rich
- 1980
|
|
18
|
Plan analysis of programs
– Letovsky
- 1988
|
|
17
|
Automatic Control Understanding for Natural Programs
– Hartman
- 1990
|
|
17
|
A formal representation for plans in the Programmer’s Apprentice
– Rich
- 1981
|
|
8
|
Program improvement by automatic redistribution of intermediate results: An overview
– Hall
- 1991
|
|
7
|
Program comprehension through the identification of abstract data types
– Cimitile, Tortorella, et al.
- 1994
|
|
5
|
Challenges to the field of reverse engineering -- A position paper
– Selfridge, Waters, et al.
- 1993
|
|
4
|
Potpourri module detection
– Calliss, Cornelius
- 1990
|
|
2
|
Challenges to the eld of reverse engineering | a position paper
– Selfridge, Waters, et al.
- 1993
|
|
1
|
Reliable Sojtware through Composite Design. Petrocelli Charter
– Myers
- 1975
|
|
1
|
The Programmer’s ilpPrentice
– Rich, Waters
- 1990
|
