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.

Slides:



Advertisements
Similar presentations
3.4 B4: Establishing and maintaining consistent standards of classroom behavior How does establishing and maintaining consistent standards of classroom.
Advertisements

MGT-555 PERFORMANCE AND CAREER MANAGEMENT
Annoy Your Users Less Session 202 Philip Wolfe, Lead Developer Farm Credit Services of America.
COMP 3715 Spring 05. Computer Interface Interaction between human and computer Has to deal with two things  User’s mental model Different user has different.
Representation at the Interface Gabriel Spitz 1 Lecture #13.
Ch 11 Cognitive Walkthroughs and Heuristic Evaluation Yonglei Tao School of Computing and Info Systems GVSU.
Good Design Visibility is key to interaction design Take advantage of affordances/constraints Provide a good conceptual model for the user.
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
Usage Profiles. Usage profiles never-ending 4 Process of “knowing the user” is never-ending much 4 So much to discover (social background, organisational.
Today’s class Group Presentation More about principles, guidelines, style guides and standards In-class exercises More about usability Norman’s model of.
Help and Documentation CSCI324, IACT403, IACT 931, MCS9324 Human Computer Interfaces.
User Interface Design Users should not have to adapt to a piece of software; the software should be designed to fit the user.
Usability and Evaluation Dov Te’eni. Figure ‎ 7-2: Attitudes, use, performance and satisfaction AttitudesUsePerformance Satisfaction Perceived usability.
User Centered Design Lecture # 5 Gabriel Spitz.
User Interface Evaluation CIS 376 Bruce R. Maxim UM-Dearborn.
User Interface Design Principles Gabriel Spitz 1 Lecture # 4.
User Characteristics & Design Principles Gabriel Spitz 1 Lecture # 11.
Heuristic evaluation IS 403: User Interface Design Shaun Kane.
©Ian Sommerville 2003Human FallibilitySlide 1 Human Fallibility.
Human factors in Complex Aviation Systems Cognition and some related errors.
Chapter #2: Motor Learning for Effective Coaching and Performance
Interplay, Eleventh Edition, Adler/Rosenfeld/Proctor
1 The User Lecture 5. 2 Overview of Lecture Introduce final cognitive process – learning Interaction of cognitive processes.
SCV2113 Human Computer Interaction Semester 1, 2013/2013.
User Interface Design Session 11- LBSC 790 / INFM 718B Building the Human-Computer Interface Cartoon removed.
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.
Multimedia Specification Design and Production 2012 / Semester 1 / week 5 Lecturer: Dr. Nikos Gazepidis
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
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?
1 Chapter 15 User Interface Design. 2 Interface Design Easy to use? Easy to understand? Easy to learn?
More on Design of Everyday Things. Turn it up, or shut it down?
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
Human-computer interaction: users, tasks & designs User modelling in user-centred system design (UCSD) Use with Human Computer Interaction by Serengul.
Understanding Users Cognition & Cognitive Frameworks
1 Chapter 4: User Interface Design. 2 Introduction … Purpose of user interface design:-  Easy to learn  Easy to use  Easy to understand.
Heuristic Evaluation Short tutorial to heuristic evaluation
U SER I NTERFACE L ABORATORY Situation Awareness a state of knowledge, from the processes used to achieve that state (situation assessment) not encompass.
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.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Importance of user interface design – Useful, useable, used Three golden rules – Place the user in control – Reduce the user’s memory load – Make the.
Fall 2002CS/PSY Preventing Errors An Ounce of Prevention Errors  Avoiding and preventing  Identifying and understanding  Handling and recovering.
Capabilities of Humans. Gestalt More than the sum of its parts.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
Constraints and Errors An ounce of prevention…. Outline Questions? Project reminder Recap Norman About errors Mistakes and slips Error guidelines.
TRAINING PACKAGE The User Action Framework Reliability Study July 1999.
A disciplined approach to analyzing malfunctions –Provides feedback into the redesign process 1.Play protocol, searching for malfunctions 2.Answer four.
Preparing for the Learning Experience Chapter 7. Objectives Discuss the concept of the learning experience Explain the role of the movement practitioner.
Chapter 5 Attention and Comprehension
© 2016 Cognizant. © 2016 Cognizant Introduction PREREQUISITES SCOPE Heuristic evaluation is a discount usability engineering method for quick, cheap,
Ten Usability Heuristics These are ten general principles for user interface design. They are called "heuristics" because they are more in the nature of.
CEN3722 Human Computer Interaction Attention and Memory
CEN3722 Human Computer Interaction Title of Presentation
Inspecting Software Requirement Document
SIE 515 Design Evaluation Lecture 7.
Chapter 2 Hix & Hartson Guidelines.
Human-Computer Interaction
Human Errors and the Error Abstraction Process
BASICS OF SOFTWARE TESTING Chapter 1. Topics to be covered 1. Humans and errors, 2. Testing and Debugging, 3. Software Quality- Correctness Reliability.
Software engineering USER INTERFACE DESIGN.
A NEW FACE OF THE TECHNICAL COMMUNICATOR – UX IS OUR STRENGTH – WE DESIGN TO WRITE BY CHRIS GANTA © 2016, STC INDIA CHAPTER.
Software Engineering D7025E
One-timer?. A new face of the technical communicator – UX is our strength – we design to write.
Provide Effective Feedback and Guidance and Assistance
Proper functionality Good human computer interface Easy to maintain
To Err is Human Owen Brennan.
Nilesen 10 hueristics.
Presentation transcript:

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 of Everyday Things” ○ If an error is possible, someone will make it. The designer must assume that all possible errors will occur and design so as to minimize the chance of the error in the first place, or its effects once it gets made. Errors should be easy to detect, they should have minimal consequences, and, if possible, their effects should be reversible. 2.Classifying Human Error 1)the state of believing what is untrue  cognitive aspect 2)something incorrectly done  physical aspect ○ actions & consequences of the actions 1.Human Error Categories 1.phenomenological classification – phenotype or error forms 2.classification on causes – genotype or error type

U SER I NTERFACE L ABORATORY Human Error Classification by consequences ○ the superficial nature of error or the error manifestation ○ ‘how’ rather than ‘why’ the error happened Classification by underlying causes ○ cognitive mechanism involved or cognitive biases 2.Slips and Mistakes ○ at the level of intention or planning ○ correct plan but wrong action – slips – failures of execution ○ wrong plan and correct action – mistakes – planning failure ○ Reason (1990) based on SRK-behavior (Rasmussen, 1986) ○ skill-based slips – SATO, intrinsic variability of operators ○ rule-based mistakes -- wrong rules, incorrect recall, interference ○ knowledge-based mistakes – resource limitations

U SER I NTERFACE L ABORATORY Human Error 3.Cognitive Control & System Error Mechanisms ○ Rasmussen and Vicente (1987) 1.Errors related to learning and adaptation 2.Errors due to interference among competing cognitive control structures 3.Errors due to lack of resources 4.Errors due to intrinsic human variability 4.Error-Shaping Factors (Table 1)Table 1 3.Error Capture and Recovery ○ the classic rule for error-free interface design to design an interface which is free of errors 80% of the time takes 20% of the overall design time ○ Not justifiable because of money

U SER I NTERFACE L ABORATORY Human Error

U SER I NTERFACE L ABORATORY Human Error System Response to Human Error ○ six possible responses (Lewis and Norman, 1995) (1) Gag (prevent user from continuing, (2) Warn (beeps), (3) Do Nothing (4) self-correct, (5) Let’s talk about it, and (6) Teach me Error Messages ○ not only tells the user what went wrong but also provides some information on how to take the right action ○ Eberts (1994) -- lacking in feedback effetiveness, unfriendly Feedback – facilitates error recovering 4.Error Reduction: Issues and Guidelines ○ R & V (1987) – guidelines of dealing with errors 1.Avoiding Mode Error ○ reduce the number of modes or totally eliminated

U SER I NTERFACE L ABORATORY Human Error 2.Maintaining Consistency ○ the concept of consistency implies that the mechanisms should be used in the same way wherever and whenever they occur ○ lack of consistency in the command structure – description errors 3.Facilitating Multiple Activities ○ human errors because of limitations of memory and environmental disruption ○ two aspects – levels of cognitive control and levels of attention ○ cognitive control 1)conscious control – performance of novel tasks, rule-based or knowledge-based level of control 2)unconscious or sub-conscious control – skill-based behavior (well practiced routine tasks)

U SER I NTERFACE L ABORATORY Human Error ○ Attention -- limits of selective, focused and divided attention ○ when multiple activities are significant (Miyata & Norman, 1986) ○ systems should be easy to suspend an activity ○ sufficient info should be saved with the suspended task ○ a reminding structure should be available 4.KIH vs. KIW ○ KIW in the task components reduces the load on human memory ○ KIW through design aids, memory checklists, cue cards, etc. ○ KIH rely on the users’ memory – Miller (1956) ○ recognition rather than recall ○ KIW – unaesthetic, time consuming, impossible due to physical constraints but makes the system easy to use ○ KIH – more efficient and aesthetic but errors due to memory loss, recall problems, more time to learn

U SER I NTERFACE L ABORATORY Human Error 5.Knowledge about users ○ all ages with varying levels of experience; different cultural backgrounds and some have disabilities ○ people with disabilities – 1/10 hearing impairment, 1/125 deaf, 1/100 visual disability 6.Understanding Cultural Biases ○ Silverman (1992) – cultural biases, cultural motivation, and missing knowledge as possible causes for mistakes ○ Yeo (1996) – cultural user interface (CUI) ○ overt factors – tangible and easily observed ○ covert factors – metaphors, colors, sounds are intangible 7.Generating Appropriate Interface Metaphors

U SER I NTERFACE L ABORATORY Human Error 7.Selecting Interface Icons ○ the design of icons carefully analyzed as they can lead to errors ○ semantic – the relationship of a visual image to a meaning  how well does this symbol represent the message? ○ syntactic – the relationship of one visual image to another  how does this icon look and related to other icons? ○ pragmatic – the relationship of visual image to a user  can the symbol be seen and does it remain visible? 8.Use of Colors ○ with great care by location, size, shape of the area it fills, surrounding colors, external conditions, physiological and cultural differences among individuals

U SER I NTERFACE L ABORATORY Human Error 10.On-Line Help ○ help system predicated on (Roesler and Mclellan, 1995) 1)information needs – help items and types 2)help access methods – how to access help, what help where 11.Training 5.Designing for Error Tolerance ○Rasmussen (1990), Senders and Moray (1991) ○errors are inavoidable side effects – have a role in the development and maintaining of expertise ○an error-forgiving design ○features for an error-tolerance interface (Hollnagel, 1990) 6.Benefits of Reducing Error ○ increase user productivity, decrease training costs, user frustrations, & customer support