|Re: One EClass for Two Ecore models [message #1517020 is a reply to message #1516221]
||Fri, 19 December 2014 07:42
| Ed Merks
Registered: July 2009
On 18/12/2014 7:50 PM, Vinicius Pereira wrote:
> Hmmm... I did in separated models because in thought it was better to
> understand and have images.
There's nothing wrong with having multiple models, it's just misguided
to "I want the same thing to be in both models".
> For example, in a model I show how to map a formal element to an UML
> element using a mapping.
Now sure what you mean by "showing"? Are we really talking about Ecore
models? In Ecore models you define structure, you don't just "show" things.
> In the other model, I show how to create the mapping that I use above.
I don't get this "show how to create" terminology.
> In my opinion, two models was better... So I just put everything in
> one model?
That's not what I said. A concept should be defined once and if you
want to reuse it, you should reuse it, not define it a second time and
then "link" it.
Powered by FUDForum
. Page generated in 0.02256 seconds