Overview

This assignment corresponds to the second half of the needs assessment process for this project. You will create task scenarios, do an analysis of existing systems, and work out initial design ideas. These designs will form the basis of what you test in your low-fidelity prototypes in the next project assignment.

Project Vocabulary

Start to keep track of your project vocabulary. Personas are one kind of vocabulary, but you should also develop one for the tasks, and for attributes of the system that you are creating. Ideally the task vocabulary maps onto the system components, but don't force this if it causes convoluted design. This should probably appear on a separate page as you'll be continually updating it and adding to it. One group is already doing this, see http://www.sims.berkeley.edu/courses/is213/s01/projects/P4/vocabulary.htm

Task Scenarios

Using the task matrix that you created for the previous assignment, create a set of task scenarios that demonstrate the sequence of actions the personas will have to go through in order to achieve their practical goals. You will use these scenarios both to guide your designs and to assess your designs throughout the rest of the project. You should end up with 3 to 5 primary scenarios; more than this will make it difficult to focus.

You will have to make a judgement call about how many scenarios to create, and whether or not you will focus on central (typical) tasks or central tasks plus less common tasks. If your project is wide-ranging you may want the initial design to focus only on central tasks. If your project is more contained (for example, the main tasks for the personas all overlap pretty well) then you may be able to accomodate the less common tasks.

You will also have to make a judgement call about how detailed to make the task descriptions. You need to create a balance between taking into account the constraints of the environment in which they system will be used (at a stand-up kiosk, in a web browser, as a stand-alone GUI) but at the same time not tying it too much to the implementation, in order to allow for flexibility in the designs.

You might try writing tasks components on cards and organizing them into groups. You might also try working in pairs or individually to get initial scenarios, and then combine them together as a group.

Revisions to Personas, Task Analysis

You may find that in the course of doing this assignment, you need to combine some of your personas, or ignore one or more of them. Use this section to record any such revisions you need to do.

Also, if you find that you need to update the task matrix based on new information, that is fine. If you need to do this, leave the original matrix in the old assignment and put the new one in this assignment.

If you don't need to make changes, then you don't need to put anything in this section.

Competitive Analysis

Find and analyze a set of existing systems that attempt to support at least some of your project goals. (The term "competitive" is somewhat unfortunate here, as you should view existing ideas as something to learn from as well as improve on, but not necessarily something to compete against.) Explain the strengths and weaknesses relative to your personas' goals and tasks. Describe which aspects of existing systems you are likely (but not committed) to include in your design(s).

You are encouraged to borrow the best ideas, combining them in new and better ways. Keep in mind that good ideas might also come from systems that do things utterly different from your project goal. One reason we have a lot of reading in this class is to give you lots of ideas about potential designs.

Initial design ideas

Using the scenarios and the results of the competitive analysis, create two or three initial designs for the system. For each design, you should have a description of the main flow of interaction, and some sketches of screen layout. You can use whatever mechanism you want to describe this, some suggestions appear below. You should illustrate the movement through this flow using the scenarios created above, and explanatory narration to make this easy to understand.

One strategy is to create ideal design ideas for each persona separately, then look for ways that the ideas and persona needs can be logically combined, focusing on your primary persona.

One way to create different designs is to put different priorities on the scenarios. Emphasizing one scenario over another might end up creating a different organization to the interaction flow.

Initial ideas about graphical design is optional, and should not be done at the expense of doing the task flows and initial sketches.

You may also need to describe the main components of the system's architecture (e.g., the interface between the backend and the front end) but this is not required, and is project-dependent.

Suggested Tools for Interaction Flow Design

These are entirely optional, and are only meant as suggestions.

• Jesse James Garrett's visual vocabulary He explains how to use visio and other tools. You could also use this in combination with Denim, below.

• Denim. You can use Denim to sketch out the main components and use its storyboarding facility to show interaction flow. The Denim designers tell me they have have fixed the problems that last semester's 202 class found. They have improved the performance for large designs, fixed the gesture recognition, and responded to a host of other comments. They will provide us with a special version of the software that addresses these issues, as well as Wacom tablets and stylii if anyone is interested.
• You can use paper and pencil for this and scan in the results.

To turn in:

1. The project vocabulary (You might want to have a separate page for this, which you update throughout the project.)
2. The scenarios, including which persona(s) they apply to (3 page maximum).
3. Revisions to personas and task analysis (if applicable).
4. Competitive analysis, including screenshots where available (3 page maximum, not including screenshots).
5. Initial design ideas. You should have either two or three main designs. These should include interaction flows, initial sketches and explanatory narrative. It optionally can include system architecture and initial graphic design ideas (7 page maximum, excluding graphic design).
6. Description of which team members did which part(s) of the work. (You might want to have a separate page for this table, which you update for each assignment. That way it is separate from the content of the project.)
7. Appendices (if applicable).

Grading will be out of 100 points possible.

Upcoming due dates:

• Tues Feb 20: Scenarios, Competitive Analysis, and Preliminary Design
• Tues Feb 27: Heuristic Evaluation (individual)
• Tues Mar 6: Midterm
• Thur Mar 8: Flow Chart, Low-fi Prototype, and Test Results
• Thur Mar 22: First Interactive Prototype
• Tues/Thur Mar 20 & 22: Class presentations