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 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 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.

On the use of patterns to recover business processes

“…The full replacement of these systems from scratch has a great impact in technological and economical terms. Moreover, LIS represent a huge business value for companies [5]. Therefore, the most appropriate kind of maintenance is evolutionary maintenance based on re-engineering processes.…”