SEKE 2012 Proceedings - Knowledge Systems Institute

Analysis method plug-in Unique identifier of the plug -in in Eclipse
identifier
platform
Type of extension point The type of extension point associated with the
action
Plug-in action class The class for invocation of an action
Command structure The abstracted structure for generating
concrete command
The integrator provides the integration definition in the user
interface, as s hown in Fig. 3. The analysis method name is
“JDepend”. Its required input is of the type
“IPackageFragmentRoot(binary files)” for Java application.
To integrate JDepend implemented as Eclipse plug-in, our
framework provides facility to ease the definition specification.
If the integrator provides t he analyzer implementation, our
framework interprets the plug-in configuration file and lists all
the actions as analysis method candidates. The JDepend plug-in
includes only one analysis method candidate, as shown in Fig.
3. The integrator can add the definition by selecting the
JDepend analysis method or inputting the definition directly.
Its extension type is “popupmenu”. The action class name is
“de.loskutov.eclipse.jdepend.actions.ShowDependecy”.
To integrate JDepend analyzer with command line interface,
we refer to its documents and find that its command follows the
syntax “java j depend.xmlui.JDepend [-components
] [-file ] [directory2
[directory 3] ...] ”. By abstracting its input and output, one of
the running mode of JDepend command structure is defined as
“java jdepend.xmlui.JDepend -file #OUTPUT# #INPUT#”.
UI for analysis method selection
Figure 3. User interface for integration sepecification and selection of
analysis method in Eclipse plug-in analyzer
(2) Using an integrated analysis method
The user plan to analyze the software project Log4j [10].
Log4j is an open source project of the Apache Software
Foundation. Log4j enables logging at runtime without
modifying the application binary so as to avoid a heavy
performance cost for logging. The artifacts of Log4j contain
about 20000 lines of source code and 188 classes.
Because the artifacts of Log4j do not contain a so ftware
model, our framework first generates a UML model based on
the source code of Log4j using a reverse tool EclipseUML [21].
We build a tree view of the UML model in our framework. The
user selects the whole project as analysis object in the tree view
of the Log4j U ML model. The integration definition of an
analysis method is saved in an XML file. The integration
definitions form a repository of reusable analysis methods.
Based on the integration definitions, our framework provides a
list of integrated analysis methods for the analysis method
users. The user interface for selecting analysis object and
analysis method is shown in Fig. 4.
Figure 4. User interface for analysis object and analysis method selection
Our framework accepts UML model elements and maps the
input to the artifact set IJavaProject of Log4j project. Because
the required input of JDepend is an IPackageFragmentRoot
folder holding binary files, our framework breadth-first
searches IPackageFragmentRoot in the project and find two
folders: “src” folder holding source code and “bi n” folder
holding binary files. The “bin” f older is the proper analysis
input. Our framework invokes the analyzers with the adapted
inputs. For analysis method with one analyzer implementation,
our framework runs the analyzer by default. For analysis
method with two analyzer implementations, user can select to
run one or two analyzer implementations.
The user selects to run two JDe pend analyzer
implementations. Our framework first pre pares proper inputs
for analyzers. The inpu t of plug-in analyzer is an object with
“IFolder” interface representing the IPackageFragmentRoot
folder “bin” in Eclipse workspace. The input of analyzer with
command line interface is the folder location. After invocation
of the plug-in analyzer, the command for analyzing the Log4j
is triggered and the analysis results are shown in the graphical
user interface. For the a nalyzer with co mmand line interface,
our framework generates a concrete command “java
jdepend.xmlui.JDepend
-file
C:\log4j\AnalyticalResult\JDepend_bin_20111223161327.xml
C:\log4j\bin” automatically when the log4j project locates at
C:\log4j. Our framework uses runtime class to create a c hild
process for command execution.
Analysis Input:
log4j/bin/
ResultMap.xml
Figure 5. The traceability recording process
Analysis Result:
JDepend_bin_20111223161327.xml
In the input adaptation and analyzer execution stage, our
framework saves tr aceability information to dedu ce the
relationship between UML elements and analysis results. The
relationship between the element “project” in the UML m odel
and the analysis result file generated by JDepend is saved in an
XML file “ResultMap.xml”. The process is shown in Fig. 5.
Our framework extends the UML model with th e JDepend
analysis result. The user can interpret the analysis results in the
215