Reverse engineering UML class and sequence diagrams from Java code with IBM Rational Software Architect

Three techniques to overcome limitations

This article is for software architects, designers, and developers who want to use IBM® Rational® Software Architect to reverse engineer UML class and sequence diagrams from Java™ source code. Reverse engineering is often used to retrieve missing design documentation from existing source code in an abstract model UML format for studying both the static structure and dynamic behavior of a system and for expanding the new features to the product. The authors explain limitations of reverse engineering with Rational Software Architect and describe techniques to overcome them. You will benefit from using these technical tips and tricks to identify components and generate high-level abstractions as UML class and sequence diagrams from Java classes.

Fenglian Xu (, Software Engineer, IBM United Kingdom

Dr. Fenglian Xu photoDr. Fenglian Xu is a Software Developer on the WebSphere Enterprise Service Bus Development team at the IBM Hursley Software Lab in the UK. Her expertise includes WebSphere MQ JMS bindings, WebSphere Application Server, and WebSphere Enterprise Service Bus. She has worked in various IT companies on both middleware to applications, and with the UK eScience pilot project GEODISE, which involved workflow and SOA. She received a B.Sc. in Applied Math and Software Engineering from Xian Jiaotong University in China in 1989, and a Ph.D. in Computer Science from the University of Southampton in the UK in 1998. You can contact Fenglian at

developerWorks Contributing author

Alex Wood (, Software Engineer, IBM United Kingdom

Alex WoodAlex Wood works at IBM Hursley Lab in England as a Software Developer for the IBM WebSphere Business Integration suite of products. He has extensive experience in development on many of the WebSphere products, including WebSphere MQ, WebSphere Message Broker, WebSphere Enterprise Service Bus, and WebSphere Process Server. He received a BSc in Physics with Astrophysics from Birmingham University in the United Kingdom in 1998.

10 June 2008

Also available in Chinese

The Unified Modeling Language (UML) is well-known by all software architects, developers, and testers. It is used for documenting use cases, class diagrams, sequence diagrams, and the other diagrams. There are many software tools that help software engineers to accomplish this either by forward engineering or reverse engineering.

  • Forward engineering is a traditional process of moving high-level abstracts and logical, implementation-independent designs to the physical implementation of a system.
  • Reverse engineering is a process of analysing an existing system to identify its components and their interrelationships and to create representations of the system at a high level of abstraction. In most cases, reverse engineering is used to retrieve missing design documents from the existing source code in an abstract model UML format for studying both the static structure and dynamic behaviour of a system.

Nature of the problems with class and sequence diagrams

IBM® Rational® Software Architect is widely used by many industries because it provides many features to support reverse engineering. The problem is that when you reverse engineer UML class and sequence diagrams from Java™ code, Rational Software Architect does not automatically produce useful class and sequence diagrams. However there are techniques to improve the output from Rational Software Architect. This article demonstrates how to identify components and generate high-level abstractions of UML class and sequence diagrams from Java™ code by using the technical tips and tricks explained here.

With reverse engineering, it is not always easy to achieve what you expect from forward engineering. This article addresses problems that occurred during reverse engineering in these areas:

  • Discovering abstraction classes and identify their hierarchical structures
  • Producing high-level abstraction class diagrams with aggregation and association relationships
  • Creating sequence diagrams

The sections that follow provide solutions to each problem and demonstrate how to produce meaningful class and sequence diagrams. The examples show how to identify the inheritance trees and components of a system in the source code of a given Java project and how to generate high-level abstractions of UML class diagrams and sequence diagrams.

The examples in this article apply to Rational Software Architect Version 7.0, though the screens were generated in Rational Software Architect Version 6.0.

Identify an inheritance tree UML class diagram

Inheritance is a common object-oriented pattern that allows a group of classes to share common states and behaviours so that subclasses can inherit the common states and behaviours from their superclasses. Discovering the entire inheritance tree structure from an existing system is particularly useful, because it helps you uncover what the top-level class is and what subclasses are in the tree. Furthermore, you can identify what common states and behaviours are within a tree and how the common behaviours are implemented. You can use Rational Software Architect for this discovery process in these three steps:

  • Discover abstractions from a workspace or a working set
  • Show an abstraction class diagram by selecting a class from the abstraction list
  • Explore the tree structure in a browser diagram and you will see a list of abstract classes shown under Abstraction.

The first step is automatically retrieving the top-level abstraction classes in an existing system. You can use these classes as entry points to discover the classes in the inheritance tree. To do this, you need follow these steps:

  1. Open the Diagram Navigation view in Rational Software Architect.
  2. Under Object-oriented Patterns, right-click Abstraction and then click Discover Architecture (see Figure 1).

This will reveal the architecture for an entire workspace.

Figure 1. Discover the architecture for an entire workspace
Discover Architecture selected in drop-down menu

Figures 2 and 3 show the rest of the steps required to produce a tree structure of an abstraction class diagram:

  1. Bring up the context menu by right clicking on the Car class under Abstraction.
  2. Show the Car class diagram on the right panel by selecting Show Diagram from the menu.
  3. Bring up the context menu by selecting and right clicking on the Car class diagram on the right panel.
  4. Generate the tree structure of the abstract class diagram by selecting the Explore in Browse Diagram from the context menu.

As the result of step 6, you will see the tree structure of the Car class diagram on the right panel.

Figure 2. Discover abstractions from entire workspace
Diagram Navigation tab and steps to follow

The result has these limitations:

  • The grandchildren of the discovered class in the tree may be missed.
  • The classes except for the discovered abstraction class do not have attributes and operations.

Additional steps are needed to achieve the required tree structure generated by Step 6. You need to increase the degree of separation (see Figure 3), which controls the level of expansion from the discovered class.

Figure 3. Change degree of separation
Where to increase degree of separation

The default degree is 1, and this is why some grandchildren are missed in the inheritance tree. In this example, the degree of separation has been increased to 2.

The second problem is that there are no attributes and operations for the classes except for the discovered class in the tree. This prevents users from studying the existing common patterns for reuse.

The following example demonstrates how to identify an entire inheritance tree with optional attributes and operations:

  1. Load a Java project into Rational Software Architect.
  2. Switch to the Diagram Navigation view and discover the abstractions from the workspace as described in the previous steps.
  3. Find an abstraction class from Step 2 in which you are interested.
  4. Discover the hierarchical tree structure classes by finding the class in the Model Explorer, double-click to open the class in the editor, and press F4 to open the hierarchy tree. Ensure that the type hierarchy is selected.
  5. Right-click on one class and change it to a visual class diagram by selecting Visualize > Add to New Diagram File > Class Diagram, as shown in Figure 4.
  6. Add the rest of the classes to the current diagram by right-clicking and selecting Visualize > Add to Current Diagram.
Figure 4. Visualize class into new class diagram
Selections shown in 3 drop-down menus

Figure 5 demonstrates the process of generating an inheritance tree class diagram:

  1. Open and press F4 to show the class hierarchy.
  2. Select each class and add it to the class diagram.
  3. Review the completed diagram on the right.
Figure 5. A mechanism to generate an inheritance tree class diagram
Shows steps and result

The class diagram is generated with the Rational Software Architect default format. There are several useful modifications that you can make to the visual representation of the diagram. For example, you can modify the connections routing style to use the tree style routing, and you can right-click in the workspace to bring up a context menu and then click Arrange all. The class diagram now looks much better than the one automatically generated, as Figure 6 shows.

Figure 6. Inheritance tree diagram with attributes and the tree style routing connections
New hierarchy

The classes in Figure 6 show both attributes and operations. The benefit of showing the attributes and operations is that you can study the common states and behaviours further to discover what has been implemented in the existing system for reuse.

Generate a high-level UML class diagram

Rational Software Architect enables you to generate class diagrams by selecting multiple Java files from a Java project:

  1. In the Model Explorer, use Visualize to add them to a new diagram or the current class diagram.

If multiple classes have been added in the current diagram, then the relationships among these classes are also shown.

Figure 7 is an example of a class diagram that was automatically generated from the Java code in a package.

Figure 7. An auto-generated class diagram
Model Explorer view on R, classdiagram2.dnx on R

As Figure 7 shows, you can select multiple Java files from the Model Explorer to visualize them in a new class diagram. If you want to add more classes, you can select more Java source code to visualize in the current class diagram. This diagram shows the classes included in the project and their basic relationships. It is useful to automatically discover the UML classes in the project, but the auto-discovered relationships are less useful here.

In Figure 7, almost every relationship is a use apart from the inheritance. The use relationship is too general to give useful design information. The more specific relationships of aggregation and composition are hidden, even when all of the relationships are turned on for this diagram. The aggregation is represented as one-to-many relationships when a class contains many items of another class, and the composition is used for describing a one-to-one relationship when a class contains only one instance of another class. This high-level abstraction represents more accurate relationships among the classes and provides useful information for the implementation of this design. This class diagram is not useful without the details of the abstract relationships.

Here, we have experienced and explored a semi-automated method for generating a high-level abstraction of a UML class diagram. The UML classes are discovered with the same technique as before, and the relationships among classes are created manually. The high-level abstraction is based on the knowledge acquired from studying the existing source code.

Figure 8 shows the first step of this method to create the high-level UML class diagram.

Figure 8. Create a blank model by using the UML model wizard
New UML Model view

To generate a high-level class diagram, you need to create a blank model first:

  1. Create a new blank model by using the steps shown in Figure 8:
    1. Under File Types, select UML Modeling.
    2. Under Templates, select Blank Model.
    3. In the File Name field, type Blank Model.
    4. For Destination folder, type example.
    5. The Default diagram check box for "Create a default diagram in the new model" should be checked.
    6. For Default diagram type, select Freeform Diagram.
    7. Click Finish.

The next step is to harvest the selected classes from the auto-generated class diagram. Harvesting in Rational Software Architect enables you to copy a class from one class diagram and paste it into another class diagram, which must be within a blank model. If you paste the harvested class into the same class diagram or into another class diagram that is outside of a blank model, the class attributes and functions are invisible.

  1. Harvest the selected Java classes from the auto-generated class diagram by using the steps shown in Figure 9:
    1. Select the FuelTank, Engine, Passenger and Car classes from the classdiagram2.dnx.
    2. Right click on one of the selected classes to bring up a context menu.
    3. Select the Harvest menu
  2. Paste the harvested classes into the separated class diagram that you created in Step 2.
  3. Create relationships with aggregation or composition between the classes.
Figure 9. Harvest classes from a class diagram
New view under classdiagram2.dnx tab

Next, create an association relationship between the classes that enables you to choose either an aggregation or a composition relationship. An example of a high-level class diagram is shown in Figure 10.

Figure 10. A high-level abstraction of a UML class diagram generated by the semi-automatic method
Diagram: FuelTank, Passenger, Engine > Car

By comparing Figure 10 with Figure 9, you can tell that the class relationships have been shown accurately by the semi-automated method. This diagram can be used for an implementation independent design document or for exploring any further improvement to the existing system.

Without harvesting, the aggregation and composition relationships cannot be used in Rational Software Architect

Generate a sequence diagram

The sequence diagram is the most popular UML artifact for dynamic modeling. It focuses on identifying the behaviour of a system. A sequence diagram is typically used for modeling use cases, to show the logic of both the methods and the services of a system.

Rational Software Architect does not create a sequence diagram automatically from the Java code. The following steps show you how to create one:

  1. Create a blank model.
  2. Create a sequence diagram:
    1. Right-click on a Blank Model.
    2. From the drop-down (context) menus, select Add Diagram and then select Sequence Diagram (see Figure 11).
  3. Add the classes to the sequence diagram.
  4. Make a sequence of method invocation between two classes.
  5. Save the sequence diagram.
Figure 11. Create a sequence diagram
Add Diagram and Sequence Diagram selected

When you have finished creating a sequence diagram, a sequence file is created under the Collaboration: Interaction tab. You can add the class from the Java code to the sequence diagram. Both are shown in Figure 12.

The main workspace in Figure 12 shows an example of a sequence diagram.

Figure 12. Sequence diagram created from Java source files
Also: Method invocation selected from target class

A method invocation is represented by a message sent from a caller to a callee. The callee is the method owner that receives a message from the method caller. The message can be either a one-way or a two-way message. A sequence diagram consists of a sequence of method invocations among a group of method owners and an initial invoker. The first invocation must be started from an actor that initialises the first method invocation.


This article demonstrated how to use reverse engineering to create UML class and sequence diagrams from Java code by using Rational Software Architect v7.0. The hierarchical class diagram demonstrates a way to discover an entire class inheritance relationship within a project or a work set. This helps developers expand and add new functions to an existing system. The high-level class diagram clearly shows aggregation or composition relationships between classes, which is helpful for developers to extend or modify an existing design. This is particularly powerful for developers to explore a large system. The sequence diagram shows the dynamic method invocations among classes for performing certain tasks. This provides clear runtime interactions within the system.


The authors thank Philip Norton and Noel Rooney for their reviews and feedback on this article.



Get products and technologies



developerWorks: Sign in

Required fields are indicated with an asterisk (*).

Need an IBM ID?
Forgot your IBM ID?

Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.


All information submitted is secure.

Dig deeper into Rational software on developerWorks

ArticleTitle=Reverse engineering UML class and sequence diagrams from Java code with IBM Rational Software Architect