Home > Research > Publications & Outputs > Pattern-driven reuse in architecture-centric ev...
View graph of relations

Pattern-driven reuse in architecture-centric evolution for service software

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSNConference contribution/Paperpeer-review

Published
Close
Publication date24/07/2012
Host publicationICSOFT 2012 - Proceedings of the 7th International Conference on Software Paradigm Trends
PublisherSciTePress
Pages279-284
Number of pages6
ISBN (print)9789898565198
<mark>Original language</mark>English
Event7th International Conference on Software Paradigm Trends, ICSOFT 2012 - Rome, Italy
Duration: 24/07/201227/07/2012

Conference

Conference7th International Conference on Software Paradigm Trends, ICSOFT 2012
Country/TerritoryItaly
CityRome
Period24/07/1227/07/12

Publication series

NameICSOFT 2012 - Proceedings of the 7th International Conference on Software Paradigm Trends

Conference

Conference7th International Conference on Software Paradigm Trends, ICSOFT 2012
Country/TerritoryItaly
CityRome
Period24/07/1227/07/12

Abstract

Service-based architectures implement business processes as technical software services to develop enterprise software. As a consequence of frequent business and technical change cycles, the architect requires a reusecentered approach to systematically accommodate recurring changes in existing software. Our 'Pat-Evol' project aims at supporting pattern-driven reuse in architecture-centric evolution for service software. We propose architecture change mining as a complementary phase to a systematic architecture change execution. Therefore, we investigate the 'history' of sequential changes - exploiting change logs - to discover patterns of change that occur during evolution. To foster reuse, a pattern catalogue maintains an updated collection with once-off specification for identified pattern instances. This allows us to exploit change pattern as a generic, first class abstractions (that can be operationalised and parameterised) to support reuse in architecture-centric software evolution. The notion of 'build-once, use-often' empowers the role of an architect to model and execute generic and potentially reusable solution to recurring architecture evolution problems.