the to the (if in time edit mode), to the day (if in time edit “second”, “month” mode), to the year (if in time edit mode) and back to the “hour”. To help clarify the requirements, you can find a working solution in the zip file (to run the demo use digitalwatch.jar”, note that the file “java –jar “watch.gif” must be in the working directory). This solution implements requirements 1-5. What to submit? A zip file containing the Yakindu project with your solution and also a document explaining your solution. You must provide everything required to execute your solution in Yakindu. The document must be a PDF file (Word is also accepted), describing your solution. The document should indicate the set of satisfied requirements, open issues, known bugs, etc. and the list of names of the team members. NOTE: You must not change the code of the GUI. Grading The solution will be graded as follows: One point for each of the following requirements: 1 and 2 Two points for each of the following requirements: 4, 6 and 7 Two points for simplicity and understandability of the overall solution If the statechart you produce can be simulated, but for some reason the application does not work, you can get up to 80% of the points. To get 100% of the points, the application has to run as well (and of course it should be possible to simulate your statechart). Starting point The zip file provided to you contains a Yakindu project that implements “dwatch” the GUI. As the entry point for starting to launch the application, you must use the class org.yakindu.src.test.Main. The latter class sets up all the elements in the application (State machine, Timer Service, GUI controllers and views, etc.) and launches the simulation. The code provided to you is decomposed into three components exposing the following interfaces. Interface Buttons: This interface give a hook for the simulation to generate the events associated with the buttons in the watch. We distinguish the following events: topRightPressed topRightReleased topLeftPressed topLeftReleased bottomRightPressed
the “second”, to the “month” (if in time edit mode), to the day (if in time edit mode), to the year (if in time edit mode) and back to the “hour”. To help clarify the requirements, you can find a working solution in the zip file (to run the demo use “java –jar digitalwatch.jar”, note that the file “watch.gif” must be in the working directory). This solution implements requirements 1-5. What to submit? A zip file containing the Yakindu project with your solution and also a document explaining your solution. You must provide everything required to execute your solution in Yakindu. The document must be a PDF file (Word is also accepted), describing your solution. The document should indicate the set of satisfied requirements, open issues, known bugs, etc. and the list of names of the team members. NOTE: You must not change the code of the GUI. Grading The solution will be graded as follows: One point for each of the following requirements: 1 and 2 Two points for each of the following requirements: 4, 6 and 7 Two points for simplicity and understandability of the overall solution If the statechart you produce can be simulated, but for some reason the application does not work, you can get up to 80% of the points. To get 100% of the points, the application has to run as well (and of course it should be possible to simulate your statechart). Starting point The “dwatch” zip file provided to you contains a Yakindu project that implements the GUI. As the entry point for starting to launch the application, you must use the class org.yakindu.src.test.Main. The latter class sets up all the elements in the application (State machine, Timer Service, GUI controllers and views, etc.) and launches the simulation. The code provided to you is decomposed into three components exposing the following interfaces. Interface Buttons: This interface give a hook for the simulation to generate the events associated with the buttons in the watch. We distinguish the following events: topRightPressed topRightReleased topLeftPressed topLeftReleased bottomRightPressed
2017StateModelingHomework.docx