The Community for Technology Leaders
RSS Icon
Issue No.04 - July/August (2008 vol.25)
pp: 66-73
A case study using a new complexity measurement framework called Structure 101 tracked the structural complexity of three open source software products through their different releases. The analysis found that, as these software products evolved, a large proportion of structural complexity in early releases at the application-code level progressively migrated to higher-level design and architectural elements in subsequent releases, or vice-versa. This pattern repeated itself throughout the evolution of the software product. Refactoring efforts successfully reduced complexity at lower levels, but shifted the complexity to higher levels in the design hierarchy. Conversely, design restructuring at higher levels shifted complexity to lower levels. If this trend holds true for other software products, then mere code refactoring might not be enough to effectively managing structural complexity. Periodic major restructuring of software applications at the design or architectural level could be necessary.
Packaging, Software packages, Open source software, Software measurement, Application software, Software testing, Software maintenance, Design methodology, Software design, Software systems, structural epochs, software evolution, software complexity, software structure, Structure 101
"Structural Epochs in the Complexity of Software over Time", IEEE Software, vol.25, no. 4, pp. 66-73, July/August 2008, doi:10.1109/MS.2008.96
7247 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool