Heuristic evaluation

The heuristic evaluation of our latest prototype

Tasks and components to be carried out by evaluators:
- Create a new booking
- Change a booking
- Cancel a booking
- Marked attendance (when giving pass)
- Move a person from waiting list to attendance list
- Change settings (delete old and add new class)
- List outlook

Heuristics to be evaluated:

1. Visibility of system status;

* if the main list is long, there should be some notification that the person had been added to the list; it could be done e.g. by scrolling the list to the point where new client had been added or by pop up window
* the title with day and time in the main window is too small;
* no title for the main window and for the settings window - the user may not know what is going on;
* user may not know what the arrow on the left edge means

2. Match between system and the real world;

* on the "back" button on the settings window there should be an information that no changes will be saved;
* the user may not know what the blue arrows in main window are for - they should be placed together with only the date;
* hints may be useful after placing mouse cursor above the buttons;
* "Done!" button perhaps should be called "Save" and "Back" should be called "Exit" or "Back to control panel"

3. User control and freedom;

* no undo function (especially after deleting a person from the list)
* in the setting page, user may want to save the changes but still stay on the setting page and currently it is not possible
* there is no option to leave the program
* there is no way of editing already added bookings.
* if the wrong booking has been removed from the waiting list, in some case it takes a lot of effort to fix it (For example when list is full and user removes the first booking by mistake).

4. Consistency and standards;

* Print button may mean that the user can print the whole page, not only the list

5. Error prevention;

* before changing the schedule by clicking "Done!" button maybe it is good to prompt for confirmation;
* confirmation before canceling the booking and moving the person from waiting list to the main list;
* confirmation when deleting a user

6. Recognition rather than recall;

* changing a booking may be problematic, as the user has to switch between two lists; a supporting function may be useful - e.g. a clipboard which stores last deleted name;

7. Flexibility and efficiency of use;

* there are no options to customize the view

8. Aesthetic and minimalist design;

* the clock may turn out to be unnecessary and unpractical (there is always a clock on task bar)

9. Help users recognize, diagnose, and recover from errors;

* there is no error messages

10. Help and documentation .

* there is no help; a short introduction function may be useful;
* Q&A could also be introduced