Reliability and Safety

Slides:



Advertisements
Similar presentations
The Basics of Patient Safety How You Can Improve the Safety of Patient Care.
Advertisements

CSCI 5230: Project Management Software Reuse Disasters: Therac-25 and Ariane 5 Flight 501 David Sumpter 12/4/2001.
“An Investigation of the Therac-25 Accidents” by Nancy G. Leveson and Clark S. Turner Catherine Schell CSC 508 October 13, 2004.
The Therac-25: A Software Fatal Failure
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.
Background Increasing use of automated systems Hardware and software technology are improving rapidly User interface technology is lagging Critical bottleneck.
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
+ THE THERAC-25 - A SOFTWARE FATAL FAILURE Kpea, Aagbara Saturday SYSM 6309 Spring ’12 UT-Dallas.
© 2011 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of The Complete A+ Guide to PC Repair 5/e Chapter 5 Logical Trobleshooting.
Software Engineering Disasters
Protecting patients- now and in the future Linda Matthew Senior Pharmacist National Patient Safety Agency.
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,
1 Basic Definitions: Testing What is software testing? Running a program In order to find faults a.k.a. defects a.k.a. errors a.k.a. flaws a.k.a. faults.
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
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.
Software Failures Ron Gilmore, CMC Edmonton April 2006.
DJ Wattam, Han Junyi, C Mongin1 COMP60611 Directed Reading 1: Therac-25 Background – Therac-25 was a new design dual mode machine developed from previous.
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.
Software Safety Case Study Medical Devices : Therac 25 and beyond Matthew Dwyer.
Therac 25 Nancy Leveson: Medical Devices: The Therac-25 (updated version of IEEE Computer article)
ITGS Software Reliability. ITGS All IT systems are a combination of: –Hardware –Software –People –Data Problems with any of these parts, or a combination.
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,
The Complete A+ Guide to PC Repair 5/e Update Chapter 5 Logical Trobleshooting.
Liability for Computer Errors Not covered in textbook.
Slides prepared by Cyndi Chie and Sarah Frye1 A Gift of Fire Third edition Sara Baase Chapter 8: Errors, Failures, and Risks.
Security and Reliability THERAC CASE STUDY TEXTBOOK: BRINKMAN’S ETHICS IN A COMPUTING CULTURE READING: CHAPTER 5, PAGES
Dimitrios Christias Robert Lyon Andreas Petrou Dimitrios Christias Robert Lyon Andreas Petrou.
Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
© 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. System design techniques Quality assurance. 1.
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?
1 Fault-Tolerant Computing Systems #1 Introduction Pattara Leelaprute Computer Engineering Department Kasetsart University
CS, AUHenrik Bærbak Christensen1 Critical Systems Sommerville 7th Ed Chapter 3.
Dr. Rob Hasker. Classic Quality Assurance  Ensure follow process Solid, reviewed requirements Reviewed design Reviewed, passing tests  Why doesn’t “we.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Finish Ethics Next Week Research Topics in HCI CS 321 Human-Computer Interaction.
Chapter 8 Errors, Failures, & Risks. Real Headlines Navigation system directs car into river Data entry typo mutes millions of U.S. pagers Flaws found.
Dr. Rob Hasker. Classic Quality Assurance  Ensure follow process Solid, reviewed requirements Reviewed design Reviewed, passing tests  Why doesn’t “we.
Directed Reading 1 Girish Ramesh – Andres Martin-Lopez – Bamdad Dashtban –
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.
GATE SAFETY WEEK TH OCTOBER GUIDANCE FOR HOMEOWNERS AND THE PUBLIC KEEPING THE NATION SAFE A guide to keeping you safe around powered gates.
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?
Organization and Implementation of a National Regulatory Program for the Control of Radiation Sources Need for a Regulatory program.
Increasing use of automated systems
Why study Software Design/Engineering ?
Introduction to Assurance
ATTRACT TWD Symposium, Barcelona, Spain, 1st July 2016
EE 585 : FAULT TOLERANT COMPUTING SYSTEMS B.RAM MOHAN
COMP60611 Directed Reading 1: Therac-25
Therac-25 Accidents What was Therac-25? Who developed it?
A Gift of Fire Third edition Sara Baase
PowerPoint® Slides to Accompany
JOB HAZARD ANALYSIS (JHA)
IENE5(Intercultural Education of Nurses in Europe Project 5)
Workshop on Accelerator Operations
Therac-25.
System design techniques
Therac-25: A Lesson Learned
Reliability and Safety
Week 13: Errors, Failures, and Risks
Errors, Failures, & Risks
Reliability and Safety
A Gift of Fire Third edition Sara Baase
Software Engineering Disasters
Presentation transcript:

Reliability and Safety Therac-25

Case Study - Therac-25 Software controlled radiation therapy machine used to treat people with cancer Problems: Massive overdoses administered Repeated overdoses due to faulty display Death of patients Operated in dual machine mode - electron beam or x-ray photon beam

Why Did Problems Arise? Lapses in good safety design Insufficient testing Bugs in software that controlled machines Inadequate system of reporting and investigating accidents and deaths

Specific Problems Some hardware safety features were eliminated in newer models Software used was assumed correct form older systems Malfunctioned frequently requiring operator intervention Weakness in design of operator interface Inadequate explanation of error messages if any

Specific Problems continued… Machine allowed one-key intervention versus automatic shutdown Inadequate documentation Poor test plan

Software Errors - Bugs Fatal error was a simple fix Fixes are complex, expensive, and prevents use of machine while fixing Bugs can be intermittent and hard to detect importance of self checking importance of using good programming techniques

Overconfidence Leaving out changes that are necessary (by designers) Ignoring error messages (by technicians) Not using backup devices (video or audio communication with patient)

Conclusion and Perspective Irresponsibility leads to criminal charges Responsibility leads to merit awards Importance of good software development Consequences of carelessness, cutting corners, unprofessional work, or attempts to avoid responsibility Lack of appreciation for risks Poor training Overconfidence in systems can prove deadly