lecture 6 – user-oriented designcs 3053 - mark woehrer - lecture 6 – user-oriented design mark...

CS 3053 - Mark Woehrer -

Lecture 6 – User-oriented Design

Mark WoehrerCS 3053 - Human-Computer Interaction

Computer Science Department Oklahoma University

Spring 2007

[Taken from Stanford CS147 with permission]


Prototyping

NEEDSDESIGN

IMPLEMENTEVALUATE


Using Prototypes

• Allows multiple parties to envision together– Designers– Users– Engineering, marketing, planning,…..

• Reflective conversation with the materials

• Focus for identifying alternatives and tradeoffs


Low-Fidelity “Paper” Prototype

NEEDSDESIGN

IMPLEMENTEVALUATE


Tools

• Paper, Cardboard, Transparencies• Tape, Glue, Rubber Cement• Pens, Pencils, Markers• Scissors• Plastic Tubes, Paper Cups, CD

“Coasters”• Anything that you can buy in an arts

and crafts store (and that a kindergartener would have fun using).


Examples: Low-Fidelity Prototype



http://www.mindspring.com/~bryce_g/projects/lo_fi.html



http://bmrc.berkeley.edu/courseware/cs160/fall99/projects/t4/body/low-fi/


User Testing

NEEDSDESIGN

IMPLEMENTEVALUATE


Tools

• 3-4 group members• Greeter/Facilitator• Computer (not necessary for low-fi

testing)• 2 Observers/Note takers• Prototype• Users!!!!


User Testing

http://www.cs.waikato.ac.nz/usability/facilities.html

http://www.itl.nist.gov/iad/gallery.html


High Fidelity “Interactive” Prototype

NEEDSDESIGN

IMPLEMENTEVALUATE


Tools

• HTML & Javascript• Java JFC/Swing• Visual C++, Visual Basic• Flash MX, Director• Mac Interface Builder• others…or a mix of the above!!!


Examples: Interactive Prototype

From cs247a at Stanford University


Examples: Interactive Prototype

From cs160 at UC Berkeley


Examples of Projects

• Visual Voicemail• Interactive Academic Planner• Suzie Q• ToneDeaf Revolution


Appendix

Details on each of the data gathering techniques


Getting Users Involved

NEEDS

DESIGN

IMPLEMENTEVALUATE USE


Stages of User Involvement

• Need finding• Design [Participatory design]• Implementation [End-user

programming]• Evaluation• Use in the target setting

Users can be involved in any of the stages of the Design Process!


An Overview of Data Gathering Techniques

• Questionnaires• Interviews• Focus groups• Observation

– Naturalistic (ethnography)– Controlled (laboratory)

• Studying documentation (artifacts)


Questionnaires

• Qualitative vs. quantitative data• Motivation to complete – Response

rate• Uses of on-line questionnaires• Good for demographics, evaluation

of specific features or properties• Design of Scales

– Precision– Effort needed to decide on a response

See the detailed questionnaire guidelines in the text


Likert Scales and Semantic Differentials

How easy was the system to use?Easy Difficult 1 2 3 4 5 6 7

The system was easy to use

How easy was the system to use?Easy___________________________________Difficult

StronglyAgree Agree Neutral Disagree Strongly

Disagree


Interviews

• Degrees of structuring for different purposes– Structured - Like a guided questionnaire– Semi-structured - Basic script guides the

conversation– Open-ended - Still has a goal and focus

• Phone or face-to-face• Develop trust

– Be sensitive to the setting– Explain your goals to the interviewee

See the detailed interviewing guidelines in the text


Focus groups

• Group Interviews– Can be 2 or more

• Try to work with representatives of intended users

• Try to bring out differences• Require expert facilitation


Naturalistic observation

• “Quick-and-dirty”• Participant observation (ethnography)

– Insider-outsider spectrum• User camera studies• Diaries and pager studies• Audio/video recording• Walkthroughs

Many ethical issues are involved and it is important to have full user understanding and agreement to what you are doing


Insights from ethnography

• Seeing what is invisible to inhabitants– What they say vs. what they do

• The Heisenberg principle– Observation changes what is being observed


Observational Data Gathering

• Notes• Camera• Audio• Video

– Good for presentations, hard to analyze

– It’s the AUDIO, stupid.• Diaries

– User diaries• Logs


Controlled observation

• Laboratory settings and tasks• Techniques for understanding what

the user is doing– Walkthroughs– Think-aloud– Paired-think-aloud

More to come when we talk about testing


Studying documentation (artifacts)

• Official documentation/description• Physical and digital artifacts in the

environment


Data Gathering Guidelines

• Set clear goals for the data collection– Focus on identifying the stakeholders’ needs

• Involve all the stakeholder groups• Evaluate cost/benefit for your effort

– Understand the tradeoffs– Use a combination of techniques– Balance specific goals and openness

• Support data-gathering with appropriate props

• Run a pilot trial

lecture 6 – user-oriented designcs 3053 - mark woehrer - lecture 6 – user-oriented design mark...

Documents