| Extending the Standard profile [message #628289] |
Wed, 03 March 2010 01:15  |
Eclipse User |
|
|
|
All,
I am currently working on a custom profile using the MDT and UML2. So far I have been able to successfully define a metamodel and reference the metamodel and associated metaclasses from the profile.
One area where I am a bit confused, is if I create a Stereotype in the profile and an extension to one of the custom metaclasses, I am unable to apply the Stereotype to a Class once the profile is defined and then applied to a Class diagram.
Is it possible to define an inheritance hierarchy between metaclasses (i.e. custom metaclass A inherits from uml::Class)?
That said, I may be headed down the wrong path - what I truly need is a way to apply a metamodel construct to a Stereotype which extends uml::Class - if there is another way to do this, any pointers would be helpful!
TIA
|
|
|
|
|
|
| Re: Extending the Standard profile [message #628294 is a reply to message #628289] |
Wed, 03 March 2010 12:46  |
| Eclipse User |
|
|
|
Am 03.03.2010 07:15, schrieb Steven Stallion:
> One area where I am a bit confused, is if I create a Stereotype in the
> profile and an extension to one of the custom metaclasses, I am unable
> to apply the Stereotype to a Class once the profile is defined and then
> applied to a Class diagram.
I do not quite get your scenario. So first you provide your own
metamodel - understood. Now you want to define a profile for these
metaclasses? Wouldn't it be a lot easier to define this metamodel
according to your needs from the beginning?
In general, do you not use the UML2 metamodel at all, or is there
another reason why you cannot simply stick to profiles?
> Is it possible to define an inheritance hierarchy between metaclasses
> (i.e. custom metaclass A inherits from uml::Class)?
Not in a profile. Stereotypes are the way to go here.
You can of course define your own metamodel library and reference UML
metaclasses therein - but in contrast to profiles, tool-support will be
quite close to non-existent when it comes to instantiate this metamodel.
UML tools are just not meant to be used completely without UML :)
> That said, I may be headed down the wrong path - what I truly need is a
> way to apply a metamodel construct to a Stereotype which extends
> uml::Class - if there is another way to do this, any pointers would be
> helpful!
What do you mean by "apply a metamodel construct"? Examples?
Best regards,
Erhard
|
|
|
|
| Re: Extending the Standard profile [message #628297 is a reply to message #628294] |
Wed, 03 March 2010 16:13 |
| Eclipse User |
|
|
|
(Reposting as the original seems to have gotten lost...)
> I do not quite get your scenario. So first you provide your own
> metamodel - understood. Now you want to define a profile for these
> metaclasses? Wouldn't it be a lot easier to define this metamodel
> according to your needs from the beginning?
>
> In general, do you not use the UML2 metamodel at all, or is there
> another reason why you cannot simply stick to profiles?
I'm implementing an OMG specification in process. The spec calls for a metamodel and a profile. Unfortunately the spec is a little scant on details, particularly with how the metamodel is "glued" to the profile so I'm left to my own devices at the moment.
> Not in a profile. Stereotypes are the way to go here.
Right. In this case, I have a Stereotype which extends the uml::Class metaclass. In the documentation it states that a secondary "metaclass construct" should be applied to the Stereotype. I'm taking this to mean that the Stereo type should extend the secondary metaclass which in turn extends the uml::Class metaclass.
> You can of course define your own metamodel library and reference UML
> metaclasses therein - but in contrast to profiles, tool-support will be
> quite close to non-existent when it comes to instantiate this metamodel.
> UML tools are just not meant to be used completely without UML Smile
Right. The end goal here is to produce a compliant profile which can then be used with the graphical tools Wink
> What do you mean by "apply a metamodel construct"? Examples?
See above; this is the exact wording in the specification (which is not public yet) - the term confused me a bit, I was hoping someone could shed some light on it.
Cheers,
Steve
|
|
|
Powered by
FUDForum. Page generated in 0.03635 seconds
Home