Impact of Unanticipated software evolution on development cost and quality: an empirical evaluation

Citations Over TimeTop 17% of 2015 papers

Abstract

Most techniques to aid maintenance and evolution of software require to define extension points. Generally, developers try to anticipate the parts that are more likely to evolve, but they can make mistakes and spend money in vain. With Unanticipated Software Evolution, developers can easily change any element of the software, even those that are not related with an extension point. However, we have not found empirical validations of Unanticipated Software Evolution impact on development cost and quality. In this work, we design and execute an experiment for Unanticipated Software Evolution (specifically, using the COMPOR platform), in order to compare its results metrics -time, lines of code, test coverage and complexity --using OO systems as baseline. 30 undergraduate students were subjects in this experiment. We concluded that COMPOR have significant impact on the Lines of code and Complexity metrics, reducing the amount of lines changed and the McCabe cyclomatic complexity on evolution of a small system.

Related Papers

• → A critique of cyclomatic complexity as a software metric(1988)231 cited
• → Effectiveness of traditional software metrics for object-oriented systems(1992)66 cited
• → Correlations between Internal Software Metrics and Software Dependability in a Large Population of Small C/C++ Programs(2007)58 cited
• On the Improvement of Cyclomatic Complexity Metric(2015)
• → Retraction Note to: Correlation between amount-of-reuse metrics and other software measures with respect to programming code in C++(2011)