|
| Re: Features UML Model can't be expressed ina Ecore Model [message #883004 is a reply to message #882995] |
Thu, 07 June 2012 16:08   |
 Ed Merks
Messages: 33218
Registered: July 2009 |
Senior Member |
|
|
Arnedo,
Comments below.
On 07/06/2012 5:49 PM, Arnedo Ramon wrote:
> Hi,
>
> I have to find something in a UML model that is not possible to
> convert into an Ecore model.
For what purpose do you need to find such things?
> I know some of the features of a Ecore Model cannot be expressed
> directly in UML, for example: resolveproxies, nsURI and nsPrefix
> attributes of a Package,...
Yes, there's an Ecore profile for such things.
> But, what is not possible to express in Ecore from a UML model?
That's a long list. All the information in diagrams other than class
diagrams. Ecore/EMOF also don't have associations, only references
paired as opposites....
>
> Thanks in advance.
>
> Ramón.
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Features UML Model can't be expressed ina Ecore Model [message #883018 is a reply to message #883004] |
Thu, 07 June 2012 16:48 |
Arnedo Ramon
Messages: 14
Registered: March 2012 |
Junior Member |
|
|
Thanks for all.
Comments in green.
> I have to find something in a UML model that is not possible to
> convert into an Ecore model.
For what purpose do you need to find such things?
Because I am doing some research on this issue. I need it for my project. Is it so weird?
> I know some of the features of a Ecore Model cannot be expressed
> directly in UML, for example: resolveproxies, nsURI and nsPrefix
> attributes of a Package,...
Yes, there's an Ecore profile for such things.
> But, what is not possible to express in Ecore from a UML model?
That's a long list. All the information in diagrams other than class
diagrams. Ecore/EMOF also don't have associations, only references
paired as opposites...
Yes, I know this because I read (not deeply) the chapter 6- UML of your book "EMF Eclipse Modeling Framework".
I meant only in the class diagrams. UML has associations and Ecore doesn't, but the association s map to two references. So, it exists a mapping.
Are there some features (in a UML class diagram) which have not a mapping to Ecore?
|
|
|
| Re: Features UML Model can't be expressed ina Ecore Model [message #883024 is a reply to message #883018] |
Thu, 07 June 2012 16:57 |
Ed Willink
Messages: 7670
Registered: July 2009 |
Senior Member |
|
|
Hi
For the purposes of your question you can consider EMOF and Ecore to be
identical, so I recommend studying the OMG specifications to see what
was lost in the trimming of UML to EMOF. You could use tooling to
compare meta-models.
Regards
Ed Willink
On 07/06/2012 17:48, Arnedo Ramon wrote:
> Thanks for all.
>
> Comments in green.
>
>> I have to find something in a UML model that is not possible to
>> convert into an Ecore model.
>
> For what purpose do you need to find such things?
>
> Because I am doing some research on this issue. I need it for my
> project. Is it so weird?
>> I know some of the features of a Ecore Model cannot be expressed
>> directly in UML, for example: resolveproxies, nsURI and nsPrefix
>> attributes of a Package,...
>
> Yes, there's an Ecore profile for such things.
>
>> But, what is not possible to express in Ecore from a UML model?
>
> That's a long list. All the information in diagrams other than class
> diagrams. Ecore/EMOF also don't have associations, only references
> paired as opposites...
>
> Yes, I know this because I read (not deeply) the chapter 6- UML of
> your book "EMF Eclipse Modeling Framework".
> I meant only in the class diagrams. UML has associations and Ecore
> doesn't, but the association s map to two references. So, it exists a
> mapping.
> Are there some features (in a UML class diagram) which have not a
> mapping to Ecore?
|
|
|
| Re: Features UML Model can't be expressed ina Ecore Model [message #883061 is a reply to message #883018] |
Thu, 07 June 2012 19:02 |
Ed Merks
Messages: 33218
Registered: July 2009 |
Senior Member |
|
|
Arnedo,
Comments below.
On 07/06/2012 6:48 PM, Arnedo Ramon wrote:
> Thanks for all.
>
> Comments in green.
>
>> I have to find something in a UML model that is not possible to
>> convert into an Ecore model.
>
> For what purpose do you need to find such things?
>
> Because I am doing some research on this issue. I need it for my
> project. Is it so weird?
No, though research generally involves figuring out how to answer
questions yourself...
>> I know some of the features of a Ecore Model cannot be expressed
>> directly in UML, for example: resolveproxies, nsURI and nsPrefix
>> attributes of a Package,...
>
> Yes, there's an Ecore profile for such things.
>
>> But, what is not possible to express in Ecore from a UML model?
>
> That's a long list. All the information in diagrams other than class
> diagrams. Ecore/EMOF also don't have associations, only references
> paired as opposites...
>
> Yes, I know this because I read (not deeply) the chapter 6- UML of
> your book "EMF Eclipse Modeling Framework".
Research generally involves reaching deep understanding... Or am I
weird to think that?
> I meant only in the class diagrams. UML has associations and Ecore
> doesn't, but the association s map to two references. So, it exists a
> mapping.
Yes, but association attributes can't be mapped because there is no
modeled object representing an association instance....
> Are there some features (in a UML class diagram) which have not a
> mapping to Ecore?
I prefer to spend my time answering questions for people who are solving
real problems not just asking questions for purely interest sake....
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04130 seconds
] 
Search
Help
Register
Login
Home
