|
Synopsis: Your team project is a hands-on effort in which you will begin with an analysis of an existing human activity in need of better support, then iteratively prototype and demonstrate the value of a new version. The prototype will usually take more than one form - e.g. you'll often deliver both a physical shape mockup and a working interactive software prototype, although specifics vary by project. You'll also turn in a final report and give a presentation to the class.
[a few past projects topics] [some details about project administration]
More Detail: Your
team project will have several marked deliverables
throughout the term. The project's larger goal is to provide
you with practical experience in negotiating the iterative
stages of the user interface design cycle. You will
participate in the same team throughout the course.
For the project, you will first choose a human activity which is currently receiving inadequate interface support. You will analyze the activity and its existing support, and then specify,
design, prototype and evaluate an improvement to that interface on the basis of the task the human needs to do.
The lab sessions (not tutorials) which occur with higher frequency in 2nd half of term are scheduled time for you to work with your team on the project. This reduces (but does not eliminate) the need for out-of-class project time, as well as the difficulties of scheduling team face-time.
There are five stages to the team
project, each with a deliverable; plus an "overall" mark component. More detail for each component will become available as the term proceeds. Please consult the course calendar (early and often) for timing of components, and for the component of the project you are expected to work on during the lab sessions.
|
stage |
components |
|
|
| |
- choose several candidate human activities in need of better support |
| |
- describe these in pre-proposal direction check & discuss w/ course staff |
| |
- select a single project candidate |
| |
- conduct a simple
preliminary analysis based on task examples |
| |
DELIVER brief written proposal |
| |
DESIGN REVIEW (TA) |
|
|
|
| |
- carry out an informal user assessment |
| |
- conduct requirements definition based on user assessment |
| |
DELIVER brief written report |
| |
DESIGN REVIEW (TA + instructor) |
|
|
|
| |
- create a revised design (using low-fi prototyping) |
| |
- plan your Stage IV evaluation |
| |
- build a testable prototype using medium-fidelity method of choice |
| |
DELIVER description of eval plan and prototype |
| |
DESIGN REVIEW (TA+instructor) - open review includes a 5-min presentation and demo |
|
|
|
| |
- carry out a usability study |
| |
- compile recommendations |
| |
DELIVER report of evaluation, results and recommendation |
|
|
| |
DELIVER: presentation to class and design jury |
|
overall
[15%]
|
| |
Ambitiousness, ingenuity and resourcefulness; general excellence and quality of improvement as assessed at conclusion of project. Assessed by the entire course staff with input from the final project presentation design jury, assembled from HCI professionals in industry and academia. |
|

|