2007 · 56 citations · 23 references
ComputingComputer ScienceChange MeasurementSoftware EngineeringSystems ArchitectureObject-oriented DesignSoftware ArchitectureSoftware DesignSoftware EvolutionSoftware MaintenanceSoftware MetricsObject-oriented ArchitectureObject-oriented MetricsSoftware Change Impact AnalysisSoftware Evolution AnalysisSoftware Evolution MetricsSoftware VersioningSource Code Change Analysis
Real software systems change and become more complex over time. But which parts change and which parts remain stable? Common wisdom, for example, states that in a well-designed object-oriented system, the more popular a class is, the less likely it is to change from one version to the next, since changes to this class are likely to impact its clients. We have studied consecutive releases of several public domain, object-oriented software systems and analyzed a number of measures indicative of size, popularity, and complexity of classes and interfaces. As it turns out, the distributions of these measures are remarkably stable as an application evolves. The distribution of class size and complexity retains its shape over time. Relatively little code is modified over time. Classes that tend to be modified, however, are also the more popular ones, that is, those with greater Fan-In. In general, the more "complex" a class or interface becomes, the more likely it is to change from one version to the next.
23
Thomas J. McCabe · IEEE Transactions on Software Engineering · 1976 · 5.8K citations
Programs, life cycles, and laws of software evolution
M. M. Lehman · Proceedings of the IEEE · 1980 · 1.2K citations
Predicting Defects for Eclipse
Thomas Zimmermann, Rahul Premraj, Andreas Zeller · 2007 · 752 citations