LSC Language Reference - Revision history

Smadar: Smadar moved page LSC Reference to LSC Language Reference

2014-04-29T09:10:06Z

2014-04-29T07:07:03Z

2014-04-29T07:06:11Z

2014-04-29T06:58:17Z

2014-04-29T06:57:56Z

2014-04-29T06:57:39Z

2014-04-29T06:45:45Z

2014-04-29T06:45:24Z

‎Step and Superstep

2014-04-29T06:45:02Z

2014-04-29T06:42:15Z

‎Step and Superstep

← Older revision		Revision as of 07:07, 29 April 2014
Line 17:		Line 17:

	<br><br><br>		<br><br><br>
−	[[Image:Download.jpg\|~~link=~~]] <span style="font-size: ~~medium~~;"> [[Media:LSC Language Reference PlayGo.pdf \| Download the LSC language reference document]]	+	[[Image:Download.jpg\|40px]] <span style="font-size: small;"> [[Media:LSC Language Reference PlayGo.pdf \| Download the LSC language reference document]]

← Older revision		Revision as of 07:06, 29 April 2014
Line 17:		Line 17:

	<br><br><br>		<br><br><br>
−	[[Media:LSC Language Reference PlayGo.pdf \| Download the LSC language reference document]]	+	[[Image:Download.jpg\|link=]] <span style="font-size: medium;"> [[Media:LSC Language Reference PlayGo.pdf \| Download the LSC language reference document]]

@@ Line 1: / Line 1: @@
 ==LSC Specification==
 An LSC specification is a finite set of live sequence charts.
 == Existential Dynamic Lifeline ==
@@ Line 14: / Line 9: @@
 A universal dynamic lifeline represents all the objects of the given class.
 This is used, e.g., when specifying behavior such as “when the controller issues message ‘abort’, all the lights are turned off”.
 <br><br><br>
 [[Media:LSC Language Reference PlayGo.pdf | Download the LSC language reference document]]

@@ Line 6: / Line 6: @@
 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.
 == Existential Dynamic Lifeline ==
 An existential dynamic lifeline represents one object.
 This is used, e.g., when specifying behavior such as “when any button is pressed, the light associated with this button is turned to red”.
 == Universal Dynamic Lifeline ==
 A universal dynamic lifeline represents all the objects of the given class.
 This is used, e.g., when specifying behavior such as “when the controller issues message ‘abort’, all the lights are turned off”.

← Older revision		Revision as of 06:57, 29 April 2014
Line 8:		Line 8:
	<br><br><br>		<br><br><br>
	[[Media:LSC Language Reference PlayGo.pdf \| Download the LSC language reference document]]		[[Media:LSC Language Reference PlayGo.pdf \| Download the LSC language reference document]]
		+
		+	== Existential Dynamic Lifeline ==
		+	An existential dynamic lifeline represents one object.
		+	This is used, e.g., when specifying behavior such as “when any button is pressed, the light associated with this button is turned to red”.
		+
		+	== Universal Dynamic Lifeline ==
		+	A universal dynamic lifeline represents all the objects of the given class.
		+	This is used, e.g., when specifying behavior such as “when the controller issues message ‘abort’, all the lights are turned off”.

← Older revision	Revision as of 09:10, 29 April 2014
(No difference)

← Older revision		Revision as of 06:45, 29 April 2014
Line 7:		Line 7:
	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.

−	[[Media:LSC Language Reference PlayGo.pdf \| Download the LSC ~~Language Reference~~ document]]	+	[[Media:LSC Language Reference PlayGo.pdf \| Download the LSC language reference document]]

← Older revision		Revision as of 06:45, 29 April 2014
Line 6:		Line 6:
	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.
		+
		+	[[Media:LSC Language Reference PlayGo.pdf \| Download the LSC Language Reference document]]

@@ Line 3: / Line 3: @@
 ==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>
 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.