1 / 13

Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough

Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough. CS352. Announcements. Notice upcoming events (web page). Midterm: where to stop studying. Team matters. Recall that: Everyone does everything. Specialties: make sure it’s done right .

hawa
Download Presentation

Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Evaluation (cont.):Heuristic EvaluationCognitive Walkthrough CS352

  2. Announcements • Notice upcoming events (web page). • Midterm: where to stop studying. • Team matters. Recall that: • Everyone does everything. • Specialties: make sure it’s done right. • Your grade depends on what your team thinks of your pulling your share.

  3. 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 • Design Gallery: • where did that fit in? • what to do with what happened there?

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

  5. Analytical methods • You follow established guidelines/procedures/models to decide (in your head) how good your design is. • Examples: • GOMS/KLM – for skilledusers. • evaluating efficiency of regular use. • Heuristic Evaluation • Cognitive Walkthrough – for first-time users. • evaluating ease of learning.

  6. 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: • ambient displays: pp. 699-700 (2nded). • web design: Box 15.1 (3rded). • Default: use Nielsen’s: • http://www.useit.com/papers/heuristic/heuristic_list.html

  7. Heuristic Evaluation: How • How: • Pick some usability guidelines, experts, task. • Brief the experts. • 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.

  8. Heuristic Evaluation: Activity • Applying this version of the guidelines to your projects: • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5

  9. 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. • Make up multiple copies of the Questions (next slide...)

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

  11. 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).

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

  13. Comparison • GOMS/KLM vs. HE vs. CogWalk • how long it takes you to do • how much detail it gives you • about what kind of user • how much of the UI you focus on at once

More Related