UML 2.5 FTF Avatar
  1. OMG Issue

UML25 — Location: 18.1.3 Semantics Use Cases and Actors P. 685 - Variants are not defined

  • Key: UML25-413
  • Legacy Issue Number: 18047
  • Status: closed  
  • Source: Soluta.net ( Adriano Comai)
  • Summary:

    current text: “Each UseCase specifies some behavior, possibly including variants, that the subject can perform in collaboration with one or more Actors”.

    [AC] I think the clause “possibly including variants” could and should be avoided, because: a) “variant” is not a term defined in the specification, and could be interpreted differently by different readers
    b) it does not lead to a better explanation of what a behavior specification is.

    However, the clause “possibly including variants” was also included in the 11-08-06 version

  • Reported: UML 2.4.1 — Fri, 28 Sep 2012 04:00 GMT
  • Disposition: Resolved — UML 2.5
  • Disposition Summary:

    Agreed. “Possibly including variants” is not the language of a normative specification. The variation capabilities
    (include, extend) are specified elsewhere

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