A greedy approach to object identification in imperative code

The benefits of such recent innovations as object-oriented programming are not realized in most systems currently in use because they are, on average, over 10 years old. Additionally, they suffer from extensive maintenance. The paper addresses these concerns in the context of reverse engineering. It discusses the development of a method to identify objects in imperative code, specifically FORTRAN-77. An algorithm that uses a greedy approach to object extraction is presented. The imperative code is analyzed at the subroutine level and, using the concepts of graph theory, a set of objects is generated.<<ETX>>

[1]  Aniello Cimitile,et al.  A reverse engineering method for identifying reusable abstract data types , 1993, [1993] Proceedings Working Conference on Reverse Engineering.

[2]  Bhanu Prasad Pokkunuri.  Object Oriented Programming , 1989, SIGP.

[3]  Betty H. C. Cheng,et al.  A Two-Phase Approach to Reverse Engineering Using Formal Methods , 1993, Formal Methods in Programming and Their Applications.

[4]  Chap-Liong Ong.  Class and object extraction from imperative code , 1994 .

[5]  J. A. Zimmer.  Restructuring for style , 1990, Softw. Pract. Exp..

[6]  Richard C. Waters,et al.  Reverse engineering: progress along many dimensions , 1994, CACM.

[7]  James H. Cross,et al.  Reverse engineering and design recovery: a taxonomy , 1990, IEEE Software.

[8]  Aniello Cimitile,et al.  Experiments in identifying reusable abstract data types in program code , 1993, [1993] IEEE Second Workshop on Program Comprehension.

[9]  Wilma M. Osborne,et al.  Fitting Pieces to the Maintenance Puzzle - Guest Editors' Introduction , 1990, IEEE Softw..

[10]  N. Wilde,et al.  Identifying objects in a conventional procedural language: an example of data design recovery , 1990, Proceedings. Conference on Software Maintenance 1990.

[11]  P. E. Livadas,et al.  Program dependence analysis , 1992, Proceedings Conference on Software Maintenance 1992.