Issue 18081: Location: 18.2 Classifier Descriptions Use Case Constraints. 697 - Need stricter limit on associations (uml25-ftf)
Source: Soluta.net (Dr. Adriano Comai, acomai(at)soluta.net)
Nature: Uncategorized Issue
Severity: Significant
Summary: current text (688): UseCases may have other Associations and Dependencies to other Classifiers (e.g., to denote input/output, events, and behaviors

 [AC] I believe here one or more constraints are missing. The associations an Actor can have are correctly constrained (see page 694) to be only with UseCase, Class and Component. 
A UseCase, in my opinion and in the whole literature that I know, can only have associations with Actors (while it can have other types of relationship, such as dependencies with other classifiers). 
If I am right, then also what is written on page 688 - “UseCases may have other Associations and Dependencies to other Classifiers (e.g., to denote input/output, events, and behaviors).” - should be corrected.


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

I believe Adriano is being overly limiting, For example, a particular instance of a use case might have a relationship to a particular message instance (with values). This instance to instance relationship requires an association at the classifier level. 

Michael Jesse Chonoles

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

Problem: 18.050

Severity: Medium
Type: Missing material
Location: 18.2 Classifier Descriptions Use Case Constraints. 697
Title Need stricter limit on associations
 
Description:
 
current text (688): UseCases may have other Associations and Dependencies to other Classifiers (e.g., to denote input/output, events, and behaviors
 
 [AC] I believe here one or more constraints are missing. The associations an Actor can have are correctly constrained (see page 694) to be only with UseCase, Class and Component. 
A UseCase, in my opinion and in the whole literature that I know, can only have associations with Actors (while it can have other types of relationship, such as dependencies with other classifiers). 
If I am right, then also what is written on page 688 - .UseCases may have other Associations and Dependencies to other Classifiers (e.g., to denote input/output, events, and behaviors).. - should be corrected.
 
Source: Adriano Comai
 
Discussion: 
 
I believe Adriano is being overly limiting, For example, a particular instance of a use case might have a relationship to a particular message instance (with values). This instance to instance relationship requires an association at the classifier level. 
 
Michael Jesse Chonoles