Heuristic Analysis for Interactive System Design - Prof. Charles Michael Lewis, Exams of Information Technology

Download Heuristic Analysis for Interactive System Design - Prof. Charles Michael Lewis and more Exams Information Technology in PDF only on Docsity!

INFSCI 2470Interactive System Design

Lecture 4: Heuristic Analysis Peter Brusilovskyhttp://www2.sis.pitt.edu/~peterb/2470-022/

Evaluating the Design

With the user

• Think-aloud usability testing
  Without the user - Cognitive Walkthrough– Action Analysis (GOMS)– Heuristic Analysis
  When? - Design stage– Final product Task-centeredapproach

Nine heuristics (1)

Simple and natural dialog– Simple means no irrelevant or rarely used information. Natural means an order that matchesthe task.
Speak the user's language

• Use words and concepts from the user's world. Don't use system-specific engineering terms.
  Minimize user memory load - Don't make the user remember things from one action to the next. Leave information on thescreen until it's not needed.

Nine heuristics (2)

Be consistent

• Users should be able to learn an action sequence in one part of the system and apply it again to getsimilar results in other places.
  Provide feedback - Let users know what effect their actions have on the system.
  Provide clearly marked exits - If users get into part of the system that doesn't interest them, they should always be able to getout quickly without damaging anything.

Heuristic Analysis Procedure

Several evaluators have to be used.Each one have to check the “wholething” with all 9 heuristics
Problems identified by evaluators haveto be combined in a single list
Just a few evaluators can find most ofthe problems
Experience vs. number of evaluators

The Place of Heuristic Analysis

Heuristic Analysis can be applied fordesign testing at several stages (theearlier, the better) Analyze Design Build Test

Speak the user's language Match between system and real world

• Use concepts, language, and real-world conventions familiar to the user
  Concepts - Desktop, trash can, ...
  Language - “Core dumped…”
  Conventions and cultural issues - Letterhead, highlighting, grouping...

Example: Date and time panel

ID: HE1 - Good feature
Description: Presentation ofthe date and time speaksuser language
Evidence: Match betweensystem and real world
Explanation: format for dateand time matches traditionalformat for NA residents
Benefit: the users will beable to recognize date andtime immediately withoutconversion to another format

Example: Fetch FTP Interface

Explanation:
Benefit:
ID: HE2 - Good feature
Description:
Evidence:

Be Consistent

Consistency, guidelines, standards

• Same things should always appear the same (words, icons, position on thescreen), different things should beexpressed differently
  Application consistency
  Platform consistency - new conventions and guidelines!

Before next lecture

Readings:

• Lewis and Rieman
  • Chapter 4: intro and 4.
    Homework (Due 2/13/02) - Check and grade three samples of the previous homework using posted rubrics - You will be graded on consistency of your own grading