UML 2.5 FTF Avatar
  1. OMG Issue

UML25 — included use case wrongly referred to as the including use case

  • Key: UML25-598
  • Legacy Issue Number: 7683
  • Status: closed  
  • Source: Capability Measurement ( Karl Frank)
  • 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".

  • Reported: UML 1.4.2 — Tue, 7 Sep 2004 04:00 GMT
  • Disposition: Resolved — UML 2.5
  • Disposition Summary:

    Discussion
    This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
    Disposition: Closed - No Change

  • Updated: Fri, 6 Mar 2015 20:59 GMT