Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » UML2 » XML/XMI import/export issues?
XML/XMI import/export issues? [message #477505] Wed, 11 June 2008 12:29 Go to next message
Eclipse UserFriend
Originally posted by: kmcgarghan.csc.com

We bought Visual Paradigm to draw UML diagrams [including collaborative
models], and were assured we'd be able, if need be, to convert the XMI to
XML and import into either Eclipse, MyEclipse, or Visio, which are the
preferred tools used by our client. [We need to supply the client with
editable overview, golden path, and alternate path collaboration diagrams.]

We cannot get Visio to import the drawings. We wrote Visual Paradigm about
the problem, and they initially encouraged us to try both in Eclipse and
in MyEclipse.

Having done so, we find that we cannot get either Eclipse or MyEclipse to
import the diagrams as diagrams either, although both programs do 'see'
the attributes and elements as XML.

We wrote Visual Paradigm about the problem again, and this is what they
said:

"Subject [#ZZQ-732542]: problems with XMI

Our engineers had investigated on your problem but unfortunately didn't
able to find you the solution. We have tried the MyEclipse and seems
MyEclipse is still using UML 1.x (but our diagrams are UML 2.1). I think
that's the reason why they cannot import our XMI.

We also tried an alternative solution, which is eclipse uml2tool plugin.
Eclipse uml2tool was able to import our model (XMI 2.1 for UML2), and
re-construct the diagram based on the model (the diagram layout will be
different). But it's shame that they do not support sequence diagram and
communication/collaboration diagram.

Therefore currently there is no way to import our model (communication
diagram) into eclipse in editable way. We are very sorry about this. If
you need any help, please do not hesitate to contact me."

Does anyone know of a way we can get those diagrams exported successfully
AS editable diagrams to Eclipse, MyEclipse, Visio, or some other
widely-used tool?

--kmcgarghan @ csc.com, kmcgarghan @ yahoo.com
Re: XML/XMI import/export issues? [message #477506 is a reply to message #477505] Wed, 11 June 2008 14:04 Go to previous messageGo to next message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Kim,

I've cc'd the uml2tools newsgroup about this. The UML2Tools group would be
able to let you know the status of the various supported diagrams.

It would be nice to keep the newsgroup product neutral but another tool that
supports all the diagram types except timing diagrams is IBM's RSx. It is
built on the opensource UML2 project. It's not freeware however.
Somewhere in the history of postings there was a link to applications that
use the opensource UML2 project. You will probably find a freebie there
that supports Sequence diagrams.

Cheers,
- James.



"Kim McGarghan" <kmcgarghan@csc.com> wrote in message
news:723041abad26765c9b84ee524b352bda$1@www.eclipse.org...
> We bought Visual Paradigm to draw UML diagrams [including collaborative
> models], and were assured we'd be able, if need be, to convert the XMI to
> XML and import into either Eclipse, MyEclipse, or Visio, which are the
> preferred tools used by our client. [We need to supply the client with
> editable overview, golden path, and alternate path collaboration
> diagrams.]
>
> We cannot get Visio to import the drawings. We wrote Visual Paradigm about
> the problem, and they initially encouraged us to try both in Eclipse and
> in MyEclipse.
>
> Having done so, we find that we cannot get either Eclipse or MyEclipse to
> import the diagrams as diagrams either, although both programs do 'see'
> the attributes and elements as XML.
>
> We wrote Visual Paradigm about the problem again, and this is what they
> said:
>
> "Subject [#ZZQ-732542]: problems with XMI
>
> Our engineers had investigated on your problem but unfortunately didn't
> able to find you the solution. We have tried the MyEclipse and seems
> MyEclipse is still using UML 1.x (but our diagrams are UML 2.1). I think
> that's the reason why they cannot import our XMI.
>
> We also tried an alternative solution, which is eclipse uml2tool plugin.
> Eclipse uml2tool was able to import our model (XMI 2.1 for UML2), and
> re-construct the diagram based on the model (the diagram layout will be
> different). But it's shame that they do not support sequence diagram and
> communication/collaboration diagram.
>
> Therefore currently there is no way to import our model (communication
> diagram) into eclipse in editable way. We are very sorry about this. If
> you need any help, please do not hesitate to contact me."
>
> Does anyone know of a way we can get those diagrams exported successfully
> AS editable diagrams to Eclipse, MyEclipse, Visio, or some other
> widely-used tool?
>
> --kmcgarghan @ csc.com, kmcgarghan @ yahoo.com
>
Re: XML/XMI import/export issues? [message #477507 is a reply to message #477506] Wed, 11 June 2008 15:42 Go to previous messageGo to next message
Kenn Hussey is currently offline Kenn HusseyFriend
Messages: 1620
Registered: July 2009
Senior Member
http://wiki.eclipse.org/MDT-UML2-Tool-Compatibility

"James Bruck" <jbruck@ca.ibm.com> wrote in message
news:g2om0k$llo$1@build.eclipse.org...
> Hi Kim,
>
> I've cc'd the uml2tools newsgroup about this. The UML2Tools group would
> be able to let you know the status of the various supported diagrams.
>
> It would be nice to keep the newsgroup product neutral but another tool
> that supports all the diagram types except timing diagrams is IBM's RSx.
> It is built on the opensource UML2 project. It's not freeware however.
> Somewhere in the history of postings there was a link to applications that
> use the opensource UML2 project. You will probably find a freebie there
> that supports Sequence diagrams.
>
> Cheers,
> - James.
>
>
>
> "Kim McGarghan" <kmcgarghan@csc.com> wrote in message
> news:723041abad26765c9b84ee524b352bda$1@www.eclipse.org...
>> We bought Visual Paradigm to draw UML diagrams [including collaborative
>> models], and were assured we'd be able, if need be, to convert the XMI to
>> XML and import into either Eclipse, MyEclipse, or Visio, which are the
>> preferred tools used by our client. [We need to supply the client with
>> editable overview, golden path, and alternate path collaboration
>> diagrams.]
>>
>> We cannot get Visio to import the drawings. We wrote Visual Paradigm
>> about the problem, and they initially encouraged us to try both in
>> Eclipse and in MyEclipse.
>>
>> Having done so, we find that we cannot get either Eclipse or MyEclipse to
>> import the diagrams as diagrams either, although both programs do 'see'
>> the attributes and elements as XML.
>>
>> We wrote Visual Paradigm about the problem again, and this is what they
>> said:
>>
>> "Subject [#ZZQ-732542]: problems with XMI
>>
>> Our engineers had investigated on your problem but unfortunately didn't
>> able to find you the solution. We have tried the MyEclipse and seems
>> MyEclipse is still using UML 1.x (but our diagrams are UML 2.1). I think
>> that's the reason why they cannot import our XMI.
>>
>> We also tried an alternative solution, which is eclipse uml2tool plugin.
>> Eclipse uml2tool was able to import our model (XMI 2.1 for UML2), and
>> re-construct the diagram based on the model (the diagram layout will be
>> different). But it's shame that they do not support sequence diagram and
>> communication/collaboration diagram.
>>
>> Therefore currently there is no way to import our model (communication
>> diagram) into eclipse in editable way. We are very sorry about this. If
>> you need any help, please do not hesitate to contact me."
>>
>> Does anyone know of a way we can get those diagrams exported successfully
>> AS editable diagrams to Eclipse, MyEclipse, Visio, or some other
>> widely-used tool?
>>
>> --kmcgarghan @ csc.com, kmcgarghan @ yahoo.com
>>
>
>
Re: XML/XMI import/export issues? [message #477511 is a reply to message #477505] Thu, 12 June 2008 13:35 Go to previous messageGo to next message
Kenn Hussey is currently offline Kenn HusseyFriend
Messages: 1620
Registered: July 2009
Senior Member
Kim,

Note that interchange of diagrams is still not viable in today's tools (in
the absence of a robust diagram interchange specification). Interchange of
the semantic elements is, as indicated by the vendor below, possible, so I'm
afraid the best you can hope for at this point is to export/import the
semantic elements and recreate the diagrams using the other tool...

Kenn

"Kim McGarghan" <kmcgarghan@csc.com> wrote in message
news:723041abad26765c9b84ee524b352bda$1@www.eclipse.org...
> We bought Visual Paradigm to draw UML diagrams [including collaborative
> models], and were assured we'd be able, if need be, to convert the XMI to
> XML and import into either Eclipse, MyEclipse, or Visio, which are the
> preferred tools used by our client. [We need to supply the client with
> editable overview, golden path, and alternate path collaboration
> diagrams.]
>
> We cannot get Visio to import the drawings. We wrote Visual Paradigm about
> the problem, and they initially encouraged us to try both in Eclipse and
> in MyEclipse.
>
> Having done so, we find that we cannot get either Eclipse or MyEclipse to
> import the diagrams as diagrams either, although both programs do 'see'
> the attributes and elements as XML.
>
> We wrote Visual Paradigm about the problem again, and this is what they
> said:
>
> "Subject [#ZZQ-732542]: problems with XMI
>
> Our engineers had investigated on your problem but unfortunately didn't
> able to find you the solution. We have tried the MyEclipse and seems
> MyEclipse is still using UML 1.x (but our diagrams are UML 2.1). I think
> that's the reason why they cannot import our XMI.
>
> We also tried an alternative solution, which is eclipse uml2tool plugin.
> Eclipse uml2tool was able to import our model (XMI 2.1 for UML2), and
> re-construct the diagram based on the model (the diagram layout will be
> different). But it's shame that they do not support sequence diagram and
> communication/collaboration diagram.
>
> Therefore currently there is no way to import our model (communication
> diagram) into eclipse in editable way. We are very sorry about this. If
> you need any help, please do not hesitate to contact me."
>
> Does anyone know of a way we can get those diagrams exported successfully
> AS editable diagrams to Eclipse, MyEclipse, Visio, or some other
> widely-used tool?
>
> --kmcgarghan @ csc.com, kmcgarghan @ yahoo.com
>
Re: XML/XMI import/export issues? [message #477512 is a reply to message #477511] Thu, 12 June 2008 15:00 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: kmcgarghan.csc.com

Thank you, James. Thanks you, Kenn. Kenn, that was what I was afraid of.
I'll keep hoping someday we'll all support diagram interchange. -- Kim
Re: XML/XMI import/export issues? [message #477561 is a reply to message #477505] Tue, 01 July 2008 14:58 Go to previous messageGo to next message
Tom Morris is currently offline Tom MorrisFriend
Messages: 89
Registered: July 2009
Member
Kim McGarghan wrote:
> We bought Visual Paradigm to draw UML diagrams [including collaborative
> models], and were assured we'd be able, if need be, to convert the XMI
> to XML and import into either Eclipse, MyEclipse, or Visio, which are
> the preferred tools used by our client.

This was disingenuous, to put it politely, of the vendor. In the decade
that the OMG has been working on this graphical modeling language (UML),
there's never been a single instance of graphical interchange between
heterogenous tools.

MyEclipse's UML support is based on a closed source fork of ArgoUML
0.16, which was a UML 1.3-based tool. The latest version of UML that
Visio even attempted to implement was something like UML 1.1.

Kenn Hussey wrote:

> Note that interchange of diagrams is still not viable in today's
tools (in
> the absence of a robust diagram interchange specification).
Interchange of
> the semantic elements is, as indicated by the vendor below, possible,
so I'm
> afraid the best you can hope for at this point is to export/import the
> semantic elements and recreate the diagrams using the other tool...

Semantic data interchange is not completely impossible, but it's often
difficult. In this particular case with three different versions of UML
involved, it will be especially difficult because none of the versions
of UML are compatible with each other (UML 1.5 is a superset of UML 1.4,
but it's not represented among the tools here).

The OMG is a vendor run trade group and standards body, so they're going
to do what the vendors tell them to. Customers need to impress upon
their vendors that the current situation is unacceptable and that
they're not willing to have their design data held hostage any longer.

Since the thread contains a plug for IBM, I'll note that IBM holds the
chair of the group that does this standards work at the OMG as well as a
dominant positition in this market segment, so they probably deserve a
disproportionate share of the blame for the current state of affairs.

Tom
Re: XML/XMI import/export issues? [message #477562 is a reply to message #477561] Tue, 01 July 2008 16:35 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 29552
Registered: July 2009
Senior Member
This is a multi-part message in MIME format.
--------------030203010004070709030802
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Tom,

I was at the OMG meetings last week and my impression is that there's
more than enough blame to be shared by everyone involved.
< http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml>

http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml

From what I've heard, the specification for how to represent diagram
information is so unworkable as to be effectively unimplementable. It
should be possible to exchange conforming serializations of the
underlying UML instances, but diagram exchange I think is still a great
many years away.


Tom Morris wrote:
> Kim McGarghan wrote:
>> We bought Visual Paradigm to draw UML diagrams [including
>> collaborative models], and were assured we'd be able, if need be, to
>> convert the XMI to XML and import into either Eclipse, MyEclipse, or
>> Visio, which are the preferred tools used by our client.
>
> This was disingenuous, to put it politely, of the vendor. In the
> decade that the OMG has been working on this graphical modeling
> language (UML), there's never been a single instance of graphical
> interchange between heterogenous tools.
>
> MyEclipse's UML support is based on a closed source fork of ArgoUML
> 0.16, which was a UML 1.3-based tool. The latest version of UML that
> Visio even attempted to implement was something like UML 1.1.
>
> Kenn Hussey wrote:
>
> > Note that interchange of diagrams is still not viable in today's
> tools (in
> > the absence of a robust diagram interchange specification).
> Interchange of
> > the semantic elements is, as indicated by the vendor below,
> possible, so I'm
> > afraid the best you can hope for at this point is to export/import the
> > semantic elements and recreate the diagrams using the other tool...
>
> Semantic data interchange is not completely impossible, but it's often
> difficult. In this particular case with three different versions of
> UML involved, it will be especially difficult because none of the
> versions of UML are compatible with each other (UML 1.5 is a superset
> of UML 1.4, but it's not represented among the tools here).
>
> The OMG is a vendor run trade group and standards body, so they're
> going to do what the vendors tell them to. Customers need to impress
> upon their vendors that the current situation is unacceptable and that
> they're not willing to have their design data held hostage any longer.
>
> Since the thread contains a plug for IBM, I'll note that IBM holds the
> chair of the group that does this standards work at the OMG as well as
> a dominant positition in this market segment, so they probably deserve
> a disproportionate share of the blame for the current state of affairs.
>
> Tom

--------------030203010004070709030802
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tom,<br>
<br>
I was at the OMG meetings last week and my impression is that there's
more than enough blame to be shared by everyone involved. <a
href=" http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml"><br>
</a>
<blockquote><a
href=" http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml"> http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml</a><br>
</blockquote>
From what I've heard, the specification for how to represent diagram
information is so unworkable as to be effectively unimplementable.
Re: XML/XMI import/export issues? [message #477563 is a reply to message #477562] Tue, 01 July 2008 18:37 Go to previous messageGo to next message
Tom Morris is currently offline Tom MorrisFriend
Messages: 89
Registered: July 2009
Member
Ed Merks wrote:

> I was at the OMG meetings last week and my impression is that there's
> more than enough blame to be shared by everyone involved.
> < http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml>

Thanks for the great writeup!

> It should be possible to exchange conforming serializations of the
> underlying UML instances,

But how would you know you had a "conforming serialization?" :-) In
real world practice, interchange of XMI serialized UML models is
possible, but difficult at best.

> From what I've heard, the specification for how to represent diagram
> information is so unworkable as to be effectively unimplementable.
> [...] but diagram exchange I think is still a great
> many years away.

Rather ironic for a graphical modeling language, particularly one that's
been the focus of a professional standards body for a decade.

Tom
Re: XML/XMI import/export issues? [message #477566 is a reply to message #477563] Wed, 02 July 2008 21:11 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
I think that XMI interchange is currently impossible because UML has moved
too fast from UML 1.4, 1.5, 2.0 to UML 2.1 in just few years.
The only way to make xmi interchange possible is that different vendors
use the same metamodel and the same version(e.g. eclipseuml2). You will
never be able to recover your UML Editor graphical presentation but you
will be able to get back your model displayed and arranged by the new tool.

Another problem is the metamodel approach.
Is-it better to use a model for each diagram or a model for each project ?
It is still possible to merge all small models, but ....
I wrote a small article on the metamodel approach, it could help you to
understand the differences :
http://www.uml2.org/feature_charts/eclipseuml_versus_modelin g_project_diagrams.html

I think that the best is to use one model per project and use the same
metamodel version. For example RSA 7 and Omondo EclipseUML 2008 are using
one model per project and we can easily interchange full project model.
My tool vendor recommendation is to be sure when you purchase a tool that
it is built on the top of EclipseUML2 metamodel.
You will then not have any problem to migrate and maintain your models :-)

Vlad VARNICA
OMONDO
Re: XML/XMI import/export issues? [message #477573 is a reply to message #477561] Mon, 07 July 2008 07:06 Go to previous messageGo to next message
Rafael Chaves is currently offline Rafael ChavesFriend
Messages: 362
Registered: July 2009
Senior Member
Tom Morris wrote:

> MyEclipse's UML support is based on a closed source fork of ArgoUML
> 0.16, which was a UML 1.3-based tool.

Oh, I didn't know that. I had for some reason assumed they were Eclipse
UML2-based. Went to check their website, and they actually don't claim
UML2 compatibility at all. I thus removed MyEclipse from the list of UML2
compatible tools:

http://wiki.eclipse.org/MDT-UML2-Tool-Compatibility

Cheers,

Rafael
Re: XML/XMI import/export issues? [message #477738 is a reply to message #477511] Fri, 19 September 2008 09:33 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
Hi Kenn,

I think that XMI should not just be considered only as a way to import
model from one tool to another. It could a lot more !!
XMI could become the project Datawarehouse having all project information
inside this model.

We are currently working on two issues in our lab:
1. How to import inside an existing EclipseUML model more than one Eclipse
modeling projects.
I have written a small documentation on this subject at:
http://www.forum-omondo.com/documentation_eclipseuml_2008/Mo del_Editor/Multiple_project_model/index.html
2. How to import more than one RSA 7 model inside one EclipseUML project.

We will publish here next week a new link to download our latest beta
build including the merge feature and a tutorial on how to consolidate
RSA 7 models created created with Eclipse 3.2 inside a single EclipseUML
2008 model integrated inside Eclipse 3.4 Ganymede.

Please note that we are only focus on standard UML 2.1 XMI models. If you
model is not valid then you need to transform it using for example ATL
project.
My next week tutorial goal is to prove that model interchange is not a
problem anymore, the problem is the quality of the information, and to be
able to dynamically navigate inside your models and projects.
UML should not just be a blue print because the dark side of the metamodel
force is just about to begin :-)

Vlad VARNICA
OMONDO
Re: XML/XMI import/export issues? [message #477755 is a reply to message #477738] Thu, 25 September 2008 15:55 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
My first tutorial test failed, because we have an EMF problem with
template signature duplication. This problem has already been reported
previously by other community members !!
Except this duplication problem everything is just fine :-).
UML ID remained the same (e.g. the source model ID versus the targeted
merged model).
Dynamic navigation was possible in order to recreate diagram views from
the RSA/ EclipseModeling/ EclipseUML merged models.
Linking models elements being in different models were possible. Adding
dependencies, inheritance, associations etc...

My test was:
First I have created three different projects with RSA 7, Eclipse Modeling
Tools few small models (e.g. default package level is used) and EclipseUML.

Then I have created a new EclipseUML Project and created a class diagram.

Finally I have merged all models coming from different tools by adding one
element of each model (e.g. the model merge is immediately activated after
the first drag and drop).

The tutorial will therefore be delayed because our research lab office
will be closed next week and we need to fix the reported EMF problem.
Thanks,

Vlad VARNICA
OMONDO
Re: XML/XMI import/export issues? [message #477774 is a reply to message #477755] Thu, 02 October 2008 13:18 Go to previous messageGo to next message
Kenn Hussey is currently offline Kenn HusseyFriend
Messages: 1620
Registered: July 2009
Senior Member
OK, thanks Vlad. Just let us know when it's available.

Kenn

"Vlad Varnica" <varnica@omondo.com> wrote in message
news:a4ea15e3f0f3fa9832b5058e9e21a4b9$1@www.eclipse.org...
> My first tutorial test failed, because we have an EMF problem with
> template signature duplication. This problem has already been reported
> previously by other community members !! Except this duplication problem
> everything is just fine :-). UML ID remained the same (e.g. the source
> model ID versus the targeted merged model). Dynamic navigation was
> possible in order to recreate diagram views from the RSA/ EclipseModeling/
> EclipseUML merged models.
> Linking models elements being in different models were possible. Adding
> dependencies, inheritance, associations etc...
>
> My test was:
> First I have created three different projects with RSA 7, Eclipse Modeling
> Tools few small models (e.g. default package level is used) and
> EclipseUML.
>
> Then I have created a new EclipseUML Project and created a class diagram.
>
> Finally I have merged all models coming from different tools by adding one
> element of each model (e.g. the model merge is immediately activated after
> the first drag and drop).
>
> The tutorial will therefore be delayed because our research lab office
> will be closed next week and we need to fix the reported EMF problem.
> Thanks,
>
> Vlad VARNICA
> OMONDO
>
Re: XML/XMI import/export issues? [message #477846 is a reply to message #477774] Fri, 17 October 2008 22:45 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
Kenn Hussey wrote:

> OK, thanks Vlad. Just let us know when it's available.

> Kenn

> "Vlad Varnica" <varnica@omondo.com> wrote in message
> news:a4ea15e3f0f3fa9832b5058e9e21a4b9$1@www.eclipse.org...
>> My first tutorial test failed, because we have an EMF problem with
>> template signature duplication. This problem has already been reported
>> previously by other community members !! Except this duplication problem
>> everything is just fine :-). UML ID remained the same (e.g. the source
>> model ID versus the targeted merged model). Dynamic navigation was
>> possible in order to recreate diagram views from the RSA/ EclipseModeling/
>> EclipseUML merged models.
>> Linking models elements being in different models were possible. Adding
>> dependencies, inheritance, associations etc...
>>
>> My test was:
>> First I have created three different projects with RSA 7, Eclipse Modeling
>> Tools few small models (e.g. default package level is used) and
>> EclipseUML.
>>
>> Then I have created a new EclipseUML Project and created a class diagram.
>>
>> Finally I have merged all models coming from different tools by adding one
>> element of each model (e.g. the model merge is immediately activated after
>> the first drag and drop).
>>
>> The tutorial will therefore be delayed because our research lab office
>> will be closed next week and we need to fix the reported EMF problem.
>> Thanks,
>>
>> Vlad VARNICA
>> OMONDO
>>
Hi Kenn,

The build is finish and will be public next week.
All bugs have been fixed and everything is just perfect.
You can for example have a RSA, or Eclipse Modeling Project model and just
merge them inside EclipseUML.
The question is now why this approach is important and how to explain it.

I think what is important is to be able to model multiple projects.
For example JEE or Java projects are already composed by multiple
projects.
Why UML should only be working at diagram level and not even at project
level ? Why this limitation ?

Another issue is the interoperability between different tools. I mean that
inside the same company you can have architects using RSA, Togethersoft,
etc... and java developers using EclipseUML, Visual ... . Being able for
example by just drag and drop to merge different tools models inside
EclipseUML allows architects to immediately forward theirs project to the
implementation stage. The UML modeling project is now agile from
requirements to implementation without loosing any information.

Another important concept is the dynamic modeling. I mean that being able
to merge different tools model inside EclipseUML model and get a
consolidated model open new perspective. Let's talk about a kind of
company UML super datawharehouse. This will allow dynamic navigation
inside company models. If you look at BI and how they use the datas to
extract critical information then you can see the new frontier of merging
multiple projects and using dynamic navigation inside your models.

I think that these concepts are important and give incredible
opportunities to move from a static UML based on model and model
transformation to dynamic UML based on model datawarehouses.
These concepts are possible because Omondo 2008 architecture is based on a
native GEF, EMF and xmi model integration.
I will come back shortly to explain our vision.
Thanks Kenn for your answer :-)

Vlad VARNICA
Omondo
Re: XML/XMI import/export issues? [message #477951 is a reply to message #477774] Sun, 09 November 2008 12:55 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
Hi kenn,

I have written a tutorial on model interchange between RSA 7 and
EclipseUML 2008
http://www.forum-omondo.com/documentation_eclipseuml_2008/ec lipseuml2008_dynamic_navigation.html#5._Model_interchange_wi ht_RSA_7

The model merge is also successful with our latest build available for
download at:
http://www.omondo-internal-build.com/eclipseUML_E340_2008_st udioEdition_3.4.1.v20081106.jar

Thanks Kenn for your last six years contribution to the EclipseUML2 model
plugin. After so much job done it seems that it is now the official OMG
standard for UML 2.2 :-)

Vlad
Omondo
Re: XML/XMI import/export issues? [message #626696 is a reply to message #477505] Wed, 11 June 2008 14:04 Go to previous messageGo to next message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Kim,

I've cc'd the uml2tools newsgroup about this. The UML2Tools group would be
able to let you know the status of the various supported diagrams.

It would be nice to keep the newsgroup product neutral but another tool that
supports all the diagram types except timing diagrams is IBM's RSx. It is
built on the opensource UML2 project. It's not freeware however.
Somewhere in the history of postings there was a link to applications that
use the opensource UML2 project. You will probably find a freebie there
that supports Sequence diagrams.

Cheers,
- James.



"Kim McGarghan" <kmcgarghan@csc.com> wrote in message
news:723041abad26765c9b84ee524b352bda$1@www.eclipse.org...
> We bought Visual Paradigm to draw UML diagrams [including collaborative
> models], and were assured we'd be able, if need be, to convert the XMI to
> XML and import into either Eclipse, MyEclipse, or Visio, which are the
> preferred tools used by our client. [We need to supply the client with
> editable overview, golden path, and alternate path collaboration
> diagrams.]
>
> We cannot get Visio to import the drawings. We wrote Visual Paradigm about
> the problem, and they initially encouraged us to try both in Eclipse and
> in MyEclipse.
>
> Having done so, we find that we cannot get either Eclipse or MyEclipse to
> import the diagrams as diagrams either, although both programs do 'see'
> the attributes and elements as XML.
>
> We wrote Visual Paradigm about the problem again, and this is what they
> said:
>
> "Subject [#ZZQ-732542]: problems with XMI
>
> Our engineers had investigated on your problem but unfortunately didn't
> able to find you the solution. We have tried the MyEclipse and seems
> MyEclipse is still using UML 1.x (but our diagrams are UML 2.1). I think
> that's the reason why they cannot import our XMI.
>
> We also tried an alternative solution, which is eclipse uml2tool plugin.
> Eclipse uml2tool was able to import our model (XMI 2.1 for UML2), and
> re-construct the diagram based on the model (the diagram layout will be
> different). But it's shame that they do not support sequence diagram and
> communication/collaboration diagram.
>
> Therefore currently there is no way to import our model (communication
> diagram) into eclipse in editable way. We are very sorry about this. If
> you need any help, please do not hesitate to contact me."
>
> Does anyone know of a way we can get those diagrams exported successfully
> AS editable diagrams to Eclipse, MyEclipse, Visio, or some other
> widely-used tool?
>
> --kmcgarghan @ csc.com, kmcgarghan @ yahoo.com
>
Re: XML/XMI import/export issues? [message #626697 is a reply to message #477506] Wed, 11 June 2008 15:42 Go to previous messageGo to next message
Kenn Hussey is currently offline Kenn HusseyFriend
Messages: 1620
Registered: July 2009
Senior Member
http://wiki.eclipse.org/MDT-UML2-Tool-Compatibility

"James Bruck" <jbruck@ca.ibm.com> wrote in message
news:g2om0k$llo$1@build.eclipse.org...
> Hi Kim,
>
> I've cc'd the uml2tools newsgroup about this. The UML2Tools group would
> be able to let you know the status of the various supported diagrams.
>
> It would be nice to keep the newsgroup product neutral but another tool
> that supports all the diagram types except timing diagrams is IBM's RSx.
> It is built on the opensource UML2 project. It's not freeware however.
> Somewhere in the history of postings there was a link to applications that
> use the opensource UML2 project. You will probably find a freebie there
> that supports Sequence diagrams.
>
> Cheers,
> - James.
>
>
>
> "Kim McGarghan" <kmcgarghan@csc.com> wrote in message
> news:723041abad26765c9b84ee524b352bda$1@www.eclipse.org...
>> We bought Visual Paradigm to draw UML diagrams [including collaborative
>> models], and were assured we'd be able, if need be, to convert the XMI to
>> XML and import into either Eclipse, MyEclipse, or Visio, which are the
>> preferred tools used by our client. [We need to supply the client with
>> editable overview, golden path, and alternate path collaboration
>> diagrams.]
>>
>> We cannot get Visio to import the drawings. We wrote Visual Paradigm
>> about the problem, and they initially encouraged us to try both in
>> Eclipse and in MyEclipse.
>>
>> Having done so, we find that we cannot get either Eclipse or MyEclipse to
>> import the diagrams as diagrams either, although both programs do 'see'
>> the attributes and elements as XML.
>>
>> We wrote Visual Paradigm about the problem again, and this is what they
>> said:
>>
>> "Subject [#ZZQ-732542]: problems with XMI
>>
>> Our engineers had investigated on your problem but unfortunately didn't
>> able to find you the solution. We have tried the MyEclipse and seems
>> MyEclipse is still using UML 1.x (but our diagrams are UML 2.1). I think
>> that's the reason why they cannot import our XMI.
>>
>> We also tried an alternative solution, which is eclipse uml2tool plugin.
>> Eclipse uml2tool was able to import our model (XMI 2.1 for UML2), and
>> re-construct the diagram based on the model (the diagram layout will be
>> different). But it's shame that they do not support sequence diagram and
>> communication/collaboration diagram.
>>
>> Therefore currently there is no way to import our model (communication
>> diagram) into eclipse in editable way. We are very sorry about this. If
>> you need any help, please do not hesitate to contact me."
>>
>> Does anyone know of a way we can get those diagrams exported successfully
>> AS editable diagrams to Eclipse, MyEclipse, Visio, or some other
>> widely-used tool?
>>
>> --kmcgarghan @ csc.com, kmcgarghan @ yahoo.com
>>
>
>
Re: XML/XMI import/export issues? [message #626701 is a reply to message #477505] Thu, 12 June 2008 13:35 Go to previous messageGo to next message
Kenn Hussey is currently offline Kenn HusseyFriend
Messages: 1620
Registered: July 2009
Senior Member
Kim,

Note that interchange of diagrams is still not viable in today's tools (in
the absence of a robust diagram interchange specification). Interchange of
the semantic elements is, as indicated by the vendor below, possible, so I'm
afraid the best you can hope for at this point is to export/import the
semantic elements and recreate the diagrams using the other tool...

Kenn

"Kim McGarghan" <kmcgarghan@csc.com> wrote in message
news:723041abad26765c9b84ee524b352bda$1@www.eclipse.org...
> We bought Visual Paradigm to draw UML diagrams [including collaborative
> models], and were assured we'd be able, if need be, to convert the XMI to
> XML and import into either Eclipse, MyEclipse, or Visio, which are the
> preferred tools used by our client. [We need to supply the client with
> editable overview, golden path, and alternate path collaboration
> diagrams.]
>
> We cannot get Visio to import the drawings. We wrote Visual Paradigm about
> the problem, and they initially encouraged us to try both in Eclipse and
> in MyEclipse.
>
> Having done so, we find that we cannot get either Eclipse or MyEclipse to
> import the diagrams as diagrams either, although both programs do 'see'
> the attributes and elements as XML.
>
> We wrote Visual Paradigm about the problem again, and this is what they
> said:
>
> "Subject [#ZZQ-732542]: problems with XMI
>
> Our engineers had investigated on your problem but unfortunately didn't
> able to find you the solution. We have tried the MyEclipse and seems
> MyEclipse is still using UML 1.x (but our diagrams are UML 2.1). I think
> that's the reason why they cannot import our XMI.
>
> We also tried an alternative solution, which is eclipse uml2tool plugin.
> Eclipse uml2tool was able to import our model (XMI 2.1 for UML2), and
> re-construct the diagram based on the model (the diagram layout will be
> different). But it's shame that they do not support sequence diagram and
> communication/collaboration diagram.
>
> Therefore currently there is no way to import our model (communication
> diagram) into eclipse in editable way. We are very sorry about this. If
> you need any help, please do not hesitate to contact me."
>
> Does anyone know of a way we can get those diagrams exported successfully
> AS editable diagrams to Eclipse, MyEclipse, Visio, or some other
> widely-used tool?
>
> --kmcgarghan @ csc.com, kmcgarghan @ yahoo.com
>
Re: XML/XMI import/export issues? [message #626702 is a reply to message #477511] Thu, 12 June 2008 15:00 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: kmcgarghan.csc.com

Thank you, James. Thanks you, Kenn. Kenn, that was what I was afraid of.
I'll keep hoping someday we'll all support diagram interchange. -- Kim
Re: XML/XMI import/export issues? [message #626752 is a reply to message #477505] Tue, 01 July 2008 14:58 Go to previous messageGo to next message
Tom Morris is currently offline Tom MorrisFriend
Messages: 89
Registered: July 2009
Member
Kim McGarghan wrote:
> We bought Visual Paradigm to draw UML diagrams [including collaborative
> models], and were assured we'd be able, if need be, to convert the XMI
> to XML and import into either Eclipse, MyEclipse, or Visio, which are
> the preferred tools used by our client.

This was disingenuous, to put it politely, of the vendor. In the decade
that the OMG has been working on this graphical modeling language (UML),
there's never been a single instance of graphical interchange between
heterogenous tools.

MyEclipse's UML support is based on a closed source fork of ArgoUML
0.16, which was a UML 1.3-based tool. The latest version of UML that
Visio even attempted to implement was something like UML 1.1.

Kenn Hussey wrote:

> Note that interchange of diagrams is still not viable in today's
tools (in
> the absence of a robust diagram interchange specification).
Interchange of
> the semantic elements is, as indicated by the vendor below, possible,
so I'm
> afraid the best you can hope for at this point is to export/import the
> semantic elements and recreate the diagrams using the other tool...

Semantic data interchange is not completely impossible, but it's often
difficult. In this particular case with three different versions of UML
involved, it will be especially difficult because none of the versions
of UML are compatible with each other (UML 1.5 is a superset of UML 1.4,
but it's not represented among the tools here).

The OMG is a vendor run trade group and standards body, so they're going
to do what the vendors tell them to. Customers need to impress upon
their vendors that the current situation is unacceptable and that
they're not willing to have their design data held hostage any longer.

Since the thread contains a plug for IBM, I'll note that IBM holds the
chair of the group that does this standards work at the OMG as well as a
dominant positition in this market segment, so they probably deserve a
disproportionate share of the blame for the current state of affairs.

Tom
Re: XML/XMI import/export issues? [message #626753 is a reply to message #477561] Tue, 01 July 2008 16:35 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 29552
Registered: July 2009
Senior Member
This is a multi-part message in MIME format.
--------------030203010004070709030802
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Tom,

I was at the OMG meetings last week and my impression is that there's
more than enough blame to be shared by everyone involved.
< http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml>

http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml

From what I've heard, the specification for how to represent diagram
information is so unworkable as to be effectively unimplementable. It
should be possible to exchange conforming serializations of the
underlying UML instances, but diagram exchange I think is still a great
many years away.


Tom Morris wrote:
> Kim McGarghan wrote:
>> We bought Visual Paradigm to draw UML diagrams [including
>> collaborative models], and were assured we'd be able, if need be, to
>> convert the XMI to XML and import into either Eclipse, MyEclipse, or
>> Visio, which are the preferred tools used by our client.
>
> This was disingenuous, to put it politely, of the vendor. In the
> decade that the OMG has been working on this graphical modeling
> language (UML), there's never been a single instance of graphical
> interchange between heterogenous tools.
>
> MyEclipse's UML support is based on a closed source fork of ArgoUML
> 0.16, which was a UML 1.3-based tool. The latest version of UML that
> Visio even attempted to implement was something like UML 1.1.
>
> Kenn Hussey wrote:
>
> > Note that interchange of diagrams is still not viable in today's
> tools (in
> > the absence of a robust diagram interchange specification).
> Interchange of
> > the semantic elements is, as indicated by the vendor below,
> possible, so I'm
> > afraid the best you can hope for at this point is to export/import the
> > semantic elements and recreate the diagrams using the other tool...
>
> Semantic data interchange is not completely impossible, but it's often
> difficult. In this particular case with three different versions of
> UML involved, it will be especially difficult because none of the
> versions of UML are compatible with each other (UML 1.5 is a superset
> of UML 1.4, but it's not represented among the tools here).
>
> The OMG is a vendor run trade group and standards body, so they're
> going to do what the vendors tell them to. Customers need to impress
> upon their vendors that the current situation is unacceptable and that
> they're not willing to have their design data held hostage any longer.
>
> Since the thread contains a plug for IBM, I'll note that IBM holds the
> chair of the group that does this standards work at the OMG as well as
> a dominant positition in this market segment, so they probably deserve
> a disproportionate share of the blame for the current state of affairs.
>
> Tom

--------------030203010004070709030802
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tom,<br>
<br>
I was at the OMG meetings last week and my impression is that there's
more than enough blame to be shared by everyone involved. <a
href=" http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml"><br>
</a>
<blockquote><a
href=" http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml"> http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml</a><br>
</blockquote>
From what I've heard, the specification for how to represent diagram
information is so unworkable as to be effectively unimplementable.
Re: XML/XMI import/export issues? [message #626754 is a reply to message #477562] Tue, 01 July 2008 18:37 Go to previous messageGo to next message
Tom Morris is currently offline Tom MorrisFriend
Messages: 89
Registered: July 2009
Member
Ed Merks wrote:

> I was at the OMG meetings last week and my impression is that there's
> more than enough blame to be shared by everyone involved.
> < http://ed-merks.blogspot.com/2008/06/eclipse-omg-symposium.h tml>

Thanks for the great writeup!

> It should be possible to exchange conforming serializations of the
> underlying UML instances,

But how would you know you had a "conforming serialization?" :-) In
real world practice, interchange of XMI serialized UML models is
possible, but difficult at best.

> From what I've heard, the specification for how to represent diagram
> information is so unworkable as to be effectively unimplementable.
> [...] but diagram exchange I think is still a great
> many years away.

Rather ironic for a graphical modeling language, particularly one that's
been the focus of a professional standards body for a decade.

Tom
Re: XML/XMI import/export issues? [message #626757 is a reply to message #477563] Wed, 02 July 2008 21:11 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
I think that XMI interchange is currently impossible because UML has moved
too fast from UML 1.4, 1.5, 2.0 to UML 2.1 in just few years.
The only way to make xmi interchange possible is that different vendors
use the same metamodel and the same version(e.g. eclipseuml2). You will
never be able to recover your UML Editor graphical presentation but you
will be able to get back your model displayed and arranged by the new tool.

Another problem is the metamodel approach.
Is-it better to use a model for each diagram or a model for each project ?
It is still possible to merge all small models, but ....
I wrote a small article on the metamodel approach, it could help you to
understand the differences :
http://www.uml2.org/feature_charts/eclipseuml_versus_modelin g_project_diagrams.html

I think that the best is to use one model per project and use the same
metamodel version. For example RSA 7 and Omondo EclipseUML 2008 are using
one model per project and we can easily interchange full project model.
My tool vendor recommendation is to be sure when you purchase a tool that
it is built on the top of EclipseUML2 metamodel.
You will then not have any problem to migrate and maintain your models :-)

Vlad VARNICA
OMONDO
Re: XML/XMI import/export issues? [message #626766 is a reply to message #477561] Mon, 07 July 2008 07:06 Go to previous messageGo to next message
Rafael Chaves is currently offline Rafael ChavesFriend
Messages: 362
Registered: July 2009
Senior Member
Tom Morris wrote:

> MyEclipse's UML support is based on a closed source fork of ArgoUML
> 0.16, which was a UML 1.3-based tool.

Oh, I didn't know that. I had for some reason assumed they were Eclipse
UML2-based. Went to check their website, and they actually don't claim
UML2 compatibility at all. I thus removed MyEclipse from the list of UML2
compatible tools:

http://wiki.eclipse.org/MDT-UML2-Tool-Compatibility

Cheers,

Rafael
Re: XML/XMI import/export issues? [message #626937 is a reply to message #477511] Fri, 19 September 2008 09:33 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
Hi Kenn,

I think that XMI should not just be considered only as a way to import
model from one tool to another. It could a lot more !!
XMI could become the project Datawarehouse having all project information
inside this model.

We are currently working on two issues in our lab:
1. How to import inside an existing EclipseUML model more than one Eclipse
modeling projects.
I have written a small documentation on this subject at:
http://www.forum-omondo.com/documentation_eclipseuml_2008/Mo del_Editor/Multiple_project_model/index.html
2. How to import more than one RSA 7 model inside one EclipseUML project.

We will publish here next week a new link to download our latest beta
build including the merge feature and a tutorial on how to consolidate
RSA 7 models created created with Eclipse 3.2 inside a single EclipseUML
2008 model integrated inside Eclipse 3.4 Ganymede.

Please note that we are only focus on standard UML 2.1 XMI models. If you
model is not valid then you need to transform it using for example ATL
project.
My next week tutorial goal is to prove that model interchange is not a
problem anymore, the problem is the quality of the information, and to be
able to dynamically navigate inside your models and projects.
UML should not just be a blue print because the dark side of the metamodel
force is just about to begin :-)

Vlad VARNICA
OMONDO
Re: XML/XMI import/export issues? [message #626954 is a reply to message #477738] Thu, 25 September 2008 15:55 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
My first tutorial test failed, because we have an EMF problem with
template signature duplication. This problem has already been reported
previously by other community members !!
Except this duplication problem everything is just fine :-).
UML ID remained the same (e.g. the source model ID versus the targeted
merged model).
Dynamic navigation was possible in order to recreate diagram views from
the RSA/ EclipseModeling/ EclipseUML merged models.
Linking models elements being in different models were possible. Adding
dependencies, inheritance, associations etc...

My test was:
First I have created three different projects with RSA 7, Eclipse Modeling
Tools few small models (e.g. default package level is used) and EclipseUML.

Then I have created a new EclipseUML Project and created a class diagram.

Finally I have merged all models coming from different tools by adding one
element of each model (e.g. the model merge is immediately activated after
the first drag and drop).

The tutorial will therefore be delayed because our research lab office
will be closed next week and we need to fix the reported EMF problem.
Thanks,

Vlad VARNICA
OMONDO
Re: XML/XMI import/export issues? [message #626972 is a reply to message #477755] Thu, 02 October 2008 13:18 Go to previous messageGo to next message
Kenn Hussey is currently offline Kenn HusseyFriend
Messages: 1620
Registered: July 2009
Senior Member
OK, thanks Vlad. Just let us know when it's available.

Kenn

"Vlad Varnica" <varnica@omondo.com> wrote in message
news:a4ea15e3f0f3fa9832b5058e9e21a4b9$1@www.eclipse.org...
> My first tutorial test failed, because we have an EMF problem with
> template signature duplication. This problem has already been reported
> previously by other community members !! Except this duplication problem
> everything is just fine :-). UML ID remained the same (e.g. the source
> model ID versus the targeted merged model). Dynamic navigation was
> possible in order to recreate diagram views from the RSA/ EclipseModeling/
> EclipseUML merged models.
> Linking models elements being in different models were possible. Adding
> dependencies, inheritance, associations etc...
>
> My test was:
> First I have created three different projects with RSA 7, Eclipse Modeling
> Tools few small models (e.g. default package level is used) and
> EclipseUML.
>
> Then I have created a new EclipseUML Project and created a class diagram.
>
> Finally I have merged all models coming from different tools by adding one
> element of each model (e.g. the model merge is immediately activated after
> the first drag and drop).
>
> The tutorial will therefore be delayed because our research lab office
> will be closed next week and we need to fix the reported EMF problem.
> Thanks,
>
> Vlad VARNICA
> OMONDO
>
Re: XML/XMI import/export issues? [message #627049 is a reply to message #477774] Fri, 17 October 2008 22:45 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
Kenn Hussey wrote:

> OK, thanks Vlad. Just let us know when it's available.

> Kenn

> "Vlad Varnica" <varnica@omondo.com> wrote in message
> news:a4ea15e3f0f3fa9832b5058e9e21a4b9$1@www.eclipse.org...
>> My first tutorial test failed, because we have an EMF problem with
>> template signature duplication. This problem has already been reported
>> previously by other community members !! Except this duplication problem
>> everything is just fine :-). UML ID remained the same (e.g. the source
>> model ID versus the targeted merged model). Dynamic navigation was
>> possible in order to recreate diagram views from the RSA/ EclipseModeling/
>> EclipseUML merged models.
>> Linking models elements being in different models were possible. Adding
>> dependencies, inheritance, associations etc...
>>
>> My test was:
>> First I have created three different projects with RSA 7, Eclipse Modeling
>> Tools few small models (e.g. default package level is used) and
>> EclipseUML.
>>
>> Then I have created a new EclipseUML Project and created a class diagram.
>>
>> Finally I have merged all models coming from different tools by adding one
>> element of each model (e.g. the model merge is immediately activated after
>> the first drag and drop).
>>
>> The tutorial will therefore be delayed because our research lab office
>> will be closed next week and we need to fix the reported EMF problem.
>> Thanks,
>>
>> Vlad VARNICA
>> OMONDO
>>
Hi Kenn,

The build is finish and will be public next week.
All bugs have been fixed and everything is just perfect.
You can for example have a RSA, or Eclipse Modeling Project model and just
merge them inside EclipseUML.
The question is now why this approach is important and how to explain it.

I think what is important is to be able to model multiple projects.
For example JEE or Java projects are already composed by multiple
projects.
Why UML should only be working at diagram level and not even at project
level ? Why this limitation ?

Another issue is the interoperability between different tools. I mean that
inside the same company you can have architects using RSA, Togethersoft,
etc... and java developers using EclipseUML, Visual ... . Being able for
example by just drag and drop to merge different tools models inside
EclipseUML allows architects to immediately forward theirs project to the
implementation stage. The UML modeling project is now agile from
requirements to implementation without loosing any information.

Another important concept is the dynamic modeling. I mean that being able
to merge different tools model inside EclipseUML model and get a
consolidated model open new perspective. Let's talk about a kind of
company UML super datawharehouse. This will allow dynamic navigation
inside company models. If you look at BI and how they use the datas to
extract critical information then you can see the new frontier of merging
multiple projects and using dynamic navigation inside your models.

I think that these concepts are important and give incredible
opportunities to move from a static UML based on model and model
transformation to dynamic UML based on model datawarehouses.
These concepts are possible because Omondo 2008 architecture is based on a
native GEF, EMF and xmi model integration.
I will come back shortly to explain our vision.
Thanks Kenn for your answer :-)

Vlad VARNICA
Omondo
Re: XML/XMI import/export issues? [message #627163 is a reply to message #477774] Sun, 09 November 2008 12:55 Go to previous messageGo to next message
Vlad Varnica is currently offline Vlad VarnicaFriend
Messages: 546
Registered: July 2009
Location: Milton Keynes - UK
Senior Member
Hi kenn,

I have written a tutorial on model interchange between RSA 7 and
EclipseUML 2008
http://www.forum-omondo.com/documentation_eclipseuml_2008/ec lipseuml2008_dynamic_navigation.html#5._Model_interchange_wi ht_RSA_7

The model merge is also successful with our latest build available for
download at:
http://www.omondo-internal-build.com/eclipseUML_E340_2008_st udioEdition_3.4.1.v20081106.jar

Thanks Kenn for your last six years contribution to the EclipseUML2 model
plugin. After so much job done it seems that it is now the official OMG
standard for UML 2.2 :-)

Vlad
Omondo
Re: XML/XMI import/export issues? [message #1792631 is a reply to message #477951] Fri, 20 July 2018 11:12 Go to previous messageGo to next message
Bea Perez is currently offline Bea PerezFriend
Messages: 24
Registered: July 2012
Junior Member
Hello!
does anyone know whether it is possible to export a model in XMI using Visual Paradigm and importing it from an UML compliant Eclipse plug-in?

Thank you very much in advance.
Bea
Re: XML/XMI import/export issues? [message #1792632 is a reply to message #477951] Fri, 20 July 2018 11:12 Go to previous messageGo to next message
Bea Perez is currently offline Bea PerezFriend
Messages: 24
Registered: July 2012
Junior Member
Hello!
does anyone know whether it is possible to export a model in XMI using Visual Paradigm and importing it from a UML compliant Eclipse plug-in?

Thank you very much in advance.
Bea

[Updated on: Fri, 20 July 2018 11:13]

Report message to a moderator

Re: XML/XMI import/export issues? [message #1792640 is a reply to message #1792632] Fri, 20 July 2018 12:07 Go to previous messageGo to next message
Ed Willink is currently offline Ed WillinkFriend
Messages: 6044
Registered: July 2009
Senior Member
Hi

Any UML model should be using XMI, which Eclipse UML2 uses, so it should just work. Hiwever some tools have not yet moved to UML 2.5 yet, so without an example, who knows?

Regards

Ed Willink

Re: XML/XMI import/export issues? [message #1792766 is a reply to message #1792640] Mon, 23 July 2018 16:12 Go to previous message
Bea Perez is currently offline Bea PerezFriend
Messages: 24
Registered: July 2012
Junior Member
Thanks Ed!
I know that, at least a time ago, XMI models generated from Visual Paradigm where not compatible with the standard UML used by other tools (such as Eclipse UML2).

Anybody has tried that?
Bea
Previous Topic:OMG XMI to Eclipse UML or to Ecore - best option?
Next Topic:How to get instance of stereotype as generated ecore class instance
Goto Forum:
  


Current Time: Wed Sep 26 00:28:29 GMT 2018

Powered by FUDForum. Page generated in 0.03617 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top