Fall 2002CS/PSY 67501 Preventing Errors An Ounce of Prevention Errors  Avoiding and preventing  Identifying and understanding  Handling and recovering.

Slides:



Advertisements
Similar presentations
Chapter 3: Editing and Debugging SAS Programs. Some useful tips of using Program Editor Add line number: In the Command Box, type num, enter. Save SAS.
Advertisements

2-May-15 GUI Design. 2 HMI design There are entire college courses taught on HMI (Human-Machine Interface) design This is just a very brief presentation.
Ch 11 Cognitive Walkthroughs and Heuristic Evaluation Yonglei Tao School of Computing and Info Systems GVSU.
11 HCI - Lesson 5.1 Heuristic Inspection (Nielsen’s Heuristics) Prof. Garzotto.
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
Constraints and Errors An ounce of prevention…. Outline Part 1 comments Recap Norman About errors Mistakes and slips Error prevention guidelines Error.
Constraints and Errors
Case study - usability evaluation Howell Istance.
7M701 1 User Interface Design Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 15
Designing Appropriate User Interfaces Professor Larry Heimann Carnegie Mellon University Lecture Notes — Fall 1999.
Design of Everyday Things
1 SWE Introduction to Software Engineering Lecture 26 – User Interface Design (Chapter 16)
Today’s class Group Presentation More about principles, guidelines, style guides and standards In-class exercises More about usability Norman’s model of.
ICS 463, Intro to Human Computer Interaction Design: 4. Attention and Memory Dan Suthers.
User Interface Design. Overview The Developer’s Responsibilities Goals and Considerations of UI Design Common UI Methods A UI Design Process Guidelines.
Prevent Errors Do not let the user make the mistake in the first place. Limit choices –Hide or gray out unusable functions Look ahead –Have the system.
Errors & Error Assistance Discussion Section Wed 8:30-9:30 & Thu 1:30-2:30 Introductory HCI: User Interface Design, Prototyping, and Evaluation CSE 440.
Usability and Evaluation Dov Te’eni. Figure ‎ 7-2: Attitudes, use, performance and satisfaction AttitudesUsePerformance Satisfaction Perceived usability.
ISE554 The WWW 3.2 Multimedia Design Principles. Interaction Design Principles Guidelines Principles Rules Standards.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
User interface design.
User Interface Design Principles Gabriel Spitz 1 Lecture # 4.
User Characteristics & Design Principles Gabriel Spitz 1 Lecture # 11.
Speech Guidelines 2 of Errors VUIs are error-prone due to speech recognition. Humans aren’t perfect speech recognizers, therefore, machines aren’t.
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
CCT384 – Universal Design and Access
3461 Design Principles and Guidelines Hints for good design.
Errors & the Art of Error Assistance CSE 440 Autumn 2008.
Introduction to Visual Basic. Quick Links Windows Application Programming Event-Driven Application Becoming familiar with VB Control Objects Saving and.
1 Human-Computer Interaction  Design process  Task and User Characteristics  Guidelines  Evaluation.
CSC 480 Software Engineering Lecture 19 Nov 11, 2002.
Lecture 6 User Interface Design
1 The User Lecture 5. 2 Overview of Lecture Introduce final cognitive process – learning Interaction of cognitive processes.
Navigation Sequences Proper navigation Poor navigation Poor Navigation.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
10 Usability Heuristics for User Interface Design.
DOET 5 Human error. Question! When I poured the ground up coffee into my coffee cup rather than the French press, what type of Slip was that?
Fall 2002CS/PSY Design. Fall 2002CS/PSY System-Centered Design Focus is on the technology  What can be built easily using the available tools.
Errors & Help An ounce of prevention.... Microsoft’s Spectacular Errors Adobe UI Gripes Fall 2006PSYCH / CS
Fall 2002CS/PSY Human Capabilities Why do we care? (better design!) Want to improve user performance Knowing the user informs the design  Senses.
U SER I NTERFACE L ABORATORY Human Error 1.Introduction ○ To err is human, to forgive is the role of the computer interface ○ Norman (1988) in “The Psychology.
Heuristic Evaluation Short tutorial to heuristic evaluation
AS Level ICT Data entry: Creating validation checks.
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
Gabriel Spitz 1. Light Switch Issues  Consistency – The switch design is inconsistent with common light switches  Visibility – No visible cue regarding.
Ch16: User Interface Design Users often judge a system by its interface rather than its functionality Poorly designed interfaces can cause users to make.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Fall 2002CS/PSY UI Design Principles Categories  Learnability Support for learning for users of all levels  Flexibility Support for multiple ways.
Constraints and Errors An ounce of prevention…. Outline Questions? Project reminder Recap Norman About errors Mistakes and slips Error guidelines.
Design Principles Don Norman on design and HCI Basic process and guidelines for interaction design.
IT323 - Software Engineering 2 1 Tutorial 3.  Suggest ways in which the user interface to an e-commerce system such as an online stores might be adapted.
A disciplined approach to analyzing malfunctions –Provides feedback into the redesign process 1.Play protocol, searching for malfunctions 2.Answer four.
1 Design Principles – Part 2 of 3 Learnability Principles Flexibility Principles.
Prof. James A. Landay University of Washington Spring 2008 Guest Lecturer: Kate Everitt Web Interface Design, Prototyping, and Implementation Errors &
© 2016 Cognizant. © 2016 Cognizant Introduction PREREQUISITES SCOPE Heuristic evaluation is a discount usability engineering method for quick, cheap,
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
CEN3722 Human Computer Interaction Title of Presentation
Wrapping up DOET.
Errors & the Art of Error Assistance
Typical Person :^) Fall 2002 CS/PSY 6750.
Testing and Debugging.
Errors ECE 695 Alexander J. Quinn 3/9/2016.
MBI 630: Week 11 Interface Design
Design : Agenda Design challenges Idea generation Design principles
10 Design Principles.
Design dilbert Fall 2002 CS/PSY 6750.
Typical Person :^) Fall 2002 CS/PSY 6750.
Proper functionality Good human computer interface Easy to maintain
Usability Principles Human Ability Human Capabilities Memory Process
The Troubleshooting theory
Presentation transcript:

Fall 2002CS/PSY Preventing Errors An Ounce of Prevention Errors  Avoiding and preventing  Identifying and understanding  Handling and recovering

Fall 2002CS/PSY User-Computer Dialog Three phases  Read-scan phase -- Perceptual errors  Think phase -- Cognitive errors  Respond phase -- Motor errors

Fall 2002CS/PSY Perceptual Errors Result from insufficient or poor perceptual cues  Display of objects that are visually similar  Invisible or poorly expressed states  Failure to capture user’s attention  Lack of perceivable feedback

Fall 2002CS/PSY Cognitive Errors Caused by taxing the memory and problem solving capabilities  Tax recall memory  Lack of or poor mnemonic aids  Inconsistency  Lack of context or status info e.g., where came from in a menu  Mental calculations and translations

Fall 2002CS/PSY Motor Errors Taxing the eye-hand coordination and motor skills  Awkward motor movements  Highly similar motor sequences e.g., double click, click  Pressure for speed  Require a high degree of hand-eye coordination  Requiring special types of motor skills (type)

Fall 2002CS/PSY Example Studies 170 experienced UNIX users over 9 days  Individual commands had error rates of 3-50% 300 security system users over 20 months  12,117 error messages  Most common 11 errors -> 65%  2517 involved repeated errors (with no non-errors in between) within 10 minutes  Bad error recovery/help Kraut et al, CHI ‘83 Mosteller & Ballas, Human Factors ‘89

Fall 2002CS/PSY Slips Automatic (subconscious) error that occurs without deliberation Examples?

Fall 2002CS/PSY Types of Slips 1. Capture error - Continue frequently done activity instead of intended one (similar starts)  Type “animation” instead of animate  Confirm deletion of file instead of cancel 2. Description error - Intended action has much in common with others possible (usually when distracted, close proximity)  ctrl key & caps lock key / Sun & Mac 3. Data driven error - Triggered by arrival of sensory info which intrudes into normal action  Call to give someone a number, dial that number instead

Fall 2002CS/PSY Types of Slips 4. Associative activation - Internal thoughts and associations trigger action  Phone rings, yell “come in” 5. Loss of activation - Forgetting goal in middle of sequence of actions  Start going into room, then forget why you’re going there 6. Mode errors - Do action in one mode thinking you’re in another  Delete file, but you’re in wrong directory

Fall 2002CS/PSY Error Prevention Guidelines Eliminate modes or provide visible cues for modes Use good coding techniques (color, style) Maximize recognition, minimize recall Design non-similar motor sequences or commands Minimize need for typing Test and monitor for errors and engineer them out Allow reconsideration of action by user (e.g., removing file from trash)

Fall 2002CS/PSY Error Recovery Guidelines Provide appropriate type of response  Gag - Prevent user from continuing Erroneous login  Warn - Warn user an unusual situation is occurring Bell or alert box  Nothing - Just don’t do anything (Careful, user must determine problem) Mac: move file to bad place Responses (continued)  Self-correct - Guess correct action & do it Spell-check correction  Dialog - System opens dialog with user Go into debugger on run-time crash Query - Ask user what should’ve been done, then allow error action as legal one Command language naming error

Fall 2002CS/PSY Error Recovery Guidelines Provide undo function Provide cancel function from operations in progress Require confirmation for drastic, destructive commands Provide reasonableness checks on input data  Did you really mean to order 5000? Return cursor to error field, allow fix Provide some intelligence  Guess what they wanted to do) Provide quick access to context-sensitive help