CPSC 871 John D. McGregor Module 2 Session 2 Fault Analysis.

Slides:



Advertisements
Similar presentations
Robots Leslie B.. What is a robot? A robot is a machine that is capable of doing many kinds of actions.
Advertisements

On the Relation between Design Contracts and Errors Karlstad University Computer Science On the Relation Between Design Contracts and Errors A Software.
CSE 322: Software Reliability Engineering Topics covered: Dependability concepts Dependability models.
Page 1 Copyright © Alexander Allister Shvartsman CSE 6510 (461) Fall 2010 Selected Notes on Fault-Tolerance (12) Alexander A. Shvartsman Computer.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 1 Requirements Analysis Document Template 1.Introduction.
CPSC 872 John D. McGregor Session 12 Software Design, cont’d.
CPSC 372 John D. McGregor Module 0 Session 1 Introduction.
Software Reliability Growth. Three Questions Frequently Asked Just Prior to Release 1.Is this version of software ready for release (however “ready” is.
MagicInfo Pro Server Software All control, content, and scheduling is performed within the MagicInfo Pro Server software previously installed. Before.
Chapter 1: Introduction to Software Testing Software Testing
CPSC 372 John D. McGregor Module 3 Session 2 Architecture Analysis/Design.
CPSC 871 John D. McGregor Module 0 Session 1 Introduction.
Software Metrics - Data Collection What is good data? Are they correct? Are they accurate? Are they appropriately precise? Are they consist? Are they associated.
Installing and Using Active Directory Written by Marc Zacharko.
CPSC 875 John D. McGregor C16 - DSMs. Partitioning _jetta_horn_recall/index.htm?hpt=T2
Introduction to Dependability. Overview Dependability: "the trustworthiness of a computing system which allows reliance to be justifiably placed on the.
Software Requirements Lecture # 3. 2 Kinds of Software Requirements Functional requirements Non-functional requirements Domain requirements Inverse requirements.
CPSC 871 John D. McGregor Module 6 Session 3 System of Systems.
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
Ch. 1.  High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle.
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
CPSC 871 John D. McGregor Module 2 Session 4 CMMI & assignment.
SENG521 (Fall SENG 521 Software Reliability & Testing Fault Tolerant Software Systems: Techniques (Part 4b) Department of Electrical.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
1 ITGD 2202 Supervision:- Assistant Professor Dr. Sana’a Wafa Al-Sayegh Dr. Sana’a Wafa Al-SayeghStudent: Anwaar Ahmed Abu-AlQumboz.
CPSC 871 John D. McGregor Module 7 Session 1 More UML.
CPSC 871 John D. McGregor Module 4 Session 1 Architecture Analysis/Design.
CPSC 371 John D. McGregor Session 32 This is it..
Quality Assurance.
QA and Testing. QA Activity Processes monitoring Standards compliance monitoring Software testing Infrastructure testing Documentation testing Usability.
Defect resolution  Defect logging  Defect tracking  Consistent defect interpretation and tracking  Timely defect reporting.
CPSC 372 John D. McGregor Module 2 Session 5 Android App.
Module 1.5 Problems with I/O devices and storage Theme: Finding solutions.
Ensure that the right functions are performed Ensure that the these functions are performed right and are reliable.
Defect Classes and the defect repository
CPSC 873 John D. McGregor Session 9 Testing Vocabulary.
Testing OO software. State Based Testing State machine: implementation-independent specification (model) of the dynamic behaviour of the system State:
CPSC 873 John D. McGregor Session 15 Test suites and tools.
CPSC 871 John D. McGregor Module 8 Session 1 Testing.
GCSE ICT By the end of this session, you will be able to:  Understand concept of a Windows operating system and have a basic understanding of GUI.
CPSC 871 John D. McGregor Module 8 Session 3 Assignment.
CPSC 371 John D. McGregor Session 10 Requirements analysis methods.
CPSC 372 John D. McGregor Module 1 Session 2 Process Measurement.
CPSC 873 John D. McGregor Session 3 Requirements V & V.
CPSC 873 John D. McGregor S20 More measurement. Utility is a term used by economists to describe the measurement of "useful-ness" that a consumer obtains.
Chapter Nine NetWare-Based Networking. Objectives Identify the advantages of using the NetWare network operating system Describe NetWare’s server hardware.
CPSC 372 John D. McGregor Module 8 Session 1 Testing.
John D. McGregor Session 9 Testing Vocabulary
Testing More In CS430.
John D. McGregor Session 5 Domain Analysis, cont’d
John D. McGregor Session 3 Requirements V & V
Fault Tolerance In Operating System
BASICS OF SOFTWARE TESTING Chapter 1. Topics to be covered 1. Humans and errors, 2. Testing and Debugging, 3. Software Quality- Correctness Reliability.
John D. McGregor Session 9 Testing Vocabulary
John D. McGregor Session 9 Testing Vocabulary
Design for Quality Design for Quality and Safety Design Improvement
Fault Injection: A Method for Validating Fault-tolerant System
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Software Requirements
Mattan Erez The University of Texas at Austin July 2015
Software Requirements Engineering
Alternate Game Play in the Classroom
Which way does the robot have to turn to get to the charger?
John D. McGregor Module 1 Session 3 Assignment
John D. McGregor M11S4 Value of designs and assignment
Software Engineering for Safety: a Roadmap
Overview Dependability: "[..] the trustworthiness of a computing system which allows reliance to be justifiably placed on the service it delivers [..]"
Human and Computer Interaction (H.C.I.) &Communication Skills
John D. McGregor Session 10 Misc.
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Presentation transcript:

CPSC 871 John D. McGregor Module 2 Session 2 Fault Analysis

Fault/Failure A fault is a defect in a workproduct A failure is a discrepancy from the expected behavior at runtime. Explicitly identifying what can go wrong and designing for it is an important part of safety design.

Fault Tree Analysis

State machine for FHA

Fault tolerant design We will expand on this later but in the context of understanding the problem: – The software product should be able to recognize failures – The software product should be able to either restart itself or correct or notify user of the failure in a graceful manner (no blue screen of death) We will build as carefully as possible but fault tolerance allows the software to continue some level of operation in the presence of failures.

Fault tolerance and domains What is an acceptable fault tolerant action varies from one domain to another. In aircraft, simply stopping the system is not an option while in robotic surgery stopping may be the safest option, not moving forward or backward.