Leveson Chapters 5 & 6 Gus Scheidt Joel Winstead November 4, 2002.

Slides:



Advertisements
Similar presentations
1 The role of human in ATM automation: a key issue Alain Printemps head of DNA/CENA.
Advertisements

Auditing Concepts.
Chapter 5: Common Support Problems
Accident Causes, Prevention and Control
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
Chapter 11 Artificial Intelligence and Expert Systems.
Psychological Aspects of Risk Management and Technology – G. Grote ETHZ, Fall09 Psychological Aspects of Risk Management and Technology – Overview.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Prototyping. CS351 - Software Engineering (AY2004)2 Scenario Customer: “We would like the word processor to check the spelling of what is typed in. We.
Computer Security: Principles and Practice
Title slide PIPELINE QRA SEMINAR. PIPELINE RISK ASSESSMENT INTRODUCTION TO GENERAL RISK MANAGEMENT 2.
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
1 Computer Systems & Architecture Lesson 1 1. The Architecture Business Cycle.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 4th Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Software Reliability: The “Physics” of “Failure” SJSU ISE 297 Donald Kerns 7/31/00.
Anomaly detection Problem motivation Machine Learning.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Lecture 1 What is Modeling? What is Modeling? Creating a simplified version of reality Working with this version to understand or control some.
Topic 5 Understanding and learning from error. LEARNING OBJECTIVE Understand the nature of error and how health care can learn from error to improve patient.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
By Anthony W. Hill & Course Technology1 Common End User Problems.
ITEC224 Database Programming
Classroom Assessment A Practical Guide for Educators by Craig A
1. 2 IMPORTANCE OF MANAGEMENT Some organizations have begun to ask their contractors to provide only project managers who have been certified as professionals.
1 Can We Trust the Computer? What Can Go Wrong? Case Study: The Therac-25 Increasing Reliability and Safety Perspectives on Failures, Dependence, Risk,
11 C H A P T E R Artificial Intelligence and Expert Systems.
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
Ecological Interface Design
Risk Management for Technology Projects Geography 463 : GIS Workshop May
Ranga Rodrigo. The purpose of software engineering is to find ways of building quality software.
1 TenStep Project Management Process ™ PM00.7 PM00.7 Project Management Preparation for Success * Manage Risk *
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Chapter 16 Problem Solving and Decision Making. Objectives After reading the chapter and reviewing the materials presented the students will be able to:
Hypotheses tests for means
1 IE 590D Applied Ergonomics Lecture 26 – Ergonomics in Manufacturing & Automation Vincent G. Duffy Associate Prof. School of IE and ABE Thursday April.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
Software Engineering Principles. SE Principles Principles are statements describing desirable properties of the product and process.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Chapter 6 DECISION MAKING: THE ESSENCE OF THE MANAGER’S JOB 6.1 © 2003 Pearson Education Canada Inc.
SESSION 2 The Sociotechnical Gap, Do Artifacts Have Politics?
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
CSE 303 – Software Design and Architecture
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Writing to Teach - Tutorials Chapter 2. Writing to Teach - Tutorials The purpose of a tutorial is to accommodate information to the needs of the user.
1 Chapter 13 (Week 13) SYSTEMS MAINTENANCE AND EVALUATION Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION Throughout its life, a system should operate effectively.
Human Reliability HUMAN RELIABILITY HUMAN ERROR
Crew Resources Management
Study & Conclusions. Perspectives on Face-to-face Interaction Success at anticipating the actions of the other – Implies need for Model of user that supports.
Projection and the Reality of Routines – reflections of a computational modeller Bruce Edmonds Centre for Policy Modelling Manchester Metropolitan University.
Can We Trust the Computer? FIRE, Chapter 4. What Can Go Wrong? What are the risks and reasons for computer failures? How much risk must or should we accept?
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Human Performance Enhancement System Park Young Ho Dept. of Nuclear & Quantum Engineering Korea Advanced Institute of Science and Technology December 23.
Human Performance Improvement/ HRO
Auditing Concepts.
Software Project Configuration Management
Adam Backman Chief Cat Wrangler – White Star Software
Classroom Assessment A Practical Guide for Educators by Craig A
Chapter 21 More About Tests.
Chapter 8 – Software Testing
BASICS OF SOFTWARE TESTING Chapter 1. Topics to be covered 1. Humans and errors, 2. Testing and Debugging, 3. Software Quality- Correctness Reliability.
Dept. of Nuclear and Quantum Engineering
Chapter 2 – Software Processes
Chapter 13 Quality Management
System Testing.
Presentation transcript:

Leveson Chapters 5 & 6 Gus Scheidt Joel Winstead November 4, 2002

“Human Error” in 2001: A Space Odyssey “The 9000-series is the most reliable computer ever made. No 9000-computer has ever made a mistake or distorted information.” “Well I don’t think there is any question about it. It can only be attributed to human error. This sort of thing has cropped up before and it has always been due to human error.” HAL then proceeds to eliminate the sources of “human error” on the spacecraft.

Alternate Explanations for “Operator Error” Data biased or incomplete Positive actions usually not noted Hindsight is always 20/20 Premise that operators can overcome every emergency Operators often intervene at the limits Difficult/Impossible to separate operator error from design error

Alternate Explanations for “Operator Error” Data biased or incomplete Positive actions usually not noted Hindsight is always 20/20 Difficult/Impossible to separate operator error from design error –Premise that operators can overcome every emergency –Operators often intervene at the limits

Blame the designers? Designers fail to fully understand system characteristics or anticipate all environmental conditions –Difficulty assessing probabilities of rare events –Bias against considering side effects –Tendency to overlook contingencies –Control complexity by concentrating on only a few aspects of the system –Limited capacity to comprehend complex relationships

Blame the designers? Designers fail to understand fully system characteristics or anticipate all environmental conditions Important to us as software designers

Human Error & Problem Solving Human Error: behavior that is inconsistent with normal, programmed patterns and that differs from prescribed procedures Exactly what is required to solve problems in unforeseen situations

Human Error & Rasmussen Skill-based: “errors” have a function in maintaining skill Rule-based: process of adapting rules and learning how to apply them requires experiments, some of which will fail Knowledge-based: human errors are the inevitable side effects of human adaptability and creativity

Relationship Between Experimentation and Error Designers have tools to assist with the experimentation process; Operators do not Examples of experimentation in software –Test-bed machines –New programming libraries –Exploring graphics tool features –Tweaking of a production system

Experimentation & Error in Software Differences between software and other industries –Undo –Error from Experimentation usually has less than catastrophic consequences

Lesson for Software Designers Summary: Human Error = unsuccessful experiments performed in “unkind” environment Our job: create “kind” environments –i.e. “design for error tolerance”

Mental Models and the Role of Human Operators

Mental Models as Abstractions Without abstraction, humans would be unable to cope with complex systems Mental models reflect goals and experience –Designer’s model vs. operator’s model

Mental Models Actual System Designer’s Model Operator’s Model Operational Experience Original Design Operational procedures, training Manufacturing and construction variances Evolution and changes over time

Model Mismatches as Source of Errors Guam Accident –Pilots assumed beacon was at end of runway –They then flew into side of mountain Three Mile Island –Operators built mental model assuming no loss of coolant –They then took actions making situation worse

Model Changes in Recovery Three Mile Island, again: –Operators eventually realized their model was wrong, and took action to correct it Human operators can change mental models when conflicts occur The same ability that causes model- mismatch accidents is also what allows for recovery from accidents

Maintaining Mental Models When designing a system, it is important to help operators maintain a good mental model of the system Operators must participate in the system in order to understand it Operators must have enough information to realize when their models are wrong

Three Roles Human as monitor Human as backup Human as partner

Human as Monitor The operator must know what correct behavior is, and how to maintain it The operator is dependent on information provided Failures may be silent or masked Tasks that require little operator activity may result in lowered alertness

Human as Backup When the operator must intervene, he must understand the situation –Operator may lack situational awareness Over-reliance on automated systems may make operators reluctant to intervene The system must provide enough information and enough control for operator to make correct decision

Human as Partner Automated systems may be better at repetitive tasks –But automation may reduce operator awareness Operator may simply be given the tasks that could not be automated Partially-automated systems might not actually decrease overall load on operator

Role of Human Operator The role of human operators must be considered in design The ability of human operators to maintain and correct mental models is important Human operators should not be treated as automatons in the system to handle tasks the designers could not automate

Autopilot Systems The aircraft can fly itself under normal circumstances When something unusual happens, the pilot must intervene Accidents occur when the pilot has an incorrect mental model Human as backup?

Lightweight Analysis Tools Tools like lint, ESC/Java, and Splint detect possible errors in source code Such tools are necessarily incomplete, unsound, or both A human must evaluate whether or not a real problem has been found

Version Control CVS can usually automatically merge different versions of a document CVS cannot always resolve conflicting changes It provides context so the user can build a mental model of the conflict and resolve it

Counterpane Systems Founded by Bruce Schneier of Applied Cryptography fame Human operators monitor their clients’ networks, looking for suspicious or abnormal activity Operators assisted by complex displays at control center Operators may take action by changing security policies

Grammar Checking The computer cannot write a thesis The computer can assist you as you write to find potential speling and grammar errors The computer is often wrong because it cannot understand the semantic context –e.g. passive voice is always assumed wrong Is the system monitoring the user or vice-versa?