UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Additional events for Interactions

  • Key: UML22-1364
  • Legacy Issue Number: 7637
  • Status: closed  
  • Source: X-Change Technologies and Klocwork ( Joaquin Miller for Nikolai Mansurov)
  • Summary:

    13.1 Overview of Common Behaviors discusses occurrences for which there is no event in the FAS nor in the proposed revision to triggers and events. Figure 307 - Invocation Domain Model shows occurrences of Start, Termination, Trigger, and CallBehavior events. Figure 308 - Communication Domain Model shows occurrences of Invocation and Receiving events. Figure 309 - Domain Model Showing Request Kinds shows occurrences of SendInvocation, CallInvocation, SendRequest, Call Request, Signal, and Call events. These are all discussed in the text, along with occurrences of change and time events. Figure 310 - Domain Model Showing Event Kinds shows two supertypes, for occurrences of Trigger and Spontaneous events. These are discussed in the text. It appears that AcceptEventAction is intended to be used with any kind of event and AcceptCallAction for call request events. [by Nick:] I've reviewed the effects of the proposed alignment of event/occurences/types on Interactions. I believe, the proposed changes will have a very positive effect indeed on making the new Interactions a better part of the overall spec. I would suggest that we do add more subtypes of event in order to have a better match with Interactions: - CreationEvent - DestructionEvent - ExecutionStartEvent - ExecutionFinishEvent

  • Reported: UML 2.0 — Mon, 16 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 22:55 GMT