Issue 17975: Location: Page 328, 14.2.3  - UseCase cannot be the context of a StateMachine (uml25-ftf)
Source: oose Innovative Informatik GmbH (Mr. Axel Scheithauer, axel.scheithauer(at)oose.de)
Nature: Revision
Severity: Significant
Summary:  “If the StateMachine has a kind of BehavioredClassifier context, then that Classifier defines which Signal and CallEvent triggers 
are applicable”. A UseCase is a BehavioredClassifier and thus would be the context of a Statemachine. Since a UseCase cannot have Signal receptions or operations no such triggers would be applicable to this StateMachine.  
 
Proposed Res 
The radical solution would be to make UseCase not a BehavioredClassifier. However this would be out of scope. Therefore the next sentence should be changed:
“If the StateMachine has no BehavioredClassifier context or this context is a UseCase…”   

Resolution: 
Revised Text: 
Actions taken:
September 27, 2012: received issue
Discussion: 
Source: Axel Scheithauer  
Discussion 
A usecase can have operations. For example see  §18.1.4 Notation, 5th¶ it says
“Attributes and operations may be shown in compartments within the UseCase oval, with the same content as though they were in a normal Classifier rectangle.”
Michael Jesse Chonoles
A UseCase is a BehavioredClassifier, which is a Classifier, which has features of Type Property (Subclasses are Operation and Reception). However "feature" is a derived union and neither BehavioredClassifier nor UseCase define subsets of it. Therefore the features of a UseCase are always an empty set. I heard of one UML-Tool that actually enforces this rule.
Axel Scheithauer    

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

Problem: 14.003

Severity: Significant  
Type:  Contradiction  
Location: Page 328, 14.2.3  
Title: UseCase cannot be the context of a StateMachine  
 
 .If the StateMachine has a kind of BehavioredClassifier context, then that Classifier defines which Signal and CallEvent triggers 
are applicable.. A UseCase is a BehavioredClassifier and thus would be the context of a Statemachine. Since a UseCase cannot have Signal receptions or operations no such triggers would be applicable to this StateMachine.  
 
Proposed Res 
The radical solution would be to make UseCase not a BehavioredClassifier. However this would be out of scope. Therefore the next sentence should be changed:
.If the StateMachine has no BehavioredClassifier context or this context is a UseCase..   
 
Source: Axel Scheithauer  
Discussion 
A usecase can have operations. For example see  §18.1.4 Notation, 5th¶ it says
.Attributes and operations may be shown in compartments within the UseCase oval, with the same content as though they were in a normal Classifier rectangle..
Michael Jesse Chonoles
A UseCase is a BehavioredClassifier, which is a Classifier, which has features of Type Property (Subclasses are Operation and Reception). However "feature" is a derived union and neither BehavioredClassifier nor UseCase define subsets of it. Therefore the features of a UseCase are always an empty set. I heard of one UML-Tool that actually enforces this rule.
Axel Scheithauer