Answers are grounded in this paper and cite their sources.
The authors introduce an object-oriented model of software that is derived semiautomatically from the actual code. The model and its associated object methods are used to support basic tasks required during software maintenance. The object-oriented model provides a series of successively more abstract views of the code structure. Object methods provide an approximation to the functionality (specification) of the software as well as a two-way map between the functionality and the code structures. Object methods also provide the means of detailed connectivity analysis associated with the ripple effect and program-slicing types of activities during maintenance.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
No takes yet. Share an insight, caveat, or question.
Heisler et al. (2003) studied this question.
Synapse has enriched one closely related paper. Consider it for comparative context: