Shimba—an environment for reverse engineering Java software systems

Abstract

Shimba is a reverse engineering environment to support the understanding of Java software systems. Shimba integrates the Rigi and SCED tools to analyze and visualize the static and dynamic aspects of a subject system. The static software artifacts and their dependencies are extracted from Java byte code and viewed as directed graphs using the Rigi reverse engineering environment. The run‐time information is generated by running the target software under a customized SDK debugger. The generated information is viewed as sequence diagrams using the SCED tool. In SCED, statechart diagrams can be synthesized automatically from sequence diagrams, allowing the user to investigate the overall run‐time behavior of objects in the target system. Shimba provides facilities to manage the different diagrams and to trace artifacts and relations across views. In Shimba, SCED sequence diagrams are used to slice the static dependency graphs produced by Rigi. In turn, Rigi graphs are used to guide the generation of SCED sequence diagrams and to raise their level of abstraction. We show how the information exchange among the views enables goal‐driven reverse engineering tasks and aids the overall understanding of the target software system. The FUJABA software system serves as a case study to illustrate and validate the Shimba reverse engineering environment. Copyright © 2001 John Wiley & Sons, Ltd.

Understanding Ajax applications by connecting client and server-side execution traces

“…Typically, there are a lot of those patterns, since programs often contain repetitions, and "execution patterns of iterative behavior rarely justify the space they consume" (Pauw et al 1998). Examples are methods based on string matching (Systä et al 2001), run-length encoding or grammars (Reiss and Renieris 2001), techniques that are borrowed from the signal processing field (Kuhn and Greevy 2006;Zaidman and Demeyer 2004) and approaches that use information from source code (Myers et al 2010). A question that arises when identifying patterns, is how far we should go with generalizing parts of traces to patterns.…”

Visualizing Testsuites to Aid in Software Understanding

“…Summarize recurrent patterns [22,31]. Patterns may be identical or very similar (sets of) method calls.…”

“…Systä et al aid in the understanding of Java systems in an environment called Shimba, which uses both static analysis and dynamic information [31]. The Shimba environment considers static and dynamic information to be complementary and uses static information to bring focus to dynamically generated diagrams, and vice versa.…”

Using compression algorithms to support the comprehension of program traces

“…One of the main comprehension tasks [13] is the task of identifying repeated phases of behaviour -repeated patterns of trace elements such as method calls -that occur at runtime. Such phases indicate cohesive units of functionality that can be used as a basis for investigating the broader behaviour of the program.…”