skip to main content
10.1145/1159733.1159737acmconferencesArticle/Chapter ViewAbstractPublication PagesesemConference Proceedingsconference-collections
Article

Comparing the fault-proneness of new and modified code: an industrial case study

Published: 21 September 2006 Publication History

Abstract

Faults are considered as one of the important factors affecting the cost of software development projects. To be able to efficiently handle faults, we must increase our understanding of the factors that make the code fault-prone. A majority of large software systems evolve during their lifetime. In each new release of the system the functionality can be added by writing new classes or/and by modifying already existing ones. In this study we compared the fault-proneness of new and modified classes in such systems. Our study is based on two releases of two large telecommunication systems developed at Ericsson. The major finding of the study is that the risk of introducing faults (the number of faults in the class /the number of new or modified lines of code in the class) is 20 to 40 times as high in modified classes compared to new ones. In the systems which we analyzed a small modification (a few percent) of the class resulted in as many faults as we would expect when the same class was written from scratch. Previous research on this relationship does not appear to exist. Partly in conflict with related research, we found that there is no statistically significant difference between the average number of faults in modified and new classes, and that the average fault-densities (the number of faults/the size of the entire class) in new and in modified classes are very similar. Finally, we also suggest how our findings can be used in practice.

References

[1]
A. D. Aczel and J. Sounderpandian, Complete business statistics, 6. ed. Boston, Mass.: McGraw-Hill, 2006.
[2]
B. Boehm and V. R. Basili, "Software Defect Reduction Top 10 List", Computer, vol. 34, 2001, pp. 135--137.
[3]
L. C. Briand, J. Wust, S. V. Ikonomovski, and L. H., "Investigating quality factors in object-oriented designs: an industrial case study", Proc. of the 1999 Int'l Conf. on software Eng., 1999, pp. 345--354.
[4]
T. M. Khoshgoftaar, E. B. Allen, R. Halstead, G. P. Trio, and R. M. Flass, "Using process history to predict software quality", Computer, vol. 31, 1998, pp. 66--73.
[5]
B. Meyer, Object-oriented software construction, 2. ed. Upper Saddle River, N.J.: Prentice Hall, 1997.
[6]
T. J. Ostrand, E. J. Weyuker, and R. M. Bell, "Predicting the Location and Number of Faults in Large Software Systems", IEEE Transactions on Software Engineering, vol. 31, 2005, pp. 340--355.
[7]
M. Pighin and A. Marzona, "An empirical analysis of fault persistence through software releases", Proceedings of the International Symposium on Empirical Software Engineering, 2003, pp. 206--212.
[8]
R. W. Selby, "Empirically based analysis of failures in software systems", IEEE Transactions on Reliability, vol. 39, 1990, pp. 444--454.
[9]
F. Shull, V. Basili, B. Boehm, A. W. Brown, P. Costa, M. Lindvall, D. Port, I. Rus, R. Tesoriero, and M. Zelkowitz, "What we have learned about fighting defects", Software Metrics, 2002. Proceedings. Eighth IEEE Symposium on, 2002, pp. 249--258.
[10]
The Collaborative Software Development Laboratory, University of Hawaii, USA;LOCC Project Homepage, http://csdl.ics.hawaii.edu/Tools/LOCC/;2005
[11]
C. Wohlin, P. Runeson, M. Höst, M. Ohlsson, B. Regnell, and A. Wesslen, Experimentation in software engineering: an introduction. Boston: Kluwer, 2000.

Cited By

View all
  • (2021)A Classification of Software Defect Prediction Models2021 International Conference "Nonlinearity, Information and Robotics" (NIR)10.1109/NIR52917.2021.9666110(1-6)Online publication date: 26-Aug-2021
  • (2019)A model for software rework reduction through a combination of anomaly metricsJournal of Systems and Software10.1016/j.jss.2008.01.01781:11(1968-1982)Online publication date: 2-Jan-2019

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences
ISESE '06: Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
September 2006
388 pages
ISBN:1595932186
DOI:10.1145/1159733
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 21 September 2006

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. fault prediction
  2. fault-proneness
  3. modified code

Qualifiers

  • Article

Conference

ISESE06
Sponsor:

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)3
  • Downloads (Last 6 weeks)0
Reflects downloads up to 20 Feb 2025

Other Metrics

Citations

Cited By

View all
  • (2021)A Classification of Software Defect Prediction Models2021 International Conference "Nonlinearity, Information and Robotics" (NIR)10.1109/NIR52917.2021.9666110(1-6)Online publication date: 26-Aug-2021
  • (2019)A model for software rework reduction through a combination of anomaly metricsJournal of Systems and Software10.1016/j.jss.2008.01.01781:11(1968-1982)Online publication date: 2-Jan-2019

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media