Issue 7683: included use case wrongly referred to as the including use case (uml2-superstructure-ftf)
Source: Capability Measurement (Mr. Karl Frank, karl.karolus(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
Summary: Section 16.3.5 Include (from UseCases) 
 
The Semantics section for Inlcude, page 603 in the 042808.pdf convenience document, says "An include relationship between two use cases means that the behavior defined in the including use case is included in the behavior of the base use case."
 
For "including" read "included (or addition) " and for "base" read "base (or including)".
 
The parenthetical "addition" is needed because this is the term used in the abstract syntax, which does not have "included" as a rolename. Likewise, the abstract syntax does not recognize a role called "base use case" but calls it the "includingCase".
 

Resolution: 
Revised Text: 
Actions taken:
September 7, 2004: received issue
Discussion: 

End of Annotations:=====
ubject: New issue on Include (from usecases) 
Date: Tue, 7 Sep 2004 12:52:58 -0700 
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New issue on Include (from usecases) 
Thread-Index: AcSUVGgmsl+AqpJMRdG6VpZ7cW7YygAvX0GA 
From: "Karl Frank" <Karl.Frank@borland.com> 
To: "Branislav Selic" <bselic@ca.ibm.com>, <issues@omg.org> 
Cc: "UML Superstructure FTF" <uml2-superstructure-ftf@omg.org> 
X-OriginalArrivalTime: 07 Sep 2004 19:53:01.0234 (UTC) FILETIME=[47F50120:01C49514] 


Issue:  included use case wrongly referred to as the including use case
 
Section 16.3.5 Include (from UseCases) 
 
The Semantics section for Inlcude, page 603 in the 042808.pdf convenience document, says "An include relationship between two use cases means that the behavior defined in the including use case is included in the behavior of the base use case."
 
For "including" read "included (or addition) " and for "base" read "base (or including)".
 
The parenthetical "addition" is needed because this is the term used in the abstract syntax, which does not have "included" as a rolename. Likewise, the abstract syntax does not recognize a role called "base use case" but calls it the "includingCase".
 
 
- Karl:wq