Legacy Issue Number: 1290
Summary: in UML I"m missing a specified way (e.g. a class stereotype) to
support the paradigm of "interfaces and support classes". I think it
would be a convienient way to specify the interfaces which are offered
by a class like methods and properties:
SomeContainer <<implementation Class>> interface IIndexAccess interface IEnumerationAccess interface ISomewhatOther property PropA property PropB
The other thing annoying for me is the definition of aggregation. My
understanding of aggregation ist that the aggregating object offers
the interfaces of the aggregated objects as they where it"s own (for
the outer view). The definition of UML seems to be only a "containing"
Reported: UML 1.1 — Wed, 29 Apr 1998 04:00 GMT
Disposition: Resolved — UML 1.2
Considered and declined.
Updated: Fri, 6 Mar 2015 21:35 GMT