FUML 1.5 RTF Avatar
  1. OMG Issue

FUML15 — fUML should not require signal receptions

  • Key: FUML15-27
  • Status: open  
  • Source: Model Driven Solutions ( Ed Seidewitz)
  • Summary:

    UML does not require that a model include signal receptions in order to send or accept signals. However, fUML adds the constraints SendSignalAction::fuml_send_signal_action_target_signal_reception (in and AcceptEventAction::fuml_accept_event_receive_all_triggering_signals (in that require the use of signal receptions for both sending and accepting signals. These constraints are entirely methodologically motivated, and they are unnecessary to the execution semantics for SendSignalActionActivation (in or AcceptEventActionActivation (in, since both deal directly with signals (and their instances), not signal receptions.

    Since UML does not itself require the use of signal receptions, they are often not use in practice by modelers, and having to add them just to be properly conformant with fUML is a nuisance. The constraints should be removed.

  • Reported: FUML 1.4 — Tue, 23 Apr 2019 23:20 GMT
  • Updated: Tue, 21 Jan 2020 00:34 GMT