Book a Demo

Author Topic: importing of profiles / AndroMDA profile  (Read 3513 times)

olafk

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
importing of profiles / AndroMDA profile
« on: August 16, 2005, 08:18:06 pm »
Hi.

I am trying to load the AndroMDA profile --- but am getting "parsing" errors on loading.

(This is the AndroMDA v3.0 profile)

Has anybody had any experience hooking AndroMDA into EA; specifically AndroMDA v3.0?

What exactly are the specs - i.e. the DTD requirements? Andromda shows me the following header content:

<!-- <!DOCTYPE XMI SYSTEM "uml14xmi12.dtd"> -->
<XMI xmi.version='1.2' timestamp='Sun May 08 21:41:43 MDT 2005' xmlns:UML='omg.org/UML/1.4'>
<XMI.header>
 <XMI.documentation>
 <XMI.exporter>MagicDraw UML</XMI.exporter>
 <XMI.exporterVersion>9.0</XMI.exporterVersion>
 </XMI.documentation>
 <XMI.metamodel xmi.name='UML' xmi.version='1.4'/>
</XMI.header>

[snip]


seemingly pointing to UML1.4 and xmi 1.2 (or is that xmi 1.4?).

More interestingly on this forum... what exactly does EA support?

Any comments, help, etc. much appreciated...

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: importing of profiles / AndroMDA profile
« Reply #1 on: August 16, 2005, 08:32:21 pm »
From memory Andromeda uses XMI 1.2 for UML 1.4, so I'm guessing that's what this is.

Are you importing this as XMI and not as a profile?

Make sure you are using Project | Import Project from XMI file. (Or the same in the context menu of a package in the tree view.)

Simon

olafk

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Re: importing of profiles / AndroMDA profile
« Reply #2 on: August 16, 2005, 09:25:14 pm »
Hmm... I am confused now. I thought I was importing a Profile. That is, should I not be using ResourceView->UMLProfiles->ImportProfile?

However, I tried your suggestion - and, well, the importer certainly does not seem to have any further parsing problems. So... seemingly no problem with the UML/XMI versions.

But now, as I thought, I end up with package structures that look like they might very well reflect a profile --- except under the UseCaseView (parent) package; e.g. UseCaseView->Data->...->org.andromda.profile...  with each such package being empty. And no entries under the UML Profiles.

Any further thoughts?

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: importing of profiles / AndroMDA profile
« Reply #3 on: August 17, 2005, 03:42:59 pm »
What you have may be used as a profile in AndroMDA, but it is an XMI file.  Have a look at http://www.sparxsystems.com.au/resources/developers/uml_profiles.html for some examples of what EA expects a Profile to look like.

I'm not sure why the packages would be empty.  It's possible that some information is still being lost in the import.

Look over the file, to make sure that the packages aren't empty.  Then when you are sure that EA is doing the wrong thing, I recommend sending an email to support ([email protected]) with the problem XMI file.

Simon

olafk

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Re: importing of profiles / AndroMDA profile
« Reply #4 on: August 17, 2005, 04:16:14 pm »
Thanks Simon for taking the time...

I had just come to the same conclusion - the page you mention (and the various others leading into and out of it) give a fairly good picture.

In short, it appears to me that the AndroMDA profile  (created by MagicDraw, really) exports the profile into a XMI1.2 format file. EA, on the other hand, represents its profiles in its own custom format (as described on said web pages). Clearly, no go with compatibility.

Now back to importing the thing as an XMI file... Say I was successful (and end up with package content), what would model packages do for me? MagicDraw has exported is profile specs (using XMI profile-related tags etc.), so how can I hope to end up with meaningful package contents? I am needing content in the UML Profile - so as to stereotype/tag/etc. elements in my model...

Or am I missing your point?

cheers,
-olaf.