Assignment 02: Task Analysis
| Assignment | Description | Due on | Value |
|---|---|---|---|
| 01 | user analysis | 06 Feb | 10% |
| 02 | task analysis | 25 Feb | 10% |
| 03 | your rationale for the design decisions made | 06 Mar | 20% |
| 04 | prototype and system description | 10 Apr | 20% |
| 05a | usability inspection of a design developed by one of your classmates | 17 Apr | 10% |
| 05b | response to a usability inspection of your design | 22 Apr | 05% |
| 06 | planning a usability test of your own design | 06 May | 15% |
| participation | in class and online | daily | 10% |
The task analysis is focused on the definition of the task, from the user's perspective. The goals or intentions of the user should be documented, as well as the essential steps required to complete the task.
Your documentation of the tasks is in two components, as indicated in the sample outline.
- In the first component, you will analyze the task itself. The documentation should include a high-level overview of the task structure, a use case for each subtask, and one or more scenarios for each use case.
- The second component describes other aspects of the task, such as its frequency and the environment in which it occurs.
- You also have an example to study.
The draft version is due on Monday 25 Feb 2013
[top]