Week 13: Errors, Failures, and Risks

Slides:



Advertisements
Similar presentations
“An Investigation of the Therac-25 Accidents” by Nancy G. Leveson and Clark S. Turner Catherine Schell CSC 508 October 13, 2004.
Advertisements

A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 PowerPoint ® Slides to Accompany A Gift of Fire : Social, Legal, and Ethical Issues for Computers.
Social Implications of a Computerized Society Computer Errors Instructor: Oliver Schulte Simon Fraser University.
An Investigation of the Therac-25 Accidents Nancy G. Leveson Clark S. Turner IEEE, 1993 Presented by Jack Kustanowitz April 26, 2005 University of Maryland.
Therac-25 Lawsuit for Victims Against the AECL
Can We Trust the Computer?
Slides prepared by Cyndi Chie and Sarah Frye. Fourth edition revisions by Sharon Gray. A Gift of Fire Fourth edition Sara Baase Chapter 8: Errors, Failures,
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
Motivation Why study Software Engineering ?. What is Engineering ? 2 Engineering (Webster) – The application of scientific and mathematical principles.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
A Gift of Fire Third edition Sara Baase
A Gift of Fire Third edition Sara Baase
Errors, Failures and Risks CS4020 Overview Failures and Errors in Computer Systems Case Study: The Therac-25 Increasing Reliability and Safety Dependence,
Jacky: “Safety-Critical Computing …” ► Therac-25 illustrated that comp controlled equipment could be less safe. ► Why use computers at all, if satisfactory.
International Health and Safety at Work
Lecture 7, part 2: Software Reliability
Ethical and Social...J.M.Kizza 1 Module 8: Software Issues: Risks and Liabilities Definitions Causes of Software Failures Risks Consumer Protection Improving.
Slides prepared by Cyndi Chie and Sarah Frye A Gift of Fire Third edition Sara Baase Chapter 8: Errors, Failures, and Risks Version modified by Cheryl.
Therac 25 Nancy Leveson: Medical Devices: The Therac-25 (updated version of IEEE Computer article)
Chapter 8: Errors, Failures, and Risk
1 Can We Trust the Computer? What Can Go Wrong? Case Study: The Therac-25 Increasing Reliability and Safety Perspectives on Failures, Dependence, Risk,
Liability for Computer Errors Not covered in textbook.
2.2 Software Myths 2.2 Software Myths Myth 1. The cost of computers is lower than that of analog or electromechanical devices. –Hardware is cheap compared.
Slides prepared by Cyndi Chie and Sarah Frye1 A Gift of Fire Third edition Sara Baase Chapter 8: Errors, Failures, and Risks.
Engineering Safety in Design Bo Hu John Nieber. Safety Damage from an unsafe process or product – A defective automobile brake system: Collision: driver,
Therac-25 Case Family vs. Programmer. People Suffered From Different Type of Bad Programming Database accuracy problems. Many people could not vote in.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Dimitrios Christias Robert Lyon Andreas Petrou Dimitrios Christias Robert Lyon Andreas Petrou.
CS 4001Mary Jean Harrold 1 Can We Trust the Computer?
CptS 401 Adam Carter. Announcement  Executive decision: no class Thursday! (CH and exam review will take place tomorrow instead)  Be sure that.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 Can We Trust the Computer?
Computing is Socio-Technical or: Why Stakeholder Listing is Inadequate for Thoughtful Ethical Analysis Chuck Huff St. Olaf College For NSF Computer Ethics.
Therac-25 CS4001 Kristin Marsicano. Therac-25 Overview  What was the Therac-25?  How did it relate to previous models? In what ways was it similar/different?
Copyright © 2012 Pearson Education, Inc. All rights reserved. Chapter 4 The Ethics of Manufacturing and Marketing.
Software Engineering. Acknowledgement Charles Moen Sharon White Bun Yue.
CS 4001Mary Jean Harrold1 Class 20 ŸSoftware safety ŸRest of semester Ÿ11/1 (Thursday) Term paper approach due Ÿ11/13 (Tuesday) Assignment 8 on software.
Chapter 8 Errors, Failures, & Risks. Real Headlines Navigation system directs car into river Data entry typo mutes millions of U.S. pagers Flaws found.
Topic: Reliability and Integrity. Reliability refers to the operation of hardware, the design of software, the accuracy of data or the correspondence.
Randy Modowski Adam Reimel Max Varner COSC 380 May 23, 2011 Accountability.
Chapter 8: Errors, Failures, and Risk Zach Archer Daniel O’Hara Eric Strittmatter.
CHAPTER 9: PROFESSIONAL ETHICS AND RESPONSIBILITIES BY: MATT JENNINGS SHANE CRAKER KYLER RHOADES.
1 Advanced Computer Programming Project Management: Basics Copyright © Texas Education Agency, 2013.
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?
FUNDAMENTALS OF COMPUTER SYSTEMS Lesson 1. Starter What is the difference between hardware and software?
Chapter 3 Agile software development 1 Chapter 3 – Agile Software Development.
Regression Testing with its types
Why study Software Design/Engineering ?
Managing Changes in the Real World
Chapter 18 Maintaining Information Systems
Medical Ethics Chapter 6.
VP, Institutional Services
FMEA.
Clinical Engineering Lecture (3).
Chapter 5 The Ethics of Manufacturing and Marketing
A Gift of Fire Third edition Sara Baase
PowerPoint® Slides to Accompany
Reliability and Safety
Chapter 1. Introduction Eric Braude and Michael Bernstein.
Reliability and Safety
CS385T Software Engineering Dr.Doaa Sami
Errors, Failures, & Risks
Lecture 06:Software Maintenance
Reliability and Safety
Chapter 5 The Ethics of Manufacturing and Marketing
Managing Project Risks and Opportunities
Computer in Safety-Critical Systems
A Gift of Fire Third edition Sara Baase
Chapter 1: Software and Software Engineering
Presentation transcript:

Week 13: Errors, Failures, and Risks www.hndit.com IT and Society Week 13: Errors, Failures, and Risks

What We Will Cover Failures and Errors in Computer Systems www.hndit.com What We Will Cover Failures and Errors in Computer Systems Case Study: The Therac-25 Increasing Reliability and Safety Dependence, Risk, and Progress

Failures and Errors in Computer Systems www.hndit.com Failures and Errors in Computer Systems Most computer applications are so complex it is virtually impossible to produce programs with no errors The cause of failure is often more than one factor Computer professionals must study failures to learn how to avoid them Computer professionals must study failures to understand the impacts of poor work

Failures and Errors in Computer Systems (cont.) www.hndit.com Failures and Errors in Computer Systems (cont.) Individual Problems: Billing errors Inaccurate and misinterpreted data in databases Large population where people may share names Automated processing may not be able to recognize special cases Overconfidence in the accuracy of data Errors in data entry Lack of accountability for errors

Failures and Errors in Computer Systems (cont.) www.hndit.com Failures and Errors in Computer Systems (cont.) High-level Causes of Computer-System Failures: Lack of clear, well thought out goals and specifications Poor management and poor communication among customers, designers, programmers, etc. Pressures that encourage unrealistically low bids, low budget requests, and underestimates of time requirements Use of very new technology, with unknown reliability and problems Refusal to recognize or admit a project is in trouble

Failures and Errors in Computer Systems (cont.) www.hndit.com Failures and Errors in Computer Systems (cont.) Safety-Critical Applications: A-320: "fly-by-the-wire" airplanes (many systems are controlled by computers and not directly by the pilots) Between 1988-1992 four planes crashed Air traffic control is extremely complex, and includes computers on the ground at airports, devices in thousands of airplanes, radar, databases, communications, and so on - all of which must work in real time, tracking airplanes that move very fast In spite of problems, computers and other technologies have made air travel safer

Case Study: The Therac-25 (cont.) www.hndit.com Case Study: The Therac-25 (cont.) Software and Design problems: Re-used software from older systems, unaware of bugs in previous software Weaknesses in design of operator interface Inadequate test plan Bugs in software Allowed beam to deploy when table not in proper position Ignored changes and corrections operators made at console

Case Study: The Therac-25 (cont.) www.hndit.com Case Study: The Therac-25 (cont.) Why So Many Incidents? Hospitals had never seen such massive overdoses before, were unsure of the cause Manufacturer said the machine could not have caused the overdoses and no other incidents had been reported (which was untrue) The manufacturer made changes to the turntable and claimed they had improved safety after the second accident. The changes did not correct any of the causes identified later

Case Study: The Therac-25 (cont.) www.hndit.com Case Study: The Therac-25 (cont.) Why So Many Incidents? (cont.) Recommendations were made for further changes to enhance safety; the manufacturer did not implement them The FDA declared the machine defective after the fifth accident The sixth accident occurred while the FDA was negotiating with the manufacturer on what changes were needed

Case Study: The Therac-25 (cont.) www.hndit.com Case Study: The Therac-25 (cont.) Observations and Perspective: Minor design and implementation errors usually occur in complex systems; they are to be expected The problems in the Therac-25 case were not minor and suggest irresponsibility Accidents occurred on other radiation treatment equipment without computer controls when the technicians: Left a patient after treatment started to attend a party Did not properly measure the radioactive drugs Confused micro-curies and milli-curies

Case Study: The Therac-25 Discussion Question www.hndit.com Case Study: The Therac-25 Discussion Question If you were a judge who had to assign responsibility in this case, how much responsibility would you assign to the programmer, the manufacturer, and the hospital or clinic using the machine?

Increasing Reliability and Safety www.hndit.com Increasing Reliability and Safety What goes Wrong? Design and development problems Management and use problems Misrepresentation, hiding problems and inadequate response to reported problems Insufficient market or legal incentives to do a better job Re-use of software without sufficiently understanding the code and testing it Failure to update or maintain a database

Increasing Reliability and Safety (cont.) www.hndit.com Increasing Reliability and Safety (cont.) Professional techniques: Importance of good software engineering and professional responsibility User interfaces and human factors Feedback Should behave as an experienced user expects Workload that is too low can lead to mistakes Redundancy and self-checking Testing Include real world testing with real users

Increasing Reliability and Safety (cont.) www.hndit.com Increasing Reliability and Safety (cont.) Law, Regulation and Markets: Criminal and civil penalties Provide incentives to produce good systems, but shouldn't inhibit innovation Warranties for consumer software Most are sold ‘as-is’ Regulation for safety-critical applications Professional licensing Arguments for and against Taking responsibility

Dependence, Risk, and Progress www.hndit.com Dependence, Risk, and Progress Are We Too Dependent on Computers? Computers are tools They are not the only dependence Electricity Risk and Progress Many new technologies were not very safe when they were first developed We develop and improve new technologies in response to accidents and disasters We should compare the risks of using computers with the risks of other methods and the benefits to be gained

Dependence, Risk, and Progress Discussion Questions www.hndit.com Dependence, Risk, and Progress Discussion Questions Do you believe we are too dependent on computers? Why or why not? In what ways are we safer due to new technologies?