Professional Documents
Culture Documents
IACT315 07 HeuristicEvaluation
IACT315 07 HeuristicEvaluation
Overview
Where we left off Underlying principles How to do it Presenting the findings
TEST DESIGN
BUILD
IDUS315 - HCI | 1
IDUS315 - HCI | 2
IDUS315 - HCI | 3
IDUS315 - HCI | 4
Heuristics are not: .. hard/fast rules .. always right .. the end of the discussion
IDUS315 - HCI | 5
IDUS315 - HCI | 6
1. Visibility of system status 2. Match between system and the real world 3. User control and freedom 4. Consistency and standards 5. Error prevention 6. Recognition rather than recall 7. Flexibility and efficiency of use 8. Aesthetic and minimalist design 9. Help users recognize, diagnose and recover from errors 10. Help and documentation
The system should always keep users informed about what is going on, through appropriate feedback within reasonable time
IDUS315 - HCI | 7
IDUS315 - HCI | 8
IDUS315 - HCI | 9
IDUS315 - HCI | 10
IDUS315 - HCI | 11
IDUS315 - HCI | 12
IDUS315 - HCI | 13
IDUS315 - HCI | 14
IDUS315 - HCI | 15
IDUS315 - HCI | 16
IDUS315 - HCI | 17
IDUS315 - HCI | 18
none
IDUS315 - HCI | 19
IDUS315 - HCI | 20
Wrap Up
Expert based, no users involved Based on a set of guidelines, previously established and recognized by the profession, known as heuristics Individual finds some problems, team finds lots of problems
IDUS315 - HCI | 21