-
Key: UML25-655
-
Legacy Issue Number: 17172
-
Status: closed
-
Source: Oracle ( Dave Hawkins)
-
Summary:
Action::inputPin and Action::outputPin are both derived unions. Both also have opposite association owned ends that are not derived. While I don't think the metamodel is actually incorrect, those owned ends are implicitly derived unions too. So I think it would make more sense to make that explicit.
I've just picked two examples, however I believe there are more in the specification.
-
Reported: UML 2.4.1 — Fri, 24 Feb 2012 05:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
The FTF agrees that the other ends ought to be derived unions. Because all cases of this are associationowned
ends, this does not affect serialization. There are ten cases of this in the metamodel, which are the
opposite ends for:
DirectedRelationship::source
DirectedRelationship::target
Classifier::attribute
StructuredClassifier::role
Action::input
Action::output
RedefinableElement::redefinedElement
RedefinableElement::redefinitionContext
Namespace::member
Relationship::relatedElement -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Opposite ends of derived unions should be derived unions
- Key: UML25-655
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF