CSE 322: Software Reliability Engineering Topics covered: Architecture-based reliability analysis.

Slides:



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

Master/Slave Architecture Pattern Source: Pattern-Oriented Software Architecture, Vol. 1, Buschmann, et al.
CS 795 – Spring  “Software Systems are increasingly Situated in dynamic, mission critical settings ◦ Operational profile is dynamic, and depends.
Probability and Statistics with Reliability, Queuing and Computer Science Applications: Chapter 8 on Continuous-Time Markov Chains Kishor Trivedi.
Reliable System Design 2011 by: Amir M. Rahmani
Lecture 13 – Continuous-Time Markov Chains
1 Software Reliability Growth Models Incorporating Fault Dependency with Various Debugging Time Lags Chin-Yu Huang, Chu-Ti Lin, Sy-Yen Kuo, Michael R.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Conditional probability Independent events Bayes rule Bernoulli trials (Sec )
CSE 322: Software Reliability Engineering Topics covered: Architecture-based reliability analysis.
CSE 300: Software Reliability Engineering Topics covered: Project overview.
CSE 3504: Probabilistic Analysis of Computer Systems Topics covered: Continuous time Markov chains (Sec )
A. BobbioBertinoro, March 10-14, Dependability Theory and Methods 5. Markov Models Andrea Bobbio Dipartimento di Informatica Università del Piemonte.
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.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Independent events Bayes rule Bernoulli trials (Sec )
CSE 300: Software Reliability Engineering Topics covered: Software Reliability Models.
CSE 322: Software Reliability Engineering Topics covered: Software Reliability Models.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Simple queuing models (Sec )
CSE 322: Software Reliability Engineering Topics covered: Software Reliability Models.
CSE 322: Software Reliability Engineering Topics covered: Dependability concepts Dependability models.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Pure death process Availability analysis (Sec , 8.4.1)
Software Testing and Quality Assurance
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Multiple random variables Transform methods (Sec , 4.5.7)
CSE 300: Software Reliability Engineering Topics covered: Software architecture styles.
CSE 322: Software Reliability Engineering Topics covered: Software Reliability Models.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Statistical inference.
CSE 322: Software Reliability Engineering Topics covered: Software reliability models with explicit fault removal.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
CSE 300: Software Reliability Engineering Topics covered: Software metrics and software reliability.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Exponential distribution Reliability and failure rate (Sec )
CSE 300: Software Reliability Engineering Topics covered: Software metrics and software reliability Software complexity and software quality.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Combinatorial problems Conditional probability Independent events (Sec , )
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Analysis of software reliability and performance.
CSE 300: Software Reliability Engineering Topics covered: Software Reliability Models.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Discrete time Markov chains (Sec )
CSE 3504: Probabilistic Analysis of Computer Systems Topics covered: Discrete time Markov chains (Sec )
EEE499 Real Time Systems Software Reliability (Part II)
Computer Science, Software Engineering & Robotics Workshop, FGCU, April 27-28, 2012 Bayesian Belief Networks in Anomaly Detection, Fault Diagnosis & Failure.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Analysis of software reliability and performance.
CSE 221: Probabilistic Analysis of Computer Systems Topics covered: Statistical inference.
Overview Software Quality Assurance Reliability and Availability
Models for Software Reliability N. El Kadri SEG3202.
4. Dynamic reliability models Objectives Be able to find reliability of series, parallel, stand-by and shared load parallel systems, when the reliabilities.
Chapter 22. Software Reliability Engineering (SRE)
A User-Oriented Software Reliability Model Per Trygve Myhrer 20 februar Roger C. Cheung.
WIR FORSCHEN FÜR SIE The Palladio Component Model (PCM) for Performance and Reliability Prediction of Component-based Software Architectures Franz Brosch.
ECE 355: Software Engineering
Slide 6.1 CHAPTER 6 TESTING. Slide 6.2 Overview l Quality issues l Nonexecution-based testing l Execution-based testing l What should be tested? l Testing.
Validation Metrics. Metrics are Needed to Answer the Following Questions How much time is required to find bugs, fix them, and verify that they are fixed?
Probability and Statistics with Reliability, Queuing and Computer Science Applications: Chapter 7 on Discrete Time Markov Chains Kishor S. Trivedi Visiting.
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Software Reliability SEG3202 N. El Kadri.
IV&V Facility PI: Katerina Goseva – Popstojanova Students: Sunil Kamavaram & Olaolu Adekunle Lane Department of Computer Science and Electrical Engineering.
Ch. 1.  High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle.
Software Testing and Quality Assurance Software Quality Assurance 1.
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.
Increased Reliability Through Failure Predictive Scheduling with Temperature Sensor Feedback Wesley Emeneker CSE 534 Dr. Sandeep Gupta.
Copyright , Dennis J. Frailey CSE Software Measurement and Quality Engineering CSE8314 M00 - Version 7.09 SMU CSE 8314 Software Measurement.
Reliability Engineering
Slide (Ch.22) 1 Tian: Software Quality Engineering Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement Jeff Tian Chapter.
More on Exponential Distribution, Hypo exponential distribution
Conditional probability
Software Defects Cmpe 550 Fall 2005
Discrete-time Markov chain (DTMC) State space distribution
Hazards, Instantaneous failure rates Group Activity
Software Reliability Models.
Problem Solving: Structure Charts
Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach
Software Reliability It is defined as the ability of a system or component to perform its required functions under stated conditions for a specified period.
© Oxford University Press All rights reserved.
Presentation transcript:

CSE 322: Software Reliability Engineering Topics covered: Architecture-based reliability analysis

Failure models of components  Three types of failure models  Probability of failure or reliability:  Constant failure rate:  Time-dependent failure intensity:

Steps in architecture-based analysis Architecture-based models Architecture of the application Failure behavior of components Solve the model Superimpose + Performance predictions Performance bottlenecks Reliability predictions Reliability bottlenecks Description Solution

Combinations of architecture & failure behavior Absorbing DTMC Probability of failure, R Constant fail. Rate, Time dep. fail int. ( t ) Irreducible DTMC Absorbing CTMC Irreducible CTMC Model #1 Model #2 Model #3 Model #4 Model #7 Model #6 Model #5 Model #8 Model #9 Model #10 Failure behavior of components Architecture Consider only DTMC and CTMC based models Shaded area indicates solution infeasible using DTMC and CTMC models

Model #1

Example - Model #1 Terminating application 10 modules 1 is the input, 10 is the exit module Architecture modeled by absorbing DTMC Reliability, mean execution time of each component known Probability that the control is transferred to module j, upon execution of module i Reliability of component i Execution time of component i per visit - Time to completion of the application - Reliability of the application

Example - Model #1 (contd..) Component Reliability Mean execution time per visit Known for component i Reliability Time to completion units Computed overall

Combinations of architecture & failure behavior Absorbing DTMC Probability of failure, R Constant fail. Rate, Time dep. fail int. ( t ) Irreducible DTMC Absorbing CTMC Irreducible CTMC Model #1 Model #2 Model #3 Model #4 Model #7 Model #6 Model #5 Model #8 Model #9 Model #10 Failure behavior of components Architecture Consider only DTMC and CTMC based models Shaded area indicates solution infeasible using DTMC and CTMC models

Model #2

Example - Model #2,Terminating application, 10 modules 1 is the input, 10 is the exit module Architecture modeled by absorbing DTMC Time independent failure rate known Execution time of the component per visit known Probability that the control is transferred to module j, upon execution of module i Mean execution time of component i per visit Failure rate of component i - Time to completion of the application - Reliability of the application

Example - Model #2 (contd..) Component Failure rate Known for component i Expected execution time of the component per visit Reliability Time to completion units Computed overall

Combinations of architecture & failure behavior Absorbing DTMC Probability of failure, R Constant fail. Rate, Time dep. fail int. ( t ) Irreducible DTMC Absorbing CTMC Irreducible CTMC Model #1 Model #2 Model #3 Model #4 Model #7 Model #6 Model #5 Model #8 Model #9 Model #10 Failure behavior of components Architecture Consider only DTMC and CTMC based models Shaded area indicates solution infeasible using DTMC and CTMC models

Model #3

Example - Model #3,Terminating application, 10 modules 1 is the input, 10 is the exit module Architecture modeled by absorbing DTMC Time dependent failure rate and mean execution time of each component per visit known Probability that the control is transferred to module j, upon execution of module i Time spent in component i per visit Failure rate of component i - Time to completion of the application - Reliability of the application

Example - Model #3 (contd..) Component Failure rate Known for component i Expected total number of faults Mean execution time of the component per visit Fault detection rate per fault Failure rate of the Goel-Okumoto model Reliability Time to completion units Computed overall

Combinations of architecture & failure behavior Absorbing DTMC Probability of failure, R Constant fail. Rate, Time dep. fail int. ( t ) Irreducible DTMC Absorbing CTMC Irreducible CTMC Model #1 Model #2 Model #3 Model #4 Model #7 Model #6 Model #5 Model #8 Model #9 Model #10 Failure behavior of components Architecture Consider only DTMC and CTMC based models Shaded area indicates solution infeasible using DTMC and CTMC models

Model #4

Example - Model #4 Non-terminating application 10 modules Architecture modeled by irreducible DTMC Reliability of each component known Probability that the control is transferred to module j, upon execution of module i Reliability of component i - Utilization of module i - Reliability of the application

Example - Model #4 (contd..) Component Utilization of the component Reliability of the application Computed for component i Computed overall Known for component i Reliability of the component

Combinations of architecture & failure behavior Absorbing DTMC Probability of failure, R Constant fail. Rate, Time dep. fail int. ( t ) Irreducible DTMC Absorbing CTMC Irreducible CTMC Model #1 Model #2 Model #3 Model #4 Model #7 Model #6 Model #5 Model #8 Model #9 Model #10 Failure behavior of components Architecture Consider only DTMC and CTMC based models Shaded area indicates solution infeasible using DTMC and CTMC models

Model #5

Example - Model #6,Terminating application, 10 modules 1 is the input, 10 is the exit module Architecture modeled by absorbing CTMC Reliability of each module known Execution time in each module follows exponential distribution, mean known Probability that the control is transferred to module j, upon execution of module i Mean execution time in component i Reliability of component i - Time to completion of the application - Reliability of the application

Example - Model #5 (contd..) Component Utilization of the component Computed for component i Computed overall Known for component i Failure rate of the component Failure rate of the application