Reverse engineering of object oriented code.
It is not only with the legacy programs of the 60s and 70s typically coded in Fortran but also now and certainly more in the future with object-oriented programs of the 80s up. The lifecycle involves not only traditional maintenance, at some time a thorough re-design may become necessary when too many small or bigger modifications and add-ons are no more manageable. Following a maintenance phase of, say, 15 years, a re-design phase may occur. If design documentation has not been accurately updated, at first a reverse engineering phase is required. The monograph at hand is a well-written, well-structured guide for reverse engineering of complex object-oriented programs, i.e., for extracting original design specifications as far as possible in a form easily understandable by a re-designer team. The Unified Modelling Language chosen here, UML, offers itself as a well-chosen graphically supported specification means. Following the UML approach, by analysing available program code to be reverse engineered, the authors clearly describe analysis methods and develop algorithms leading to an ``Object Flow Graph, a ``Class Diagram, ``Object Diagram, ``Interaction Diagrams, ``State Diagrams, and a ``Package Diagram. The notation follows standard UML, however is open for alternate formalisms. Each of the six chapters covering their methods and algorithms begin with a chapter outline and end with a section about related work showing detailed relations to published work in the respective area. After presenting a method and/or algorithm you will find sandwiched in intersections mainly taken from a rather elaborated example program (library management) coded in Java. A change request to this example program, adding a reservation mechanism for borrowing a book out of the library, is discussed in the final chapter proving the practicability and usability of their work in reverse engineering for preparing a redesign phase. The authors emphasize static analysis approaches using program code. Results are general findings, then. To exhibit behaviour in special cases they extend their methods and algorithms for dynamic analysis, too. For a reader it is very helpful to document the analysis results in similar diagrams as for the static approaches. 100+ literature references at the end of the book demonstrate the deep research and strong know-how of the authors and make the book a valuable monographic textbook for reverse engineering courses of object-oriented programs. (A hint if a reprint would be considered: The programming languages ``C and ``Java are written with capital letters, refs. 18, 57, 60, 68, and 96!) The book has a foreword by Harry Sneed, the well-known, not to say famous, software engineering guru (and by Prof. Aniello Cimitile): In my opinion, in high-level academic monographs published by Springer, one should write in correct English/American English, ``through, not in a slang ``thru (line 5 of the Foreword).
- Classes extraction from procedural programs
- A framework for memory efficient context-sensitive program analysis
- Modeling and visualizing object-oriented programs with Codecharts
- A tool chain for reverse engineering C++ applications
- Codecharts. Roadmaps and blueprints for object-oriented programs. With contributions from Jonathan Nicholson
- Understanding existing software with use case map scenarios
- scientific article; zbMATH DE number 1486664 (Why is no real title available?)
- scientific article; zbMATH DE number 1790637 (Why is no real title available?)
- Graph-based tools for re-engineering
- Shimba-an environment for reverse engineering Java software systems
- scientific article; zbMATH DE number 783540 (Why is no real title available?)
This page was built for publication: Reverse engineering of object oriented code.
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q4658275)