Toward Understanding the Rhetoric of Small Source Code Changes
IEEE Transactions on Software Engineering
Analyzing the Evolutionary History of the Logical Design of Object-Oriented Software
IEEE Transactions on Software Engineering
Automated classification of change messages in open source projects
Proceedings of the 2008 ACM symposium on Applied computing
Predicting faults using the complexity of code changes
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
WikiDev 2.0: discovering clusters of related team artifacts
CASCON '09 Proceedings of the 2009 Conference of the Center for Advanced Studies on Collaborative Research
Bug prediction using entropy-based measures
International Journal of Knowledge Engineering and Data Mining
| Hi-index | 0.00 |
As large software systems evolve, controlling their complexityis a major challenge for many companies, as they striveto deliver future releases on time and within budget. Severalsource code based metrics have been proposed to assist indetermining the complexity of code to help control developmentcosts and outcome.In this paper we offer a novel view on the problem of complexityin software. We present a complexity metric that isbased on the process followed by the developers to producethe code instead of on the code directly. We conjecture thata chaotic/complex development process negatively affect itsoutcome, the source code. We validate our hypothesis empiricallyusing data derived from the development processhistory of six large open source projects (three operatingsystems: NetBSD, FreeBSD, OpenBSD; a window manager:KDE; an office productivity suite: KOffice; and a databasemanagement system: Postgres).