SEKE 2012 Proceedings - Knowledge Systems Institute

ified from this path to determine the test’s Result, in which
each criterion has its own standard to verify whether the test
has been completely or partially met. The instrumentation
sends to the tool, during a test execution, information about
each visited portion of code. This information is stored to
be used in each visual representation. By these two analysis
steps (static and dynamic analyses), the tool gathers data to
generate visual representations [7].
At Control layer, the data obtained from Reading Module
(to generate visual presentations – all presentations are
generated at the same time) are organized by the Integration
Module, which provides mechanisms to coordinate the
visualizations. These mechanisms capture user interactions
in visual presentations to reflect the related events into another
view. From each captured event, caused by an user interaction
in a specific visualization, the Integration Module
obtains data about the selected program unit (class, method,
aspect or advice). An event is then sent to the Visualization
layer, informing the new visual representation state (i.e.,
highlighted items), performing, this way, the coordination,
using the data structures stored in the Dataset layer (i.e., the
list containing information provided by the instrumentation,
the hierarchical structure, the node and edge tables and the
graph data structure).
The Visualization layer is responsible for providing
CFG, TreeMap and Hyperbolic visual presentations, highlighting
AOP features (i.e., aspects and its crosscuts) depending
on the visualization in question. This layer receives
data from the Control layer (i.e., events captured from user
interactions and data obtained from the Dataset layer) to
generate and update each visual representation.
From the working together of these three layers, the developed
Software Visualization tool uses the proposed coordinated
visual mapping to visualize Java and AspectJ compiled
programs. The next section presents an application
and descriptions of the coordinated multiple views from
SoftV iz OAH .
(a) Hyperbolic projection
(b) Treemap visualization
4 Applications
In this section we show an application of SoftV iz OAH :
we performed a visual exploration of the Aspect-Oriented
program of an on-line music store simulation, coded in AspectJ
by Lesiecki [16].
Figure 4(b) shows a Control Flow Graph visual representation
used to present methods, advices or test case executions.
In this visual representation, basic code blocks
are represented by rectangles outlined by a continuous line;
code blocks advised by aspects (advices) are represented by
rectangles outlined by a dashed line; the respective pointcuts
are represented by the advice sequence in the graph;
and method returns are represented by rectangles outlined
by a double line. Inside each rectangle a number indi-
(c) List of Methods/Advices
Figure 3. Coordination from Hyperbolic to
TreeMap view and Methods/Advices List
cates the code block execution sequence. Normal code sequences
are represented by continuous lines, and automatic
generated code sequence (as exceptions) are represented by
dashed lines. When a test case is applied, each rectangle is
171