Thanks, Raphael. Could you sent
the corresponding XMI (model) as well?
Cheers,
Kenn
Hussey
Program Manager, Modeling and Design Solutions
![[Embarcadero Technologies Logo]](jpgzQqIbXxSn2.jpg)
Embarcadero Technologies, Inc. | www.embarcadero.com
82
Peter Street, Second Floor |
Toronto, ON M5V
2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office:
416-593-1585 x9296 Mobile:
613-301-9105
From: Raphael FAUDOU
[mailto:raphael.faudou@xxxxxxxxxxxxxx]
Sent: Friday, April 03, 2009 12:55 PM
To: Kenn Hussey
Cc: TANGUY Yann 176637; Papyrus Project list
Subject: Re: [mdt-papyrus.dev] Model Interchange
Hi Kenn, Yann,
here is the MDT papyrus version for test case1.
Some elements do not appear graphically (composition, aggregation,
multiplicity on association end) but most elements are there.
To be honest, I coudl not work with only the diagram editor and the property
view. I had sometimes to use the model explorer to set some values and then use
drag and drop from the model explorer to reflect it in the diagram.
That is a good beggining.
regards
raphaël
Remark : I tried to commit this test case but could not (commit
refused...).Perhaps due to ssh authorizations that I do not get ?
I will try again on monday
TANGUY Yann 176637 a écrit :
Sure, feel free to create the Papyrus MDT version.
Regards,
Yann
I can if Tanguy has no time to do it. Just tell me
regards
raphaël
Kenn Hussey a écrit :
Yann,
Thanks very much for the update.
Would it be possible for you (or someone else) to produce similar results using
the “new” Papyrus, i.e. based on the source code that’s available at Eclipse?
Thanks,
Kenn Hussey
Program Manager, Modeling and Design Solutions
![[Embarcadero Technologies Logo]](jpgzQqIbXxSn2.jpg)
Embarcadero Technologies, Inc. | www.embarcadero.com
82 Peter Street, Second Floor | Toronto, ON M5V 2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office: 416-593-1585 x9296 Mobile: 613-301-9105
I
join the project with both models.
The
archive contains the following files:
-
KennXMITest_P1.di2 / .uml / .xmi : the model created from scratch (based on you
image)
-
valid.di2 / .uml : the model initiated from your xmi file
-
valid_original.xmi / .uml : a copy of your xmi file and its "manual"
conversion to uml with the UML2 sample editor. You may want to use this
copy to compare with other xmi files.
-
valid_reexport.xmi : the "valid" model reexported back to xmi (still
via UML2 sample editor) after the creation of diagram in valid.di2. I was
curious to compare the initial valid.xmi to the same model after import /
export in the UML2 sample editor.
CEA
SACLAY DRT/LIST/DTSI/SOL/LISE
91191
Gif sur Yvette FRANCE
De: mdt-papyrus.dev-bounces@xxxxxxxxxxx
de la part de Kenn Hussey
Date: ven. 20/03/2009 22:21
À: Papyrus Project list; GERARD Sebastien 166342
Objet : RE: [mdt-papyrus.dev] Model Interchange
Thanks, Yann. Could you remind
me again where the “old” Papyrus can be found? Also, could you send me the XMI
for the models these diagrams are based on?
Cheers,
Kenn Hussey
Program Manager, Modeling and Design Solutions
![Image removed by sender. [Embarcadero Technologies Logo]](jpgte9VSQ2Rts.jpg)
Embarcadero Technologies, Inc. | www.embarcadero.com
82 Peter Street, Second Floor | Toronto, ON M5V 2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office: 416-593-1585 x9296 Mobile: 613-301-9105
Hi Kenn,
I made the test with "old" Papyrus version, creating the
model from scratch, and importing your xmi (via UML2 sample editor) then
creating a class diagram that reference the imported model.
You'll find the results joined to this mail.
Regards
Yann Tanguy.
Sébastien,
Some (minor) changes have been
made to the test case. Could you base your model/diagram on the updated diagram
and “reference” XMI attached?
Thanks,
Kenn Hussey
Program Manager, Modeling and Design Solutions
![Image removed by sender. [Embarcadero Technologies Logo]](jpgte9VSQ2Rts.jpg)
Embarcadero Technologies, Inc. | www.embarcadero.com
82 Peter Street, Second Floor | Toronto, ON M5V 2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office: 416-593-1585 x9296 Mobile: 613-301-9105
Sebastien,
Thanks for your willingness to
participate! To get started, could you please use Papyrus to produce a diagram
similar (as close as possible) to the attached reference diagram (the first
test case) and send a PNG image if it to me. Also, to participate in the
interchange initiative, we will need to provide “standard” UML 2.1.1 XMI based
on the semantic elements shown in the diagram. According to the rules of
engagement for the working group, there should be a user-accessible action to
trigger saving/exporting of the XMI, but it’s OK if that’s not the case
currently (e.g. I could use the UML2 sample editor to produce it for now).
It would be great if you could
do this and send me the results by (my) Monday, although I realize that may be
pushing it… ;)
Cheers,
Kenn Hussey
Program Manager, Modeling and Design Solutions
![Image removed by sender. [Embarcadero Technologies Logo]](jpgte9VSQ2Rts.jpg)
Embarcadero Technologies, Inc. | www.embarcadero.com
82 Peter Street, Second Floor | Toronto, ON M5V 2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office: 416-593-1585 x9296 Mobile: 613-301-9105
From: GERARD Sebastien
166342 [mailto:Sebastien.GERARD@xxxxxx]
Sent: Thursday, March 12, 2009 10:11 AM
To: Kenn Hussey
Cc: MDT UML2 mailing list; Papyrus Project list; MDT UML2 Tools mailing
list
Subject: RE: [mdt-papyrus.dev] Model Interchange
Hi Kenn,
Of course, that's sound good for us. I am also ok to work with you
on that task.
Cheers… Sébastien.
Teams,
There is an initiative underway at the OMG to try to
successfully demonstrate interchange between different products/tools that support
UML modeling. To date, I have been involved the working group that is pursuing
this, by helping prepare test cases. The basic idea is that, for each test
case, a reference diagram and XMI serialization are provided (so far by me) and
each participating vendor/tool is to 1) attempt to create the diagram from
scratch using their tool and save/export the corresponding XMI and 2) attempt
to open/import the XMI produced by the other vendors/tools and report on the
results.
I think it should be important to us that tools based on the
reference open source implementation of UML (like UML2 Tools and Papyrus)
participate in this initiative. I would be happy to represent you in this
initiative, but first I would need an _expression_ of interest from you (e.g.
from your component/project lead) and a general commitment to fixing any issues
that are identified. What do you think?
Please let me know if you have any questions and/or concerns.
Thanks,
Kenn Hussey
Program Manager, Modeling and Design Solutions
![Image removed by sender. [Embarcadero Technologies Logo]](jpgte9VSQ2Rts.jpg)
Embarcadero Technologies, Inc. | www.embarcadero.com
82 Peter Street, Second Floor | Toronto, ON M5V 2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office: 416-593-1585 x9296 Mobile: 613-301-9105
_______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
--

|
Raphaël FAUDOU
Responsable
cellule Innovation / bureau méthodes
Head
of Innovation & Method Definition
Atos
Origin
Tel : +33 (0)5 34 36 32 89
Tel : +33 (0)6 10 53 50 44
Mail : raphael.faudou@xxxxxxxxxxxxxx
|
Atos Origin
6, Impasse Alice Guy
BP 43045
31024 Toulouse Cedex 3
|
P Avant d'imprimer cet e-mail, pensez à
l'environnement. 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.
P Please
consider your environmental responsibility before printing this e-mail. 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.
|
--

|
Raphaël FAUDOU
Responsable
cellule Innovation / bureau méthodes
Head
of Innovation & Method Definition
Atos
Origin
Tel : +33 (0)5 34 36 32 89
Tel : +33 (0)6 10 53 50 44
Mail : raphael.faudou@xxxxxxxxxxxxxx
|
Atos Origin
6, Impasse Alice Guy
BP 43045
31024 Toulouse Cedex 3
|
P Avant d'imprimer cet e-mail, pensez à
l'environnement. 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.
P Please
consider your environmental responsibility before printing this e-mail. 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.
|
|