This preview shows page 1. Sign up to view the full content.
Unformatted text preview: system? Is this interaction interesting? Is there a good back-and-forth? We don't want a simple interaction between the user and the system. For example, the user should have to do more than input information and get some output (such as route planning, where the user puts in two addresses and gets a map). What particular parts of your system will you prototype and test? See the overview for a discussion of how to scope your solution. 4. Representative Tasks (3 total)- Provide three tasks that users should be able to accomplish using the prototype you develop. We want an easy task, a medium task, and a hard tasks. See the overview for some examples of how to pick good representative tasks. In general, they should be varied enough that they let you test several different paths through your system. These tasks should help you gauge the general usability of the system you are designing....
View Full Document
This note was uploaded on 11/29/2011 for the course COMPSCI 325 taught by Professor Dunn during the Fall '11 term at UMass (Amherst).
- Fall '11