Home » Modeling » UML2 » Re: UMLProfile vs Ecore
| Re: UMLProfile vs Ecore [message #476459] |
Wed, 07 November 2007 09:15  |
Eclipse User |
|
|
|
Swetha,
I've added the UML2 newsgroups to the "to" list of the reply.
I'm not sure if you are planning to develop a model for a DSL and then
generate an API for it or if you are considering using UML with profiles
as your DSL? The answers for these two are quite different
If it's the former, well, you can use UML and now the UMLTools project
to draw class diagrams, and you can use the Ecore profile to effectively
specify your whole Ecore model using UML. You can then import this into
a GenModel to convert the UML model to an Ecore model and generate your
API and other cool stuff for that model; you can also use GMF to
generate even more cool stuff for your model. You could also do this
directly using Ecore, and with the advent of
http://wiki.eclipse.org/Ecore_Tools_Proposal, you'll be able to draw
your class diagram directly using Ecore. It's also possible to export
your Ecore to UML later. So I see those two approaches as entirely
equivalent and interchangeable. My preference would be for Ecore,
because it's an order of magnitude simpler.
If it's the latter, then UML is very complex and profiles add another
layer of complexity to that. The advantage is that if folks are
familiar with UML, they can reuse those concepts to use UML with
profiles as a DSL. The disadvantage is that UML is complex and might
contain far more concepts than you need. Building your own DSL API will
likely be more work, but will result in something more specifically
tailored to your needs.
Hopefully I've characterized this fairly. I'm sure I'll be corrected if
I didn't.
Swetha wrote:
> Hi,
>
> I am trying to compare the advantages and disadvantages of modeling in
> UMLProfile vs modeling in Ecore.I would like to know from the users of
> either of these which one they prefer since i have no working
> knowledge on either of them.
>
> My modeling will be bascially domain specific,hence i thought
> UMLProfile is the best way to do.But the features provided by Ecore
> and the development happening at Ecore community cannot be ignored.Can
> anybody give me your opinion regarding the pros n cons of the two
> modeling language which will help me decide which modeling language to
> select.
>
>
> Regards,
> Swetha.
>
|
|
|
| Re: UMLProfile vs Ecore [message #476524 is a reply to message #476459] |
Wed, 07 November 2007 10:38  |
| Eclipse User |
|
|
|
Some pros/cons can be found here ...
http://www.eclipse.org/modeling/mdt/uml2/docs/articles/Custo mizing_UML2_Which_Technique_is_Right_For_You/article.html
Cheers,
- James.
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:fgsh6o$e7e$1@build.eclipse.org...
> Swetha,
>
> I've added the UML2 newsgroups to the "to" list of the reply.
>
> I'm not sure if you are planning to develop a model for a DSL and then
> generate an API for it or if you are considering using UML with profiles
> as your DSL? The answers for these two are quite different
>
> If it's the former, well, you can use UML and now the UMLTools project to
> draw class diagrams, and you can use the Ecore profile to effectively
> specify your whole Ecore model using UML. You can then import this into a
> GenModel to convert the UML model to an Ecore model and generate your API
> and other cool stuff for that model; you can also use GMF to generate even
> more cool stuff for your model. You could also do this directly using
> Ecore, and with the advent of
> http://wiki.eclipse.org/Ecore_Tools_Proposal, you'll be able to draw your
> class diagram directly using Ecore. It's also possible to export your
> Ecore to UML later. So I see those two approaches as entirely equivalent
> and interchangeable. My preference would be for Ecore, because it's an
> order of magnitude simpler.
> If it's the latter, then UML is very complex and profiles add another
> layer of complexity to that. The advantage is that if folks are familiar
> with UML, they can reuse those concepts to use UML with profiles as a DSL.
> The disadvantage is that UML is complex and might contain far more
> concepts than you need. Building your own DSL API will likely be more
> work, but will result in something more specifically tailored to your
> needs.
>
> Hopefully I've characterized this fairly. I'm sure I'll be corrected if I
> didn't.
>
>
> Swetha wrote:
>> Hi,
>>
>> I am trying to compare the advantages and disadvantages of modeling in
>> UMLProfile vs modeling in Ecore.I would like to know from the users of
>> either of these which one they prefer since i have no working knowledge
>> on either of them.
>>
>> My modeling will be bascially domain specific,hence i thought UMLProfile
>> is the best way to do.But the features provided by Ecore and the
>> development happening at Ecore community cannot be ignored.Can anybody
>> give me your opinion regarding the pros n cons of the two modeling
>> language which will help me decide which modeling language to select.
>>
>>
>> Regards,
>> Swetha.
>>
|
|
| |
| Re: UMLProfile vs Ecore [message #476680 is a reply to message #476679] |
Wed, 28 November 2007 06:07 |
| Eclipse User |
|
|
|
Hi,
Ecore Tools only provides "Class diagram like" support because the Ecore
langage does not contain Usecase, Component... and all the UML concepts.
But it's the same with UML Profile : you can just define stereotypes and
tagged values.
You must compare equivalent concepts :
- an Ecore metamodel is comparable with a UML Profile
- an instance of your metamodel is comparable with a UML model where
objects are stereotyped with your UML profile.
and equivalent tools :
- Ecore Tools can be used to design an Ecore metamodel / compare to
/ Profile diagram from a UML tool to designe your profile
- Graphical editor for your metamodel (based on GMF) to create
domain specific models / compare to / UML Designer with applied profile
to create UML models stereotyped with your UML profile
I don't know if it's clear but I hope it will help you.
David
Swetha a écrit :
> Hi,
>
> Does Ecore tool provide support for Class diagram only or can we find
> support for Usecase,Component,Deployment,Activity kind of diagrams also.
>
> Regards,
> Swetha.
>
--
David SCIAMMA
Expert Eclipse / Eclipse Expert
ANYWARE TECHNOLOGIES
Tel : + 33 (0)5.61.00.73.44
Fax : + 33 (0)5.61.00.51.46
http://www.anyware-tech.com
|
|
|
| Re: UMLProfile vs Ecore [message #625440 is a reply to message #476459] |
Wed, 07 November 2007 10:38 |
| Eclipse User |
|
|
|
Some pros/cons can be found here ...
http://www.eclipse.org/modeling/mdt/uml2/docs/articles/Custo mizing_UML2_Which_Technique_is_Right_For_You/article.html
Cheers,
- James.
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:fgsh6o$e7e$1@build.eclipse.org...
> Swetha,
>
> I've added the UML2 newsgroups to the "to" list of the reply.
>
> I'm not sure if you are planning to develop a model for a DSL and then
> generate an API for it or if you are considering using UML with profiles
> as your DSL? The answers for these two are quite different
>
> If it's the former, well, you can use UML and now the UMLTools project to
> draw class diagrams, and you can use the Ecore profile to effectively
> specify your whole Ecore model using UML. You can then import this into a
> GenModel to convert the UML model to an Ecore model and generate your API
> and other cool stuff for that model; you can also use GMF to generate even
> more cool stuff for your model. You could also do this directly using
> Ecore, and with the advent of
> http://wiki.eclipse.org/Ecore_Tools_Proposal, you'll be able to draw your
> class diagram directly using Ecore. It's also possible to export your
> Ecore to UML later. So I see those two approaches as entirely equivalent
> and interchangeable. My preference would be for Ecore, because it's an
> order of magnitude simpler.
> If it's the latter, then UML is very complex and profiles add another
> layer of complexity to that. The advantage is that if folks are familiar
> with UML, they can reuse those concepts to use UML with profiles as a DSL.
> The disadvantage is that UML is complex and might contain far more
> concepts than you need. Building your own DSL API will likely be more
> work, but will result in something more specifically tailored to your
> needs.
>
> Hopefully I've characterized this fairly. I'm sure I'll be corrected if I
> didn't.
>
>
> Swetha wrote:
>> Hi,
>>
>> I am trying to compare the advantages and disadvantages of modeling in
>> UMLProfile vs modeling in Ecore.I would like to know from the users of
>> either of these which one they prefer since i have no working knowledge
>> on either of them.
>>
>> My modeling will be bascially domain specific,hence i thought UMLProfile
>> is the best way to do.But the features provided by Ecore and the
>> development happening at Ecore community cannot be ignored.Can anybody
>> give me your opinion regarding the pros n cons of the two modeling
>> language which will help me decide which modeling language to select.
>>
>>
>> Regards,
>> Swetha.
>>
|
|
|
| Re: UMLProfile vs Ecore [message #625579 is a reply to message #476524] |
Wed, 28 November 2007 04:25 |
| Eclipse User |
|
|
|
Hi,
Does Ecore tool provide support for Class diagram only or can we find
support for Usecase,Component,Deployment,Activity kind of diagrams also.
Regards,
Swetha.
|
|
|
| Re: UMLProfile vs Ecore [message #625580 is a reply to message #476679] |
Wed, 28 November 2007 06:07 |
| Eclipse User |
|
|
|
Hi,
Ecore Tools only provides "Class diagram like" support because the Ecore
langage does not contain Usecase, Component... and all the UML concepts.
But it's the same with UML Profile : you can just define stereotypes and
tagged values.
You must compare equivalent concepts :
- an Ecore metamodel is comparable with a UML Profile
- an instance of your metamodel is comparable with a UML model where
objects are stereotyped with your UML profile.
and equivalent tools :
- Ecore Tools can be used to design an Ecore metamodel / compare to
/ Profile diagram from a UML tool to designe your profile
- Graphical editor for your metamodel (based on GMF) to create
domain specific models / compare to / UML Designer with applied profile
to create UML models stereotyped with your UML profile
I don't know if it's clear but I hope it will help you.
David
Swetha a écrit :
> Hi,
>
> Does Ecore tool provide support for Class diagram only or can we find
> support for Usecase,Component,Deployment,Activity kind of diagrams also.
>
> Regards,
> Swetha.
>
--
David SCIAMMA
Expert Eclipse / Eclipse Expert
ANYWARE TECHNOLOGIES
Tel : + 33 (0)5.61.00.73.44
Fax : + 33 (0)5.61.00.51.46
http://www.anyware-tech.com
|
|
|
Goto Forum:
Current Time: Sun Aug 31 16:32:43 EDT 2025
Powered by FUDForum. Page generated in 0.04201 seconds |
Home