Software Engineering Background Dr. David A. Gaitros.

Slides:



Advertisements
Similar presentations
Electronic Measure and Test Unit 53 Task 4 (P4).  A plan that clearly details the tests that will be performed  What to test  How to test (step by.
Advertisements

CSCI 5230: Project Management Software Reuse Disasters: Therac-25 and Ariane 5 Flight 501 David Sumpter 12/4/2001.
Overview CNS 3320 – Numerical Software Engineering.
Social Implications of a Computerized Society Computer Errors Instructor: Oliver Schulte Simon Fraser University.
1. Software in our lives, then and now  Medical (processing and analysis, Computer Aided Surgery, other various equipment)  Financial and business (banking,
Can We Trust the Computer?
Syllabus Case Histories WW III Almost Medical Killing Machine
CSC 4250 Computer Architectures September 12, 2006 Appendix H. Computer Arithmetic.
Software Engineering Disasters
Computers in Society Week 10: Software System Failures.
Ethics in a Computing Culture
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.
Motivation Why study Software Engineering ?. What is Engineering ? 2 Engineering (Webster) – The application of scientific and mathematical principles.
15 November Essay 1  Methodologies Points on the spectrum All can adapt to changes Required vs. permitted  Releases vs. iterations  Spool’s.
Modern Software Development Fawzi Emad Chau-Wen Tseng Department of Computer Science University of Maryland, College Park.
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.
A Gift of Fire Third edition Sara Baase
1 CMSC 132: Object-Oriented Programming II Software Development I Department of Computer Science University of Maryland, College Park.
©Ian Sommerville 2004Software Engineering Case Studies Slide 1 The Ariane 5 Launcher Failure June 4th 1996 Total failure of the Ariane 5 launcher on its.
Software Errors Who is to blame?. Almost everything in our daily lives is controlled by CPU’s and software… Does Embedded Software = Embedded Disasters?
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.
Ch 1: The Scope of Software Engineering
IMPROVING SOFTWARE QUALITY FOR THE MODERN WEB EUAN GARDEN MICROSOFT
CPSC 871 John D. McGregor Module 0 Session 1 Introduction.
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
Introduction to Software Quality Assurance
Ganssle 1 MAPLD 2005/S110 Learning from Jack Ganssle Disaster.
The Ariane 5 Launcher Failure June 4th 1996 Total failure of the Ariane 5 launcher on its maiden flight.
B. Todd AB/CO/MI 30 th January 2008 Safety in Mind…
Slides prepared by Cyndi Chie and Sarah Frye1 A Gift of Fire Third edition Sara Baase Chapter 8: Errors, Failures, and Risks.
THE SPACE SHUTTLE. Shuttle Take Off T-31s ground computer system hands over to shuttle system T-16s sound suppression system soaks the launch pad with.
SPACE TRAVEL Space, the final frontier Astronaut  A person that is trained to be a pilot, navigator or scientist in space.
CS 430/530 Formal Semantics Paul Hudak Yale University Department of Computer Science Lecture 1 Course Overview September 6, 2007.
CSc161 Software Quality Pete Sawyer & Alan Dix
INVARIANTS EEN 417 Fall When is a Design of a System “Correct”? A design is correct when it meets its specification (requirements) in its operating.
Modern Software Development Nelson Padua-Perez Chau-Wen Tseng Department of Computer Science University of Maryland, College Park.
CS 4001Mary Jean Harrold 1 Can We Trust the Computer?
Unit Conversions Karan Patel. Different Units Units are measurements of things Examples Time (seconds) Distance (meters) Mass (kilograms) Force (pounds)
16 October Reminder Types of Testing: Purpose  Functional testing  Usability testing  Conformance testing  Performance testing  Acceptance.
Chapter 1 Physical Quantities, Units, Measurements and Estimation In the quest to understand nature, scientists use physical quantities to describe the.
“I am not in the office at the moment. Send any work to be translated.”
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(UIT), M.S(S.E) AAU Denmark Assistant Professor Department.
1 Software Quality Assurance COMP 4004 Notes Adapted from S. Som é, A. Williams.
Software Engineering. Acknowledgement Charles Moen Sharon White Bun Yue.
Ch. 1: Introduction: Physics and Measurement. Estimating.
29 March Software Quality and Testing. Why do we care? Therac-25 (1985) Multiple space fiascos (1990s) Ariane V exploded after 40 seconds (conversion)
Space Exploration Timeline
1 Software Engineering--Introduction. 2 1.Syllabus, grading, schedule--class + lab--will all be on 2.Contact.
Dividing with Significant Figures. In calculations, the accuracy of the calculated result is limited by the least accurate measurement involved in the.
The asteroid entered our atmosphere at a height of 12 miles and it is falling at a rate of 2 miles every 3 minutes. Write and graph an equation to represent.
Chapter 8 Errors, Failures, & Risks. Real Headlines Navigation system directs car into river Data entry typo mutes millions of U.S. pagers Flaws found.
Space Exploration Timeline Amy Oliver Russia- a scientist named Tsiolkovsky started testing rockets. Konstantin Tsiolkovsky developed.
Topic 10Summer Ariane 5 Some slides based on talk from Sommerville.
Mars Climate Orbiter Error in transfer of information from spacecraft team in Colorado.
SOFTWARE FAILURES.
CS 389 – Software Engineering Lecture 1 Introduction Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
Software Engineering--Introduction
Why study Software Design/Engineering ?
ECE 103 Engineering Programming Chapter 2 SW Disasters
The Top 10 bugs
Historical Engineers This presentation is about historical engineers.
A Gift of Fire Third edition Sara Baase
Software Engineering Lecture 1 Introduction Adapted from:
Space Technology and History
Scale of things : Big and Small
C021TV-I3-S3.
Reliability and Safety
A Gift of Fire Third edition Sara Baase
Software Engineering Disasters
Presentation transcript:

Software Engineering Background Dr. David A. Gaitros

Classic Software Engineering problems IBM OS/260 – Decade long project with many cost overruns. – Fred Brooks claims to have made a multi-million dollar mistake by not developing a coherent architecture first. Ariane 5 Flight 501 – First unsuccessful flight of the Equropean Ariane 5 expendable launch system. Reused software from the Ariane 4 and a data conversion problem not previousley discovered.

Classic Software Engineering problems MIM-104 Patriot surface-to-air missile system. – Not designed to stay in operation for an extended period of time. The longer the system was on the higher the error on a continuous calculation which through of the accuracy of the system. Mariner 1 – A hardware failure caused the system to lose contact with the ground and the computer took over. A mistranslation of an equation sent the rocket off course.

Classic Software Engineering problems Therac-25 Radiation Therapy Machine – Allowed patients to receive lethal doses of radiation. Denver Airport Baggage Handling – Significant mechanical and software problems plagued the automated baggage handling system. In tests of the system, bags were misloaded, were misrouted, or fell out of telecarts, causing the system to jam.

Classic Software Engineering problems Mars Climate Orbiter – The Mars Climate Orbiter crashed because a contractor delivered a navigational instrument that output Imperial units instead of metric. 180 Degree Bug – Torpedoes use to be programmed so that if they deviated more than 90 degrees they exploded to avoid self destruction of the ship. One time a ship fired a torpedo that go stuck in the tube and he ordered the ship to return to the harbor! BOOM!

Classic Software Engineering problems USS Yorktown Stops, 1998 – A crewmember of the computer controlled guided-missile cruiser USS Yorktown mistakenly entered a zero on their console. A divide by zero operation caused the engines to shut down. Pentium Chip – 1994 pentium chip used pre-calculated set of numbers to speed up division. Initially there were five missing numbers. Cost - $4 billion.

However – Before Software Engineering Scientists accurately calculated the mathematics needed to detonate a nuclear explosion. Man traveled to the moon on a computer less powerful than today’s hand held calculators. The Unix operating system was developed using the C- programming language which has been touted by the world of Software Engineers to be the worst language to use. The Voyager spacecraft is still working. The SR-71 Aircraft was developed in the 1950’s and is still today the fastest production aircraft ever built.

Why were some projects successful and other not? Answer: – Poor software developers produce poor software. – Mediocre software developers produce mediocre software. – Outstanding software developers produce superior quality software. Software Engineering was conceived to take the human element out of the equation.

Class Discussion What were some of the initiatives designed to aid in improving the quality of software? What would you compare the development of software to? What are the attributes of a good software developer? What are the attributes of an excellent software developer? Have these attributes changed over the years?