How do architecture patterns and tactics interact? A model and annotation

Abstract

a b s t r a c tSoftware architecture designers inevitably work with both architecture patterns and tactics. Architecture patterns describe the high-level structure and behavior of software systems as the solution to multiple system requirements, whereas tactics are design decisions that improve individual quality attribute concerns. Tactics that are implemented in existing architectures can have significant impact on the architecture patterns in the system. Similarly, tactics that are selected during initial architecture design significantly impact the architecture of the system to be designed: which patterns to use, and how they must be changed to accommodate the tactics. However, little is understood about how patterns and tactics interact. In this paper, we develop a model for the interaction of patterns and tactics that enables software architects to annotate architecture diagrams with information about the tactics used and their impact on the overall structure. This model is based on our in-depth analysis of the types of interactions involved, and we show several examples of how the model can be used to annotate different kinds of architecture diagrams. We illustrate the model and annotation by showing examples taken from real systems, and describe how the annotation was used in architecture reviews. Tactics and patterns are known architectural concepts; this work provides more specific and in-depth understanding of how they interact. Its other key contribution is that it explores the larger problem of understanding the relation between strategic decisions and how they need to be tailored in light of more tactical decisions.

A Quality Attributes Approach to Defining Reactive Systems Solution Applied to Cloud of Sensors

“…A resilient system is one that delivers a service that can be justifiably trusted when facing changes [9]. Resilience is related to a system's ability of maintaining service provision without deviating from the fulfillment of system goals, despite changes that might affect the system or its environment.…”

“…An example of resilience evaluation is presented in [7]. For description of resilience the following sub attributes are selected based on the "technologies" defined in [9].…”

“…They determine the overall style of the design and include wellknown solutions schemes [8]. Tactics and patterns are known architectural concepts; the work [9] provides more specific and in-depth understanding of how they interact. In the next subsections tactics are proposed for a previously selected set of quality attributes.…”

Exploring How the Attribute Driven Design Method Is Perceived

“…Harrison and Avgeriou analyze the impact of architectural patterns on quality attributes, and how patterns interact with tactics [17], [18]. The documentation of this kind of analysis can aid in creating repositories for tactics and patterns based on quality attributes.…”

The Importance of Architectural Knowledge in Integrating Open Source Software

“…Integrators consider it to be important to understand how a component behaves regarding these system resources; one participant reported to have used a "sandbox" to measure performance, processor usage, disk usage, and similar parameters. One factor that affects a component's behavior is the use of architectural tactics [26,40]. A tactic is a common technique to achieve a certain quality attribute.…”