A case study of source code evolution

Arbi Ghazarian

Research output: Chapter in Book/Report/Conference proceedingConference contribution

9 Citations (Scopus)

Abstract

Obtaining an accurate characterization of pre-release changes, especially those related to fault corrections, can give indications for the quality of the software development process and its product. The resulting indications can then be leveraged to identify areas for quality improvement within software development organizations. Towards this objective, we studied the evolution of the source code modules in an industrial enterprise resource planning software system spanning a time period of two years from the initial creation of the source code modules to the release of the software product. In this paper, we describe our case study process, and present the frequency distributions of pre-release changes and faults along with lessons learnedfrom the case study. Overall, we found that (a) only 22% of pre-release changes contribute new functionality to the system under development; the remaining majority of the prerelease changes are either fault corrections or code cleanups (b) over 72% of pre-release faults are propagated from upper-stream requirements and design activities (c) fault classes that are the target of most fault detection tools have a low frequency.

Original languageEnglish (US)
Title of host publicationProceedings of the European Conference on Software Maintenance and Reengineering, CSMR
Pages159-168
Number of pages10
DOIs
StatePublished - 2009
Externally publishedYes
Event13th European Conference on Software Maintenance and Reengineering, CSMR 2009 - Kaiserslautern, Germany
Duration: Mar 24 2009Mar 27 2009

Other

Other13th European Conference on Software Maintenance and Reengineering, CSMR 2009
CountryGermany
CityKaiserslautern
Period3/24/093/27/09

Fingerprint

Software engineering
Enterprise resource planning
Fault detection

ASJC Scopus subject areas

  • Software

Cite this

Ghazarian, A. (2009). A case study of source code evolution. In Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR (pp. 159-168). [4812749] https://doi.org/10.1109/CSMR.2009.12

A case study of source code evolution. / Ghazarian, Arbi.

Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR. 2009. p. 159-168 4812749.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Ghazarian, A 2009, A case study of source code evolution. in Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR., 4812749, pp. 159-168, 13th European Conference on Software Maintenance and Reengineering, CSMR 2009, Kaiserslautern, Germany, 3/24/09. https://doi.org/10.1109/CSMR.2009.12
Ghazarian A. A case study of source code evolution. In Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR. 2009. p. 159-168. 4812749 https://doi.org/10.1109/CSMR.2009.12
Ghazarian, Arbi. / A case study of source code evolution. Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR. 2009. pp. 159-168
@inproceedings{5bac20d3a386439bb505b4d6d371a5f2,
title = "A case study of source code evolution",
abstract = "Obtaining an accurate characterization of pre-release changes, especially those related to fault corrections, can give indications for the quality of the software development process and its product. The resulting indications can then be leveraged to identify areas for quality improvement within software development organizations. Towards this objective, we studied the evolution of the source code modules in an industrial enterprise resource planning software system spanning a time period of two years from the initial creation of the source code modules to the release of the software product. In this paper, we describe our case study process, and present the frequency distributions of pre-release changes and faults along with lessons learnedfrom the case study. Overall, we found that (a) only 22{\%} of pre-release changes contribute new functionality to the system under development; the remaining majority of the prerelease changes are either fault corrections or code cleanups (b) over 72{\%} of pre-release faults are propagated from upper-stream requirements and design activities (c) fault classes that are the target of most fault detection tools have a low frequency.",
author = "Arbi Ghazarian",
year = "2009",
doi = "10.1109/CSMR.2009.12",
language = "English (US)",
isbn = "9780769535890",
pages = "159--168",
booktitle = "Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR",

}

TY - GEN

T1 - A case study of source code evolution

AU - Ghazarian, Arbi

PY - 2009

Y1 - 2009

N2 - Obtaining an accurate characterization of pre-release changes, especially those related to fault corrections, can give indications for the quality of the software development process and its product. The resulting indications can then be leveraged to identify areas for quality improvement within software development organizations. Towards this objective, we studied the evolution of the source code modules in an industrial enterprise resource planning software system spanning a time period of two years from the initial creation of the source code modules to the release of the software product. In this paper, we describe our case study process, and present the frequency distributions of pre-release changes and faults along with lessons learnedfrom the case study. Overall, we found that (a) only 22% of pre-release changes contribute new functionality to the system under development; the remaining majority of the prerelease changes are either fault corrections or code cleanups (b) over 72% of pre-release faults are propagated from upper-stream requirements and design activities (c) fault classes that are the target of most fault detection tools have a low frequency.

AB - Obtaining an accurate characterization of pre-release changes, especially those related to fault corrections, can give indications for the quality of the software development process and its product. The resulting indications can then be leveraged to identify areas for quality improvement within software development organizations. Towards this objective, we studied the evolution of the source code modules in an industrial enterprise resource planning software system spanning a time period of two years from the initial creation of the source code modules to the release of the software product. In this paper, we describe our case study process, and present the frequency distributions of pre-release changes and faults along with lessons learnedfrom the case study. Overall, we found that (a) only 22% of pre-release changes contribute new functionality to the system under development; the remaining majority of the prerelease changes are either fault corrections or code cleanups (b) over 72% of pre-release faults are propagated from upper-stream requirements and design activities (c) fault classes that are the target of most fault detection tools have a low frequency.

UR - http://www.scopus.com/inward/record.url?scp=67649849896&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=67649849896&partnerID=8YFLogxK

U2 - 10.1109/CSMR.2009.12

DO - 10.1109/CSMR.2009.12

M3 - Conference contribution

AN - SCOPUS:67649849896

SN - 9780769535890

SP - 159

EP - 168

BT - Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR

ER -