%0 Conference Paper %1 gustafsson_architectureCentricSoftwareEvolution_2002 %A Gustafsson, J. %A Paakki, J. %A Nenonen, L. %A Verkamo, A.I. %B Software Maintenance and Reengineering, 2002. Proceedings. Sixth European Conference on %D 2002 %K Columbus;Maisa;architectural anti-patterns;design architecture;software design evolution;design evolution;software history;integrated improvement; metrics;object-oriented metrics;software patterns;architecture-centric patterns;development phase;software process programming;software software tool;reverse-engineering tool;software tools;pattern-mining %P 108 -115 %R 10.1109/CSMR.2002.995795 %T Architecture-centric software evolution by software metrics and design patterns %X It is shown how software metrics and architectural patterns can be used for the management of software evolution. In the presented architecture-centric software evolution method the quality of a software system is assured in the software design phase by computing various kinds of design metrics from the system architecture, by automatically exploring instances of design patterns and anti-patterns from the architecture, and by reporting potential quality problems to the designers. The same analysis is applied in the implementation phase to the software code, thus ensuring that it matches the quality and structure of the reference architecture. Finally, the quality of the ultimate system is predicted by studying the development history of previous projects with a similar composition of characteristic software metrics and patterns. The architecture-centric software evolution method is supported by two integrated software tools, the metrics and pattern-mining tool Maisa and the reverse-engineering tool Columbus

@inproceedings{gustafsson_architectureCentricSoftwareEvolution_2002, abstract = {It is shown how software metrics and architectural patterns can be used for the management of software evolution. In the presented architecture-centric software evolution method the quality of a software system is assured in the software design phase by computing various kinds of design metrics from the system architecture, by automatically exploring instances of design patterns and anti-patterns from the architecture, and by reporting potential quality problems to the designers. The same analysis is applied in the implementation phase to the software code, thus ensuring that it matches the quality and structure of the reference architecture. Finally, the quality of the ultimate system is predicted by studying the development history of previous projects with a similar composition of characteristic software metrics and patterns. The architecture-centric software evolution method is supported by two integrated software tools, the metrics and pattern-mining tool Maisa and the reverse-engineering tool Columbus}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Gustafsson, J. and Paakki, J. and Nenonen, L. and Verkamo, A.I.}, biburl = {https://www.bibsonomy.org/bibtex/2127327c24b6c8ff616e764e89690ad28/fritzsolms}, booktitle = {Software Maintenance and Reengineering, 2002. Proceedings. Sixth European Conference on}, doi = {10.1109/CSMR.2002.995795}, interhash = {f0b67f97f0059501097f3d0b255946cc}, intrahash = {127327c24b6c8ff616e764e89690ad28}, keywords = {Columbus;Maisa;architectural anti-patterns;design architecture;software design evolution;design evolution;software history;integrated improvement; metrics;object-oriented metrics;software patterns;architecture-centric patterns;development phase;software process programming;software software tool;reverse-engineering tool;software tools;pattern-mining}, pages = {108 -115}, timestamp = {2013-02-28T11:14:18.000+0100}, title = {Architecture-centric software evolution by software metrics and design patterns}, year = 2002 }