Import XMI from MagicDraw

[Wilko Quak]

Hi All,

Since both EA (6.5) and MagicDraw support XMI2.1 I was hoping that I could exchange UML 2.0 class diagrams between the two tools. So far, I've been partially successful: I can import classes from MagicDraw(11.6) but Enumerations get lost in translation.

I've had a look at the XMI produced by both products and I can see where it goes wrong: Magicdraw creates uml:Enumeration elements and EA makes a Class element with a <<enumeration>> stereotype. (So much for interoperability).

Short term question: Does anybody have a workaround or a best practice guide to overcome these kind of problems.

Thanks in advance, Wilko

[«Midnight»]

Why not look into an XSLT tweak?

There's a bit of a learning curve involved if you're not there already, but if that's the only difference in the dialects it should not be too difficult to write a transform.

[Wilko Quak]

Thanks for the suggestion; I'm moderately proficient in writing XSLT and have written a transform that does the trick for me.

Now for the long term question I left out of my original message:

Is someone working on these interoperability issues between the different UML2.1/XMI2.1 documents. I was hoping that the XMI hell was finally over with XMI2.1, but apparently it isn't  

Best wishes, Wilko

[«Midnight»]

We're really in a vise here. OMG is the obvious "someone" who's working on this. But their idea of interoperability is that it is now 'allowed' so the vendors should do it. Sadly, that's were we came in...

Sparx has been pretty good about this, and handles a few of the common dialects.

Unfortunately, this is a two-edged sword for vendors. It can put them in a situation where they are spending a lot of money to ease transition to competing tools.

There are a (very) few tool makers who provide general purpose XMI (or proprietary format) interchange programs. These tools tend to be a bit pricey - they are the core programs of these vendors - but they do work. Problem is, if you are only converting between a small number of applications you're not going to get the best price per use ratio.

Life goes on. Sigh...

[softwaredeveloper]

Hi Midnight & Wilko !

I agree that XMI - as far as I UML newbie knows it - is still much too weak and not exact enough but reg. Wilkos enumeration issue I must answer to Midnight that OMG clearly defines the enumeration element and I think it should be imported/exported as uml:Enumeration (I don't find any "enumeration" stereotype in the whole UML specification).
@Midknight: Was there any reason to use a stereoytpe or did I miss something ?

Thanks a lot

[Eve]

Hey guys,

What exactly is the problem with the xmi import?  EA reads the type of uml:Enumeration and it creates the element that it uses for this element.  On export it recognises this and exports the correct type.  I don't see a compatibility issue at all.

Yes, there is an issue with EA internally using a stereotyped class, but this isn't exposed to XMI.

[«Midnight»]

The stereotype is not mine...

And Simon:

Sparx has been pretty good about this, and handles a few of the common dialects.

I agree with you there.