Software Safety Chloe Sanderson CNS07U. Overview What is software safety? What are its causes? How can it be overcome? Example of analysis technique Example.

Slides:



Advertisements
Similar presentations
Integra Consult A/S Safety Assessment. Integra Consult A/S SAFETY ASSESSMENT Objective Objective –Demonstrate that an acceptable level of safety will.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 24 Slide 1 Critical Systems Validation 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development.
Protecting patients- now and in the future Linda Matthew Senior Pharmacist National Patient Safety Agency.
Why do accidents happen?  Accidents happen for one or both of the following Unsafe acts & Unsafe conditions.
Chapter 21: Product Issues Design of Biomedical Devices and Systems By: Paul H. King Richard C. Fries.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
Presentation R. R. Lutz. Analyzing Software Requirements Errors in Safety-Critical Embedded Systems. In Proceedings of the IEEE International Symposium.
Software Engineering for Safety : A Roadmap Presentation by: Manu D Vij CS 599 Software Engineering for Embedded Systems.
1 Software Testing and Quality Assurance Lecture 39 – 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...)
Introduction ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
Risk Management Infection prevention and control (IP&C) professionals have, amongst other things, duty to identify unsafe and hazardous IP&C practices.
Risk Management. What is risk? You have some expected outcome –Of some event in the future Risk is the deviation of the actual future outcome from the.
Testing safety-critical software systems
Hazard Identification and Control Courtesy of the Public Education and Conferences Section Oregon Occupational Safety and Health Division (OR-OSHA)
Accident Prevention.
Risk Management at a Glance. Terms Hazard Hazard Risk Risk Probability Probability Severity Severity Estimating Estimating Exposure Exposure Risk Assessment.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Environmental hazards What are the procedures in your workplace for managing environmental hazards? What is a hazard? How can hazards be managed?
SEDS Research GroupSchool of EECS, Washington State University Annual Reliability & Maintainability Symposium January 30, 2002 Frederick T. Sheldon and.
1 Chapter 3 Critical Systems (cont.). 2 Safety Safety is a property of a system that reflects the system’s ability to operate, normally or abnormally,
OHS Risk Management - Overview Risk management is a system that allows workplaces to identify OHS issues and to methodically control them by the best means.
Hazard Identification
EE551 Real-Time Operating Systems
FAILURES AND CAUSES NASA MISSIONS SYSM Advance Requirements Engineering Dr. Chung Muhammad Ayaz Shaikh 05/19/2012.
Topic 5 Understanding and learning from error. LEARNING OBJECTIVE Understand the nature of error and how health care can learn from error to improve patient.
WHAT IS SYSTEM SAFETY? The field of safety analysis in which systems are evaluated using a number of different techniques to improve safety. There are.
Safety-Critical Systems 6 Certification
CSE 403 Lecture 14 Safety and Security Requirements.
Preventing Surgical Complications Prevent Harm from High Alert Medication- Anticoagulants in Primary Care Insert Date here Presenter:
1 Chapter 3 Critical Systems. 2 Objectives To explain what is meant by a critical system where system failure can have severe human or economic consequence.
Intent Specification Intent Specification is used in SpecTRM
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Risk management.
Safety Critical Systems ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University.
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Software Testing and Quality Assurance Software Quality Assurance 1.
Safety on Call ACCIDENT PREVENTION. Safety on Call WHY DO ACCIDENTS HAPPEN? Accidents happen for one or both of the following: – Unsafe acts – Unsafe.
1 Reducing the Software Impact to System Safety Paul Mayo – SafeEng Limited.
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.
A guide to... Safe Systems of Work.
Safe Systems of Work. Legislation w HSWA Section 2 (2) (a): Provide and maintain plant and systems of work that are, so far as is reasonably practicable,
Making Decisions. The act of making a choice or coming to a solution that can affect: – Your health and well-being – Someone else’s health or well-being.
1 INDUSTRIAL SKILLS. OSHA OCCUPATIONAL SAFETY & HEALTH ADMINISTRATION
GCSE Geography Data Collection. Year 10 The Appleton School.
Development, Validation, Implementation and Enhancement for a Voluntary Protection Programs Center of Excellence (VPP CX) Capability for the Department.
Department of Defense Voluntary Protection Programs Center of Excellence Development, Validation, Implementation and Enhancement for a Voluntary Protection.
EFFECTIVE ACCIDENT/INCIDENT INVESTIGATION 15 FEBRUARY 2013 PHILIPPINE ASSOCIATION OF SAFETY ENGINEERS -QATAR- -QATAR- COMMITTEE ON SAFETY EDUCATION 2013.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
Department of Defense Voluntary Protection Programs Center of Excellence Development, Validation, Implementation and Enhancement for a Voluntary Protection.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
October 22, 2005 Parvaiz Ahmed Khand An Overview of Software Safety.
KEVIN BEDAL LISA CARLIN MATT CARROLL ERIN NICHOLS Product Safety & Failure Analysis.
BPM/NPC Individual-Managing Your Risk Training
Safety and Risk.
Safety Programs for Construction
BPM/NPC Individual-Managing Your Risk Training
68.3 million errors (28% of total) cause moderate or serious harm
Reporting Incidents and Hazards Accident Prevention
ايمني بيمار PATIENT SAFETY حق بيمار و مسئوليت ما
Software Engineering for Safety: a Roadmap
Presentation transcript:

Software Safety Chloe Sanderson CNS07U

Overview What is software safety? What are its causes? How can it be overcome? Example of analysis technique Example of safety standards

What is Software Safety? Software Safety is concerned with avoiding hazardous situations and alerting the correct systems if the situation becomes unsafe People damage Environment damage

Safety Critical Software Classes Primary Can cause direct harm to a person or the environment For example, by crashing into something Secondary Can only cause harm indirectly For example, a system which dispenses incorrect drugs to patients

Where do hazards come from? Ambiguous definition “Discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system” Lutz 1996 Reusing software modules Famous MCO/MGS example Modules interaction with rest of system Human monitoring error

Hazard solutions Remove hazard completely Minimise hazard probability to acceptable risk Reduce hazards negative impact Contingency plan

Software Safety Techniques Formal requirement definition Fault tree analysis

Software Safety Techniques Back up system Component 1Component 2 Both work 98.01% chance First works only 0.99% chance Outcome Both fail 0.01% chance Second works only 0.99% chance Component Work 99% Fail 1% Work 99% Fail 1% Work 99% Fail 1%

STAMP hazard analysis 1.Identify the system hazards 2.Identify safety related requirements and constraints 3.Define the basic system control structure 4.Identify inadequate control actions that lead to a hazard 5.Determine what constraints could be violated and eliminate, prevent or control them through the system design

Safety Standards Guidelines for development and certification of safety ISO examples: Health Informatics – Classification of safety risks from health software Safety of machinery – Safety related parts of control systems Space systems – Safety requirements for ground support equipment for use at launch, landing or retrieval sites

References 1. Sommerville, Ian. Software Engineering. s.l. : Pearson Education. 2. Leveson, Nancy G and Weiss, Kathryn Anne. Making Embedded Software Reuse Practical and Safe. [Online] 3. Ericson, Clifton A. Software Safety in a Nutshell. [Online] 4. Leveson, Nancy. Completeness in Formal Specification Language Design for Process- Control Systems. [Online] 5. Leveson, Nancy and Dulac, Nicolas. An Approach to Design for Safety in Complex Systems. [Online] 6. ISO. [Online]