SAS 03/ GSFC/SATC-ERAU-DoC Fault Tree Analysis Application for Safety and Reliability Massood Towhidnejad Embry-Riddle University Dolores Wallace & Al.

Slides:



Advertisements
Similar presentations
Unit 2. Software Lifecycle
Advertisements

Software Project Management
Alternate Software Development Methodologies
Ask Pete Acquired Software Knowledge Project - Estimation- Tool - Effort Presented to the NASA OSMA SAS ‘01 NASA IV&V Facility September 5-7, 2001 Tim.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Risk Management Chapter 7.
Reliability Risk Assessment
SE 450 Software Processes & Product Metrics Reliability: An Introduction.
Telecommunications Project Management Quality Management PERT.
RIT Software Engineering
SE 450 Software Processes & Product Metrics 1 Defect Removal.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 2 Introduction to Database Development.
Introduction to Database Development. 2-2 Outline  Context for database development  Goals of database development  Phases of database development.
Karolina Muszyńska Based on
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
13.1 © 2007 by Prentice Hall 13 Chapter Building Systems.
Hazards Analysis & Risks Assessment By Sebastien A. Daleyden Vincent M. Goussen.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Testing in SDLC. COURSE CONTENT - Summary Part 1 – Life Cycle / Processes / SDLC Part 2 – LC Management in Turkcell.
Introduction to Computer Technology
Chapter 3 Software Processes.
Chapter 20: Defect Classification and Analysis  General Types of Defect Analyses.  ODC: Orthogonal Defect Classification.  Analysis of ODC Data.
1 NASA OSMA SAS02 Software Reliability Modeling: Traditional and Non-Parametric Dolores R. Wallace Victor Laing SRS Information Services Software Assurance.
S/W Project Management
IV&V Facility 1 Software Reliability Corroboration Bojan Cukic, Erdogan Gunel, Harshinder Singh, Lan Guo West Virginia University Carol Smidts University.
1SAS 03/ GSFC/SATC- NSWC-DD System and Software Reliability Dolores R. Wallace SRS Technologies Software Assurance Technology Center
Information Systems Analysis and Design
Architecture Business Cycle
Chapter 16 Designing Effective Output. E – 2 Before H000 Produce Hardware Investment Report HI000 Produce Hardware Investment Lines H100 Read Hardware.
Views from different perspectives
Introduction to Software Testing Chapter 9.1 Challenges in Testing Software – Testing for Emergent Properties: Safety and Security Paul Ammann & Jeff Offutt.
Software Development Software Testing. Testing Definitions There are many tests going under various names. The following is a general list to get a feel.
National Aeronautics and Space Administration From Determinism to “Probabilism” Changing our mindsets, or why PTC isn’t an easy sell - yet.
West Virginia University Towards Practical Software Reliability Assessment for IV&V Projects B. Cukic, E. Gunel, H. Singh, V. Cortellessa Department of.
1 Reliability-Sept2001 Software Reliability Through Hardware Reliability Dolores R. Wallace SRS Information Services Software Assurance Technology Center.
Quality Software Project Management Software Size and Reuse Estimating.
CSCE 522 Secure Software Development Best Practices.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
Chapter 3 Managing Design Processes. 3.1 Introduction Design should be based on: –User observation Analysis of task frequency and sequences –Prototypes,
Project Management Cross lifecycle Activity
ME 4054W: Design Projects RISK MANAGEMENT. 2 Lecture Topics What is risk? Types of risk Risk assessment and management techniques.
1 Technology Infusion of the Software Developer’s Assistant (SDA) into the MOD Software Development Process NASA/JSC/MOD/Brian O’Hagan 2008 Software Assurance.
1 NASA OSMA SAS02 Software Fault Tree Analysis Dolores R. Wallace SRS Information Services Software Assurance Technology Center
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
Quality Engineering.
Rational Unified Process (RUP)
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
SAS_05_Contingency_Lutz_Tal1 Contingency Software in Autonomous Systems Robyn Lutz, JPL/Caltech & ISU Doron Tal, USRA at NASA Ames Ann Patterson-Hine,
CI R1 LCO Review Panel Preliminary Report. General Comments –Provide clear definition of the goals of the phase (e.g. inception), the scope, etc. in order.
Slide 1SATC June 2000 Dolores R. Wallace* NASA Goddard Space Flight Center Greenbelt, Maryland for the American Society.
Skills and products portfolio an overview Lorenzo Martinelli – Business Development Contact:
Chapter 1 Assuming the Role of the Systems Analyst.
 Define and recognize risk  Define the contents of a risk management plan  Conduct a risk identification and prioritization process  Define.
SDLC and Related Methodologies
NASA OSMA SAS '02 Software Fault Tree Analysis Dolores R. Wallace SRS Information Services Software Assurance Technology Center
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Product reliability Measuring
Business System Development
CHAPTER 2 Testing Throughout the Software Life Cycle
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
SDLC and Related Methodologies
Failure Mode and Effect Analysis
Project Risk Management
Hazards Analysis & Risks Assessment
Chapter 13 Building Systems.
Presentation transcript:

SAS 03/ GSFC/SATC-ERAU-DoC Fault Tree Analysis Application for Safety and Reliability Massood Towhidnejad Embry-Riddle University Dolores Wallace & Al Gallo NASA Goddard, SATC NASA OSMA SAS '03

SAS 03/ GSFC/SATC-ERAU-DoC 2 Overview FTA Background SFTA and the System Life Cycle SFTA Examples and Diagrams Modeling System Behavior Advantages & Disadvantages of SFTA Impact of Our Research Summary

SAS 03/ GSFC/SATC-ERAU-DoC 3 Fault Tree Analysis General Hazard Analysis technique started in the 1960s Attributes: –Graphical –Top Down –Analytical Qualitative Quantitative Goal: To identify all conditions that put system in a Hazardous States FTA applied to software –Little work has been done to date –SFTA focuses on the code and requirements –Generally applied to “small” projects (<2000 LOC) Observations: –SFTA impractical at code level –Should be applied to Systems at the early stages of life cycle –Need to address the quantitative analysis

SAS 03/ GSFC/SATC-ERAU-DoC 4 SFTA Applied to System Life Cycle Requirements Phase Design Phase. Coding & Test Highlight requirements for Safety concerns & hazards Perform analysis on elements of the design (i.e., Activity, Sequence, and State diagram) Adjust design to eliminate /mitigate hazardous states... Increase reviews and walkthroughs effectiveness Applied only to critical code Adjust design to eliminate /mitigate hazardous states

SAS 03/ GSFC/SATC-ERAU-DoC 5 SFTA Road Map Requirements, Design, Code and Test Fault Tree Use fault tree diagrams as a graphical communication vehicle for developers, testers, designers, managers and customers Verify and Modify Verify/add missing Customer/Domain expert Software Engineer

SAS 03/ GSFC/SATC-ERAU-DoC 6 Fault Tree Example (Activity Diagram) User enter security data System validate Permission System validate entry Security access denied System update profile Display security screen Update priority: Update Address: Update name: User modifies profile Yes Try > 3 Try <=3 Valid Access No Mod. Accept No Reenter Yes Yes No

SAS 03/ GSFC/SATC-ERAU-DoC 7 Fault Tree Example (Activity Diagram)

SAS 03/ GSFC/SATC-ERAU-DoC 8 Fault Tree Example (Sequence Diagram)

SAS 03/ GSFC/SATC-ERAU-DoC 9 Fault Tree Example (Sequence Diagram)

SAS 03/ GSFC/SATC-ERAU-DoC 10 Fault Tree Example (Sequence Diagram)

SAS 03/ GSFC/SATC-ERAU-DoC 11 Fault Tree Example (State Diagram) Source: Smart Draw

SAS 03/ GSFC/SATC-ERAU-DoC 12 Fault Tree Example (State Diagram)

SAS 03/ GSFC/SATC-ERAU-DoC 13 Modeling System Behavior Hardware –Large sample size –Large collections of historic data –Classification of failure types –Degradation (increase failure rate) Software –Limited sample size (usually one) –Limited availability of software failure data –Classification of cause more relevant –Improvement!!!! (decrease failure rate) –Probability values not available, though subject of research efforts Time Reliability H/W S/W t = release 0

SAS 03/ GSFC/SATC-ERAU-DoC 14 Assessing SFTA Advantages: –Easy to learn –Graphical Representation –Communication vehicle with customer –Partial automatic conversion possible (but not desirable) Disadvantages: –Conversion is labor intensive –Automatic conversion is not attractive –Lack of software reliability data –Timing and Loops need special attention –No dedicated SFTA tool

SAS 03/ GSFC/SATC-ERAU-DoC 15 Impact of Our Research Technology Transfer, Infusion, Recognition & Commercialization –SATC collaborating with commercial vendor of commercial FTA tool Enhancing product to accommodate software uniquenesses Planning to build in paradigm features –GSFC Center Director and SMA Director tracking through center’s Tech Transfer Office SFTA activity and a safety-related tool Assisting in the collaboration / licensing

SAS 03/ GSFC/SATC-ERAU-DoC 16 Summary Applied Fault Tree (FT) to Object Oriented design In addition to fault detection, FT can serve as a communication medium with customer Lack of reliability data reduces the quantitative analysis of the FT Seeking alternative sources of data for quantitative analysis Collaborating with a FT tool vendor to develop software fault tree tool