Software availability –the probability that a program is operating according to requirements at a given point in time. Availability = (MTTF/MTBF) x 100.

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

PROJECT RISK MANAGEMENT
“Those who are not dissatisfied will never make any progress
Module 3 UNIT I " Copyright 2002, Information Spectrum, Inc. All Rights Reserved." INTRODUCTION TO RCM RCM TERMINOLOGY AND CONCEPTS.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
Science 8: Unit D – Mechanical Systems Topic 6: Combining Systems.
1 Software Testing and Quality Assurance Lecture 36 – Software Quality Assurance.
Overview Lesson 10,11 - Software Quality Assurance
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
SWE Introduction to Software Engineering
Title slide PIPELINE QRA SEMINAR. PIPELINE RISK ASSESSMENT INTRODUCTION TO RISK IDENTIFICATION 2.
Tony Gould Quality Risk Management. 2 | PQ Workshop, Abu Dhabi | October 2010 Introduction Risk management is not new – we do it informally all the time.
Hazards Analysis & Risks Assessment By Sebastien A. Daleyden Vincent M. Goussen.
Chapter 16 Software Quality Assurance
Software Project Management
Chapter 16 Software Quality Assurance
Software Project Management
Software Project Management
Chapter 25 Risk Management
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
ERT 312 SAFETY & LOSS PREVENTION IN BIOPROCESS RISK ASSESSMENT Prepared by: Miss Hairul Nazirah Abdul Halim.
ERT 322 SAFETY AND LOSS PREVENTION RISK ASSESSMENT
Root Cause Tutorial Page 1 More on Hazard Identification Techniques 1.Identify potential hazards that could threaten the safety of your employees,
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
Quality Control and Patient Risk Curtis A. Parvin, Ph. D
Lecture: Reliability & FMECA Lecturer: Dr. Dave Olwell Dr. Cliff Whitcomb, CSEP System Suitability.
Software Quality Assurance
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Objectives Students will be able to:
1 Software Quality Assurance. 2 Quality Concepts - 1 Variation control is the heart of quality control Software engineers strive to control the – process.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
WHAT IF ANALYSIS USED TO IDENTIFY HAZARDS HAZARDOUS EVENTS
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
Software reviews Cost impact of software defects Defect amplification model Review metrics and their use – Preparation effort (E p ), assessment effort.
Software Engineering Lecture 8: Quality Assurance.
Failure Modes and Effects Analysis (FMEA)
CS223: Software Engineering Lecture 36: Software Quality.
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
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.
Risk Mitigation Submitted By, S. Anitha Devi, M.E-CSE.
UNIT - 8 QUALITY MANAGEMENT snistforum.com. Quality Management Quality management (often called software quality assurance) is an umbrella activity that.
Software Quality Assurance
Critical systems design
Software Quality Assurance
Software Project Management
Software Engineering Lecture #41
Software Engineering B.Tech Ii csE Sem-II
Software Reliability Definition: The probability of failure-free operation of the software for a specified period of time in a specified environment.
Safety and Risk.
Chapter 21 Software Quality Assurance
Chapter 21 Software Quality Assurance
Software Engineering Lecture #39
SE Tasks for a Concept Development Project
Assessing Risk Impact Factors affecting the consequences Nature Scope
Software Engineering Lecture #25
Software Engineering Lecture # 17
Software Engineering Lecture #26
Quality Measurable characteristic Cyclomatic complexity Cohesion
CREOG Patient Safety Series: Safety in Women’s Healthcare
Unit I Module 3 - RCM Terminology and Concepts
Software Engineering Lecture #29
Software Engineering: A Practitioner’s Approach, 6/e Chapter 26 Quality Management copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For.
Hazards Analysis & Risks Assessment
Definitions Cumulative time to failure (T): Mean life:
Presentation transcript:

Software availability –the probability that a program is operating according to requirements at a given point in time. Availability = (MTTF/MTBF) x 100

Software Engineering II Lecture 31 Fakhar Lodhi

Software Safety Software Safety is a software SQA activity that focuses on identification of potential hazards that may affect software negatively and cause an entire system to fail. Modeling and analysis process is conducted as part of software safety. Hazards are identified and categorized by criticality and risk.

Recap

Example Hazards associated with a computer-based cruise control for an automobile: 1.Causes uncontrolled acceleration that cannot be stopped 2.Does not respond to depression of brake pedal 3.Does not engage when switch is activated 4.Slowly loses or gains speed

Once system-level hazards are identified, analysis techniques are used to assign severity, and probability of occurrence – similar to risk analysis To be effective, software must be analyzed in the context of the entire system Analysis techniques such as fault tree analysis can be used to predict the chain of events that can cause hazards and the probability that each of these events will occur to create the chain. Once hazards are identified and analyzed, safety-related requirements can be specified for the software. –For example, system can contain undesirable events and desired system responses to these events can be specified

Reliability versus Safety Closely related Software reliability uses statistical techniques to determine the likelihood that a software failure will occur Occurrence of a software failure does not necessarily result in a hazard or mishap Software safety examines the ways in which failures result in conditions that can lead to a mishap.

Poka-Yoke (Mistake-Proofing) Poka-yoke – developed as a QA technique by Mr. Shingo at Toyota in 1960’s. Poka-yoke devices – mechanisms that lead to: –Prevention of potential quality problems before they occur, or –The rapid detection of quality problems if they are introduced. Examples: –Light is on if the car door is not properly closed –Warning beep if the engine is turned-off when lights are on

Characteristic of a Poka-yoke device It is simple and cheap It is part of the process It is located near the process task where the mistake occurs