Jump to: navigation, search

Difference between revisions of "MoDisco/ModelFilter"

Line 170: Line 170:
 
* Initializations through method call are not managed
 
* Initializations through method call are not managed
  
 +
{{MoDisco}}
 
[[Category:MoDisco]]
 
[[Category:MoDisco]]

Revision as of 09:07, 24 February 2011

The goal of the ModelFilter plug-in is to extract specific information from java projects, and to show it as UML models.

First application is to initialize a dependencies graph from one selected element, the level of recursion has been provided as a parameter.

Second application is to show method calls as a pseudo sequence diagram, using dependencies between methods, numbered from one to n to indicate the order.

Third application is to represent real type of properties when an interface has been used in java code.

Description

To discover an application, you may use SimpleTransformationsChain to obtain a UML model which represents the whole application structure. Or you may use the ModelFilter plug-in to focus on different aspects. It could be represented by little models dedicated to one element, or a complete model but with added informations. Depending on the complexity of the application and resulted UML model, you will have to select one or other kind of model. The dependencies graph is clearly well fitted to show how several little models could be useful. Representation of method calls as pseudo sequence could be done by little models or by one complete model, it has been implemented as one model to show how different diagrams have to be used to mask complexity of model elements. And representation of real type for properties show how a complete model could be improved with few details.

Dependencies graph

From a selected class in a java application, you choose the recursion level of dependencies search and you will get a UML model which represents a dependencies graph from selected class. Structural links, like association, inheritance, etc. are of course available, but we have added UML dependencies to show local use of a type, or method parameters. It is very useful to detect qualified type usage or type in same package usage.

Sample of target UML model with local and method parameters dependencies.

Method calls

To represent method calls as pseudo sequence, we will use UML dependencies from one method (caller) to other methods (called), each dependency has been named with name of called method suffixed by a number which represent its order in sequence of method calls.

Sample of target UML model with method calls as dependencies.

Real type of properties

When the type of a property is an interface, it is interesting to represent its real type dependency in a UML model.

Sample of target UML model with real types as dependencies.

Requirements

Eclipse Galileo with modeling plugins:

  • EMF
  • EMF UML2
  • UML2 Tools
  • ATL 3.0.0

For advanced users in modeling, we advice to use Papyrus modeler instead of UML2 Tools.

A complete bundle of Modeling components could be found at this url : Eclipse Modeling Galileo Bundle

Warning : after installation, you will have to change your eclipse settings (file eclipse.ini) to increase memory size allowed to 1Go at least, parameter « -Xmx1024m ».

Example :

-startup
plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-product
org.eclipse.epp.package.modeling.product
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx1024m
-XX:ThreadStackSize=4096

Team

Gabriel Barbier (Mia-Software)

Install

To install this plugin, you will have to retrieve it and its dependencies from MoDisco SVN. All following bundles are available in folder "plugins/trunk":

  • org.eclipse.gmt.modisco.usecase.modelfilter
  • org.eclipse.gmt.modisco.kdm.uml2converter
  • org.eclipse.gmt.modisco.j2se5
  • org.eclipse.gmt.modisco.j2se5.discoverer
  • org.eclipse.gmt.modisco.kdm
  • org.eclipse.gmt.modisco.common.core

User manual

To illustrate ModelFilter plugin and its features, we will use a sample inspired from the Pet Store Application.

Get and install use case

The models are available from MoDisco SVN (how to...) in subdirectory "examples/trunk/org.eclipse.gmt.modisco.usecase.modelfilter.sample" or from downloadable archive. If you use a SVN client in eclipse (Subversive or Subclipse), the project will be immediately available in your Eclipse workspace.

Sources of Pet Store application are available from Sun downloads. You may have to download several libraries to obtain an eclipse project without errors (JPA, JTA, JSF-apis and Servlets-jsp-apis). A complete bundle is also available from Mia-Software... To view this application in your Eclipse workspace, you will have to extract content of this archive, and use the "import" wizard (import project in workspace).

Dependencies graph

To get the dependencies graph of a particular class, you have to select it in package explorer. Then in contextual menu, navigate in "Modelplex Use Cases" menu, click on "Create Dependencies model from selected java class" menu item.

Contextual menu entry for Modelplex use cases.

Then, you will have a simple UML model dedicated to dependencies graph presentation.

Sample of target UML model with local dependencies.

Method calls

Nota: to represent method calls from a selected method, we have to use a modeler which is able to show dependencies between methods, these methods being in classes located in different packages. Then, following diagrams have been created with Papyrus and not with UML2 Tools.

To get the UML model with method calls, select the java project you would like to inspect. Then in contextual menu, navigate in "Modelplex Use Cases" menu, click on "Create uml model with method calls" menu item.

Contextual menu entry for Modelplex use cases.

Then, you will have a complete UML model instrumented with dependencies to represent method calls.

Sample of target UML model with specific dependencies.
You will have a better look if we focus on a particular method. For example, the method
public List<SelectItem> getCategories()
in class MapBean located in package com.sun.javaee.blueprints.petstore.mapviewer.
// mapAll.jsp
    public List<SelectItem> getCategories() {
        // return categories for a JSF radio button
        ArrayList<SelectItem> arCats=new ArrayList<SelectItem>();
 
        // get the CatalogFacade for the app
        FacesContext context=FacesContext.getCurrentInstance();
        Map<String,Object> contextMap=context.getExternalContext().getApplicationMap();
        CatalogFacade cf=(CatalogFacade)contextMap.get("CatalogFacade");
 
        // get the categories from the database
        List<Category> catsx=cf.getCategories();
        for(Category catx : catsx) {
            // add categories to be displayed in a radio button
            arCats.add(new SelectItem(catx.getCategoryID(), catx.getName()));
        }
        return arCats;
    }
A diagram build with Papyrus to show method calls from method "getCategories".

Real type of properties

Nota: to represent real type of properties, we have to use a modeler which is able to show dependencies between an association and a class, these elements being located in different packages. Then, following diagrams have been created with Papyrus and not with UML2 Tools.

To get the UML model with real type of properties, select the java project you would like to inspect. Then in contextual menu, navigate in "Modelplex Use Cases" menu, click on "Create uml model with real types information on associations" menu item.

Contextual menu entry for Modelplex use cases.

Then, you will have a complete UML model instrumented with dependencies to represent method calls.

Sample of target UML model with specific dependencies.
You will have a better look if we focus on a particular association. For example, the properties
private Collection<Item> items
in class Tag and
private Collection<Tag> tags
in class Item both located in package com.sun.javaee.blueprints.petstore.model.
A diagram build with Papyrus to show real types.

Current limitations

Dependencies graph

  • The dependencies gaph does not reflect some implicit dependencies, for example with embricated method calls:
String entryPagesParam = filterConfig.getServletContext().getInitParameter("entryPages");

Method calls

  • Diagrams have to be built manually with Papyrus
  • Method calls should be represented with a uml sequence diagram

Real type of properties

  • Diagrams have to be built manually with Papyrus
  • Initializations through parameters or local variable are not managed
  • Initializations through method call are not managed


MoDisco
Components Infrastructure: KDM · SMM · GASTM · Model Browser · Discovery Manager · MoDisco Workflow · Query Manager · Facet Manager · Metrics Visualization Builder · KDM Source Extension
Technologies: Java · JEE · EjbJar · WebApp · XML
Use Cases: Simple Transformation Chain · Model Filter
Help Installation · SVN
Project API Policy · Retention Policy · Project Plan · metrics · Accessibility Guidelines · Capabilities Disablement