UML 2.4 RTF Avatar
  1. OMG Issue

UML24 — remove BehavioredClassifier::ownedTrigger

  • Key: UML24-26
  • Legacy Issue Number: 14931
  • Status: closed  
  • Source: Dassault Systemes ( Nerijus Jankevicius)
  • Summary:

    can someone explain what is the purpose of "ownedTriggers" in BehavioredClassifier (page 435 of UML 2.3 spec) and how it should be used?
    There is nothing in the spec about it. The description is : "References Trigger descriptions owned by a Classifier".

    If it is intended to be container (or filter) of event types which can be consumed by this classifier behaviors, maybe it should be derived (from all owned behaviors)?
    The samantics section talks about "event pool" of the object at runtime, is it related?

  • Reported: UML 2.3 — Fri, 8 Jan 2010 05:00 GMT
  • Disposition: Resolved — UML 2.4
  • Disposition Summary:

    In general, the event pool of an object holds events that may be dispatched to triggers of that object. However, those triggers are generally part of a state machine or activity related to the object (either as its type or as a classifier behavior of its type). The specification does not describe what the semantics of dispatching an event directly to an ownedTrigger is, since there is not response behavior associated with such triggers. And a trigger directly owned by a behaviored classifier cannot also be owned in the normal way by a state machine or activity.
    Indeed, it is not clear that owned triggers have any purpose in UML 2 as it stands, and their inclusion without any explicit semantics is confusing. Therefore, it is agreed that BehavioredClassifier::ownedTrigger should be removed.

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