Donovan Lusk and Nick Diamond
April 17, 2002
CSIS 672 Human Computer Interaction
We certify that this report is entirely our own work.
Assignment Number 5
State Transition Diagram
Part 1) Deciding the States
When presented with the task of developing a State Transistion Diagram (STD) for our UI we first had to determine what our state(s) were going to be and in the end we decided on only one primary state with multiple arcs, representing the transitions between states. The reasoning is that we found during our analysis we had multiple actions the the user could take that would change the interface functionally and visually, but in essence our UI would remain the same.
The transitions, actions which change the state, we developed by looking at the options (buttons, menus, etc.) we presented with the user in our prototype. We dismissed our "About" menu option as this might change the UI visually however it does not change it functionally. However we decided that the "Power" button and the "Always On Top" option were our main concerns. We considered how moving the alarm hand and how it affected the UI functionally and visually. Visually it was easy to decide as the alarm hand would now be pointing at a new alarm time, functionally it was more difficult to decide as it does not cause the UI to change its function. However it does cause a variable inside the code to be updated in anticipation of the alarm being activated. We also considered including the transition where the alarm was turned on and turned off. However since this transition was not instigated by a user action, other than by pressing the power button, which was already going to be covered in a different transition arc. So our final list of transitions was:
A) Power Button Pressed (alarm turned on)
B) Power Button Pressed (alarm turned off)
C) On Top Option Selected (on top option on)
D) On Top Option Selected (on top option off)
E) Alarm Hand Moved
Part 2) State Transition Diagram
Here is our final STD: