The execution semantics of Dezyne are illustrated using different model examples and the corresponding sequence diagrams.
When interpreting the models and corresponding sequence diagrams, keep in mind that the body of an event is executed atomically in the context of its behaviour.
For an in-event all action statements are executed depth-first. All out-events are stored in event queues at the receiving components. After the completion of all action statements, just before control is passed back to the caller, a component will flush its own queue of pending out-events. Recursively all out-events are handled this way.