Safety-Critical Systems T 79.232 Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.

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

Operation & Maintenance Engineering Detailed activity description
Medical Device Software Development
Lecture 8: Testing, Verification and Validation
T Safety Critical Systems (4 cr)
Safety-Critical Systems 2 Requirement Engineering T Spring 2006 Ilkka Herttua.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
Safety-Critical Systems 2 T Risk analysis and design for safety Ilkka Herttua.
Safety-Critical Systems 2 Requirement Engineering T Spring 2008 Ilkka Herttua.
Chapter 9 Testing the System, part 2. Testing  Unit testing White (glass) box Code walkthroughs and inspections  Integration testing Bottom-up Top-down.
1 Solution proposal Exam 19. Mai 2000 No help tools allowed.
CSC 402, Fall Requirements Analysis for Special Properties Systems Engineering (def?) –why? increasing complexity –ICBM’s (then TMI, Therac, Challenger...)
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 13 Reliability.
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
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.
Testing safety-critical software systems
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Systems engineering 1.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Safety-Critical Systems 6 Quality Management and Certification T
Software Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
System Testing There are several steps in testing the system: –Function testing –Performance testing –Acceptance testing –Installation testing.
Safety Critical Systems
Quality in Product and Process Design Pertemuan 13-14
 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Quality and Innovation in Product and Process Design.
EE551 Real-Time Operating Systems
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Engineering Dr. K. T. Tsang
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
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.
Software Metrics - Data Collection What is good data? Are they correct? Are they accurate? Are they appropriately precise? Are they consist? Are they associated.
Safety-Critical Systems 6 Certification
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.
Software availability –the probability that a program is operating according to requirements at a given point in time. Availability = (MTTF/MTBF) x 100.
Software Requirements Engineering: What, Why, Who, When, and How
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 3 Slide 1 Critical Systems 1.
Safety Critical Systems ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University.
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Ch. 1.  High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle.
QUALITY RISK MANAGEMENT RASHID MAHMOOD MSc. Analytical Chemistry MS in Total Quality Management Senior Manager Quality Assurance Nabiqasim Group of Industries.
Software Testing and Quality Assurance Software Quality Assurance 1.
Safety Critical Systems 5 Testing T Safety Critical Systems.
Safety-Critical Systems 5 Testing and V&V T
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.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Over View of CENELC Standards for Signalling Applications
ME 4054W: Design Projects RISK MANAGEMENT. 2 Lecture Topics What is risk? Types of risk Risk assessment and management techniques.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
1. 2 An Introduction to Software Engineering 3 What is software? Computer programs and associated documentation such as requirements, design models and.
Safety-Critical Systems 3 T Designing Safety Software Ilkka Herttua.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
About Us! Rob StockhamBA IEng MIEE General Manager Moore Industries-Europe, Inc MemberIEE Honorary Secretary ISA England Institute of Directors DirectorThe.
Introduction to Safety Engineering for Safety-Critical Systems Seo Ryong Koo Dept. of Nuclear and Quantum Engineering KAIST Lab. Seminar.
Functional Safety in industry application
Medical Device Software Development
SEVERITY & PRIORITY RELATIONSHIP
Fault Tolerance & Reliability CDA 5140 Spring 2006
Safety and Risk.
Quality Risk Management
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 13 Reliability.
Definitions Cumulative time to failure (T): Mean life:
A New Concept for Laboratory Quality Management Systems
Presentation transcript:

Safety-Critical Systems T Ilkka Herttua

Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules

Critical Applications Computer based systems used in avionics, chemical process and nuclear power plants. A failure in the system endangers human lives directly or through environment pollution. Large scale economic influence.

Safety Definition Safety: Safety is a property of a system that it will not endanger human life or the environment. Safety-Critical System: A system that is intended to achieve, on its own, the necessary level of safety integrity for the implementation of the required safety functions.

Safety Definition Safety integrity: The likelihood of a safety-related system achieving its required safety features under all the stated conditions within a stated operational environment and within a stated period of time. SIL levels 0 to 4. SIL 4 is the highest safety integrity level.

Developing safety-related systems To achieve safety: - safety requirements - quality management - design / system architecture - defined design/manufacture processes - certification and approval processes - known behaviour of the system in all conditions

V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis Requirements Model Test Scenarios Software Implementation & Unit Test Software Design Requirements Document Systems Analysis & Design Functional / Architechural - Model Specification Document Knowledge Base * * Configuration controlled Knowledge that is increasing in Understanding until Completion of the System: Requirements Documentation Requirements Traceability Model Data/Parameters Test Definition/Vectors

Safety Requirements Requirements are the stakeholders (customer) demands – what they want the system to do. Not defining how !!! Safety requirements are defining what the system must do and must not do in order to ensure safety. Positive and negative functionality.

Where do we go wrong? Many system failures are not failures to understand R ; they are mistakes in D –A NYC subway train crashed into the rear end of another train on 5th June The motorman ran through a red light. The safety system did apply the emergency brakes. However the...signal spacing was set in 1918, when trains were shorter, lighter and slower, and the emergency brake system could not stop the train in time. Or maybe D is deliberately subverted –“If you present a valid card and type the right PIN, you are entitled to withdraw £200” Are you sure?

Specification Supplier instructions how to build the system. Derived from the required functionality – requirements.

Verification and validation Verification is the process of determining that a system or module meets its specification. Validation is the process of determining that a system is appropriate for its purpose.

Fault, error and failure A fault is defect within the system. Random faults – hardware components, systematic faults – software/hardware design and manufacture processes. An error is a deviation from the required operation of the system or subsystem. A system failure occurs when the system fails to perform its required function. (Significant, major and minor)

Fault management Fault management techniques: Fault avoidance – in entire system design phase Fault removal - before system enters service Fault detection – during service to minimising effects Fault tolerance – operate correctly in the presence of faults

RAM Reliability is the probability of a component or system functioning correctly over a given period of time under a given set of operating conditions. (MTBF mean time between failure.) The availability of a system is the probability that the system will be functioning correctly at any given time. Maintainability: Maintenance is the action taken to retain a system in or return a system to its designed operating condition. (MTTR mean time to repair.)

Hazard Analysis A Hazard is situation in which there is actual or potential danger to people or to environment. Analytical techniques: - Failure modes and effects analysis (FMEA) - Failure modes, effects and criticality analysis (FMECA) - Hazard and operability studies (HAZOP) - Event tree analysis (ETA) - Fault tree analysis (FTA)

Home assignments 1.12 (primary, functional and indirect safety) 2.4 (unavailability) before 28. January to