List of software reliability models

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Software reliability is the probability of the software causing a system failure over some specified operating time. Software does not fail due to wear out but does fail due to faulty functionality, timing, sequencing, data, and exception handling. The software fails as a function of operating time as opposed to calendar time. Over 225 models have been developed since early 1970s, however, several of them have similar if not identical assumptions. The models have two basic types - prediction modeling and estimation modeling.

1.0 Overview of Software Reliability Prediction Models

These models are derived from actual historical data from real software projects. The user answers a list of questions which calibrate the historical data to yield a software reliability prediction. The accuracy of the prediction depends on how many parameters (questions) and datasets are in the model, how current the data is, and how confident the user is of their inputs. One of the earliest prediction models was the Rome Laboratory TR-92-52. It was developed in 1987 and last updated in 1992 and was geared towards software in avionics systems. Due to the age of the model and data it's no longer recommended but is the basis for several modern models such as the Shortcut model, Full-scale model, and Neufelder assessment model. There are also lookup tables for software defect density based on the capability maturity or the application type. These are very simple models but are generally not as accurate as the assessment based models.[1]

Model Number of inputs Industry supported Effort required to use the model Relative accuracy Year developed/

Last updated

Industry tables 1 Several Quick Varies 1992, 2015
CMMI® tables 1 Any Quick Low at low CMMi® 1997, 2012
Shortcut model 23 Any Moderate Medium 1993, 2012
Full-scale model 94-299 Any Detailed Medium-High 1993, 2012
Metric based models Varies Any Varies Varies NA
Historical data A minimum of 2 Any Detailed High NA
Rayleigh model 3 Any Moderate Medium NA
RADC TR-92-52 43-222 Aircraft Detailed Obsolete 1978, 1992
Neufelder model 156 Any Detailed Medium to high 2015

2.0 Overview of Software Reliability Growth (Estimation) Models

Software reliability growth (or estimation) models use failure data from testing to forecast the failure rate or MTBF into the future. The models depend on the assumptions about the fault rate during testing which can either be increasing, peaking, decreasing or some combination of decreasing and increasing. Some models assume that there is a finite and fixed number of inherent defects while others assume that it's infinite. Some models require effort for parameter estimation while others have only a few parameters to estimate. Some models require the exact time in between each failure found in testing, while others only need to have the number of failures found during any given time interval such as a day.

Model name Inherent defect count Effort required Requires exact time between failures
Increasing fault rate
Weibull Finite/not fixed High Yes
Peak
Shooman Constant Defect Removal Rate Model Finite/fixed Low Yes
Decreasing fault rate
Shooman Constant Defect Removal Rate Model Finite/fixed Low Yes
Linearly Decreasing
General exponential models including:

· Goel-Okumoto (exponential)[2]

· Musa Basic Model

· Jelinski-Moranda

Finite/fixed Medium Yes
Shooman Linearly Decreasing Model Finite/fixed Low Yes
Duane Infinite Medium No
Non-Linearly Decreasing
Musa-Okumoto (logarithmic) Infinite Low Yes
Shooman Exponentially Decreasing Model Finite/fixed High Yes
Log-logistic Finite/fixed High Yes
Geometric Infinite High No
Increasing and then decreasing
Yamada (Delayed)

S-shaped

Infinite High Yes
Weibull Finite/not fixed High

References[edit]

  1. ^ "The Cold Hard Truth About Reliable Software". www.softrel.com. Retrieved 2017-02-13. 
  2. ^ Goel, Amrit; Okumoto, Kazu (Aug 1979). "Time-Dependent Error-Detection Rate Model for Software Reliability and Other Performance Measures". IEEE Transactions on Reliability. R–28 (3): 206–211. doi:10.1109/tr.1979.5220566. Retrieved 2012-09-29. 

[1]

  1. ^ "IEEE 1633 Recommended Practices for Software Reliability, 2016.". Jan 2017.