Download PDF C++ Reverse Engineering

Sinopsis

The primary purpose of reversing C++ code is to look at the structure of the classes from an analysis and design perspective. When you reverse C++ code using GDPro a new system is created with two views, the view describing the classes is an Class Model view and the other is the Implementation Model view. When GDPro reverses C++ classes, the information about each class attribute is complete and there is no loss of any class information. Embedded information within the C++ class is maintained in the class object on the diagram. In this manner, all implementation details, those details that are not supported by a methodology, are stored for later use by code generation.

The Implementation Model is used to provide the second view that is generated when some C++ code is reverse engineered. It is a model used to represent all the files used in a reversed system. This includes both user and system include files. This model is used to provide support for seamless generation of C++ code from the system, minimizing adverse changes to the reversed code.

The Implementation Model represents all the files for a system in a hierarchical, left to right layout. For example, you can have a single C++ file representing a piece of legacy code. This file might include a single header file. That header file, however, can include quite a large number of files, one doesn’t really know until they examine the include structure. GDPro reverse engineering follows these includes and track them completely, showing you the resultant include hierarchy on an Implementation Model view. The Implementation Model does more than show a file hierarchy, it also holds all the non-class related information needed to regenerate the code. For example, each file object in this model stores what classes were generated from it enabling code generation to generate code for the classes back into the same files.

Click here to download