1 Software Testing and Quality Assurance Lecture 35 – Software Quality Assurance.

Slides:



Advertisements
Similar presentations
FPGA Configuration. Introduction What is configuration? – Process for loading data into the FPGA Configuration Data Source Configuration Data Source FPGA.
Advertisements

1 Fault-Tolerant Computing Systems #6 Network Reliability Pattara Leelaprute Computer Engineering Department Kasetsart University
COE 444 – Internetwork Design & Management Dr. Marwan Abu-Amara Computer Engineering Department King Fahd University of Petroleum and Minerals.
6. Reliability Modeling Reliable System Design 2010 by: Amir M. Rahmani.
CS 795 – Spring  “Software Systems are increasingly Situated in dynamic, mission critical settings ◦ Operational profile is dynamic, and depends.
AEM 336: Reliability & Sampling Prediction & Modeling.
Model-Driven Dependability Analysis of Web Services Apostolos Zarras Computer Science Department University of Ioannina, Greece
1 Software Testing and Quality Assurance Lecture 36 – Software Quality Assurance.
Using Rational Approximations for Evaluating the Reliability of Highly Reliable Systems Z. Koren, J. Rajagopal, C. M. Krishna, and I. Koren Dept. of Elect.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
8. Fault Tolerance in Software
Reliability on Web Services Pat Chan 31 Oct 2006.
1 Software Testing and Quality Assurance Lecture 34 – Software Quality Assurance.
Dependability Evaluation. Techniques for Dependability Evaluation The dependability evaluation of a system can be carried out either:  experimentally.
1 Software Testing and Quality Assurance Lecture 39 – Software Quality Assurance.
Maintenance and Reliability Ross L. Fink. Maintenance  All activities involved in keeping a system’s equipment in working order.
1 Software Testing and Quality Assurance Lecture 25 – Testing Interactions (Chapter 6)
EEE499 Real Time Systems Software Reliability (Part II)
Reliability Chapter 4S.
Lucas Phillips Anurag Nanajipuram FAILURE MODE AND EFFECT ANALYSIS.
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
1 Performance Evaluation of Computer Systems By Behzad Akbari Tarbiat Modares University Spring 2009 Introduction to Probabilities: Discrete Random Variables.
4. Dynamic reliability models Objectives Be able to find reliability of series, parallel, stand-by and shared load parallel systems, when the reliabilities.
1 Reliability Prediction A Quest for Reliable Parameters By Yair Shai.
Chapter 6 Time dependent reliability of components and system.
UML - Development Process 1 Software Development Process Using UML (2)
1 System Models. 2 Outline Introduction Architectural models Fundamental models Guideline.
A. BobbioBertinoro, March 10-14, Dependability Theory and Methods 2. Reliability Block Diagrams Andrea Bobbio Dipartimento di Informatica Università.
Demo. Overview Overall the project has two main goals: 1) Develop a method to use sensor data to determine behavior probability. 2) Use the behavior probability.
Software Measurement & Metrics
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Chapter 4 System Reliability Analysis of Structures.
Lecture 2: Combinatorial Modeling CS 7040 Trustworthy System Design, Implementation, and Analysis Spring 2015, Dr. Rozier Adapted from slides by WHS at.
Apps.  Understand the list of applications or application components that are required, based on the baseline Application Portfolio, what the requirements.
Reliability Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill.
4S-1 Chapter 4S Reliability –The ability of a product, part, or system to perform its intended function under a prescribed set of conditions –Reliability.
Process Analysis CHAPTER 5. Learning Objectives 1. Recognize three basic types of processes: a serial flow process, parallel processes (such as what happens.
Software Testing and Quality Assurance Software Quality Assurance 1.
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.
SS7 Signaling System No. 7 takes a whole new (digital) approach to signaling. With the new approach comes great functionality and better service.
Lect1..ppt - 01/06/05 CDA 6505 Network Architecture and Client/Server Computing Lecture 4 Frame Relay by Zornitza Genova Prodanoff.
1 Component reliability Jørn Vatn. 2 The state of a component is either “up” or “down” T 1, T 2 and T 3 are ”Uptimes” D 1 and D 2 are “Downtimes”
1 3. System reliability Objectives Learn the definitions of a component and a system from a reliability perspective Be able to calculate reliability of.
Reliability McGraw-Hill/Irwin Copyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved.
Software Testing and Quality Assurance Software Quality Assurance 1.
Multi-state System (MSS) Basic Concepts MSS is able to perform its task with partial performance “all or nothing” type of failure criterion cannot be.
Stracener_EMIS 7305/5305_Spr08_ Systems Reliability Modeling & Analysis Series and Active Parallel Configurations Dr. Jerrell T. Stracener, SAE.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
Prof. Hany H. Ammar, CSEE, WVU, and
1 Developing Aerospace Applications with a Reliable Web Services Paradigm Pat. P. W. Chan and Michael R. Lyu Department of Computer Science and Engineering.
Timer 1 and 2 operation, PWM Principles. Timer 1 Operation.
Reliability Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
Fault Tree Analysis for the BLEDP Student meeting Vegard Joa Moseng.
Chapter 4s Reliability. Learning Objectives You should be able to: 1.Define reliability 2.Perform simple reliability computations 3.Explain the purpose.
Lecture 11. Switch Hardware Nowadays switches are very high performance computers with high hardware specifications Switches usually consist of a chassis.
Reliability Engineering
FAULT TREE ANALYSIS. NOTATION Series system System fails when either component fails Pump Failure Valve Failure P(system failure) = P(pump failure  valve.
McGraw-Hill/Irwin Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. Supplement 4 Reliability.
Unit 1:Frame Relay.
SOFTWARE DESIGN AND ARCHITECTURE
Chapter 4 Frame Relay Chapter 4 Frame Relay.
CDA 6505 Network Architecture and Client/Server Computing
Distributed computing
Knowing When to Stop: An Examination of Methods to Minimize the False Negative Risk of Automated Abort Triggers RAM XI Training Summit October 2018 Patrick.
Software design and architecture
Production and Operations Management
Chapter 5 Architectural Design.
Presentation transcript:

1 Software Testing and Quality Assurance Lecture 35 – Software Quality Assurance

2 Lecture Objectives Reliability Block Diagrams Series – Parallel Systems

3 Reliability Block Diagrams We need some way of predicting and evaluating the reliability of our designs. For system there are well established modeling methods: Reliability Block Diagrams; and Markov Models These models are stochastic in nature.

4 Reliability Block Diagrams Stochastic process is one in which There is a sequence of events in time where each event is part of a probability distribution.

5 Series – Parallel Systems Reliability block diagrams seek to decompose systems into parallel and serial blocks Where each block interacts with other block to effect the reliability of the system as a whole.

6 Series – Parallel Systems - Example

7 A redundant pair of writers put values from the source onto the bus, and A reader that reads the values from the bus. The system fails if no message is received by the reader in the given time interval.

8 Series – Parallel Systems - Example A message starting at the source then it is passed to both writers and both writers pass the message to both channels.

9 Series – Parallel Systems - Example In the model, Each writer acts in serial with the bus and Both channels of bus act in serial with the reader. To analyze the model; We must calculate the reliabilities for the serial And parallel blocks in the model.

10 Series – Parallel Systems - Example

11 Reliability and Failure Logic for Serial Blocks For the system to model without failure at a given time T, Each of the components B1, B2 and B3 must function independently with out failure for the time period T. For system to function in the Time T, either Block 1 must not fail in time T; Block 2 must not fail in time T; Block 3 must not fail in time T.

12 Reliability and Failure Logic for Serial Blocks For system to fail in the Time T, Only one of the components need to fail. Thus, the probability of failure is

13 Reliability and Failure Logic for Serial Blocks The law of additive law of probability gives us; Where F(Bi) is the probability that the first failure in Bi will occur before Time T.

14 Reliability Logic for Parallel Blocks All blocks must fail before the system fails and Only one block needs to function for the system to function. Parallel blocks, work almost inversely to serial blocks.

15 Reliability Logic for Parallel Blocks For a parallel block to fail in a time T, We need all of the blocks to fail within the time T and so

16 Reliability Logic for Parallel Blocks For a parallel blocks to be reliable for a time T, We have must experience no failure in time T.

17 Reliability Block Diagrams from System Architectures - Guidelines Guideline 1 Determine what constitutes a system failure. This in turn determines which component failures causes a system to fail. Guideline 2 Determine what components need to fail in order to cause a system failure. How messages, signals or data flows

18 Reliability Block Diagrams from System Architectures - Guidelines Guidelines 3 Try to ensure that each block in the reliability block model captures one function of the system. Guideline 4 Try to ensure that you capture the parallel/serial connections from the system accurately.

19 Reliability Block Diagrams from System Architectures - Guidelines Guidelines 5 There may be more than one mode for the system. You need to create a reliability block diagrams for each mode of the system. Windows can operate in a Safe Mode, More reliable because it is limited to basic functionality.

20 Key points Reliability Block Diagrams; and Markov Models Reliability block diagrams seek to decompose systems into parallel and serial blocks Reliability and Failure Logic