BlueXML Developer Studio
Un article de Bluexml.com.
 Home
|  Official WebSite
|  Download
|  Forum
|
|---|
Sommaire |
BlueXML Developer Studio Help
| How to convert an ArgoUML file to an OBL file ?
This tutorial explains how to convert your ArgoUML file to OBL file if you want to use the new editor provided by BlueXML Developer Studio. |
| How to create a new diagram ?
This tutorial explains how to create a new diagram from Eclipse. |
| How to configure an use case diagram ?
This tutorial explains how to create a simple use case diagram and to configure it correctly. |
Road Map
- ATL Transformations
- Create an ATL transformation to convert a XMI file (UML2) to an OBL file.
- Create an ATL transformation to get metrics (KM32Metrics ; ModelMeasurement with ATL)
- HTML Documentation
- Use Acceleo to generate HTML documentation
- Give the possibility to publish on FTP server
- Availability to click on a class in the diagram and to see the HTML documentation about this class
- Integrate in the HTML documentation for a class the list of diagrams containing this class
- Add progress dialog during the generation
- BlueXML Diagram Editor
- Integrate translation in models
- Integrate OCL constraints in models
- Add an editor to simplify the redaction of the view and the layout (with preview)
- Integrate JUnit test
- Add an hyperlink on element
- Add 2 checkbox on class' dialog to indicate that the class is UI stereotyped or nomenclature stereotyped
- Add 2 boolean on attribute to know if we must generate getter and setter to Java
- BlueXML Developer Studio
- Create a perspective PortalAdminsitrator to generate simply portal, documentation (to publish after), to verify models and to evaluate it, to organize all features of an administrator in a perspective.
- Create a creation wizard for REF files and editor for REF files permitting to check simply models wanted and available in the workspace. It's a way to forgot the REF files's syntax.
- Compare/Difference between models EMF Compare
- Add an hyperlink on element
- Create an utility to navigate in models
Global schema
We explain in this part the work made by BlueXML Developer Studio generally. Previously, models are created with the tool ArgoUML. BlueXML wanted to change editor to make easily diagram and that the editor is adapted to the models created and not the inverse. We choose to create many plugins to integrate in the IDE Eclipse.
The first part to explain is the meta-model created. After, we can explain how we convert our ArgoUML files to OBL files. Next, we will see the editor and to finish the two transformations available.
Description of our meta-model
Of course, we have many elements that we can find in the meta-model UML. We need in the project BlueXML to draw 2 diagrams : the use case diagram and the class diagram.
Common elements
We have common elements of two diagrams :
- Package : it's the root object of two diagrams
- ModelElement : it's an abstract element wich is linked with comments, tags, meta-info and stereotypes
- Stereotype
- Tag
- Enumeration
- Generalization
- Meta-info : this element is to represent an information added to configure the project BlueXML
- Comment
Use case elements
- Profile (or actor)
- Use case
- Link : it's the link between a profile and an use case
- Include : it's the link between two use cases
Class diagram elements
- Class
- Association
- Attribute
- Operation
- Parameter (of an operation)
Conversion from ArgoUML
If we create a specialized editor, we must convert our old model to the new metamodel. You must to create a model transformation. We have made the choice to use an other plugin to begin. It's the plugin Argo2Ecore which permit to transform ArgoUML file to eCore file. The eCore format is used to describe meta-model and not model. The syntax is quasi equivalent to a class diagram.
We have created a new plugin based on the plugin Argo2Ecore to transform our ArgoUML files to OBL files. We have created this transformation from a XMI file with the metamodel UML but we have added shortcut from an ArgoUML file. An ArgoUML file is a compressed file. The shortcut consists to extract XMI file, to convert this file and to delete after the XMI file.
Generation of our editor
We have generated our editor with Topcased. Topcased is based on GEF and permit to create an editor simply with a metamodel. We create our metamodel, we create an editor configurator and two diagram configurator and we have our editor.
It's important to note that the editor generated at this step is usable but not very user-friendly. In the project BlueXML, we want that models can be created simply. So we have added dialogs on all elements if we double click on. Dialogs permit to link element with setereotype or to create layout and view (comments stereotyped layout or view) or create meta-information.
A meta-information is an information added on element to configure the portal generated. This element don't have to create by hand but automatically on dialog. All possible value for a meta-information are available.
Generation of PIVOT format
Previously, a transformation from a XMI file to the format PIVOT existed. The XMI file was obtained after decompression of the ArgoUML file. The PIVOT is used to generate the portal. With the new editor and the new meta-model, we must create a transformation from the OBL format to the PIVOT format.
Many similarity exist between the transformation XMI2PIVOT and the transformation OBL2PIVOT. We create a new transformation based on the transformation XMI2PIVOT. With the new editor, a model can used an other external model, we must add the concept of global model which include many OBL files. To generate the portal with OBL files or to see the PIVOT, we must create a REF files which wontains all filles. We have merged the two transformations and we can view the PIVOT file like that : http://demo.BlueXML.org:9999/UMLFormsDesigner/xmi2pivot/REF_FILE/FOLDER
The regeneration of the portal uses now ArgoUML files and REF files. So we must move your ArgoUML files to an other folder if we don't want that the generation uses your ArgoUML files.
Generation of XMI format
You work to an other transformation. This transformation permits to extract our models conform to our meta-model to a XMI file conform to the meta-model UML. This transformation permits to import our models in other modeling tools such as ArgoUML, Rational Rose...
This transformation is made with ATL (Atlas Transformation Language). It can be used in tools used ATL such as the new version of AndroMDA.
Other tools
We work actually on other tools to simplify the management of models. We have nearly finished the first tool which validate a REF file. This validation permits to know if the generation of the PORTAL will be correct and if all elements are present.
An other tool developping actually is to create pictures of all models automatically.
We work too on an other tool wich permit to create a map with all models. This map will permit to see the dependencies and too see the broken links.
