The full text of this article
An S-shaped software reliability model with imperfect debugging and improved testing learning process
by Pratik Roy; G.S. Mahapatra; Kashi Nath Dey
International Journal of Reliability and Safety (IJRS), Vol. 7, No. 4, 2013
Abstract: In this paper, we propose a non-homogeneous Poisson process (NHPP) based S-shaped software reliability growth model (SRGM) in presence of imperfect debugging with a new exponentially increasing fault content function and S-shaped fault detection rate. We develop the fault content function considering learning capability of testing team during software development process. Fault content increases rapidly at the beginning of testing process while it grows gradually at the end of testing process due to increasing efficiency of testing team with testing time. We use maximum likelihood estimation (MLE) method to estimate model parameters. Applicability of the proposed model has been presented by comparing with established models in terms of goodness of fit and predictive validity using two software failure data sets. Experimental results show that the proposed model gives better fit to real failure data sets and predicts future failure behaviour of software development accurately than established models.
Online publication date: Fri, 01-Nov-2013
is only available to individual subscribers or to users at subscribing institutions.
Go to Inderscience Online Journals to access the Full Text of this article.
Pay per view:
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.
Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Reliability and Safety (IJRS):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable).
See our Orders page to subscribe.
If you still need assistance, please email email@example.com