Author Topic: Migration from Rhapsdody to EA  (Read 2079 times)

quadrabyte

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Migration from Rhapsdody to EA
« on: September 22, 2016, 04:09:16 am »
Anybody have any experience/guidance/suggestions regarding a migration from IBM/Rational Rhapsody (we are using version 8.1)? I am trying to convince the powers that be to get away from that obscenely expensive and generally inferior modeling tool. I'm a huge and long time fan of EA but I've just started at this new company so I have to sell them on the change. Any help would be appreciated.

Aaron B

  • EA Administrator
  • EA User
  • *****
  • Posts: 921
  • Karma: +14/-0
    • View Profile
Re: Migration from Rhapsdody to EA
« Reply #1 on: September 22, 2016, 02:43:40 pm »

Uffe

  • EA Practitioner
  • ***
  • Posts: 1274
  • Karma: +93/-8
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Migration from Rhapsdody to EA
« Reply #2 on: September 22, 2016, 06:58:04 pm »
Does that include the diagrams, or is it just the packages and elements?

/U
My theories are always correct, just apply them to the right reality.

mateiacd

  • EA Novice
  • *
  • Posts: 17
  • Karma: +0/-0
    • View Profile
Re: Migration from Rhapsdody to EA
« Reply #3 on: April 16, 2018, 09:07:19 pm »
Hi,

I am also interested in this topic.

I have tried in two ways to import models created with Rhapsody 8.3 trial version into Enterprise Architect 13

I imported two sample models provided by the IBM site:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Wecb8ab5c4be5_4a1e_a0d0_e5a706eb66dc/page/Tutorials,+samples+and+demos

SimpleLogisticsComplete
https://www.ibm.com/developerworks/mydeveloperworks/files/form/anonymous/api/library/371cdc3f-28a3-48d1-b827-72a36707db38/document/1bec3f6d-834a-4538-839b-5e0ec2048361/media/SimpleLogistics_CV_OV.zip

SpaPoolTemp_Control_Architecture
https://www.ibm.com/developerworks/mydeveloperworks/files/form/anonymous/api/library/371cdc3f-28a3-48d1-b827-72a36707db38/document/d3dc766b-512b-4498-bd73-42403ee03484/media/SpaPoolTemp_Control_Architecture.zip


Method 1. Import from .XMI file
Method 2. Import from .RPY file

My experience is not very good even now in 2018, as Geert highlighted in one of his answers from 2011.

http://www.sparxsystems.com/forums/smf/index.php/topic,22895.msg192010.html#msg192010

Quote
"EA imports xmi quite well, but chances are that the diagrams will either be missing, or their layout will be messed up"
"This is a classic issue when transferring models between any two UML tools as xmi is a standard for model interchange, not for diagrams interchange."

1. Importing from an .XMI file, the diagrams are imported, but the visual appearance is not the same and some imported elements do not have the same name as in the original Rhapsody model.

2. Importing from an .RPY file, does not import any diagram at all !

« Last Edit: April 16, 2018, 09:09:38 pm by mateiacd »

aldr1c

  • EA User
  • **
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: Migration from Rhapsdody to EA
« Reply #4 on: June 06, 2018, 08:16:04 pm »
This is an issue we are seeing as well.  Importing via the rpy file omits the diagrams completely.  Importing through XMI creates multiple DAORecordset [3022] errors, creates duplicate named packages with different contents and only imports sequence and a few activity diagrams.  No sysML diagrams (BDD or iBD) coming across.  have tried stripping GUID's etc as well of course.
It is a weird one, and something that I have worked around before  I just cannot recall what we did.

any advice from the EA Druids would be appreciated :)