SPRING 2005
CS377A: Mobile Interaction

Tuesdays 1:30-4:00, Wallenberg 124

Scott Klemmer, 384 Gates
Office Hours: Fridays 2:00-3:00PM

TA: Brian Lee, 396 Gates
Office Hours: Wednesdays 1:00-2:00PM, and by appointment

Course Email: cs377a-mobile at cs dot stanford dot edu
Course Newsgroup: su.class.cs377a

PROJECT MILESTONE 1, DUE MONDAY 09 MAY

Email a project update with the following sections to the course email by 5:00PM on Monday May 9. Feel free to contact us with questions. You can email the text to us in whatever electronic format is most convenient (text, word, pdf, or html). Here is a sample update that Ron Yeh wrote.

ABSTRACT – A ~100-150 word summary of the interface you plan to prototype, the hypothesis of the value that it provides the user, and how you plan to evaluate if your hypothesis is true or false.

TASK ANALYSIS – Who are the users? What tasks will the users need to perform? What new tasks do they desire to perform? Where are the tasks performed? How are the tasks learned? What set of tools does the user have now? How often do your users perform the tasks? What happens when things go wrong? What’s the relationship between the user and his or her data? How do your users communicate with each other? With whom do they communicate?

Use the questions above to guide your task analysis. This should be one or two paragraphs.

IDEATION – Sketches and Storyboards of your ideas. This will be the main part of your grade for this assignment. We want to see lots and lots of ideas. Brainstorm! Not all your ideas have to be related to your proposed system. You are not required to digitize sketches. Sketches should be in whatever format enables you to work quickly; we recommend pen and paper. They should be accompanied by short blurbs to explain each idea. We will be evaluating sketches based on two criteria: volume and breadth. Please also turn in your half-baked and "dumb" ideas. The goal of this section is to encourage brainstorming and ideation. Come up with lots of ideas, and have them span a broad design space. Some will be more compelling than others, and that's okay.

EVIDENCE – Present some evidence that your idea is a good one. What observations did you make during your contextual inquiries that support your idea? What other systems exist that support similar tasks?

FURTHER EVIDENCE – How will you collect further evidence to support your intuition that your system is a good one?

EVALUATION PLAN – How will you evaluate your hypotheses? What type of user tests? How do you plan to set up your user tests? How many people will participate in your study?