|Re: How to define a stereotype which subsets a meta-class association / redefine an attribute [message #959013 is a reply to message #958950]
||Fri, 26 October 2012 11:35
| Camille Letavernier
Registered: February 2011
The only way to restrict the UML specification with profiles is to add constraints. You should distinguish two things:
- The model validation
- The tooling
With the generic Papyrus environment, you can not prevent the user from adding any kind of behavior in a Class. However, what you can do is to say "this is invalid", by implementing a new constraint.
It is the responsibility of the tools to actually prevent from even trying to create a non-activity behavior in a stereotyped Class. And most Papyrus tools can be extended (e.g. palette, properties view...)
Currently, this is not well supported. Constraints can be defined in a profile, but it is not yet possible to actually take these constraints into account when validating the model. And some tools (e.g. Modeling Assistants, "New child" from the ModelExplorer, ...) cannot be (easily) customized yet.
Powered by FUDForum
. Page generated in 0.11623 seconds