UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Notes versus curly braces

Open Closed All
  • Key: UML22-12
  • Legacy Issue Number: 6372
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Why do decision input behaviors use the note notation and join
    specification use curly braces?
  • Reported: UML 1.5 — Mon, 20 Oct 2003 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    A decision input behavior is a behavior, and it could potentially involve a lengthy computation. A join specification is a value specification and will typically be very short, perhaps even just a single operator (the default is "and").
    Revised Text:
    None
    Disposition: Closed, no Change
  • Updated: Fri, 6 Mar 2015 20:58 GMT