Computer in Safety-Critical Systems

Slides:



Advertisements
Similar presentations
Engineering Diploma Level 2 Unit 7 Application of Maintenance Techniques in Engineering In this unit you will get involved with both maintenance procedures.
Advertisements

FDA Human Factors of Medical Devices
Chapter 1: Introduction
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.
Concurrency: introduction1 ©Magee/Kramer 2 nd Edition Concurrency State Models and Java Programs Jeff Magee and Jeff Kramer.
Can We Trust the Computer?
Investment Appraisal and Management Chapter 1 The Role of Project Evaluation.
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
Software Testing and Quality Assurance
Dr.-Ing. M.S.TULEIMAT Dr.-Ing. M.S.TULEIMAT (PhD, Med. Equipment Safety, (W) Germany) The Patient, The Safety, The Medical Equipment & The Medical / Clinical.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
SWE Introduction to Software Engineering
CSC 402, Fall Requirements Analysis for Special Properties Systems Engineering (def?) –why? increasing complexity –ICBM’s (then TMI, Therac, Challenger...)
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
Module 8: Software Issues: Risks and Liabilities
The most precious commodity in your organisation?
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Ethical and Social...J.M.Kizza 1 Module 8: Software Issues: Risks and Liabilities Definitions Causes of Software Failures Risks Consumer Protection Improving.
Evaluation of Safety Critical Software -- David L. Parnas, -- A. John van Schouwen, -- Shu Po Kwan -- June 1990 Presented By Zhuojing Li.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Concurrency: introduction1 ©Magee/Kramer Concurrency State Models and Java Programs Jeff Magee and Jeff Kramer.
Therac 25 Nancy Leveson: Medical Devices: The Therac-25 (updated version of IEEE Computer article)
Course: Software Engineering © Alessandra RussoUnit 1 - Introduction, slide Number 1 Unit 1: Introduction Course: C525 Software Engineering Lecturer: Alessandra.
1 Can We Trust the Computer? What Can Go Wrong? Case Study: The Therac-25 Increasing Reliability and Safety Perspectives on Failures, Dependence, Risk,
Software engineering. What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects of software.
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Intent Specification Intent Specification is used in SpecTRM
Dimitrios Christias Robert Lyon Andreas Petrou Dimitrios Christias Robert Lyon Andreas Petrou.
Some Sub-Activities within Requirements Engineering 1.Prototyping 2.Requirements Documentation 3.Requirements Validation 4.Requirements Measurements 5.Requirements.
CS 4001Mary Jean Harrold 1 Can We Trust the Computer?
Mohammed Al-khwyldi  Introduction Safety is the condition of being protected against physical, social, political, emotional, educational or other.
This class cannot be shared or copied without the written permission of PracticeWorks Systems, LLC.
11th International Symposium Loss Prevention 2004 Prague Ľudovít JELEMENSKÝ Department of Chemical and Biochemical Engineering, STU BRATISLAVA, SLOVAKIA.
REGULATORY PERSPECTIVE ON USING OPERATIONAL EXPERIENCE Thomas E. Murley Former Director of Nuclear Reactor Regulation USNRC Conference on Improving Nuclear.
A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 Can We Trust the Computer?
“You have a duty of care for your own health and safety”
Main Requirements on Different Stages of the Licensing Process for New Nuclear Facilities Module 4.5/1 Design Geoff Vaughan University of Central Lancashire,
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 1.
Guidelines: Prepare at most 20 slides Headwords, no sentences A title for every slide Contents Title Overview Background Approach Summary.
SAFEWARE System Safety and Computers Chap18:Verification of Safety Author : Nancy G. Leveson University of Washington 1995 by Addison-Wesley Publishing.
Teknologi Pusat Data 12 Data Center Site Infrastructure Tier Standard: Topology Ida Nurhaida, ST., MT. FASILKOM Teknik Informatika.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
Methodological Issues in Implantable Medical Device(IMDs) Studies Abdallah ABOUIHIA Senior Statistician, Medtronic.
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?
1 Chapter 9: Design for People; Ergonomics, Repairability, Safety, and Product Liability 9.1 Important Definitions Ergonomics (or Human engineering, or.
Human Performance Enhancement System Park Young Ho Dept. of Nuclear & Quantum Engineering Korea Advanced Institute of Science and Technology December 23.
Essential Requirements of Pool Management Companies
Guide for the application of CSM design targets (CSM DT)
System Design, Implementation and Review
Critical systems design
BASIC PROFESSIONAL TRAINING COURSE Module V Safety classification of structures, systems and components Case Studies Version 1.0, May 2015.
Software Verification and Validation
Dept. of Nuclear and Quantum Engineering
Preventing Medical Device Recalls
Initiating systems development
Air Carrier Continuing Analysis and Surveillance System (CASS)
HSE Case: Risk Based Approach.
State of Configuration Management
A Gift of Fire Third edition Sara Baase
PowerPoint® Slides to Accompany
Lecture 8 Is Software Different?
Software testing and configuration : Embedded software testing
Week 13: Errors, Failures, and Risks
INFS 452 – Computer Ethics & Society
Chapter # 7 Software Development
PSS verification and validation
A Gift of Fire Third edition Sara Baase
Presentation transcript:

Computer in Safety-Critical Systems Chapter 6 Computer in Safety-Critical Systems Introduction “Safety-critical” and other definitions How and why failures occur? Risk analysis Evaluating software A case study of safety-critical failures Model verification and validation When human welfare is at stake, the price for haphazard practices is severe, and computing professionals must exercise extreme care to ensure that a system is safe. Two requirements must be satisfied: 1) Have some idea of the techniques needed to develop computer systems that are as safe as is practically possible. 2) To be able to arrive at a reasonably objective assessment of exactly what that level of safety is.

Introduction How will an accidents happen? Most accident are caused by a combination of: organizational managerial technical, and sociological or political factors. Preventing an accident requires paying attention to all the root causes.

“Safety-critical” and other definitions Sometimes seen as systems with a component of real-time control that can have a direct life-threatening impact. “Managing Murphy’s Law” Examples: Aircraft industry Medical treatment system Nuclear poser plants Missile systems What do we need? A through risk assessment of a system Risk, hazard, and reliability.

How and Why failures occur? Difficulty in assessing and predicting failures Three independent disk drives resulted in the failure of the Toronto Stock Exchange. Is a computer model an abstraction of the real world ? What is the danger of such an engineering view? Risk Analysis The responsibility of managers is to take the results of risk analysis seriously and act on them by ensuring that the system is managed conscientiously. By Selecting: Proper people Training them, Not overworking them

Evaluating Software Computers now have safety-critical functions in: both military and civilian aircraft nuclear plants medical devices It is incumbent upon those responsible for programming, purchasing, installing, and licensing these systems to determine whether or not the software is ready to be used. What standard must a software product satisfy if it is to be used in safety-critical applications? What document should be required? How much testing is required? How should the software be structured?

A case study of safety-critical failures The Therac-25 accident, failure in a radiation-therapy system. Errors in special timing-dependent sequences of events in the user interface. Software error? An appropriate software/hardware interlock could have prevented the events. What was the role of Medical Doctors in this accident? Should we use software in a safety-critical system? How the standard was used in the system? Was the redundancy check of the safety sufficient? Model verification and validation The numerical model of a real system must go through an extensive verification and validation process. Summary Risk assessment is very difficult to do Software models of real world systems can never fully present all cases.