Software Engineering Disasters

Slides:



Advertisements
Similar presentations
Complex Systems Applications Dr. Jeyakesvan Veerasamy The University of Texas at Dallas, USA Good morning!
Advertisements

CML CML CS 230: Computer Organization and Assembly Language Aviral Shrivastava Department of Computer Science and Engineering School of Computing and Informatics.
CSCI 5230: Project Management Software Reuse Disasters: Therac-25 and Ariane 5 Flight 501 David Sumpter 12/4/2001.
The Therac-25: A Software Fatal Failure
CS 262 Software Engineering Keith Vander Linden Calvin College.
1. Software in our lives, then and now  Medical (processing and analysis, Computer Aided Surgery, other various equipment)  Financial and business (banking,
+ THE THERAC-25 - A SOFTWARE FATAL FAILURE Kpea, Aagbara Saturday SYSM 6309 Spring ’12 UT-Dallas.
Syllabus Case Histories WW III Almost Medical Killing Machine
1 Miscellaneous Vocabulary Object-Oriented Stuff Algorithms Software Design Testing and Types of Errors.
Patriot Missile Failure
CSC 4250 Computer Architectures September 12, 2006 Appendix H. Computer Arithmetic.
WHY THEY FAILED AND LESSONS TO BE DRAWN Samuel Franklin G53QAT: Quality Assurance and Testing Famous Software Failures.
Software Safety Basics
Software Reliability Engineering
Computers in Society Week 10: Software System Failures.
Scuds and Patriots CSE 200. History 1 st Gulf war 1991 Iraq attacking US troops using Scud missiles US defense: Patriot missiles.
CML CSE 520: Advanced Computer Architecture: Reliability Aviral Shrivastava.
Chapter 8 Representing Information Digitally.
1 COMS 161 Introduction to Computing Title: Numeric Processing Date: November 10, 2004 Lecture Number: 31.
Module 1- Getting Started PowerPoint Karaoke Talk for 1 minute about each slide.
Promoting Ethics to Computer Science Students: a “HOW TO” Guide Zenia C. Bahorski Ph.D. MACUL Conference Detroit, MI March 17, 2011 CC BY-NC-SA.
ARIANE 5 FAILURE ► BACKGROUND:- ► European space agency’s re-useable launch vehicle. ► Ariane-4 was a major success ► Ariane -5 was developed for the larger.
Lecture 4b: Risks and Liabilities of Computer-based Systems
CS 235: User Interface Design January 22 Class Meeting
Toward A Reasonable Programmer Standard Responsibility and Negligence in Software Design.
C ASE S TUDY 1 Software Engineering. S TATISTIC Conducted by Standish Group – IT executives of US companies in different industries 8,380 projects.
Lecture 7, part 2: Software Reliability
Software Errors Who is to blame?. Almost everything in our daily lives is controlled by CPU’s and software… Does Embedded Software = Embedded Disasters?
1/ REU Program at ECU Software Testing - Foundations, Tools, and Applications Lecture 1 May 27, 2014 Introduction to Software Testing Dr. Sergiy.
Know your users!. Users Last week we looked at the physical and cognitive abilities of humans Aims this week ◦ Understand the importance of knowing your.
USS Yorktown (1998) A crew member of the guided-missile cruiser USS Yorktown mistakenly entered a zero for a data value, which resulted in a division by.
The Unintended Consequences of a career in Engineering Or How to end up a mass murderer without even trying.
Introduction to CSCI-230: Software Development. Introduction Purchasing/developing software has become the largest single expenditure for companies Why.
Therac-25 Final Presentation
1/ REU Program at ECU Software Testing - Foundations, Tools, and Applications Lecture 1 May 21, 2013 Introduction to Software Testing Dr. Sergiy.
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
CS 235: User Interface Design August 25 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Software Engineering Background Dr. David A. Gaitros.
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.
Remembering September 11, 2001 How has the events on 9/11 changed the face of America?
Lecture 08 – Documentation, debugging.  docstring  A special kind of string (text) used to provide documentation  Appears at the top of a module 
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?
“I am not in the office at the moment. Send any work to be translated.”
TWO EXAMPLES AS MOTIVATION FOR THE STUDY OF COMPUTER ERRORS
CS, AUHenrik Bærbak Christensen1 Critical Systems Sommerville 7th Ed Chapter 3.
The Unintended Consequences of a career in Engineering Or How to end up a mass murderer without even trying.
Unintended Consequences of a career in Engineering.
Chapter 8 Errors, Failures, & Risks. Real Headlines Navigation system directs car into river Data entry typo mutes millions of U.S. pagers Flaws found.
Lecture#1 Introduction
Chapter 8: Errors, Failures, and Risk Zach Archer Daniel O’Hara Eric Strittmatter.

1. Introduction to Software Engineering. Software Engineering Outline Lecture 1 What is software Software is Everywhere Software Crisis and Software Failures.
SOFTWARE FAILURES.
CS 389 – Software Engineering Lecture 1 Introduction Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
School of Business Administration
Patriot Missile Failure
ECE 103 Engineering Programming Chapter 2 SW Disasters
Floating Point.
Systems Development and Project Management BDIS Chap 9
The Top 10 bugs
Therac-25 Accidents What was Therac-25? Who developed it?
Reliability and Safety
Software Engineering Lecture 1 Introduction Adapted from:
Errors, Failures, & Risks
What this course is NOT about:
Software Engineering Disasters
Computers and Society Software Reliability
Presentation transcript:

Software Engineering Disasters CSE 2031 Fall 2011

AT&T Lines Go Dead (1990) Cost: 75 million phone calls missed, 200 thousand airline reservations lost Disaster: A single switch at one of AT&T’s 114 switching centers suffered a minor mechanical problem and shut down the center. When the center came back up, it sent a message to other switching centers, which in turn caused them to shut down and brought down the entire AT&T network for 9 hours. Cause: A single line of buggy code in a complex software upgrade implemented to speed up calling caused a ripple effect that shut down the network.

Mariner Rocket Was Destroyed Cost: $18.5 million (1962) Disaster: The Mariner 1 rocket with a space probe headed for Venus diverted from its intended flight path shortly after launch. Mission Control destroyed the rocket 293 seconds after liftoff. Cause: A programmer incorrectly transcribed a handwritten formula into computer code, missing a single superscript bar. Without the smoothing function indicated by the bar, the software treated normal variations of velocity as if they were serious, causing faulty corrections that sent the rocket off course.

Hartford Coliseum Collapse (1978) Cost: $70 million, plus another $20 million damage to the local economy Disaster: Just hours after thousands of fans had left the Hartford Coliseum, the steel-latticed roof collapsed under the weight of wet snow. Cause: The programmer of the CAD software used to design the coliseum incorrectly assumed the steel roof supports would only face pure compression. But when one of the supports unexpectedly buckled from the snow, it set off a chain reaction that brought down the other roof sections like dominoes.

World War III… Almost (1983) Cost: Nearly all of humanity Disaster: The Soviet early warning system falsely indicated the U.S. had launched five ballistic missiles. Fortunately the Soviet duty officer had a “funny feeling in my gut” and reasoned if the U.S. was really attacking they would launch more than five missiles, so he reported the apparent attack as a false alarm. Cause: A bug in the Soviet software failed to filter out false missile detections caused by sunlight reflecting off cloud-tops.

Patriot Fails Soldiers (1991) Cost: 28 soldiers dead, 100 injured Disaster: During the first Gulf War, an American Patriot Missile system in Saudi Arabia failed to intercept an incoming Iraqi Scud missile. The missile destroyed an American Army barracks. Cause: A software rounding error incorrectly calculated the time, causing the Patriot system to ignore the incoming Scud missile.

Medical Machine Kills (1985) Cost: Three people dead, three people critically injured Disaster: Canada’s Therac-25 radiation therapy machine malfunctioned and delivered lethal radiation doses to patients. Cause: Because of a subtle bug called a race condition, a technician could accidentally configure Therac-25 so the electron beam would fire in high-power mode without the proper patient shielding.

Cancer Treatment to Die For (2000) Cost: Eight people dead, 20 critically injured (Panama) Disaster: Radiation therapy software by Multidata Systems International miscalculated the proper dosage, exposing patients to harmful and in some cases fatal levels of radiation. The physicians, who were legally required to double-check the software’s calculations, were indicted for murder. Cause: The software calculated radiation dosage based on the order in which data was entered, sometimes delivering a double dose of radiation.