Does software reliability growth behavior follow a non-homogeneous Poisson process
Information and Software Technology
N-version programming with imperfect debugging
Computers and Electrical Engineering
Mathematical and Computer Modelling: An International Journal
Software reliability measurement
Journal of Systems and Software
Software error detection model with applications
Journal of Systems and Software
The Littlewood-Verrall model for software reliability compared with some rivals
Journal of Systems and Software
Use of a subjective prior distribution for the reliability of computer software
Journal of Systems and Software
Optimum release time for software systems based on reliability and cost criteria
Journal of Systems and Software
Seven basic principles of software engineering
Journal of Systems and Software
Quick and simple procedures to assess software reliability and facilitate project management
Journal of Systems and Software
Availability analysis for the design of distributed processing networks
Journal of Systems and Software
A modified Markov model for the estimation of computer software performance
Operations Research Letters
Assessing reliability of modular software
Operations Research Letters
| Hi-index | 0.00 |
An approach to a theory of software reliability based on execution time is derived. This approach provides a model that is simple, intuitively appealing, and immediately useful. The theory permits the estimation, in advance of a project, of the amount of testing in terms of execution time required to achieve a specified reliability goal (stated as a mean time to failure (MTTF)]. Execution time can then be related to calendar time, permitting a schedule to be developed. Estimates of execution time and calendar time remaining until the reliability goal is attained can be continually remade as testing proceeds, based only on the length of the execution time intervals between failures. The current MTTF and the number of errors remaining can also be estimated. Maximum likelihood estimation is employed, and confidence intervals are also established. The foregoing information is obviously very valuable in scheduling and monitoring the progress of program testing. A program has been implemented to compute the foregoing quantities. The reliability model that has been developed can be used in making system tradeoffs involving software or software and hardware components. It also provides a soundly based unit of measure for the comparative evaluation of various programming techniques that are expected to enhance reliability. The model has been applied to four medium-sized software development projects, all of which have completed their life cycles. Measurements taken of MTTF during operation agree well with the predictions made at the end of system test. As far as the author can determine, these are the first times that a software reliability model has been used during software development projects. The paper reflects and incorporates the practical experience gained.