Reverse engineering involves a great deal of effort in comprehension of the current implementation of a software system and the ways in which it differs from the original design. Automated support tools are critical to the success of such efforts. We show how program slicing techniques can be employed to assist in the comprehension of large software systems, through traditional slicing techniques at the statement level, and through a new technique, interface slicing, at the module level. 1

Locating bugs is one of the most time-consuming tasks in debugging. Though external resources, such as explicit knowledge bases or formal specifications, can reduce the debugging time, this information either may not be readily available or may be too limited for real-world software. So in general, most debuggers try to reduce the time by providing analysis tools for the programmer to reduce the search space for bugs and to guess at the bug type, location, or both. We review the current state-of-the-art in debugging and point out three shortcomings that deserve more attention. First, the programmer has to perform the analysis and keep track of the results himself while he tries to locate faults. Second, the programmer needs (but lacks) automated decision support to help him evaluate program behavior as he tries to reduce the search space for bugs. Third, the debuggers that support fault location guessing do not point out the statements most likely to be faulty. Our objective is to redu...

Software reverse engineering is a crucial task to reconstruct high-level views of a software system—with the purpose of understanding and/or maintaining it—when the only reliable source of information is the source code, or even the system binaries. This paper discusses key reverse engineering concepts through a UML conceptual model. Specifically, the model is composed of a set of UML class diagrams describing relationships existing among reverse engineering processes, tools, artifacts, and stakeholders. 1

Abstract not found