Issue No. 06 - Nov.-Dec. (2012 vol. 38)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/TSE.2011.91
Markus Michael Geipel , ETH Zurich, Zurich
Frank Schweitzer , ETH Zurich, Zurich
We investigate the relationship between class dependency and change propagation (cochange) in software written in Java. On the one hand, we find a strong correlation between dependency and cochange. Furthermore, we provide empirical evidence for the propagation of change along paths of dependency. These findings support the often alleged role of dependencies as propagators of change. On the other hand, we find that approximately half of all dependencies are never involved in cochanges and that the vast majority of cochanges pertain to only a small percentage of dependencies. This means that inferring the cochange characteristics of a software architecture solely from its dependency structure results in a severely distorted approximation of cochange characteristics. Any metric which uses dependencies alone to pass judgment on the evolvability of a piece of Java software is thus unreliable. As a consequence, we suggest to always take both the change characteristics and the dependency structure into account when evaluating software architecture.
Software development, Java, Open source software, open source, Modularity, class dependency
M. M. Geipel and F. Schweitzer, "The Link between Dependency and Cochange: Empirical Evidence," in IEEE Transactions on Software Engineering, vol. 38, no. , pp. 1432-1444, 2012.