UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — UML 2 Super / Actions / Compliance Levels of Actions

  • Key: UML22-143
  • Legacy Issue Number: 8951
  • Status: closed  
  • Source: MID GmbH ( Mr. Detlef Peters)
  • Summary:

    Actions for sending events and for calling operations and behavior are part of the "BasicActions" package which is part of Compliance Level 1. Their 'partner' actions for accepting a call or an event, however, are part of the "CompleteActions" package which is part of Compliance Level 3.
    Since there is not much sense in creating events without ever accepting them later, I recommend one of the following:
    a) Accept the first item of Issue 8459 from Mr. Amsden and move "AcceptEventAction" and "AcceptCallAction", too, to a package of L1, preferrably "BasicActions"
    b) Otherwise (if "Communications" remains an L2 package) move these two Actions together with all "InvocationAction" specializations, too, to a package of L2. In this case, maybe a new L2 package like "CommunicationActions" could be created.

  • Reported: UML 2.0 — Thu, 4 Aug 2005 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    Discussion
    This issue is obsolete. There are no compliance levels in UML 2.5.
    Disposition: Closed - No Change

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