Measuring Architectural Complexity

by: Grady Booch

Software, IEEE, Vol. 25, No. 4. (2008), pp. 14-15.

View FullText article

DOI, IEEE Explore

Reviews [Write a review of this article]

There are no reviews of this article

Find related articles from these CiteULike users

Software-Architecture (group), germoglio

Find related articles with these CiteULike tags

architecture, complexity, software-architecture, software-engineering

Abstract

Without refactoring, complex software-intensive systems become increasingly irregular and thus increasingly chaotic over time. We can understand complex software systems only when they're nearly decomposable and hierarchic. One measure the author uses is lines of source code: the greater the SLOC, the more inertia to change the system will have, the more people it will take to keep it fed, the more stakeholders who will be crawling all over it. The author describes the more complex measures he uses; these are tuned to Philippe Kruchten's 4+1 view model of architecture. He also counts the number of identifiable design patterns at work. These metrics can generally be gathered automatically via clever mining of configuration management and testing data.

@article{citeulike:2976696, abstract = {Without refactoring, complex software-intensive systems become increasingly irregular and thus increasingly chaotic over time. We can understand complex software systems only when they're nearly decomposable and hierarchic. One measure the author uses is lines of source code: the greater the SLOC, the more inertia to change the system will have, the more people it will take to keep it fed, the more stakeholders who will be crawling all over it. The author describes the more complex measures he uses; these are tuned to Philippe Kruchten's 4+1 view model of architecture. He also counts the number of identifiable design patterns at work. These metrics can generally be gathered automatically via clever mining of configuration management and testing data.}, author = {Booch, Grady }, booktitle = {Software, IEEE}, citeulike-article-id = {2976696}, doi = {10.1109/MS.2008.91}, journal = {Software, IEEE}, keywords = {architecture, complexity, software-architecture, software-engineering}, number = {4}, pages = {14--15}, posted-at = {2008-07-09 14:51:07}, priority = {0}, title = {Measuring Architectural Complexity}, url = {http://dx.doi.org/10.1109/MS.2008.91}, volume = {25}, year = {2008} }

RIS record

TY - JOUR ID - citeulike:2976696 L3 - citeulike-article-id:2976696 TI - Measuring Architectural Complexity T2 - Software, IEEE JF - Software, IEEE VL - 25 IS - 4 SP - 14 EP - 15 N2 - Without refactoring, complex software-intensive systems become increasingly irregular and thus increasingly chaotic over time. We can understand complex software systems only when they're nearly decomposable and hierarchic. One measure the author uses is lines of source code: the greater the SLOC, the more inertia to change the system will have, the more people it will take to keep it fed, the more stakeholders who will be crawling all over it. The author describes the more complex measures he uses; these are tuned to Philippe Kruchten's 4+1 view model of architecture. He also counts the number of identifiable design patterns at work. These metrics can generally be gathered automatically via clever mining of configuration management and testing data. KW - architecture KW - complexity KW - software-architecture KW - software-engineering AU - Booch, Grady PY - 2008/// UR - http://dx.doi.org/10.1109/MS.2008.91 ER -

RIS BibTeX