This document discusses using patterns to guide architecture evolution in service-driven systems. It proposes identifying recurring architecture change patterns from logs, formally specifying patterns in a catalogue, and reusing patterns to support evolution. An example evolution case integrating a new component is presented. A pattern-based evolution process involves specifying changes, retrieving relevant patterns, and instantiating patterns to implement the changes. The approach is experimentally analyzed using evaluation scenarios and a prototype for automated pattern-based evolution. Maintaining a pattern library could help discover, specify and reuse patterns to guide architecture-centric software evolution.
Ensuring Technical Readiness For Copilot in Microsoft 365
Pattern-based Evolution
1. Pattern-driven Reuse in Architecture-centric
Welcome
Evolution for Service Software
Aakash Ahmad, Pooyan Jamshidi and Claus Pahl
Presentation Title
[ahmad.aakash|pooyan.jamshidi|claus.pahl]@computing.dcu.ie
Software and System Engineering group
http://www.computing.dcu.ie/~cpahl/sse-group.htm
School of Computing, Dublin City University, Ireland
THE IRISH SOFTWARE ENGINEERING RESEARCH CENTRE