“Faultless to a fault.” - Robert Browning Albert Hsu

Slides:



Advertisements
Similar presentations
1 Fault-Tolerant Computing Systems #6 Network Reliability Pattara Leelaprute Computer Engineering Department Kasetsart University
Advertisements

Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Software Reliability Engineering
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
Chapter 14 Maintaining Information Systems Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
1 Static Testing: defect prevention SIM objectives Able to list various type of structured group examinations (manual checking) Able to statically.
Designing the system Conceptual design and technical design
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Chapter 12 File Management Systems
Testing an individual module
SENG521 (Fall SENG 521 Software Reliability & Testing Defining Necessary Reliability (Part 3b) Department of Electrical & Computer.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
Motivation  Synthesis-based methodology for quick design space exploration enabled by automatic synthesis followed by analysis  Automatic synthesis:
Unit Testing CS 414 – Software Engineering I Don Bagert Rose-Hulman Institute of Technology January 16, 2003.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 5 Data Flow Testing
Chapter 14 Maintaining Information Systems
1 Software Testing Techniques CIS 375 Bruce R. Maxim UM-Dearborn.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
A User-Oriented Software Reliability Model Per Trygve Myhrer 20 februar Roger C. Cheung.
Computer Programming and Basic Software Engineering 4. Basic Software Engineering 1 Writing a Good Program 4. Basic Software Engineering.
System/Software Testing
March 13, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #15 Tuesday, March 13, 2001.
Maintaining Information Systems Modern Systems Analysis and Design.
CS 501: Software Engineering Fall 1999 Lecture 16 Verification and Validation.
Microsoft Access Lecture -13- By lec. (Eng.) Hind Basil University of Technology Department of Materials Engineering 1.
Verification and Validation Overview References: Shach, Object Oriented and Classical Software Engineering Pressman, Software Engineering: a Practitioner’s.
Coupling and Cohesion Pfleeger, S., Software Engineering Theory and Practice. Prentice Hall, 2001.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis.
1 Software Testing and Quality Assurance Lecture 33 – Software Quality Assurance.
Software Testing and Maintenance Lecture 4 Graph Coverage for Design Element Paul Ammann & Jeff Offutt Instructor: Hossein Momeni Mazandaran.
1 Software testing. 2 Testing Objectives Testing is a process of executing a program with the intent of finding an error. A good test case is in that.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Styles.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
Software Testing Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
CCSB223/SAD/CHAPTER131 Chapter 13 Designing the System Internals.
Improving Design #1 Reduce complexity - narrow-down the project scope - optimize underlying process - eliminate unneeded parts # 2 Find and eliminate redundancies.
© 2010 Pearson Prentice Hall. All rights reserved. CHAPTER 15 Graph Theory.
ISBN Prentice-Hall, 2006 Chapter 8 Testing the Programs Copyright 2006 Pearson/Prentice Hall. All rights reserved.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
SENG521 (Fall SENG 521 Software Reliability & Testing Fault Tolerant Software Systems: Techniques (Part 4a) Department of Electrical.
Coupling and Cohesion Pfleeger, S., Software Engineering Theory and Practice. Prentice Hall, 2001.
Network Topology Computer network topology is the way various components of a network (like nodes, links, peripherals, etc) are arranged. Network topologies.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall. Section 5.1 Polynomial Functions and Models.
Reaching for k Nines Miroslaw Malek Humboldt University Berlin, Germany
Chapter 14 Maintaining Information Systems
Overview Theory of Program Testing Goodenough and Gerhart’s Theory
Coupling and Cohesion 1.
Managing the System PPT SOURCE : Shari L. Pfleeger Joann M. Atlee.
Graph Coverage for Design Elements CS 4501 / 6501 Software Testing
Copyright © 2008 Pearson Prentice Hall Inc.
Copyright © 2008 Pearson Prentice Hall Inc.
Software Engineering Lecture #45
Copyright © 2008 Pearson Prentice Hall Inc.
Graph Coverage for Design Elements CS 4501 / 6501 Software Testing
Copyright © 2008 Pearson Prentice Hall Inc.
 What is Topology  Categories of Topology  Definition, structure, advantage and disadvantage of all of the following topologies: o Mesh o Bus o Ring.
Software Testing “If you can’t test it, you can’t design it”
CAP4800/5805 Systems Simulation
Software Maintenance Part1 Introduction. Outlines What Is Software Maintenance Purposes of Maintenance Why We Need It Maintenance Difficilties Some Tips.
Copyright © 2008 Pearson Prentice Hall Inc.
Copyright © 2008 Pearson Prentice Hall Inc.
Software Testing and QA Theory and Practice (Chapter 5: Data Flow Testing) © Naik & Tripathy 1 Software Testing and Quality Assurance Theory and Practice.
Presentation transcript:

“Faultless to a fault.” - Robert Browning Albert Hsu Fault Tree Analysis “Faultless to a fault.” - Robert Browning Albert Hsu

Introduction Fault identification, correction and tolerance to improve design Fault Tree Analysis “A method to decompose it and look for situation that might lead to failure” (Software Engineering) Displayed the logical path from effect to cause Fault Tree Analysis, Fall 2006

The Fault Tree Begin Fault Analysis by identifying possible failures in design operation or maintenance Next build a graph whose nodes are failures Single contents System function Entire system Edge = relationship among nodes by logical descriptor (AND,OR) Fault Tree Analysis, Fall 2006

The Fault Tree Figure 5.19 Portion of power plant control system Fault Tree Analysis, Fall 2006

Cut-set Tree From Fault tree to cut-set tree To find single points of failure in complex tree Figure 5.20 Cut-set tree generated form the fault tree Fault Tree Analysis, Fall 2006

Fixing the Failure Remove it Add components or conditions to prevent the input condition that cause the fault to be executed Add components that will recover from the damage the failure will cause Fault Tree Analysis, Fall 2006

Some faults… Time-consuming in constructing the graphs Many systems involve many dependencies Difficult to detect inconsistencies Difficult to focus only on the most critical parts of the design on high coupling systems Not always easy to spot Fault Tree Analysis, Fall 2006

Reference Atlee, Joanne, Software Engineering Theory and Practice, Pearson Prentice Hall, New Jersey, ©2006, pg264-266 Fault Tree Analysis, Fall 2006