1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.

Slides:

Advertisements

Similar presentations

Session No. 1 Basic Contemporary Safety Concepts

Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 24 Slide 1 Critical Systems Validation 2.

Accident Investigation State of Florida Loss Prevention Program.

Accident Investigations

Learning Objectives  Recognize the need for an investigation  Investigate the scene of the accident  Interview victims & witnesses  Distinguish.

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.

ACCIDENT INVESTIGATION

Preventing Injury. Lesson Objectives Know what it means to be safety conscious Identify causes of accidental injuries Describe how to prevent accidental.

1 – Electrical Hazard Recognition EFCOG Electrical Safety Subgroup May 2015 Electrical Safety Month 2015.

1 Software Testing and Quality Assurance Lecture 37 – Software Quality Assurance.

1 Software Testing and Quality Assurance Lecture 34 – Software Quality Assurance.

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...)

Bureau of Workers’ Comp PA Training for Health & Safety (PATHS)

©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.

Accident Investigation.

Accident Prevention.

DELIVERING SAFE & RELIABLE OPERATION

Process Safety Management

PHILOSOPHY OF ACCIDENT PREVENTION

Objectives  Understand what a Loss Incident is.  Know the real cost of a Loss Incident.  Understand the Causes of a Loss Incident.  Understand what.

Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.

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.

EE551 Real-Time Operating Systems

Software Engineering Dr. K. T. Tsang

1 Software Testing and Quality Assurance Lecture 33 – Software Quality Assurance.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 3 Slide 1 Critical Systems 1.

 CS 5380 Software Engineering Chapter 11 Dependability and Security.

Safety Course Think, Talk, and Walk Safety Be Safety Conscious at Home, Work, Everywhere! Mr. Sherpinsky’s Safety First Presentation Council Rock High.

1 IE 590D Applied Ergonomics Lecture 26 – Ergonomics in Manufacturing & Automation Vincent G. Duffy Associate Prof. School of IE and ABE Thursday April.

27/05/2016 BTEC National Programmes Health, Safety, Risk Assessment and Welfare Unit Number – 20334Z Hazard Control Techniques and Inspections 27/05/2016.

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.

Jacques Vanier ICAO EUR/NAT Regional Officer Almaty, 5 to 9 September 2005 SAFETY MANAGEMENT SYSTEMS RISK VERSUS SAFETY.

Hazard Identification

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 1.

Introduction to Horticulture

Tools Toxicity SafetyGeneralInjuriesVocabulary $ $ $ $ $ $ $ $ $ $

Introduction to a Safe Workplace

2/16/06 Page 1Loui Some Notes from Sommerville Software Engineering 7 CS436 (material for quiz)

Objectives Students will be able to:

Quick Write If you have a grease fire in a pan on the stove how do you put it out?

Safety and Automated Driving Systems Kyle Vogt, Cruise, October 28, 2015.

Accident Analysis.

CS, AUHenrik Bærbak Christensen1 Critical Systems Sommerville 7th Ed Chapter 3.

Facilities Incident Notification. Reporting Requirements All employees are required to report immediately any incidents, accidents, or major equipment.

1 INDUSTRIAL SKILLS. OSHA OCCUPATIONAL SAFETY & HEALTH ADMINISTRATION

Basically... the JHA process is your “Hazard Assessment.”

1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.

Directors, Managers, & Supervisors Safety Responsibilities.

LECTURE 7 AVIATION SAFETY & SECURITY

October 22, 2005 Parvaiz Ahmed Khand An Overview of Software Safety.

Toolbox presentation: Approaches to hazard identification.

Questions HASAWA. 1. State the aims of the Health and Safety at Work Act. To protect employees by the law. To protect employers by the law. To increase.

KEVIN BEDAL LISA CARLIN MATT CARROLL ERIN NICHOLS Product Safety & Failure Analysis.

20 Principles for Managing Behavioural Safety & Process Safety

INCIDENT & ACCIDENT INVESTIGATION – OPERATORS’ PERSPECTIVE

Incident Investigations

Dept. of Nuclear and Quantum Engineering

Safety and Risk.

Air Carrier Continuing Analysis and Surveillance System (CASS)

Copyright 2001 by Allyn and Bacon

Accident Reporting and Investigation. Presented by H&S Officer name

Computer in Safety-Critical Systems

Accident Investigation.

Presentation transcript:

1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance

2 Lecture Objectives Software Safety

3 Safety in systems involving software is becoming important. For example, Computer Aided Dispatch Systems (CAD); Electronic Flight Control Systems (EFCS). Train Protection Systems; Chemical Plant control systems.

4 Software Safety

5 We wish to avoid in engineering and operating our platforms is Accidents. The system that we build must avoid the hazards that lead to accidents.

6 Software Safety Accident – an event of sequence of events leading to harm; that is, death, injury, environmental damage or financial loss. Hazard – a physical situation or state of the platform that can lead to an accident.

7 Software Safety To understand the safely of a system Understand how they can fail. Investigate accidents and accident sequences To understand the sequence of events leading to the accident and to try and determine which subsystem failed. Accidents are usually caused by combination of failures and circumstances.

8 Software Safety Hazards are really accidents “waiting to happen”. They are the pre-conditions for an accident. In hazard identification We are concerned with thinking about the safety of the personal or the platform. Start from known accidents or consider possible accidents and work back to hazards. Brainstorming exercise.

9 Software safety is not just software Reliability Failure is key to understanding software reliability. Failure is deviation from the specified behavior of the system. For safely, it is always a deviation from the intended behavior; and where the deviation can lead to harm or damage.

10 Software safety is not just software Reliability In normal usage of word failure A system may be unreliable but still safe; It may be completely reliable but totally unsafe. What failure of the system lead to an unsafe system?

11 Safety Engineering Approach Hazard analysis technique to determine the safety aspects of the system Early in the development process, then Monitoring safety throughout the product development process; and Ensuring that there is enough evidence to build a safety case at the end of the product development process.

12 Key points Accidents and Hazards Accidents are usually caused by combination of failures and circumstances. Hazards are really accidents “waiting to happen”. Safety Engineering Approach