1 Chapter 5 Software Reliability Software Engineering: Design, Reliability, and Management, International Std. Edition by Martin L. Shooman.

Slides:



Advertisements
Similar presentations
SMJ 4812 Project Mgmt and Maintenance Eng.
Advertisements

Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.
Failure Patterns Many failure-causing mechanisms give rise to measured distributions of times-to-failure which approximate quite closely to probability.
Software Testing and Quality Assurance
Chapter 3 Coding Theory.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
SOFTWARE ENGINEERING for REAL-TIME SYSTEMS (© J.E.Cooling 2003) Dependable software - slide 1 Software engineering for real-time systems Section 2 Dependable.
Copyright 2007 Koren & Krishna, Morgan-Kaufman Part.2.1 FAULT TOLERANT SYSTEMS Part 2 – Canonical.
1 Software Fault Protection Allen Goldberg Kestrel Technology.
1 Fundamentals of Reliability Engineering and Applications Dr. E. A. Elsayed Department of Industrial and Systems Engineering Rutgers University
Introduction Before… Next…
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 13 Reliability.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Galin, SQA from theory to implementation © Pearson Education Limited Chapter 13 CASE Tools and their Effect on Software Quality.
 Software Software  Program vs Software Products Program vs Software Products  Software Characteristics Software Characteristics  Software Crisis.
Methodology for Architectural Level Reliability Risk Analysis Lalitha Krothapalli CSC 532.
1 Product Reliability Chris Nabavi BSc SMIEEE © 2006 PCE Systems Ltd.
-Exponential Distribution -Weibull Distribution
Software Project Management Fifth Edition
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Slack, Chambers and Johnston, Operations Management 5 th Edition © Nigel Slack, Stuart Chambers, and Robert Johnston 2007 Chapter 19 Failure prevention.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Integration testing l Tests complete systems or subsystems composed of integrated.
Chap 11 Engineering Statistics PREP004 – Introduction to Applied Engineering College of Engineering - University of Hail Fall 2009.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 2.
Transition of Component States N F Component fails Component is repaired Failed state continues Normal state continues.
Software Reliability SEG3202 N. El Kadri.
Made by: Sambit Pulak XI-IB. Reliability refers to the operation of hardware, the design of software, the accuracy of data or the correspondence of data.
Security and Reliability THERAC CASE STUDY TEXTBOOK: BRINKMAN’S ETHICS IN A COMPUTING CULTURE READING: CHAPTER 5, PAGES
University of Sunderland CIFM03Lecture 4 1 Software Measurement and Reliability CIFM03 Lecture 4.
Stracener_EMIS 7305/5305_Spr08_ System Reliability Analysis - Concepts and Metrics Dr. Jerrell T. Stracener, SAE Fellow Leadership in Engineering.
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
Software Metrics and Reliability. Definitions According to ANSI, “ Software Reliability is defined as the probability of failure – free software operation.
Chapter 1 The Product. 2 Product  What is it?  Who does it?  Why is it important?  How to ensure it be done right?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
Latifa AlAbdlkarim King Saud University October,2009.
Determination of Sample Size: A Review of Statistical Theory
Software Testing and Quality Assurance Software Quality Assurance 1.
 How do you know how long your design is going to last?  Is there any way we can predict how long it will work?  Why do Reliability Engineers get paid.
Software Reliabilty1 Software Reliability Advanced Software Engineering COM360 University of Sunderland © 1998.
Fault-Tolerant Computing Systems #4 Reliability and Availability
1. What do you understand by software engineering? Discuss the role of engineering software development. 2. What do you understand by software requirement.
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.
Chapter 2: Software Maintenance Omar Meqdadi SE 3860 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Determination of the Optimal Replacement Age for a Preventive Maintenance Problem involving a Weibull Failure Probability Distribution Function Ernesto.
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
Chapter - Software Engineering Fail safe design problems Component jams Operator detected failure Erroneous input Unsafe modes Programming errors Sabotage.
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M12 8/20/2001Slide 1 SMU CSE 8314 /
Part.2.1 In The Name of GOD FAULT TOLERANT SYSTEMS Part 2 – Canonical Structures Chapter 2 – Hardware Fault Tolerance.
Topic: Reliability and Integrity. Reliability refers to the operation of hardware, the design of software, the accuracy of data or the correspondence.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
Text Illustrations in PPT Chapter 11. Source Coding and Error Correction Techniques Principles of Communications, 6th Edition Rodger E. Ziemer William.
MAJOR SOFTWARE FAILURES, WHY THEY FAILED AND LESSONS LEARNED BY AKPABIO UWANA.
CS203 – Advanced Computer Architecture Dependability & Reliability.
Chapter 9 Testing the System 9.1 Principles of System Testing Focus A: The objective of unit and integration ensure the code implemented the design.
MATHPOWER TM 12, WESTERN EDITION Chapter 9 Probability Distributions
Introduction to Software Engineering
Chapter 15 Finalizing Design Specifications
Hazards, Instantaneous failure rates Group Activity
IEEE Std 1074: Standard for Software Lifecycle
Failure and Design Jaime Baber October 12, 2000
The Exponential Distribution
SQA Role during Software Code and Unit Test Phase
Progression of Test Categories
Statistical Reasoning in Sports
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 13 Reliability.
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.
Methodology for Architectural Level Reliability Risk Analysis
RELIABILITY Reliability is -
Definitions Cumulative time to failure (T): Mean life:
Presentation transcript:

1 Chapter 5 Software Reliability Software Engineering: Design, Reliability, and Management, International Std. Edition by Martin L. Shooman

2 Failure Modes Mode of Failure: The general reason for a failure, e.g., poor quality of fabrication, design error, overload of the component, wear due to old age (wear-out). Hardware Failure: It refers to a system failure traceable to some component malfunction. Software Failure: It refers to a system failure traceable to some error in the software. Failure Mechanism: The detailed cause of a failure. (See Table-5.1)

3 Reliability Theory

4

5

6

7 Failure Rate

8

9

10 General form of Failure Curves t1t1 t2t2 t1t1 t2t2 Time t f(t)

11 Software Reliability & Availability Software Reliability R(t): Software Reliability is the probability that the program performs successfully, according to specifications, for a given time period. Software Availability : Software Availability is the probability that the program is performing successfully, according to specifications, at a given point in time. The important difference is that reliability means no failure in the interval 0 to t, whereas availability means only that the system is up at time t.

12 New and Old Errors Previously Fixed(Old) Error: One which recurs in substantially the same form after the programmer has terminated the work on a code change believing that the error has been corrected. Generated(New) Error: One which does not exist until it is created as a by product of a code change made to correct another error.

13 Reliability Model A Bug-Proportional (Macro) Model: (Page No.: ) (Self)