Task 1: General Description of the System

The first section of your report should provide a general description of your chosen application/system; what the system is for and does. It should also identify the user groups (e.g. age range, gender, nationality, etc.) who would typically use the system.

Task 2: The User

a. Persona

Identify a user type and create a persona for this user. This is the user you will step into the proverbial shoes of to perform your predictive evaluation

b. Task Analysis

Perform task decomposition for at least two tasks a user would normally perform with your chosen system. From the two tasks, clearly identify one task you will perform your predictive evaluation on.

Task 3: Predictive (Expert) Evaluation

a. Interface

Using screengrabs, identify and label the interactive components of the interface for the chosen user task from task 2b above.

Provide an action list for completing the sub-tasks from the chosen user task from task 2b above.

b. Functionality

Using the ‘Model’ from the ‘Model, View, Controller’ development architecture, identify (name), describe and categorise the functions required to update the model for the interactive components identified in Task 1b above. The categories are:

Read from model

Write to model (Create)

Update the model

Delete from the model

c. Usefulness

Take a copy of your task analysis for your chosen task and map in the functions from task 2b and clearly identify those the current system supports and those that are not.

d. Document a heuristic evaluation of your chosen task using the persona, task decomposition and the action list. You should use screengrabs and textual description to clearly number and describe any usability problems you identify. You should also clearly identify the level of each identified problem.

Task 4: Solution

For two key-stroke level, one component or one multi-page usability problem, clearly identifying them using their number, document at least two lo-fi solutions for each. Review each solution and choose one that you think is better than the other; clearly explaining why you think it is better, document a mid-fidelity prototype clearly describing how it will work interactively.