Enhancing domain-specific software architecture recovery

Abstract

Performing software architecture analysis and recovery on a large software system is expensive and time consuming; when it is done at all, it is often performed within a narrow context, focused on a few areas of particular concern. However, for a long-lived system within a well understood application domain, the costs for performing detailed architecture recovery may be amortized over several generations of the system; the resulting models can also be broadened and put into context by incorporating information about the history and anticipated future evolution of both the application and its underlying domain. This paper proposes a systematic approach for organizing application domain knowledge into a unified structure called the Architectural Domain Assets Set (ADAS). The ADAS structure builds on previous research, as well as our experience in performing an architecture recovery of IBM's DB2. Our initial experiences in using ADAS suggest that it brings needed focus to the recovery process and provides assistance to domain-specific architecture recovery.

Recuperación de Arquitecturas de Software: Un Mapeo Sistemático de la Literatura

“…También se determinó que las técnicas de recuperación más utilizadas son Clustering y la Heurística (ver tabla 9), entendiendo a esta última como la combinación de varias técnicas o la presentación de propuestas originales como: "morder abajo" (Zhang et al, 2009), procesos ligeros (Svetinovic y Godfrey, 2001), conjunto de activos arquitectónicos de dominio (Ivkovic y Godfrey, 2003), recuperación basada en evidencias (Ros y Sangwan, 2011), recuperación incremental (Roy y Graham, 2008), recuperación a partir de trazas de eventos (Cook y Wolf, 1998), recuperación basada en reglas de abstracción (Qiao et al, 2003), recuperación basada en componentes (Anquetil et al, 2009;Sun et al, 2005), recuperación basada en metamodelos (Ran y Lencevicius, 2003), análisis a partir de la interfaz gráfica de usuario (Staiger, 2007) y análisis a partir de XML (Riva y Yang, 2002). Para el caso concreto de la recuperación del comportamiento las técnicas más utilizadas son la heurística y la reflexión.…”

Detection and Repair of Architectural Inconsistencies in Java

“…Many approaches address the architecture-implementation mapping issue by ignoring the prescriptive architecture and simply trying to obtain the most accurate descriptive architectures possible [25,35,42,34,29,28,50,58,21,53]. A large number of these approaches rely on software clustering to determine components from implementations [62,47,25,35,14].…”

Software Architecture Reconstruction: A Process-Oriented Taxonomy

“…While SAR processes involve strategy and knowledge of the domain and the application itself, only a few approaches take human expertise explicitly into account. [71] propose to systematically update a knowledge base that would become a helpful collection of domain-specific architectural artifacts.…”

“…However it is not clear whether the approach was used in practice. Multiple inputs must be organized and Ivkovic and Godfrey propose a systematic way to organize application domain knowledge into a unified structure [71].…”