Hi, comments bellow


-----Message d'origine-----
De : [email protected] 
[mailto:[email protected]] De la part de Topcased user 
list where issues are discussed
Envoyé : mercredi 25 mai 2011 15:39
À : [email protected]
Objet : Re: [Topcased-users] SysML model export to (and import from) Rhapsody



Hi,



sorry for the late answer.



I give you some more details:

- XMI files exported from Rhapsody have UML and SysML namespaces by omg.org 
(thus it is an UML metamodel with an applied SysML profile)

[Tristan FAURE] Yes it seems "normal" as I'm not sure there is conventions 
about Namespace names

- XMI files exported from TOPCASED have an UML namespace by eclipse.org and 
SysML namespace by topcased.org (thus it is a SysML metamodel modeled with the 
Eclipse EMF/UML modeling framework?)

[Tristan FAURE] The namespace is Topcased.org, because it is a meta model 
implementation made by topcased

- Rhapsody can import TOPCASED .uml files (I suppose they are Eclipse .uml 
files in this case?), all UML model elements that I tried are recognized and 
imported

[Tristan FAURE] Yes it is

- If I try to import TOPCASED .sysml files into Rhapsody, no elements specific 
for SysML are imported (e.g., blocks), but UML-specific ones (e.g., packages)

- If I try to export XMI from Rhapsody to TOPCASED, all SysML specific 
information is lost. For instance, blocks are imported as classes since in 
Rhapsody a block is a class with stereotype block (from a profile unknown to 
TOPCASED).

[Tristan FAURE] It seems Rhapsody have problems with stereotypes export. For 
SysML import it could be normal as topcased had made the choice to describe 
SysML as a metamodel and not as a profile. Do you have problem with Rhapsody 
when you export UML models with other profiles than SysML ?



We think about model transformations, too. But until now we do not know how to 
enforce the application of the Rhapsody-SysML-Profile for the import into 
Rhapsody such that a TOPCASED-Block gets a class with stereotype block from the 
Rhapsody metamodel and profile.



[Tristan FAURE] Regards

Tristan

Regards,

Joerg



-----Ursprüngliche Nachricht-----

Von: [email protected] 
[mailto:[email protected]] Im Auftrag von Topcased user 
list where issues are discussed

Gesendet: Donnerstag, 19. Mai 2011 10:44

An: [email protected]; [email protected]

Betreff: Re: [Topcased-users] SysML model export to (and import from) Rhapsody



Hi,

We currently have no Rhapsody license, migrating is I can possible using custom 
transformation tool.



Do you know if Rhapsody can import Eclipse .uml files ?



Regards



Tristan FAURE



-----Message d'origine-----

De : [email protected] 
[mailto:[email protected]] De la part de Topcased user 
list where issues are discussed Envoyé : mardi 17 mai 2011 14:21 À : 
[email protected]

Objet : [Topcased-users] SysML model export to (and import from) Rhapsody



Hello Topcased Users,



we are currently looking for a way to export SysML models from Topcased to 
Rhapsody and import them back again. Does someone of you know a way to achieve 
this, at least one direction? A default XMI import/export does not work since 
different UML metamodels and SysML profiles are used. I found former questions 
about this subject on this mailing list, but there was no satisfying answer.



Yours sincerely,

Joerg



--

Jörg Holtmann

Diplom-Informatiker

Researcher



s-lab - Software Quality Lab

Universität Paderborn

Warburger Str. 100

D-33098 Paderborn



Fon     +49 5251 60-5252

Fax     +49 5251 60-3985

E-Mail  [email protected]

Web     http://s-lab.upb.de







_______________________________________________

Topcased-users mailing list

[email protected]

http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users



________________________________





Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra 
être recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.



This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Origin group liability cannot be triggered 
for the message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.





_______________________________________________

Topcased-users mailing list

[email protected]

http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users



_______________________________________________

Topcased-users mailing list

[email protected]

http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users


_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users

Reply via email to