## Jelinski and Moranda ModelThe ## Characteristics of JM ModelFollowing are the characteristics of JM-Model: - It is a Binomial type model
- It is certainly the earliest and certainly one of the most well-known black-box models.
- J-M model always yields an over-optimistic reliability prediction.
- JM Model follows a prefect debugging step, i.e., the detected fault is removed with certainty simple model.
- The constant software failure rate of the J?M model at the i^th failure interval is given by:
^{th} and (i)^{th} failure.The mean value and the failure intensity methods for this model which belongs to the binominal type can be obtained by multiplying the inherent number of faults by the cumulative failure and probability density functions (pdf) respectively:
Those characteristics plus four other characteristics of the J-M model are summarized in table:
## AssumptionsThe assumptions made in the J-M model contains the following: - The number of initial software errors is unknown but fixed and constant.
- Each error in the software is independent and equally likely to cause a failure during a test.
- Time intervals between occurrences of failure are separate, exponentially distributed random variables.
- The software failure rate remains fixed over the ranges among fault occurrences.
- The failure rate is corresponding to the number of faults that remain in the software.
- A detected error is removed immediately, and no new mistakes are introduced during the removal of the detected defect.
- Whenever a failure appears, the corresponding fault is reduced with certainty.
## Variations in JM ModelJM model was the first prominent software reliability model. Several researchers showed interest and modify this model, using different parameters such as failure rate, perfect debugging, imperfect debugging, number of failures, etc. now, we will discuss different existing variations of this model. ## 1. Lipow Modified Version of Jelinski-Moranda Geometric ModelIt allows multiple bugs removal in a time interval. The program failure rate becomes Where ## 2. Sukert Modified Schick-Wolverton ModelSukert modifies the Where ## 3. Schick Wolverton ModelThe Schick and Wolverton
- Errors occur by accident.
- The bug detection rate in the defined time intervals is constant.
- Errors are independent of each other.
- No new bugs are developed.
- Bugs are corrected after they have been detected.
In the model, the program failure rate method is: Where (i-1)st failure.## 4. GO-Imperfect Debugging ModelGoel and Okumoto expand the J-M model by assuming that an error is removed with probability p whenever a failure appears. The program failure rate at the ith failure interval is R(t_{i})=e^{-ϕ[N-p(i-1)]-ti)}## 5. Jelinski-Moranda Geometric ModelThis model considers that the program failure rate function is initially a constant D and reduce geometrically at failure time. The program failure rate and reliability method of time between failures at the ith failure interval are R(t_{i})=e^{-DKi-1ti)}Where ## 6. Little-Verrall Bayesian ModelThis model considers that times between failures are independent exponential random variables with a parameter € i=1, 2 ....n which itself has parameters Where ## 7. Shanthikumar General Markov ModelThis model considers that the failure intensity functions as the number of failures removed are as the given below Where ## 8. An Error Detection Model for Application during Software DevelopmentThe primary feature of this new model is that the variable (growing) size of a developing program is accommodated so that the quality of a program can be predicted by analyzing a basic segment.
This model has the following assumptions along with the JM model assumptions: - Any tested initial portion of the program describes the entire program for the number and nature of its incipient errors.
- The detect-ability of a mistake is unaffected by the "'dilution" incurred when the initially tested method is augmented by new code.
- The number of lines of code which exists at any time is known.
- The growth function and the bug detection process are independent.
## 9. The Langberg Singpurwalla ModelThis model shows how several models used to define the reliability of computer software can be comprehensively viewed by adopting a Bayesian point of view. This model provides a different motivation for a commonly used model using notions from shock models. ## 10. Jewell Bayesian Software Reliability ModelJewell extended a result by Langberg and Singpurwalla (1985) and made an expansion of the Jelinski-Moranda model.
- The testing protocol is authorized to run for a fixed length of time-possibly, but not certainly, coinciding with a failure epoch.
- The distribution of the unknown number of shortage is generalized from the one-parameter Poisson distribution by considering that the parameter is itself a random quantity with a Beta prior distribution.
- Although the estimation of the posterior distributions of the parameters leads to complex expressions, we show that the calculation of the predictive distribution for undetected bugs is straightforward.
- Although it is now identified that the MLE's for reliability, growth can be volatile, we show that, if a point estimator is needed, the predictive model is easily calculated without obtaining the full distribution first.
## 11. Quantum Modification to the JM ModelThis model replaces the JM Model assumption, each error has the same contribution to the unreliability of software, with the new assumption that different types of errors may have different effects on the failure rate of the software.
## 12. Optimal Software Released Based on Markovian Software Reliability ModelIn this model, a software fault detection method is explained by a Markovian Birth process with absorption. This paper amended the optimal software release policies by taking account of a waste of a software testing time. ## 13. A Modification to the Jelinski-Moranda Software Reliability Growth Model Based on Cloud Model TheoryA new unknown parameter θ is contained in the JM model parameters estimation such that ## 14. Modified JM Model with imperfect Debugging PhenomenonThe modified JM Model extends the J-M model by relaxing the assumptions of complete debugging process and types of incomplete removal: - The fault is not deleted successfully while no new faults are introduced
- The fault is not deleted successfully while new faults are created due to incorrect diagnoses.
The assumptions made in the Modified J-M model contain the following: - The number of initial software errors is unknown but fixed and constant.
- Each error in the software is independent and equally feasible to cause a failure during a test.
- Time intervals between occurrences of failure are independent, exponentially distributed random variables.
- The software failure rate remains fixed over the intervals between fault occurrences.
- The failure rate is proportional to the number of errors that remain in the software.
- Whenever a failure occurs, the detected error is removed with probability p, the detected fault is not entirely removed with probability q, and the new fault is generated with probability r. So it is evident that
**p+q+r=1and q≥r.**
Next TopicBasic Execution Time Model |