You are on page 1of 10

Example Group 14 Hueristic

At inspection time, evaluators were provided copies of this evaluation form. A team member explained the heuristics
to the evaluators and answered questions regarding their meaning. Evaluators were asked to document all usability
problems found whilst including severity scores based on the scale developed by Nielsen (1995c) which was
explained to evaluators, as well. Subsequently, the scope and context of the prototype were summarised. Following
that, the evaluators were first shown the Photoshop prototype using a projector. The evaluators were then provided
access to a laptop connected to the projector with the clickable Balsamiq prototype opened up so that they could
evaluate the interaction first hand. Evaluators were not given a time limit. During the evaluation, group members
were available to answer any open questions 106 regarding the usability heuristics while no further clarifications
were provided regarding the prototype itself after the initial briefing.
Evaluator: Area:
Scenario:
Gender:
Occupation:
Time Overall Testing(minutes) :

Heuristic Design Problem Severity (0-4) Recommendation/Solutio


n
Visibility of system status

Match between system and


the real world

User control and freedom

Consistency and standards

Error prevention
Recognition rather than
recall

Flexibility and efficiency of


use

Aesthetic and minimalist


design

Help users recognize,


diagnose, and recover from
errors

Help and documentation

Please note the following key to severity numbers:


0 don't agree that this is a usability problem
1 Cosmetic problem
2 Minor usability problem
3 Major usability problem; need to fix
4 Usability catastrophe; needs imperative fix
Definition:
Visibility of system status for example how the system keeps the users informed about what is going on
through appropriate feedback in a reasonable time.
Match between system and the real world The system should speak the users language, with words,
phrases and concepts familiar to the user rather than system-orientated terms. Also, does it follow real world
conventions, making information appear in a natural and logical order?
User control and freedom does the system provide backwards and forwards buttons and opportunities for
users to undo/redo the current state without having to go through extended dialogue.
Consistency and standards Users should not have to wonder whether different words, situations, or actions
mean the same thing. Follow platform conventions.
Error Prevention Even better than good error messages is a careful design that prevents a problem from
occurring in the first place. Either eliminates error-prone conditions or check for them and present users with a
confirmation option before they commit to the action. Comments:
Recognition rather than recall Minimize the user's memory load by making objects, actions, and options
visible. The user should not have to remember information from one part of the dialogue to another. Instructions for
use of the system should be visible or easily retrievable whenever appropriate.
Flexibility and efficiency of use Accelerators, unseen by the novice user, may often speed up the interaction
for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor
frequent actions.
Aesthetic and minimalist design Dialogues should not contain information that is irrelevant or rarely needed.
Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their
relative visibility.
Help users recognize, diagnose, and recover from errors Error messages should be expressed in plain
language (no codes), precisely indicate the problem, and constructively suggest a solution.
Help and documentation -- Even though it is better if the system can be used without documentation, it may be
necessary to provide help and documentation. Any such information should be easy to search, focused on the user's
task, list concrete steps to be carried out, and not be too large.

Scenario 1: User wants to plan the best choice to go to Mega Bangna


Tasks:
1. User Sign In to the system via Facebook and accept the condition to Sign In
2. Splash screen (basic layout with menu top left)
3. See the navigate best choice function on menu and then select that mode.
4. See page where to go?
5. Input the current location or turn on GPS or tag on the map. The user can zoom in and out or move the map.
6. Input the destination
7. Then, select lets go
8. It will show the best choice for user with different transportation in minutes from nearest to further

Scenario 2: User is in the Bangwa station and he/she need to go to MegaBangna, but he/she need to check the
transportation fare and the incoming time of the coming BTS and the user need to know how crowded of each
bogie.
Tasks:
1. User Sign In to the system via Facebook and accept the condition to Sign In
2. Splash screen (basic layout with menu top left)
3. See the Main Page BTS SKYTRAIN to select the current location and destination
4. Move up to select the start station
5. Move up to select the destination station
6. Zoom in and out the see the accurate station from map
7. Then, select to view detail
8. Show the transportation fare for each type of ticket in Thai baht
9. Select show time to show the real time of departure
10.Show the departure time and in coming BTS time
11.Select Available Seats and Train Area
12.Show the available seat, area and how crowded of each bogie