-
Key: UMLR-504
-
Legacy Issue Number: 18077
-
Status: open
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
current text: The ExtensionPoints referenced by the Extend relationship must belong to the UseCase that is being extended
Does this "belong" also include
1) ExtensionPoints that would be inherited?
2) ExtensionPoints that would be defined in Included Use Cases.Both of these are required to support behavioral refactoring and reuse. If a "super" UseCase or an Included UseCase are made to pull out common behavioral parts, it may be that some an extending use case needs to be inserted at
a) extension points that cross use case boundaries (e.g., in the super and child use case, or in the included and base use case) or
b) an extension UseCase needs to be inserted in a base use case, but not in all use cases tsshat include the Included UseCase, and not in all children of the generalized UseCase.Without including the extensionPoints from both these sources, such situations cannot be handled.
-
Reported: UML 2.4.1 — Fri, 28 Sep 2012 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
UMLR — Location: 18.2 Classifier Descriptions Extend Constraints. 695 - Constraint is overly restrictive
- Key: UMLR-504
- OMG Task Force: UML 2.6 RTF