-
Key: UML25-245
-
Legacy Issue Number: 17795
-
Status: closed
-
Source: INCOSE ( Sanford Friedenthal)
-
Summary:
Should this figure include a reference from MultiplicityElement to TypedElement, since MultiplicityElement constrains the numbers of values of the TypedElement
-
Reported: UML 2.4.1 — Wed, 26 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
Presumably the reference is to Figure 7.10, the abstract syntax of types and multiplicity elements. The answer to the
question is “no”. ConnectorEnd is a MultiplicityElement that is not a TypedElement. In other cases, element metaclass
specializes bothMultiplicityElement and TypedElement, so no association fromMultiplicityElement to TypedElement
is needed. The element simply is both a MultiplicityElement and a TypedElement.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:59 GMT