Issue 17922: Location p 153 complete_and_disjoint: Abstract Implication (uml25-ftf)
Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org)
Nature: Clarification
Severity: Minor
Summary: I'm not sure this is correct. i see the logic of saying this, but I can imagine circumstances where the generalization would be complete and disjoint, but the generalization class would be useful to instantiate as a temporary until I determine which one of the subclasses it is. 

Forcing it to be abstract is a coding style limitation, which should not be required 

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

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

Problem: 9.067

Severity: minor
Type: Clarification
Location p 153 complete_and_disjoint
Title: Abstract Implication
I'm not sure this is correct. i see the logic of saying this, but I can imagine circumstances where the generalization would be complete and disjoint, but the generalization class would be useful to instantiate as a temporary until I determine which one of the subclasses it is. 
 
Forcing it to be abstract is a coding style limitation, which should not be required 
Source: Michael Jesse Chonoles