A case study of source code evolution (bibtex)
by Ghazarian, Arbi
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 learned from 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 pre-release changes are either fault corrections or code clean-ups (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.
Reference:
A case study of source code evolution (Ghazarian, Arbi), In Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR, 2009.
Bibtex Entry:
@inproceedings{Ghazarian2009,
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 learned from 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 pre-release changes are either fault corrections or code clean-ups (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 = {Ghazarian, Arbi},
booktitle = {Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR},
doi = {10.1109/CSMR.2009.12},
isbn = {9780769535890},
issn = {15345351},
keywords = {cocome_lit-review,fault diagnosis;software maintenance;software quality;design activities;fault corrections;fault detection tools;frequency distributions;industrial enterprise resource planning software system;quality improvement;software development organizations;software development process;software product;source code evolution;Business;Data analysis;Enterprise resource planning;Fault diagnosis;Frequency;Information systems;Programming;Software engineering;Software maintenance;Software systems;Case Study;Change Analysis;Enterprise Resource Planning Software;Fault Distribution;Source Code Evolution},
mendeley-tags = {cocome_lit-review},
pages = {159--168},
title = {{A case study of source code evolution}},
year = {2009}
}
Powered by bibtexbrowser