UML2 and Enterprise Architect

Tutorial #1 for EA and Xpand is available!

2011-09-21T20:41:00.000+01:00

I got it!!

The updated tutorial for EA and Eclipse Xpand/Xtend is available.
You will find it here.

Don't hesitate to submit bug or feature requests.

New installation instruction is available

2011-09-18T08:33:00.001+01:00

Since more than a year, oAW is a part of Eclipse. The eclpse project is called "Xpand/Xtend".
This had impact on installation of UML2Exporter for EA.

Here you will find an installation manual for installing Eclipse Helios and UML2Exporter to work with EA models.

If you find some bugs, don't hesitate to add an entry in bug tracker of components4oaw.

Looking for employees with Java MDD skills

2011-07-13T15:04:00.000+01:00

In the company I work with, we are searching young employees with software engineering and Java skills. The most important point is, you have to speek german fluently.

Zühlke is the leading company in Switzerland for software engineering and development in Java and .Net. If you are interested in working in a great company with well educated people and want to emprove your skills significantly, don't hesitate to contact me.

Here you will find more information about this interesting job.

New features in release 2.1

2011-06-02T15:25:00.003+01:00

With the new release a few new features are available.

Selection of all packages

If you specify the package to export as following
<PackageName value="Model/Model View/Solution/*">
then all packages of "Solution" are exported into root of model directly.

Ghost Elements

If a referenced (inheritance, dependency or association) element is not in one of the exported package or in one of it's subpackages, then this element was created in the package the first reference appears during the export.

With release 2.0 these elements are not exported any more and the references are not available.

If you have to access these elements for reading extra information, you can add the the following property:
<GhostPackageName value="GhostPackage">

Now a package with the name "GhostPackage" is created in root model and all referenced elements not part of the exported packages are created in this package.

DataType

Also UML::DataType is now supported.

If you like to have more elements in exported model, don't hesitate to add a feature request.

RC1 of Release 2.1 is available

2011-05-19T10:56:00.000+01:00

I just fixed all known bugs and implemented almost all feature requests.
In download section at source forge you will find zip file containing RC1.

Please use this candidate and give me feedback.

Regards
Ueli

Release 2.0 is now available!

2011-04-07T06:54:00.000+01:00

After many discussions and lot of work in spare time, the final release of 2.0 is available now.

Following features are supported now:

MWE workflows
Several bugs fixed
Some other feature added

Version 2.1 is already in queue and will be released soon.

Have a look at project home page

Release Candidate 4 of Version 2.0 of UML2Exporter is available

2011-02-18T11:13:00.000+01:00

We are proud to inform you about the new release candidate of version 2.0.
This works with *oaw and *mwe workflows.

Also some bugs and features are implemented. Pls contact project site on sourceforge for more information.

Exporter for Ecore Models

2010-09-26T11:56:00.000+01:00

I'm working on an exporter for ecore models. It should create metamodels and models based on profiles and diagrams.

What do you think? Is this a useful functionality.
What is a goot use case?
Who would youse EA for creating ecore based models?

All comments are welcome.

Release 2.0 has massive delay

2010-09-09T17:21:00.000+01:00

Since more than a year I'm working for the release 2.0.
Unfortunately I can not complete the release due to missing maven pom files for Eclipse UML 3 and referencing components.
Do somebody know a Maven Repository containing a pom file for Eclipse.UML 3.0?

Any hint is welcome.

RC2 of Release 2.0 is available

2010-04-12T21:09:00.000+01:00

Since a couple of weeks the RC2 of release 2.0 is available in download section of SF project.
This new release supports now Eclipse MWE and oAW workflow definitions.

If you use release 2.0 the first time, be aware of changes in package names.
Rest should work as usual.
Don't hesitate to send improvement proposals as feature requests to SF project page.

Release 2.0 of EA_UML2Exporter

2009-12-05T14:15:00.002+01:00

The workarround does not work :-(.

So I work now on the new release supporting Eclipse MWE and Eclipse.UML 3.0.
It will be available in a few days.

Workarround for using with oAW5

2009-11-19T07:41:00.002+01:00

A few days ago someone asked me "Is there a workarround, due to uml2exporter is not compatible with oAW5?"
Yes, it is. You must separate the workflow into two stages.
1. Exporting of model to *.uml and check the model constraints.
2. Working with the model (Transformation to text).

Part one can be made with oAW4.3.1 within a cmd file and executed by EA (CTRL+F12).
Part two can be made with oAW5 within Eclipse Galileo.

If you need an example cmd file, don't hesitate to contact me.

UML2Exporter is not compatible with Eclipse MWE

2009-11-09T13:35:00.002+01:00

Last weekend I tested current exporter to run with Eclipse MWE (oAW 5).

Unfortunately it does not work. A bigger redesign of the component is required to support oAW 4.3.1 and Eclipse MWE.
You will hear as soon as the redesign is finished.

Release 1.7.1 is availabel

2009-10-30T17:28:00.001+01:00

Since a couple of weeks the new release 1.7.1 is availabel on http://components4oaw.sf.net

Feel free to give me feedback.

Version 1.7.0 of UML2Exporter will be released soon!

2009-08-17T03:50:00.002+01:00

In the last few weeks I worked on the new release of UML2Exporter and fixed some bugs and added some features.
If you go to download section you will see RC2.

Pleas use this version and test it with your project.
Add all bugs found to issue tracker on sf page.

Separation of Tagged Values with same name

2009-06-21T19:21:00.002+01:00

In forum of components4oaw.sf.net a user posted the problem that all tagged values of the same name have the same value, although they are of different stereotypes.

After some research work and different kind of code work I found out, that EA doesn't support different tagged values with same name of different stereotype correctly.
You're able to separate them in the view for tagged values by selecting option "Show Fully Qualified Tags", but in COM interface these fully qualified name is not visible.

I hope, Sparx Systems will add a this feature very soon.

See you at SEConf 2009 in Vienna!

2009-04-24T10:49:00.002+01:00

I will be at the SEConf 2009 in vienna between 15. and 17. June 2009.

On June 15. I will lead a workshop "Introduction in oAW and Topcased".
I can not use EA due to EA is not Open Source.

On June 16. I will have a presentation about using MDSD reducing complexity in the usage of Hibernate

Workshop and presentation will be in German.

Hope to see you there.

BUG in DbConnect of UML2Exporter Release 1.6.1

2009-04-23T18:38:00.002+01:00

There is a critical bug in the exporter concerning db based repositories of EA. Sorry for that.

When using a db connect definition in parameter DbConnect you will get an error message "File not found ....". It will be fixed in the next release.

Workaround:
Open EA and open your project with "Connect to server".
Save the project as a shortcut --> Menu "File / Save Project as ..."

This way you generate a shortcut file to your database.
Now use this shortcut file in the UML2Exporter as EAP-File.
Then it works!

Customized Toolbox for your UML profile

2009-04-19T12:44:00.002+01:00

When working with a UML profile in a diagram you have to select the profile toolbox first before you can create elements by drag&drop. When switching to another diagram and returning you have to select the profile toolbox again.

With MDG Technology of EA you can define your profile(s) as a new technology and add it to your EA installation. With MDG technology you can

create diagrams with ID of your technology
specify a toolboxes containing all the drawing elements needed
adding common elements of uml to your toolbox
defining own graphical representation for each stereotype
preparing patterns for designing
and some more

For complete overview see online help of EA.

Defining a MDG Technology is a little bit tricky. Here are the steps required to define your own technology.

Define the UML profile (as usual)
Define a new profile for diagram types (see online help)
Define a new profile for profile toolbox (see online help)
Define a new MDG technology and deploy it to your EA installation (see online help)

After fulfilling all required steps successfully you can create diagrams of your technology with your toolboxes and every time this diagram is selected the toolboxes are selected to.

Stereotypes have no tagged values

2009-04-09T20:48:00.004+01:00

When working with model sometime it happens, that you have to add a stereotype to an existing class by selecting from list in property dialog or by enter stereotype name in editbox. When going back to diagram you will see, that the tagged values are not listed in tagged value view.

How to solve this?

Change to Resource view and select the stereotype from profile.

Click right mouse button and select "Select Tagged Values and Constraints ..."

Press OK and all missing tagged values of the selected stereotype are applied to the model elements. This procedure doesn't remove tagged values not used any more. These have to be removed manually.

Starting oAW workflow out of EA

2009-04-07T21:34:00.002+01:00

Enterprise Architect has a feature for developing, compiling and debugging source code. This is based on executing commands directly or on a command script.

When activating menu "Project --> Build and Run --> Package build scripts" or just press Shift+F12 following dialog opens.
Here you can add a script definition or a call to a command file.

I created a command file containing all the steps required to execute a workflow from batch file:

Setup class path
Call worflow with java command

Command file could look like this:
echo off
set BASEDIR=.
cd C:\Personal\Programs\oaw431
set CLASSPATH=.;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.adapter.emf.check_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.base_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.core.emftools_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.core.expressions_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.core.workflow_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.core.xpand2_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.emftools_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.uml2.adapter.plugin_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.uml2.adapter_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.util.stdlib_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.openarchitectureware.workflow_4.3.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.emf.ecore_2.4.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.emf.ecore.xmi_2.4.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.emf.common_2.4.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.emf.mapping.ecore2xml_2.4.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.uml2_2.1.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.uml2.uml_2.2.1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.uml2.common_1.4.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.uml2.uml.resources_2.2.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.ant.core_3.2.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\commons-lang-2.3.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.apache.log4j_1.2.13.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.apache.commons.cli_1.0.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.apache.commons.logging_1.0.4.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.text_3.4.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.jdt.core_3.4.2.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\org.eclipse.equinox.common_3.4.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\stringtemplate-3.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\antlr-runtime-3.0.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\ea_com_interface-1.6.1-RC1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\ea_toolsupport-1.6.1-RC1.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\lib\eaapi.jar;
set CLASSPATH=%CLASSPATH%%BASEDIR%\src\workflow;

java -cp %CLASSPATH% org.openarchitectureware.workflow.WorkflowRunner workflow.oaw

An example command file you will find here.

When everything is configured correctly you can start workflow within EA by pressing Ctrl+Shift+F12. Output looks like following.

Stereotypes for Requirement, Issue or Feature

2008-11-30T21:22:00.002+01:00

In a comment of the last posting, corvo asked to extend the metatypes Requirement, Issue or Feature with own stereotypes in a profile and add additional information in tagged values.

Due to Requirements, Issues and Features are not part of the UML metamodel, these stereotypes couldn't be created in a UML profile. There is no way to express these extensions in UML. The using of the EA profile is a work arround, which creates classes for Requirements, Issues and Featurs with corresponding stereotypes containing all the predefined properties of these elements.

The metamodel of EA is not compatible with UML2.

Reading additional attributes of EA

2008-07-13T20:23:00.002+02:00

Couple of month ago, someone asked me to include some functionality for exporting EA attributes like author, create and modification date and so on. UML doesn't support these attributes.

Following solution is added to the current snappshot releases:

Add ea.profile.uml to the list of profiles in UML2Exporter
All elements will get stereotype with name ea_* automatically
This stereotype will contain the required attributes like author or create date

You will find the snapshots jar files here and here.
The ea.profile.uml is located automatically if you add the jar file to the build path.

Pls tell me, if this functionality is useful or not.

EA 7.1 (Build 829) now works with UML2Exporter 1.5.0

2008-05-22T20:35:00.002+02:00

Build 829 is available since a few weeks and today I found the time to test the new Java API against my UML2Exporter.

Et voila --> everything works now very fine.

Be aware, to use the new SSJavaCOM.dll, too.

EA 7.1 and UML2Exporter

2008-03-29T10:01:00.003+01:00

Since a few weeks Enterprise Architect 7.1 is available.

Unfortunately the released jar file eaapi.jar doesn't work. So uml2exporter doesn't work with EA 7.1.

Due to eaapi.jar works with COM interface of EA the eaapi.jar of version 7.0 can be used instead and it's working again. But they changed something inside of EA, because the export runs slower than with 7.0.

Any comments are welcome.

UML2Exporter 1.5.0 is available!!

2008-03-02T17:42:00.002+01:00

After a long periode of changing code, testing and bug fixing, code is now stable enough to make release 1.5.0.

The major change is the switch over to Java API of Enterprise Architect instead of JACOB.

You will find new release and an installation istruction on the project home page.

There you will find release notes and trackers for bugs and feature request.
Any comment is welcome.

Connecting server based EA model is supported!

2007-06-04T20:41:00.000+02:00

Here is the answer I get from SparxSystems:

Simply pass a valid connection string instead of the eap file path to connect to your DBMS repository.

Example:
<EapFile value="ora-ea1 --- DBType=3;Connect= Provider=OraOLEDB.Oracle.1;Password=tiger;Persist
Security Info=True;User ID=scott;Data Source=ea1">

There are two ways to obtain a copy of the connection string:
1. From the "Open Project" dialog (File Open Project), select the connection from the recent list, then copy the text in the "Project to Open" field.
OR
2. Save a shortcut eap file to your repository and open the file in notepad.
- Open you DBMS repository in EA
- File Save Project As
- Specify a new filename and Save
- Open the resulting file in notepad and copy the contents

Alternately, if you save a shortcut eap file as described in point 2 above, you can also simply specify this file in the OpenFile method and it will also open the database connection.

I hope this helps.

Using EA in a Server based repository

2007-06-01T17:07:00.000+02:00

Several weeks ago somebody asked me here in this blog, if it's possible to connect to a server based repository.
I made some research work in Automation Interface of EA and found out, that up to now this is not supported by Automation Interface.

I placed a support request at SparxSystems and hope that it will be available with the next release.

Using EA for Requirements modelling

2007-05-23T19:53:00.000+02:00

Several weeks ago a user of UML2Exporter asked me, how to support Requirements of EA in a UML model, because there is no element in UML corresponding to this element.

Requirements could be modeled in EA with following elements:

After a fiew minutes thinking about it, I got the following solution.

I defined in EA a Profile called "EA"
In this profile I added the stereotype "requirement" as extension of class
There I added properties for status, type, dificulty and priority.
I defined a stereotype called "feature" and make it inheriting from "requirement"

In the UML2Exporter I added components to recognise requirements and features and transform it into uml classes with stereotype "requirement" or "feature". The text body is added as comment to the class. When exporting to UML2 model you only have to assign the EA.profile.uml to the package containing the requirements.

At Xpand componente you have to specify EA.profile.uml as a metamodel and you are able to create model driven requirement specification.

New features in UML2Exporter 1.1

2007-05-14T22:05:00.000+02:00

Since my last post many things have changed in UML2Exporter. All these features helps to make work with EA_UML2Exporter much easier. Here are the topics:

UML2Exporter can now be used more than once in workflow. Last component must add <cleanup value="true"> to remove EA instance from process list.
UML2Exporter writes model direct to output slot of workflow. Use <outputslot value="model"> instead of <modelfile value="model.uml">.
Multible Stereotypes are now supported.
When defining tagged values in Profile, one can use boolean or Boolean types instead of bool.
Username and Password can be set in workflow for protected models (see ReadMe.txt).

The new release 1.1 will be availabel within the next few days.

Stereotypes for Interfaces are now supported

2007-02-10T09:51:00.001+01:00

Step by step the exporter gets more complet.

With the new release you can define an extension for interfaces in your profile. The newly defined stereotype could now be applied to the interfaces in your model.

Now you could use notes, too.

The new release is available here.