An imperfect debugging model with two types of hazard rates for software reliability measurement and assessment

Authors:
K. Tokuno;S. Yamada
Affiliations:
Department of Social Systems Engineering, Facility of Engineering Tottori University, Tottori-shi, 680-8552, Japan;Department of Social Systems Engineering, Facility of Engineering Tottori University, Tottori-shi, 680-8552, Japan
Venue:
Mathematical and Computer Modelling: An International Journal
Year:
2000

Citing 5
Cited 2

Software reliability: measurement, prediction, application

Software reliability: measurement, prediction, application
Does imperfect debugging affect software reliability growth?

ICSE '89 Proceedings of the 11th international conference on Software engineering
Software quality/reliability measurement and assessment: software reliability growth models and data analysis

Journal of Information Processing
Software Reliability Models: Assumptions, Limitations, and Applicability

IEEE Transactions on Software Engineering
A state- and time-dependent error occurrence-rate software reliability model with imperfect debugging

AFIPS '81 Proceedings of the May 4-7, 1981, national computer conference

Markovian software reliability measurement with a geometrically decreasing perfect debugging rate

Mathematical and Computer Modelling: An International Journal
Quantitative effects of software testing on reliability improvement in the presence of imperfect debugging

Information Sciences: an International Journal

Quantified Score

Hi-index	0.98

Visualization

Abstract

We propose a software reliability model which assumes that there are two types of software failures. The first type is caused by the faults latent in the system before the testing; the second type is caused by the faults regenerated randomly during the testing phase. The former and latter software failure-occurrence phenomena are described by a geometrically decreasing and a constant hazard rate, respectively. Further, this model describes the imperfect debugging environment in which the fault-correction activity corresponding to each software failure is not always performed perfectly. Defining a random variable representing the cumulative number of faults successfully corrected up to a specified time point, we use a Markov process to formulate this model. Several quantitative measures for software reliability assessment are derived from this model. Finally, numerical examples of software reliability analysis based on the actual testing data are presented.