User Interface Evaluation: Methods and Techniques - Prof. John Sibert, Study notes of Computer Science

An overview of user interface evaluation, focusing on areas of interest, user interface debugging, user observation, and evaluation methodologies. It covers various techniques for testing speed of learning and use, measuring documentation effectiveness, and observing user interactions. Methods include audio and video taping, online testing, questionnaires, structured and unstructured interviews, and focus groups.

Typology: Study notes

Pre 2010

Uploaded on 08/18/2009

koofers-user-b5w
koofers-user-b5w 🇺🇸

9 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
3/23/09
1
Evaluating User
Interfaces
CSCI 264 – Design of Human-Computer
Interface
Areas of Interest
Application being designed and developed
Design phase
Alpha/Beta Prototypes
Release version
Competitor applications
User perceptions about a task or application
Starts at design review prototyping time (if
possible)
Have typical real users involved
keep designers gagged in background to
listen, observe, learn, and sweat!
Plan on major investments here, particularly
for commercial products
Major portions, adapted from notes prepared by John Lovgren and Sherry Kalin.
Used by permission.
User Interface Debugging
Test for problems in the interface
Measure for speed of learning
Measure for speed of use
Test usefulness of documentation
All iterative, but documentation has distinct
purposes for different types of information
User Interface Debugging
Evaluate Interface Problems
Use typical users
Test typical tasks
Record details of all interactions
Record interactions between users
Record thinking protocol of user
Record signs of stress or frustration
Record user's subjective reactions
Speed of learning
Work with typical users, performing typical
sequence of typical tasks
Use typical training
Control training time
Measure performance and compare to goals
set as part of user requirements
Evaluate Interface Problems
pf3
pf4

Partial preview of the text

Download User Interface Evaluation: Methods and Techniques - Prof. John Sibert and more Study notes Computer Science in PDF only on Docsity!

Evaluating User

Interfaces

CSCI 264 – Design of Human-Computer Interface

Areas of Interest

 Application being designed and developed  Design phase  Alpha/Beta Prototypes  Release version  Competitor applications  User perceptions about a task or application  Starts at design review prototyping time (if possible)  Have typical real users involved  keep designers gagged in background to listen, observe, learn, and sweat!  Plan on major investments here, particularly for commercial products Major portions, adapted from notes prepared by John Lovgren and Sherry Kalin. Used by permission.

User Interface Debugging

 Test for problems in the interface

 Measure for speed of learning

 Measure for speed of use

 Test usefulness of documentation

 All iterative, but documentation has distinct

purposes for different types of information

User Interface Debugging

Evaluate Interface Problems

 Use typical users

 Test typical tasks

 Record details of all interactions

 Record interactions between users

 Record thinking protocol of user  Record signs of stress or frustration  Record user's subjective reactions  Speed of learning  Work with typical users, performing typical sequence of typical tasks  Use typical training  Control training time  Measure performance and compare to goals set as part of user requirements

Evaluate Interface Problems

 Speed of use  Work with typical users, performing typical sequence of typical tasks  Record time to completion, and number and types of errors  Measure enough users to have reasonable statistical validity  Compare times to goals set as part of user requirements Evaluate Interface Problems  Documentation  Apply computerized tests for:  Reading level  Overly long/complex sentences  Have users read documentation; give them a comprehension test  Have users carry out tasks, aided only by documentation  Have non-users (i.e. new users) read documentation for clarity Evaluate Interface Problems  Let users try to get past trouble spots  If they cannot:  help them, but not too much  explain only what is necessary  note how you had to explain it  give a break every 45 min.  debrief participant at end of session about problems User Observation User Observation  Mind yourself  Sit at a distance  Stay concealed (with permission)  Note places users have trouble:  where  how they got there  what happened  how did they try to recover (did they try?) Evaluation Methodologies  Audio tape  Video tape  Online testing  Questionnaires  Interviews  Structured  Unstructured  Focus groups  Always obtain written permission to tape session  Place microphone where it will not be intrusive  Conceal microphone if necessary (and appropriate)  Make sure that the microphone can pickup an appropriate sound level (boost or reposition if necessary) Audio Taping

Data Gathering  Establish a user interface testing lab  Methods  One participant, one observer  One participant thinking aloud, one observer  Two participants, no observer For Next Week  Nothing (NO CLASS 3/17/09) (but make sure to finish your Design Document for the week after)