Difference between revisions of "LSC Language Reference"
From WeizmannWiki
(→Step and Superstep) |
(→Step and Superstep) |
||
| Line 3: | Line 3: | ||
==Step and Superstep== | ==Step and Superstep== | ||
| − | The execution of a message event and all the hidden events that follow it is considered a step.<br> | + | The execution of a message event and all the hidden events that follow it is considered a step.<br><br> |
In the context of execution, some events are driven by the user, while others are triggered by the system.<br> | In the context of execution, some events are driven by the user, while others are triggered by the system.<br> | ||
Following a user action, PlayGo can execute a superstep – a sequence of steps that terminates when the next event is an environment event or a user action, or when the entire system’s execution is terminated. | Following a user action, PlayGo can execute a superstep – a sequence of steps that terminates when the next event is an environment event or a user action, or when the entire system’s execution is terminated. | ||
Revision as of 06:42, 29 April 2014
LSC Specification
An LSC specification is a finite set of live sequence charts.
Step and Superstep
The execution of a message event and all the hidden events that follow it is considered a step.
In the context of execution, some events are driven by the user, while others are triggered by the system.
Following a user action, PlayGo can execute a superstep – a sequence of steps that terminates when the next event is an environment event or a user action, or when the entire system’s execution is terminated.
