| Utility functions in the metaclasses or in external utility plugin? [message #478524] |
Fri, 19 June 2009 01:44  |
Eclipse User |
|
|
|
Hey all,
just one question for a best practice. Which kind of operations should
be declared in a metamodel (e.g. getAllOwnedElemens() in the UML
Superstructure) and which kind should be imlemented in an external
utility package?
In my case, i have a metamodel for an IOLTS (a directed graph) and for
the metaclasses Graph and State, there a several utility functions like
State::nextState(), Graph::getLastState() etc.
Because i can't see the advantages respectively disadvantages of any of
these both solutions, i hope, that some of you modeling guys may serve
any hints for this questions. Is there any rule of thumb from the
viewpoint of the model driven paradigma, that says: This kind of
operation is a "no go" in a metamodel.... or something else :-)
Thanks
Timothy
|
|
|
| Re: Utility functions in the metaclasses or in external utility plugin? [message #478542 is a reply to message #478524] |
Tue, 23 June 2009 17:27  |
| Eclipse User |
|
|
|
Hi Timothy,
The UML2 project makes use of PackageMerge to merge in additional operations
not found in the metamodel but helpful to those using the API.
The UML spec also refers to "additional operations" that are sometimes
required for OCL queries etc. These could be added in the metamodel.
Cheers,
- James.
"Timothy Marc" <timothymarc@freenet.de> wrote in message
news:h1f8ck$hed$1@build.eclipse.org...
> Hey all,
>
> just one question for a best practice. Which kind of operations should be
> declared in a metamodel (e.g. getAllOwnedElemens() in the UML
> Superstructure) and which kind should be imlemented in an external utility
> package?
>
> In my case, i have a metamodel for an IOLTS (a directed graph) and for the
> metaclasses Graph and State, there a several utility functions like
> State::nextState(), Graph::getLastState() etc.
>
> Because i can't see the advantages respectively disadvantages of any of
> these both solutions, i hope, that some of you modeling guys may serve any
> hints for this questions. Is there any rule of thumb from the viewpoint of
> the model driven paradigma, that says: This kind of operation is a "no go"
> in a metamodel.... or something else :-)
>
> Thanks
> Timothy
|
|
|
| Re: Utility functions in the metaclasses or in external utility plugin? [message #627720 is a reply to message #478524] |
Tue, 23 June 2009 17:27 |
| Eclipse User |
|
|
|
Hi Timothy,
The UML2 project makes use of PackageMerge to merge in additional operations
not found in the metamodel but helpful to those using the API.
The UML spec also refers to "additional operations" that are sometimes
required for OCL queries etc. These could be added in the metamodel.
Cheers,
- James.
"Timothy Marc" <timothymarc@freenet.de> wrote in message
news:h1f8ck$hed$1@build.eclipse.org...
> Hey all,
>
> just one question for a best practice. Which kind of operations should be
> declared in a metamodel (e.g. getAllOwnedElemens() in the UML
> Superstructure) and which kind should be imlemented in an external utility
> package?
>
> In my case, i have a metamodel for an IOLTS (a directed graph) and for the
> metaclasses Graph and State, there a several utility functions like
> State::nextState(), Graph::getLastState() etc.
>
> Because i can't see the advantages respectively disadvantages of any of
> these both solutions, i hope, that some of you modeling guys may serve any
> hints for this questions. Is there any rule of thumb from the viewpoint of
> the model driven paradigma, that says: This kind of operation is a "no go"
> in a metamodel.... or something else :-)
>
> Thanks
> Timothy
|
|
|
Powered by
FUDForum. Page generated in 0.04080 seconds
Home