Directed Reading 1 Girish Ramesh – 7680564 Andres Martin-Lopez – 8086086 Bamdad Dashtban – 8164848.

Slides:



Advertisements
Similar presentations
ES050 – Introductory Engineering Design and Innovation Studio Prof. Ken McIsaac One last word…
Advertisements

CSCI 5230: Project Management Software Reuse Disasters: Therac-25 and Ariane 5 Flight 501 David Sumpter 12/4/2001.
IT Roles and Responsibilities: How Good is Good Enough? IS 485, Professor Matt Thatcher.
“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
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.
Can We Trust the Computer? Case Study: The Therac-25 Based on Article in IEEE-Computer, July 1993.
Therac-25 Lawsuit for Victims Against the AECL
+ THE THERAC-25 - A SOFTWARE FATAL FAILURE Kpea, Aagbara Saturday SYSM 6309 Spring ’12 UT-Dallas.
Computingcases.org Safeware
Week 5 - Wednesday.  What did we talk about last time?  Attacks on hash functions.
Software Engineering Disasters
MotoHawk Training Model-Based Design of Embedded Systems.
Motivation Why study Software Engineering ?. What is Engineering ? 2 Engineering (Webster) – The application of scientific and mathematical principles.
A Gift of Fire Third edition Sara Baase
Chemotherapy Flow Sheet Eric Maurer Advisor: Ron Giles Supervisor: Phil Bolenbaugh.
A Gift of Fire Third edition Sara Baase
CSE 341 S. Tanimoto Social/Ethical Issues - 1 Social and Ethical Issues in Programming Language Design Can harm be done by designers of programming languages?
Software Reliability 25 September About the Evening Lectures  Viewing is required All lectures will be recorded and shown during a regular class.
Impacting Radiotherapy Safety and QA with Device Improvements Benedick A Fraass, PhD, FAAPM, FASTRO, FACR Allen S. Lichter Professor of Radiation Oncology.
Software Failures Ron Gilmore, CMC Edmonton April 2006.
Lecture 7, part 2: Software Reliability
Dr Andy Brooks1 Lecture 4 Therac-25, computer controlled radiation therapy machine, that killed people. FOR0383 Software Quality Assurance.
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.
Death by Software The Therac-25 Radio-Therapy Device Brian MacKay ESE Requirements Engineering – Fall 2013.
Therac-25 : Summary Malfunction Complacency Race condition (turntable / energy mismatch) Data overflow (turntable not positioned) time‘85‘86‘88 ‘87 Micro-switch.
(Using Clip Art to Help Argue That) Certifying Software Professionals (is the Wave of the Future) Brian Demers February 24, 2000 CS 99 Prof. Kotz.
Software Safety Case Study Medical Devices : Therac 25 and beyond Matthew Dwyer.
Applications of Geant4 in Proton Radiotherapy at the University of Texas M.D. Anderson Cancer Center Jerimy C. Polf Assistant Professor Department of Radiation.
Therac-25 Final Presentation
Hosted by Dr. William J. Frey Safety and Risk Educational Laptops Bus and Nat Env Therac
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.
Course: Software Engineering © Alessandra RussoUnit 1 - Introduction, slide Number 1 Unit 1: Introduction Course: C525 Software Engineering Lecturer: Alessandra.
Chapter 8: Errors, Failures, and Risk
Liability for Computer Errors Not covered in textbook.
CS 430/530 Formal Semantics Paul Hudak Yale University Department of Computer Science Lecture 1 Course Overview September 6, 2007.
Security and Reliability THERAC CASE STUDY TEXTBOOK: BRINKMAN’S ETHICS IN A COMPUTING CULTURE READING: CHAPTER 5, PAGES
Vladimir Misic: Design111:43:34 AM Software design.
Dimitrios Christias Robert Lyon Andreas Petrou Dimitrios Christias Robert Lyon Andreas Petrou.
Computer A computer is an electronic machine that takes information, processes it,and stores it. Computers are made up of hardware ( monitor, tower, keyboard,
© 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. System design techniques Quality assurance. 1.
What you know… You work at the East Texas Cancer Center in Tyler, Texas as a physicist who “maintains and checks the machine regularly.” (Huff 2005) Patient.
CS444A: Software for Critical Systems. 2 Staff Prof. David L. Dill Prof. Armando Fox.
Integrating the Health Care Enterprise- Radiation Oncology
Computingcases.org Safeware
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?
Risks CS 195 Social Implications of Computers. Risks Digest (Peter Neumann) # 1.1 Recent yet-to-be-merged items # Sep 2001 and Homeland Security.
CSCI 3428: Software Engineering Tami Meredith Chapter 7 Writing the Programs.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Finish Ethics Next Week Research Topics in HCI CS 321 Human-Computer Interaction.
FORMAL METHOD. Formal Method Formal methods are system design techniques that use rigorously specified mathematical models to build software and hardware.
Chapter 8 Errors, Failures, & Risks. Real Headlines Navigation system directs car into river Data entry typo mutes millions of U.S. pagers Flaws found.
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.
Interlock Systems for Machine Protection Manuel Zaera-Sanz Interlocks Engineer – ICS / Protection Systems AD and ICS Retreat mtg December 2014.
Laser Line work package (WP6) AWAKE Technical Board meeting 19 May 2014.
Increasing use of automated systems
ATTRACT TWD Symposium, Barcelona, Spain, 1st July 2016
Linac Commissioning Overview
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?
Reliability and Safety
Therac-25.
System design techniques
Therac-25: A Lesson Learned
Software Engineering Disasters
Computer System.
Presentation transcript:

Directed Reading 1 Girish Ramesh – Andres Martin-Lopez – Bamdad Dashtban –

Background CEG & AECL Therac 6 Therac 20 AECL Therac 25 -Dual Mode -Same PDP 11 [1] -One machine for all treatments -Software more responsible for safety -Less Hardware safety mechanisms and interlocks -Software is the key element Scanning Magnets Ion Chamber Flattening Filter Electron Beam 5-25 MeV Light Mirror

Therac 25 – The Story -Kennestone Regional Oncology Center, June Yakima Valley Memorial Hospital, December 1985 No specific bug found. - Ontario Cancer Foundation (Hamilton), July Yakima Valley Memorial Hospital, January East Texas Cancer Center (Tyler), March-April Massive Overdose. -Display error : No dose or low dose -Concurrent access to shared memory. -System not aware of changes in the mode/energy variable, if the cursor position changed after entering data. -Overdose due to exposure in field light mode. -Software error due to variable overflow. -Race condition[2] in system.

Conclusions Parallel computing has dependency on  software and hardware used. No techniques applied to avoid: - race conditions. - access to shared memory. In Therac 25: overvalued software over hardware. No proper Software Engineering[3] process applied: RequirementsDesignImplementationVerificationMaintenance Reuse of software. Not well documented. No Integration testing. No deep error investigation. Concurrency implementation and verification is not easy.

Citations [1] [2] [3]