Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation

Slides:



Advertisements
Similar presentations
Chapter 15: Analytical evaluation
Advertisements

Foundations and Strategies Attention Investment CS352.
Human Capabilities: Mental Models CS352. Announcements Notice upcoming due dates (web page). Where we are in PRICPE: –Predispositions: Did this in Project.
CS305: HCI in SW Development Continuing Evaluation: Asking Experts Inspections and walkthroughs.
Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough CS352.
Evaluation Types GOMS and KLM
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 25, 2003.
1 User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo FJK 2009.
Designing CS 352 Usability Engineering Summer 2010.
Evaluation Methodologies
Heuristics  Basis  Evaluators –Qualifications –Training  Preparation –Scenario  Results –List of problems –Severity –Group synthesis.
Inspection Methods. Inspection methods Heuristic evaluation Guidelines review Consistency inspections Standards inspections Features inspection Cognitive.
Evaluation Through Expert Analysis U U U
SIMS 213: User Interface Design & Development Marti Hearst Tues Feb 13, 2001.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
Evaluation: Inspections, Analytics & Models
HCI revision lecture. Main points Understanding Applying knowledge Knowing key points Knowing relationship between things If you’ve done the group project.
Discount Usability Engineering Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development March 2, 1999.
Usability Methods: Cognitive Walkthrough & Heuristic Evaluation Dr. Dania Bilal IS 588 Spring 2008 Dr. D. Bilal.
©2011 1www.id-book.com Analytical evaluation Chapter 15.
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
Multimedia Specification Design and Production 2013 / Semester 1 / week 9 Lecturer: Dr. Nikos Gazepidis
Usability Evaluation June 8, Why do we need to do usability evaluation?
Evaluation (cont.): Empirical Studies CS352. Announcements Notice upcoming due dates (web page). Where we are in PRICPE: –Predispositions: Did this in.
Reflection-in-action CS 352 Summer Why reflection-in-action? PRICPE is great! …but how do I carry out each step of it, e.g., Prototyping? Reflection-in-action.
Chapter 15: Analytical evaluation. Inspections Heuristic evaluation Walkthroughs.
Chapter 15: Analytical evaluation Q1, 2. Inspections Heuristic evaluation Walkthroughs Start Q3 Reviewers tend to use guidelines, heuristics and checklists.
Evaluating a UI Design Expert inspection methods Cognitive Walkthrough
Concepts and Prototypes CS352. Announcements Notice upcoming due dates (web page). Where we are in PRICPE: –Predispositions: Did this in Project Proposal.
User Interface Evaluation Cognitive Walkthrough Lecture #16.
Introduction to Usability Engineering CS 352 Winter
EVALUATION PROfessional network of Master’s degrees in Informatics as a Second Competence – PROMIS ( TEMPUS FR-TEMPUS-JPCR)
Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough CS352.
Cognitive Walkthrough More evaluating with experts.
Chapter 15: Analytical evaluation. Aims: Describe inspection methods. Show how heuristic evaluation can be adapted to evaluate different products. Explain.
Introduction to Evaluation without Users. Where are you at with readings? Should have read –TCUID, Chapter 4 For Next Week –Two Papers on Heuristics from.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
Oct 211 The next two weeks Oct 21 & 23: Lectures on user interface evaluation Oct 28: Lecture by Dr. Maurice Masliah No office hours (out of town) Oct.
Evaluation Types GOMS and KLM CS352. Quiz Announcements Notice upcoming due dates (web page). Where we are in PRICPE: –Predispositions: Did this in Project.
Usability Engineering Dr. Dania Bilal IS 587 Fall 2007.
Discount Evaluation User Interface Design. Startup Weekend Wellington CALLING ALL DESIGNERS, DEVELOPERS AND IDEAS FOLK: Startup Weekend returns to Wellington.
Asking Users and Experts Li Zhang (Jacey) Yuewei Zhou (Joanna)
SIE 515 Design Evaluation Lecture 7.
Imran Hussain University of Management and Technology (UMT)
Concepts and Prototypes
Foundations and Strategies Attention Investment
CS3205: HCI in SW Development Evaluation (Return to…)
Introduction to Usability Engineering
Evaluation without Users, Part 2
Analytical Evaluation with GOMS and KLM
Evaluation (cont.): Cognitive Walkthrough and Heuristic Evaluation
Introduction to HCI CS 565.
Introduction to Usability Engineering
Evaluation (cont.): Empirical Studies
Human Capabilities: Mental Models
Evaluation Types CS352.
Alfred Kobsa University of California, Irvine
Introduction to Usability Engineering
Learning about your users
CS305, HW1, Spring 2008 Evaluation Assignment
Evaluation.
Foundations and Strategies Attention Investment
Introduction to Usability Engineering
Evaluation (cont.): Empirical Studies
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
Cognitive Walkthrough
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
Introduction to Usability Engineering
Evaluation: Inspections, Analytics & Models
Evaluation (cont.): Empirical Studies: The Thinkaloud
Presentation transcript:

Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation CS565

Announcements (cont.) Where we are in PRICPE: Predispositions: Did this in Project Proposal. RI: Research was studying users. Hopefully led to Insights. CP: Concept and initial (very low-fi) Prototypes. Evaluate throughout, repeat iteratively

Evaluation Analytical – based on your head Empirical – based on data Formative inFORMs design what is (still) needed? Summative did it work?

Cognitive Walkthrough “Walk through” the UI, asking yourself questions along the way. Who does it: 1 or more usability experts. (3 is ideal) How: Identify characteristics of user and task. Have on hand multiple copies of the Questions (next slide...)

Cognitive Walkthrough: How (cont.) Walk through the task while answering these Questions: Will the user know what to do and how? (Gulf of exec) Will the user understand from feedback whether their action was correct? (Gulf of eval)

Cognitive Walkthrough: How (cont.) Record the answers but also: Assumptions about what would cause the problems and why. Notes about side issues. Notes about possible solutions. Example for Amazon.com p. 516 (3rd edition).

Cognitive Walkthrough: Activity PSU has a “shared car” program: http://www.zipcar.com/ Suppose a PSU student wants to consider whether to use it when she needs to shop. Walk through the steps of this task: Will s/he know what to do & how? (Gulf of exec) Will s/he understand from feedback whether the action was correct? (Gulf of eval) Notes: why, side-issues, ideas, ...

Analytical: Heuristic Evaluation One of the “Discount usability” methods Apply heuristic guidelines (eg: Nielsen’s) to a UI to find problems. Who does it: Multiple usability experts. Example heuristics: web design: Box 15.1 in Rogers pp. 508-509 ambient displays: Rogers pp. 511-512 Default: use Nielsen’s: http://www.useit.com/papers/heuristic/heuristic_list.html

Heuristic Evaluation: How Pick some usability guidelines, experts, task. Brief experts on what tasks/portions to evaluate. Experts indep’ly evaluate UI’s conformance with those guidelines for that task (1-2 hrs.) Pass 1: flow. Pass 2: focus on specific UI details. Outcome: UI problems. Experts meet to discuss problems, assign priorities, suggest solutions.

Heuristic Evaluation for this Class Use the GenderMag Heuristics

GM Heuristic Eval. Apply the GM Heuristics to the Walmart online grocery. The activity is to go through each guideline, look at the examples, then ask who sees something pertinent to that (and get a 2-sentence description of how it applies).