Open Access Open Access  Restricted Access Subscription or Fee Access

A Review of Pre-Release Metrics used for Predicting Post- Release Defects

Pooja Phogat, Kamna Solanki

Abstract


Software maintenance has consumed more than 50%
of development effort and about 90% of software lifecycle. Finding
and correcting defects after software delivery have often presented
high costs when compared to correct it on previous project phases.
The defects that are found after the release of a product are known as
post release software defects. To detect these defects before the
release of the product mainly two metrics are used that are the Mean
Time between Failures (MTBF) and the Average usage Time
(AVT).These metrics are frequently used to gauge the reliability of
the application. However, MTBF and AVT cannot capture the whole
pattern of failure occurrences in the field testing of an application. In
this paper, three metrics that capture three additional patterns of
failure occurrences: the average length of usage time before the
occurrence of the first failure, the spread of failures to the majority of
users, and the daily rates of failures are described.


Keywords


Prerelease Defects, Post-Release Defects, Predicting Defects, Software Testing Metrics.

Full Text:

PDF

References


J. Musa, A. Iannino, and K. Okumoto, “Software Reliability.

Measurement, Prediction, Application” McGraw-Hill, 1987.

A. Mockus and D. Weiss, “Interval quality: relating customer perceived

quality to process quality,” in ICSE 2008: Proceedings of the 30th

international conference on Software engineering. NY, USA: ACM,

, pp. 723–732.

Foutse Khomh et. Al. “Predicting Post-release Defects Using Pre-release

Field Testing Results” ICSM 2011.

Roberto Pepato Mellado “Predicting Post-Release Defects in OO

Software using Product Metrics” 2010.

Daren Methews, “ Calculating Network Availability ” July, 2009

S. Keene, “Modeling software R&M characteristics,” ASQC Reliability

Review, Part I and II, vol. 17, no. 2&3, pp. 13–22, June 1997.

S. Kim, “Adaptive bug prediction by analyzing project history,” Ph.D.

dissertation, Santa Cruz, CA, USA, 2006, adviser-Whitehead,Jr., E.

James.

S. Kim, T. Zimmermann, E. J. Whitehead Jr., and A. Zeller, “Predicting

faults from cached history,” in ICSE ’07: Proceedings of the 29th

international conference on Software Engineering. Washington, DC,

USA: IEEE Computer Society, 2007, pp. 489–498.

A. E. Hassan and R. C. Holt, “The top ten list: Dynamic fault

prediction,” in ICSM ’05: Proceedings of the 21st IEEE International

Conference on Software Maintenance. DC, USA: IEEE Computer

Society, 2005, pp. 263–272.

H. Joshi, C. Zhang, S. Ramaswamy, and C. Bayrak, “Local and global

recency weighting approach to bug prediction,” in MSR ’07:

Proceedings of the Fourth International Workshop on Mining Software

Repositories. Washington, DC, USA: IEEE Computer Society, 2007.

T. M. Khoshgoftaar, E. B. Allen, W. D. Jones, and J. P. Hudepohl, “Data

mining for predictors of software quality,” International Journal of

Software Engineering and Knowledge Engineering, vol. 9, no. 5, 1999.

R. Moser, W. Pedrycz, and G. Succi, “A comparative analysis of the

efficiency of change metrics and static code attributes for defect

prediction,” in Proceedings of the International Conference on Software

Engineering. New York, NY, USA: ACM, 2008, pp. 181–190.

S. Hangal and M. S. Lam, “Tracking down software bugs using

automatic anomaly detection,” in ICSE ’02: Proceedings of the 24th

International Conference on Software Engineering. New York, NY,

USA: ACM, 2002, pp. 291–301.

A. Gupta & Bhatia. “Testing functional requirements using B model

specifications”. ACM SIGSOFT. 2010Software Engineering Notes, 35,

-7

J.Walsh. “Combining the power of DMAIC with testing processes”.

Retrieved from http://www.isixsigma.com .2010.

Bertolino, A “Software Testing Research: Achievements, challenges,

dreams”. In FOSE’07: 2007 Future of Software Engineering. IEEE

Computer Society 2007.


Refbacks

  • There are currently no refbacks.


Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.