Legacy Issue Number: 6876
Source: agnos.ai UK Ltd ( Pete Rivett)
This is in my opinion important enough to be considered by the FTF since
it affects implementability.
Appendix B contains a list of Standard Stereotypes.
Ironically, due to the nature of the UML2 Profile mechanism this
mechanism is more heavyweight than a subclass since it requires a
separate instance - so for the <<call>> stereotype of Usage one ends up
with not only a instance of Usage but an attached instance of Call -
this is far more heavyweight than having a distinct subclass of Usage
which would result in only one object. And it's also harder to process
via XMI or APIs.
The Appendix is not adequate as a definition and does not use the
official Stereotype notation? In particular it does not make clear the
name of the instance of Stereotype (which I can only guess would be the
capitalized form of the stereotype keyword e.g. "Call"), nor does it
specify the name of the association used to attach an instance of the
stereotype with the instance of the metaclass. And, of course, is there
actually a Profile object (or objects) that contains these stereotypes?
Can users consider this Profile already applied to any UML model or does
it have to be explicitly done or is this a variation point?
Finally, Appendix B is not properly referenced: 7.14.1 refers to the
"Standard Profiles chapter" and 8.3.3 and 10.3.1 refer to "The UML
Reported: XMI 2.0 — Thu, 8 Jan 2004 05:00 GMT
Disposition: Resolved — UML 1.4.2
Updated: Fri, 6 Mar 2015 20:58 GMT