11.2. Rules about Signals
The following comments refer to the “Rules about Signals” enumerated in the box on page 190.
Specification, not implementation.
The primary point to grasp is that these rules are designed to describe required synchronization between objects. This means that when we say that “signals are never lost,” we mean that the sender requires the receiver to execute after the signal is sent, and that this is the required order. It is the job of the model compiler to ensure this is so by whatever mechanism it deems appropriate.
No priorities.
Similarly, there is no notion of signal priority in these rules, and a modeler cannot arbitrarily accelerate one signal ahead of another. To do so would be equivalent to “going backwards in ...
Get Executable UML: A Foundation for Model-Driven Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
