Evolution styles: using architectural knowledge as an evolution driver. Issue 9 (27th November 2012)

• Record Type: Journal Article
• Authors: Cuesta, Carlos E.; Navarro, Elena; Perry, Dewayne E.; Roda, Cristina
• Is Part Of: Journal of software. Volume 25:Issue 9(2013)
• Page Start: 957
• Page End: 980
• Publication Date: 2012-11-27
• Subjects: software architecture evolution -- architectural knowledge -- evolution styles; Software engineering -- Periodicals; Computer software -- Development -- Periodicals; Software maintenance -- Periodicals; 005.1
• DOI: 10.1002/smr.1575
• Languages: English
• ISSNs: 2047-7473

Abstract

Abstract: Software evolution is an increasingly challenging and compelling concern for every developed software system because of the changes in the requirements, the technology, etc. When software evolution is carried out, software architecture emerges as one of the cornerstones that should be considered from two different points of view: as an artifact for the evolution, as it helps the architect plan and restructure the system, and as an artifact of the evolution, because it has to be modified as well. This paper focuses on the second point of view—that is, on the evolution of the software architecture, but taking into account architectural knowledge as a key driver of the process. Given that architecture rationale and design intent are critical in evolving software systems, it is imperative that they be captured in some useful form to aid that evolution process. We present a new approach for evolution styles that extends them by considering in their description the architectural knowledge as a valuable asset of the evolution process. Copyright © 2012 John Wiley & Sons, Ltd. Abstract : There are compelling arguments for using Architectural Knowledge (AK) as an explicit artifact during the Software Architecture (SA) evolution. We argue for AK as a critical element in extended evolution styles to guide the architect during SA evolution. We call our approach 'AK‐driven Evolution Styles' (AKdES). AKdES does not depend on any existing description language but is designed to depend only on the use of structured AK.