Issue 18077: Location: 18.2 Classifier Descriptions Extend Constraints. 695 - Constraint is overly restrictive (uml25-ftf)
Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org)
Nature: Revision
Severity: Significant
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.

Resolution: 
Revised Text: 
Actions taken:
September 28, 2012: received issue
Discussion: 

End of Annotations:=====
s is issue # 18077

Problem: 18.046

Severity: Medium
Type: Overly restrictive
Location: 18.2 Classifier Descriptions Extend Constraints. 695
Title Constraint is overly restrictive
 
Description:
 
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.
 
Source: Michael Jesse Chonoles