Goal-Directed Design
Possible Topics:
- C++/Java Test Taker
- C++ for Java Programmers (or vice versa)
Overview
- Students will be assigned into teams of 2 or 3
- Half of the teams will work on each topic above.
- Students will be "users" for the other topic.
Chapter 4: Understanding
Users/Qualitative Research
- Lecture on Friday, October 6
- Friday Exercise:
- Devise a list of questions
- Identify desired interview candidates
- Share ideas with other groups
- Wednesday Exercise October 11:
- Assignment due Friday, October 13, except Ethnography due Friday
October 20. One per person.
- Ethnography. Spend 15-20 minutes observing students in a
lab. Write down your observations.
- Market Research. Look online, find tutoring
programs. Possible keyword: C++ Tutoring Program. EITHER
describe one option OR look at a couple of sites, list common features,
any feature you think is unique.
- Turn in: ethnography + market research + interviews. Neatly handwritten is
OK.
Chapter 5: Modeling Users: Personas and Goals
- Lecture on Friday, October 13. At least one team member
should bring text.
- Friday Exercise:
- Revisit the Persona Hypothesis, create list of behavior
variables
- Map interview subjects to behavior variables
- Synthesize details, develop narratives
- Which persona is the primary design target?
- Assignment due Wednesday October 18. One per team.
- Turn in: list of variables + narratives
Chapter 6 Scenarios: Translating Goals into Design
- Lecture on Wednesday, October 18. At least one team member should
bring text.
- Wednesday Exercise, possibly continue on Friday:
- Follow steps of Defining the Requirements, create context
scenarios
- Define the interaction framework
- Assignment due: Wednesday, October 25. One per team.
- Turn in interaction framework, including a) form factor and
input methods (just a brief statement), b) sketches of views, and c)
keypath scenario(s). It would probably be best to stick to one
persona/one narrative.
- Some designs will be presented in class