Program and interface slicing for reverse engineering
Authors:
- 30 December 2002
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 02705257,p. 509-518
Abstract
A case is presented for the use of conventional and interface slicing as enabling mechanisms for numerous reverse engineering and reengineering tasks. The authors first discuss the applicability of conventional slicing to algorithm extraction and design recovery at statement-level granularity. They then present interface slicing and show how it provides similar capabilities at module-level granularity. Module is a general term for a collection of subprograms, possibly with information hiding mechanisms: It includes but is not limited to Ada packages. Component refers to a module in a reuse repository. A component is thus a code asset of a repository, possibly also incorporated into a program. Ada is used for the example, as Ada's features facilitate the types of transformations which are invoked.<>Keywords
This publication has 15 references indexed in Scilit:
- Program and interface slicing for reverse engineering2002
- An integrated program representation and toolkit for the maintenance of C programs2002
- Concept recognition-based program transformation2002
- Using program slicing in software maintenanceIEEE Transactions on Software Engineering, 1991
- Contracts: specifying behavioral compositions in object-oriented systems1990
- Interprocedural slicing using dependence graphsACM Transactions on Programming Languages and Systems, 1990
- Reverse engineering and design recovery: a taxonomyIEEE Software, 1990
- Integrating non-intering versions of programs1988
- The program dependence graph and its use in optimizationACM Transactions on Programming Languages and Systems, 1987
- Program SlicingIEEE Transactions on Software Engineering, 1984