Difference between revisions of "Wristwatch Example"

From WeizmannWiki
Jump to: navigation, search
(Download the Wristwatch Example)
 
(31 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The wristwatch example is taken from <ref>D. Harel. "On Visual Formalisms", Commun. ACM, 31(5):514–530, 1988.</ref>, and is a simplified version of the original statecharts watch example of <ref>D. Harel, "Statecharts: A Visual Formalism for Complex Systems", Sci. Comput. Programming 8 (1987), 231-274.</ref>. Generally, the watch displays the time and can switch between different displays that show (and allow changes to) the alarm, date, time and stopwatch. It has an option for turning on the light, and an alarm that beeps when the set time is reached. The following examples demonstrate many constructs in the LSC language and the way they are created in natural lanague play-in, it was originally created in <ref>M. Gordon and D. Harel. Generating executable scenarios fromfckLRnatural language. In Proc. 10th Int. Conf. on Computational Linguistics and Intelligent Text Processing, CICLing’09, pages 456–467. Springer-Verlag, 2009.</ref>
+
The wristwatch example is taken from <ref>D. Harel. "On Visual Formalisms", Commun. ACM, 31(5):514–530, 1988.</ref>, and is a simplified version of the original statecharts watch example of <ref>D. Harel, "Statecharts: A Visual Formalism for Complex Systems", Sci. Comput. Programming 8, 231-274, 1987.</ref>. Generally, the watch displays the time and can switch between different displays that show (and allow changes to) the alarm, date, time and stopwatch. It has an option for turning on the light, and an alarm that beeps when the set time is reached. The following examples demonstrate many constructs in the LSC language and the way they were created in natural lanague play-in. The model was originally described in <ref>M. Gordon and D. Harel. Generating executable scenarios fromfckLRnatural language. In Proc. 10th Int. Conf. on Computational Linguistics and Intelligent Text Processing, CICLing’09, pages 456–467. Springer-Verlag, 2009.</ref>.
  
 
== Requirements  ==
 
== Requirements  ==
Line 7: Line 7:
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
|-
 
|-
! scope="col" width="60%" | Natural Language Text
+
! scope="col" width="70%" | Natural Language Text
! scope="col"  width = "20%" | Comments
+
! scope="col"  width = "15%" | Comments
! scope="col" width="20%" | LSC
+
! scope="col" width="15%" | LSC
 
|-
 
|-
| when the user clicks the d_button, if the display mode is time, the display mode changes to date, otherwise if the display mode is date, the display mode changes to time.
+
| when the user clicks the d_button, if the display mode is "time", the display mode changes to "date", otherwise if the display mode is "date", the display mode changes to "time".
 
| Demonstrates if-else.
 
| Demonstrates if-else.
 
| [[Image:WatchModes.png|thumb|left|x50px|LSC]]
 
| [[Image:WatchModes.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the user clicks the a_button, if the display mode is time, the display mode changes to alarm, otherwise if the display mode is alarm, the display mode changes to chime, otherwise if the display mode is chime, the display mode changes to stopwatch, otherwise if the display mode is stopwatch, the display mode changes to time.
+
| when the user clicks the a_button, if the display mode is "time", the display mode changes to "alarm", otherwise if the display mode is "alarm", the display mode changes to "chime", otherwise if the display mode is "chime", the display mode changes to "stopwatch", otherwise if the display mode is "stopwatch", the display mode changes to "time".
|  
+
|
 
| [[Image:Modes.png|thumb|left|x50px|LSC]]
 
| [[Image:Modes.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the user clicks the c_button , if the display mode is alarm then the display mode changes to "alarm minutes" , otherwise if the display mode is "alarm minutes" then the display mode changes to "alarm hours" , otherwise if the display mode is "alarm hours" then the display mode changes to alarm.
+
| when the user clicks the c_button , if the display mode is "alarm" then the display mode changes to "alarm minutes" , otherwise if the display mode is "alarm minutes" then the display mode changes to "alarm hours" , otherwise if the display mode is "alarm hours" then the display mode changes to "alarm".
|  
+
|
 
| [[Image:ModesAlarm.png|thumb|left|x50px|LSC]]
 
| [[Image:ModesAlarm.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the user clicks the b_button, if the display mode is “alarm minutes”, the display mode changes to alarm.
+
| when the user clicks the b_button, if the display mode is “alarm minutes”, the display mode changes to "alarm".
|  
+
|
 
| [[Image:ModeAlarmEnd.png|thumb|left|x50px|LSC]]
 
| [[Image:ModeAlarmEnd.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the user clicks the b_button, if the display mode is “alarm hours” , the display mode changes to alarm.
+
| when the user clicks the b_button, if the display mode is “alarm hours” , the display mode changes to "alarm".
|  
+
|
 
| [[Image:ModeAlarmHoursEnd.png|thumb|left|x50px|LSC]]
 
| [[Image:ModeAlarmHoursEnd.png|thumb|left|x50px|LSC]]
 
|-
 
|-
Line 35: Line 35:
 
| [[Image:IncreaseTime.png|thumb|left|x50px|LSC]]
 
| [[Image:IncreaseTime.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the user clicks the c_button , if the display mode is time , the display mode changes to update and the update type changes to seconds.
+
| when the user clicks the c_button , if the display mode is "time" , the display mode changes to "update" and the update type changes to "seconds".
 
|
 
|
 
| [[Image:UpdateSeconds.png|thumb|left|x50px|LSC]]
 
| [[Image:UpdateSeconds.png|thumb|left|x50px|LSC]]
Line 44: Line 44:
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
|-
 
|-
| when the user clicks the c_button , if the update type is seconds , the update type changes to minutes otherwise if the update type is minutes , the update type changes to hours otherwise if the update type is hours , the update type changes to date otherwise if the update type is date, the display mode changes to time and the update type changes to none.
+
! scope="col" width="70%" | Natural Language Text
 +
! scope="col"  width = "15%" | Comments
 +
! scope="col" width="15%" | LSC
 +
|-
 +
| when the user clicks the c_button , if the update type is "seconds" , the update type changes to "minutes" otherwise if the update type is "minutes" , the update type changes to "hours" otherwise if the update type is "hours" , the update type changes to "date" otherwise if the update type is "date", the display mode changes to "time" and the update type changes to "none".
 +
|
 
| [[Image:UpdateType.png|thumb|left|x50px|LSC]]
 
| [[Image:UpdateType.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the update type changes , if the update type equals seconds , the display blinks seconds , otherwise if the update type equals minutes , the display blinks minutes , otherwise the display blinks none.
+
| when the update type changes , if the update type equals "seconds" , the display blinks seconds , otherwise if the update type equals "minutes" , the display blinks minutes , otherwise the display blinks none.
 +
|
 
| [[Image:UpdateTypeBlink.png|thumb|left|x50px|LSC]]
 
| [[Image:UpdateTypeBlink.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the update type changes, the display mode changes to update.
+
| when the update type changes, the display mode changes to "update".
| [[Image:UpdateTypeChange.png|thumb|left|x50px|LSC]]
+
|
 +
| [[Image:TypeChangeUpdate.png|thumb|left|x50px|LSC]]
 
|}
 
|}
  
Line 57: Line 64:
  
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 +
|-
 +
! scope="col" width="70%" | Natural Language Text
 +
! scope="col"  width = "15%" | Comments
 +
! scope="col" width="15%" | LSC
 
|-
 
|-
 
| when the clock ticks, the time increases by one second.
 
| when the clock ticks, the time increases by one second.
 +
|
 
| [[Image:TimeTicks.png|thumb|left|x50px|LSC]]
 
| [[Image:TimeTicks.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the time value changes, if the display mode is time, the display text changes to time value. (demonstrates a property change as a trigger).
+
| when the time value changes, if the display mode is "time", the display text changes to time value.
 +
| Demonstrates a property change as a trigger.
 
| [[Image:ShowTime.png|thumb|left|x50px|LSC]]
 
| [[Image:ShowTime.png|thumb|left|x50px|LSC]]
 
|}
 
|}
Line 68: Line 81:
  
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 +
|-
 +
! scope="col" width="70%" | Natural Language Text
 +
! scope="col"  width = "15%" | Comments
 +
! scope="col" width="15%" | LSC
 
|-
 
|-
 
| when the user clicks the b_button, if the light state is on , the light state turns to off , otherwise if the light state is off , the light state turns to on.
 
| when the user clicks the b_button, if the light state is on , the light state turns to off , otherwise if the light state is off , the light state turns to on.
 +
|
 
| [[Image:LightState.png|thumb|left|x50px|LSC]]
 
| [[Image:LightState.png|thumb|left|x50px|LSC]]
 
|}
 
|}
Line 78: Line 96:
  
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 +
|-
 +
! scope="col" width="70%" | Natural Language Text
 +
! scope="col"  width = "15%" | Comments
 +
! scope="col" width="15%" | LSC
 
|-
 
|-
 
| when the time value changes , if the time value equals the alarm value and the alarm state is enabled then the beeper state turns to on.
 
| when the time value changes , if the time value equals the alarm value and the alarm state is enabled then the beeper state turns to on.
 +
|
 
| [[Image:AlarmState.png|thumb|left|x50px|LSC]]
 
| [[Image:AlarmState.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the user clicks the d_button , if the display mode is alarm , if the alarm state is enabled , the alarm state changes to disabled otherwise the alarm state changes to enabled.
+
| when the user clicks the d_button , if the display mode is "alarm" , if the alarm state is enabled , the alarm state changes to disabled otherwise the alarm state changes to enabled.
| [[Image:AlarmEnable.png|thumb|left|x50px|LSC]]
+
|
 +
| [[Image:EnableAlarm.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the display mode changes , if the display mode equals "alarm minutes" , the display blinks in minutes , otherwise if the display mode equals "alarm hours" , the display blinks in hours , otherwise the display blinks in none.
+
| when the display mode changes , if the display mode equals "alarm minutes" , the display blinks minutes , otherwise if the display mode equals "alarm hours" , the display blinks hours , otherwise the display blinks none.
| [[Image:AlarmBlink.png|thumb|left|x50px|LSC]]
+
|
 +
| [[Image:BlinkAlarm.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the beeper state changes to on, as long as the beeper state is on and two seconds elapse, the beeper beeps, the display mode may not change. (demonstrates loop and forbidden element).
+
| when the beeper state changes to on, as long as the beeper state is on and two seconds elapse, the beeper beeps, the display mode may not change.
 +
| Demonstrates loop and forbidden element.
 
| [[Image:AlarmBeep.png|thumb|left|x50px|LSC]]
 
| [[Image:AlarmBeep.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the user clicks any WButton , the beeper state turns to off. (demonstrates symbolic \ non-deterministic objects).
+
| when the user clicks any WButton , the beeper state turns to off.
 +
| Demonstrates symbolic \ non-deterministic objects.
 
| [[Image:AlarmOff.png|thumb|left|x50px|LSC]]
 
| [[Image:AlarmOff.png|thumb|left|x50px|LSC]]
 
|-
 
|-
| when the display mode changes to alarm, the display text changes to the alarm value.
+
| when the display mode changes to "alarm", the display text changes to the alarm value.
| [[Image:DisplayAlarm.png|thumb|left|x50px|LSC]]
+
|
 +
| [[Image:AlarmDisplay.png|thumb|left|x50px|LSC]]
 
|}
 
|}
  
Line 102: Line 130:
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
{| width="100%" border="1" align="left" cellpadding="1" cellspacing="1"
 
|-
 
|-
| when the display mode changes to date, the display text changes to the date value .
+
! scope="col" width="70%" | Natural Language Text
 +
! scope="col"  width = "15%" | Comments
 +
! scope="col" width="15%" | LSC
 +
|-
 +
| when the display mode changes to "date", the display text changes to the date value.
 +
|
 
| [[Image:DisplayDate.png|thumb|left|x50px|LSC]]
 
| [[Image:DisplayDate.png|thumb|left|x50px|LSC]]
 
|}
 
|}
Line 108: Line 141:
 
<br>&nbsp;<br>
 
<br>&nbsp;<br>
  
== Download the Wrist Watch Example  ==
+
== Wristwatch Example  ==
  
Below are downloads of the wrist watch final application, as well as of the LSC project that can be opened and modified in PlayGo.
+
Below is a download of the wristwatch final application, as well as instructions for creating the wristwatch example in PlayGo.
  
===Wristwatch final application (runnable jar)===
+
=== Wristwatch final application (runnable jar) ===
[[Media:WristWatchExampleSwingGUI.zip|Runnable Wrist Watch with Swing GUI]] <br> [[Media:WristWatchExampleSystemModelGUI.zip|Runnable Wrist Watch with the auto generated System Model GUI]] <br>
+
 
 +
[https://weizmann.box.com/s/vm7kdsj3689wnqkpk22i Runnable Wristwatch with Swing GUI] <br><br>
  
 
To run the wristwatch, simply extract the downloaded zip and double click the jar file.
 
To run the wristwatch, simply extract the downloaded zip and double click the jar file.
  
===Wristwatch LSC project===
+
=== Wristwatch LSC project ===
[[Media:WristWatch.zip|The Wrist Watch LSC Project (for development purposes)]] <br>
+
 
====Installation Instructions====
+
To work with the wristwatch application, you can create it in your PlayGo workspace:
#Extract the downloaded zip.
+
 
 
#[[Download PlayGo|Download PlayGo]].
 
#[[Download PlayGo|Download PlayGo]].
#Import the downloaded project to your workspace:
+
#From the 'File' menu choose New-->Example....-->PlayGo Examples-->Wristwatch
##From the File menu choose Import--&gt;General--&gt;Existing Projects into Workspace
+
#Click the 'Finish' button.
##Click the 'Next' button
+
#The wristwatch example project is now part of your workspace. You can start playing with it. For details refer to&nbsp;[[How%20to%20Play-Out | how to play out]] and [[How_to_Play-In|how to play in]].
##When prompted, select the directory to which you extracted the downloaded wrist watch example
+
##Click finish
+
#The wrist watch example project is now part of your workspace. You can start playing with it. For details refer to [[How_to_Play-Out | how to play out]].
+
  
 
== References  ==
 
== References  ==
  
 
<references />
 
<references />

Latest revision as of 11:53, 20 December 2015

The wristwatch example is taken from [1], and is a simplified version of the original statecharts watch example of [2]. Generally, the watch displays the time and can switch between different displays that show (and allow changes to) the alarm, date, time and stopwatch. It has an option for turning on the light, and an alarm that beeps when the set time is reached. The following examples demonstrate many constructs in the LSC language and the way they were created in natural lanague play-in. The model was originally described in [3].

Requirements

Watch Modes

Natural Language Text Comments LSC
when the user clicks the d_button, if the display mode is "time", the display mode changes to "date", otherwise if the display mode is "date", the display mode changes to "time". Demonstrates if-else.
LSC
when the user clicks the a_button, if the display mode is "time", the display mode changes to "alarm", otherwise if the display mode is "alarm", the display mode changes to "chime", otherwise if the display mode is "chime", the display mode changes to "stopwatch", otherwise if the display mode is "stopwatch", the display mode changes to "time".
LSC
when the user clicks the c_button , if the display mode is "alarm" then the display mode changes to "alarm minutes" , otherwise if the display mode is "alarm minutes" then the display mode changes to "alarm hours" , otherwise if the display mode is "alarm hours" then the display mode changes to "alarm".
LSC
when the user clicks the b_button, if the display mode is “alarm minutes”, the display mode changes to "alarm".
LSC
when the user clicks the b_button, if the display mode is “alarm hours” , the display mode changes to "alarm".
LSC
when the user clicks the a_button , if the display mode is "alarm minutes" , the alarm increases in one minute , otherwise if the display mode is "alarm hours" , the alarm increases by one hour.
LSC
when the user clicks the c_button , if the display mode is "time" , the display mode changes to "update" and the update type changes to "seconds".
LSC

Updates

Natural Language Text Comments LSC
when the user clicks the c_button , if the update type is "seconds" , the update type changes to "minutes" otherwise if the update type is "minutes" , the update type changes to "hours" otherwise if the update type is "hours" , the update type changes to "date" otherwise if the update type is "date", the display mode changes to "time" and the update type changes to "none".
LSC
when the update type changes , if the update type equals "seconds" , the display blinks seconds , otherwise if the update type equals "minutes" , the display blinks minutes , otherwise the display blinks none.
LSC
when the update type changes, the display mode changes to "update".
LSC

Time

Natural Language Text Comments LSC
when the clock ticks, the time increases by one second.
LSC
when the time value changes, if the display mode is "time", the display text changes to time value. Demonstrates a property change as a trigger.
LSC

Light

Natural Language Text Comments LSC
when the user clicks the b_button, if the light state is on , the light state turns to off , otherwise if the light state is off , the light state turns to on.
LSC


Alarm

Natural Language Text Comments LSC
when the time value changes , if the time value equals the alarm value and the alarm state is enabled then the beeper state turns to on.
LSC
when the user clicks the d_button , if the display mode is "alarm" , if the alarm state is enabled , the alarm state changes to disabled otherwise the alarm state changes to enabled.
LSC
when the display mode changes , if the display mode equals "alarm minutes" , the display blinks minutes , otherwise if the display mode equals "alarm hours" , the display blinks hours , otherwise the display blinks none.
LSC
when the beeper state changes to on, as long as the beeper state is on and two seconds elapse, the beeper beeps, the display mode may not change. Demonstrates loop and forbidden element.
LSC
when the user clicks any WButton , the beeper state turns to off. Demonstrates symbolic \ non-deterministic objects.
LSC
when the display mode changes to "alarm", the display text changes to the alarm value.
LSC

Date

Natural Language Text Comments LSC
when the display mode changes to "date", the display text changes to the date value.
LSC


 

Wristwatch Example

Below is a download of the wristwatch final application, as well as instructions for creating the wristwatch example in PlayGo.

Wristwatch final application (runnable jar)

Runnable Wristwatch with Swing GUI

To run the wristwatch, simply extract the downloaded zip and double click the jar file.

Wristwatch LSC project

To work with the wristwatch application, you can create it in your PlayGo workspace:

  1. Download PlayGo.
  2. From the 'File' menu choose New-->Example....-->PlayGo Examples-->Wristwatch
  3. Click the 'Finish' button.
  4. The wristwatch example project is now part of your workspace. You can start playing with it. For details refer to  how to play out and how to play in.

References

  1. D. Harel. "On Visual Formalisms", Commun. ACM, 31(5):514–530, 1988.
  2. D. Harel, "Statecharts: A Visual Formalism for Complex Systems", Sci. Comput. Programming 8, 231-274, 1987.
  3. M. Gordon and D. Harel. Generating executable scenarios fromfckLRnatural language. In Proc. 10th Int. Conf. on Computational Linguistics and Intelligent Text Processing, CICLing’09, pages 456–467. Springer-Verlag, 2009.