skip to main content
10.1145/2652524.2652577acmconferencesArticle/Chapter ViewAbstractPublication PagesesemConference Proceedingsconference-collections
research-article

The effect of evolutionary coupling on software defects: an industrial case study on a legacy system

Published: 18 September 2014 Publication History

Abstract

Evolutionary coupling is defined as the implicit relationship between two or more software artifacts that are frequently changed together. In this study we investigate the effect of evolutionary coupling on defect proneness of a large financial legacy software in an industrial software development environment. We collected historical data for 5 years from 3 different software repositories containing 150 thousand files on 274 modules. Our results indicate that there is a positive correlation between evolutionary coupling and defect measures. Furthermore, we built linear and logistic regression models by using evolutionary coupling measures in order to explain defects. Although regression analysis results show that evolutionary coupling measures can be useful to explain defects, especially for modules in which high correlation is detected, explanatory power decreases dramatically with the decreasing correlation.

References

[1]
T. Ball, J.-M. Kim, A. A. Porter, and H. P. Siy. If your version control system could talk. In ICSE Workshop on Process Modelling and Empirical Studies of Software Engineering, 1997.
[2]
C. Bauer and G. King. Hibernate in action. 2005.
[3]
D. Beyer and A. E. Hassan. Animated visualization of software history using evolution storyboards. In Reverse Engineering, 2006. WCRE'06. 13th Working Conference on, pages 199--210. IEEE, 2006.
[4]
S. Breu and T. Zimmermann. Mining aspects from version history. In Automated Software Engineering, 2006. ASE'06. 21st IEEE/ACM International Conference on, pages 221--230. IEEE, 2006.
[5]
F. Carlisle, J. Eisinger, M. Johnson, V. Kowalski, J. Mukerji, D. Snelling, W. Vambenepe, M. Waschke, and V. Wiles. Configuration management database (cmdb) federation specification, 2010.
[6]
CASCM. Web page of ca software change manager, 2013.
[7]
M. D'Ambros, M. Lanza, and R. Robbes. On the relationship between change coupling and software defects. In Reverse Engineering, 2009. WCRE'09. 16th Working Conference on, pages 135--144. IEEE, 2009.
[8]
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Software Maintenance, 1998. Proceedings., International Conference on, pages 190--198. IEEE, 1998.
[9]
H. Gall, M. Jazayeri, and J. Krajewski. Cvs release history data for detecting logical couplings. In Software Evolution, 2003. Proceedings. Sixth International Workshop on Principles of, pages 13--23. IEEE, 2003.
[10]
T. L. Graves, A. F. Karr, J. S. Marron, and H. Siy. Predicting fault incidence using software change history. Software Engineering, IEEE Transactions on, 26(7):653--661, 2000.
[11]
P. Knab, M. Pinzger, and A. Bernstein. Predicting defect densities in source code files with decision tree learners. In Proceedings of the 2006 international workshop on Mining software repositories, pages 119--125. ACM, 2006.
[12]
E. Kouroshfar. Studying the effect of co-change dispersion on software quality. In Software Engineering (ICSE), 2013 35th International Conference on, pages 1450--1452. IEEE, 2013.
[13]
H. Lu, Y. Zhou, B. Xu, H. Leung, and L. Chen. The ability of object-oriented metrics to predict change-proneness: a meta-analysis. Empirical Software Engineering, 17:200--242, 2012.
[14]
M. Pinzger, H. Gall, M. Fischer, and M. Lanza. Visualizing multiple evolution metrics. In Proceedings of the 2005 ACM symposium on Software visualization, pages 67--75. ACM, 2005.
[15]
SPSS. Web page of spss, 2013.
[16]
M. Steff and B. Russo. Co-evolution of logical couplings and commits for defect estimation. In Mining Software Repositories (MSR), 2012 9th IEEE Working Conference on, pages 213--216. IEEE, 2012.
[17]
C. Tantithamthavorn, A. Ihara, and K.-I. Matsumoto. Using co-change histories to improve bug localization performance. In Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing (SNPD), 2013 14th ACIS International Conference on, pages 543--548. IEEE, 2013.
[18]
H. WG. A new view of statistics. SportScience, 2003.
[19]
R. K. Yin. Case study research: Design and methods, volume 5. Sage, 2009.
[20]
A. T. Ying, G. C. Murphy, R. Ng, and M. C. Chu-Carroll. Predicting source code changes by mining change history. Software Engineering, IEEE Transactions on, 30(9):574--586, 2004.
[21]
T. Zimmermann, A. Zeller, P. Weissgerber, and S. Diehl. Mining version histories to guide software changes. Software Engineering, IEEE Transactions on, 31(6):429--445, 2005.

Cited By

View all

Index Terms

  1. The effect of evolutionary coupling on software defects: an industrial case study on a legacy system

      Recommendations

      Reviews

      Bálint Molnár

      What is the relationship between evolutionary coupling and software defects__?__ That is the research question raised in this paper. The scientific and empirical investigation of software development and its quality assurance has practical relevance. The evolutionary coupling concept captures the notion of entities of software systems that bear simultaneous impacts of modifications. Since the inception of original conceptualization, lots of advancement has occurred in management, software development techniques, and data analytics. The specific case study that is reported in this paper is a legacy, financial information system. The operation of the system follows the basic guidelines of the IT Infrastructure Library (ITIL), especially with respect to configuration management, source code handling, and defect tracking. During the life cycle of the particular system, plenty of data piled up. The availability of data mining software and the incorporated statistical packages provides an opportunity for analysis. Well-known correlation analysis, clustering, and logistic regression methods were used in the research. The outcome of the research conducted in this paper is that correlation can be demonstrated with some preconditions between the investigated parameters. The accurate measurement of data requires disciplined source code management. The results will be interesting to people who deal with the operational management of IT systems. From a research point of view, the paper contains quite a few new approaches; however, the conducted research can be considered as an accurate empirical investigation, exploiting the capability of recent statistical packages. The paper contributes to the scientific and empirical investigation of software development and operation, but can yield some clues for practitioners as well. Online Computing Reviews Service

      Access critical reviews of Computing literature here

      Become a reviewer for Computing Reviews.

      Comments

      Information & Contributors

      Information

      Published In

      cover image ACM Conferences
      ESEM '14: Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement
      September 2014
      461 pages
      ISBN:9781450327749
      DOI:10.1145/2652524
      Permission to make digital or hard copies of part or all 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 third-party components of this work must be honored. For all other uses, contact the Owner/Author.

      Sponsors

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      Published: 18 September 2014

      Check for updates

      Author Tags

      1. evolutionary coupling
      2. legacy software
      3. measurement
      4. mining software repositories
      5. software defects

      Qualifiers

      • Research-article

      Funding Sources

      Conference

      ESEM '14
      Sponsor:

      Acceptance Rates

      ESEM '14 Paper Acceptance Rate 23 of 123 submissions, 19%;
      Overall Acceptance Rate 130 of 594 submissions, 22%

      Contributors

      Other Metrics

      Bibliometrics & Citations

      Bibliometrics

      Article Metrics

      • Downloads (Last 12 months)8
      • Downloads (Last 6 weeks)1
      Reflects downloads up to 20 Jan 2025

      Other Metrics

      Citations

      Cited By

      View all

      View Options

      Login options

      View options

      PDF

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader

      Media

      Figures

      Other

      Tables

      Share

      Share

      Share this Publication link

      Share on social media