software defect discovery and resolution modeling incorporating severity

Traditional software reliability growth models only consider defect discovery data, yet the primary concern of software engineers is defect removal. past attempts to model defect resolution emphasize approaches based on differential equations and queueing theory. however, these models do not explicitly identify the activities performed to remove defects and resources allocated to these activities according to their severity. models should consider these practical factors to enable more detailed resource allocation and planning.this paper presents a model to predict the number of defects resolved according to the discrete cox proportional hazard model with covariates, demonstrating the approach with covariates on the number of low, medium, and high severity defects that were discovered but not resolved in successive intervals. a comparison with differential equation-based and distributional approaches reveals that the covariate model performs better on each goodness of fit measure considered and requires less time to apply. the covariate model also better tracks unresolved defects and exhibits low predictive error, even when as little as 10-20% of testing has been completed. these results suggest that collecting information on defect resolution activities and the corresponding effort dedicated could substantially improve defect resolution modeling to guide process improvement.