Reverse Engineering using UML Graph

Reverse Engineering using UML Graph

I have been on several teams where we studiously designed UML diagrams at the beginning of the project. As the project progressed, and deadlines approached,

the UML diagrams were left somewhere behind, not to be updated in months. When a new developer joined the team, we showcased the old UML diagrams,

and kept telling “Oh, we never had time to update them, please see the source code to get an idea. And, don’t hesitate to ask if you have any doubt’s”.

I am sure, you all have gone through the same scenario.

However, we don’t have to keep making up stories anymore, since this article shows how easy and simple it is to include UML diagrams

within your Javadoc and also keep them updated with every change in the source code repository. We can do these in less than a few minutes,

and in a few simple steps.

Getting started with UmlGraph takes five steps:

  1. Download the source code for UMlGraph.
  2. Download and install Graphviz.
  3. Make changes to your Ant build file.
  4. Run the Ant target.
  5. Add this target to your CI job.

Step 1: Download the source code for UMLGraph from here. Unzip the contents. To compile the Java doclet from the source code run

ant on the build.xml file. Copy the UmlGraph.jar file to your projects library. If there is a version mismatch between the different versions

of JDK you are using you get an exception like this:

java.lang.UnsupportedClassVersionError: Bad version number in .class file

Make sure you recompile the UMLGraph source code, and copy the library to your project.

Step2 : Download and install Graphviz from
here. The dot file needs to be post-processed with Graphviz to produce the actual UML diagram.

Running the UmlGraph doclet will generate a Graphviz diagram specification that can be automatically processed to create png drawings.

You can also generate other formats using Graphviz as well. If Graphviz isn’t installed you will get an exception as shown below:

Execute failed: dot: not found
Total time: 269 milliseconds

Step 3. Changes to your build.xml file.
Assuming you already have a working project, with Ant build file. Add the following target to your build.xml file as shown below:

view plaincopy to clipboardprint?

  1. <target name=“javadocs” depends=“build” description=“generates javadoc and also UML Diagram”>
  2. <mkdir dir=“${reports.dir}/javadoc”/>
  3. <javadoc sourcepath=“${src.dir}” packagenames=“com.stelligent.*” destdir=“${reports.dir}/javadoc”
  4. classpathref=“java.classpath” private=“true”>
  5. <doclet name=“org.umlgraph.doclet.UmlGraphDoc”
  6. path=“lib/UMLGraph.jar”>
  7. <param name=“-attributes” />
  8. <param name=“-operations” />
  9. <param name=“-qualify” />
  10. <param name=“-types” />
  11. <param name=“-visibility” />
  12. </doclet>
  13. </javadoc>
  14. <apply executable=“dot” dest=“${reports.dir}” parallel=“false”>
  15. <arg value=“-Tpng”/>
  16. <arg value=“-o”/>
  17. <targetfile/>
  18. <srcfile/>
  19. <fileset dir=“${reports.dir}” includes=“*.dot”/>
  20. <mapper type=“glob” from=“*.dot” to=“*.png”/>
  21. </apply>
  22. </target>

<target name=”javadocs” depends=”build” description=”generates javadoc and also UML Diagram”>
<mkdir dir=”${reports.dir}/javadoc”/>
<javadoc sourcepath=”${src.dir}” packagenames=”com.stelligent.*” destdir=”${reports.dir}/javadoc”
classpathref=”java.classpath” private=”true”>
<doclet name=”org.umlgraph.doclet.UmlGraphDoc”
<param name=”-attributes” />
<param name=”-operations” />
<param name=”-qualify” />
<param name=”-types” />
<param name=”-visibility” />
<apply executable=”dot” dest=”${reports.dir}” parallel=”false”>
<arg value=”-Tpng”/>
<arg value=”-o”/>
<fileset dir=”${reports.dir}” includes=”*.dot”/>
<mapper type=”glob” from=”*.dot” to=”*.png”/>

A number of options contol the operation of UMLGraph class diagram generator. These can be specified as parameters within your build file as shown above.

Details about a few options are:

Specify the output file (default
Specify the output directory (defaults to the current directory).
Produce fully-qualified class names.
Layout the graph in the horizontal direction.
Show class attributes (Java fields)
Show class operations (Java methods)
Show a class’s constructors
Adorn class elements according to their visibility (private, public, protected, package)
Add type information to attributes and operations
Show enumarations as separate stereotyped primitive types.
When showing enumerations, also show the values they can take.
Same as -attributes -operations -visibility -types -enumerations -enumconstants

Take a look here for more options.

Step 4. Run the ant target:
Open a command window and run the ant target: ant javadocs and you should see output as such in your console window:

meera-subbaraos-macbook-9:webservices-samples meerasubbarao$ ant javadocs
Buildfile: build.xml



[javac] Compiling 22 source files to /Users/meerasubbarao/Development/ci-jobs/jobs/PetStore_Nightly/workspace/webservices-samples/classes
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.

[javadoc] Generating Javadoc
[javadoc] Javadoc execution
[javadoc] Loading source files for package…
[javadoc] Loading source files for package com.stelligent.ent.jpa…
[javadoc] Constructing Javadoc information…
[javadoc] UmlGraphDoc version 5.0, running the standard doclet
[javadoc] Standard Doclet version 1.5.0_13
[javadoc] Building tree for all the packages and classes…
[javadoc] Building index for all the packages and classes…
[javadoc] Building index for all classes…
[javadoc] Generating /Users/meerasubbarao/Development/ci-jobs/jobs/PetStore_Nightly/workspace/webservices-samples/reports/javadoc/stylesheet.css…
[javadoc] UmlGraphDoc version 5.0, altering javadocs
[javadoc] Building Package view for package
[javadoc] Building Package view for package com.stelligent.ent.jpa
[javadoc] Building Context view for class
[javadoc] Building Context view for class
[javadoc] Building Context view for class
[javadoc] Building Context view for class

Total time: 8 seconds
meera-subbaraos-macbook-9:webservices-samples meerasubbarao$

The javadoc generated is pretty neat with UML diagrams on the top:

Step 5: Add this target to your CI Job.
If you already have a CI server like
Hudson up and running, which runs commit builds and nightly builds, adding this new target is a one step process.

In my case, I already have a nightly job running, I added this ant target to my default target as shown below:

view plaincopy to clipboardprint?

  1. <target name=“all” depends=“cleanAndDeployForCoverage, javadocs” />

<target name=”all” depends=”cleanAndDeployForCoverage, javadocs” />

Next, force a build on the Hudson job, publish the javadocs, and you can see the results on the hudson dashboard.

The Javadoc embedded with UML diagrams displayed from within the Hudson dashboard:

Now that we have UML diagram integrated within our build file, and also our CI job, we can ensure that our code base and the UML diagrams are always in sync.

We saw how to include these ant targets in our commit builds or nightly builds of our CI jobs, and also published these artifacts as part of our post build process.