Extracting reusable functions by flow graph based program slicing

An alternative approach to developing reusable components from scratch is to recover them from existing systems. We apply program slicing, a program decomposition method, to the problem of extracting reusable functions from ill structured programs. As with conventional slicing first described by M....

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering 1997-04, Vol.23 (4), p.246-259
Main Authors: Lanubile, F., Visaggio, G.
Format: Article
Language:English
Subjects:
Applied sciences
Code reuse
Computer science
control theory
systems
Computer Society
Data mining
Data models
Decomposition
Equations
Exact sciences and technology
Flow graphs
Input variables
Legacy systems
Programming profession
Reverse engineering
Software
Software engineering
Software quality
Software reusability
Software systems
Studies
Transforms
Variables
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:An alternative approach to developing reusable components from scratch is to recover them from existing systems. We apply program slicing, a program decomposition method, to the problem of extracting reusable functions from ill structured programs. As with conventional slicing first described by M. Weiser (1984), a slice is obtained by iteratively solving data flow equations based on a program flow graph. We extend the definition of program slice to a transform slice, one that includes statements which contribute directly or indirectly to transform a set of input variables into a set of output variables. Unlike conventional program slicing, these statements do not include either the statements necessary to get input data or the statements which test the binding conditions of the function. Transform slicing presupposes the knowledge that a function is performed in the code and its partial specification, only in terms of input and output data. Using domain knowledge we discuss how to formulate expectations of the functions implemented in the code. In addition to the input/output parameters of the function, the slicing criterion depends on an initial statement, which is difficult to obtain for large programs. Using the notions of decomposition slice and concept validation we show how to produce a set of candidate functions, which are independent of line numbers but must be evaluated with respect to the expected behavior. Although human interaction is required, the limited size of candidate functions makes this task easier than looking for the last function instruction in the original source code.
ISSN:0098-5589
1939-3520
DOI:10.1109/32.588543