Introducing Recovery Style for Modeling and Analyzing System Recovery

Abstract

An analysis of the existing approaches for representing architectural views reveals that they focus mainly on functional concerns and are limited when considering quality concerns. We introduce the recovery style for modeling the structure of the system related to the recovery concern. The recovery style is a specialization of the module viewtype in the Views&Beyond approach. It is used to communicate and analyze architectural design decisions and to support detailed design with respect to recovery. We illustrate the style for modeling the recovery views for the open-source software, MPlayer.

Model Driven Configuration of Fault Tolerance Solutions for Component-Based Software System

“…We use a UML profile for both SA and FT [20,25] and made necessary extensions to specify FTSs and FTSAs. There are three kinds of components in this UML profile: «NFTUnit», «FTUnit» and «FTFaci» components.…”

“…Previous work in the area mainly focuses on how to model a specific fault-tolerant mechanism [10,13,14,25,26], for example, exception handling-based mechanism [14,26]. A few studies consider the reasoning or analysis on an FTS.…”

“…Sözer et al [25] specify the structure of a local recovery style in an UML profile, and perform performance overhead and availability analysis. In contrast, we uniformly model and analysis various mechanisms that can be used for third-party components as fault-tolerant styles.…”

Defining and documenting execution viewpoints for a large and complex software-intensive system

“…-Project planning: Practitioners need to construct 'To be' execution models to support two particular activities. On the one hand, these models are needed to distinguish and analyze the difference between considered alternative or future architectures and designs that aim to improve quality attributes such as reliability (Sozer and Tekinerdogan, 2008), dependability, and safety (Hunt et al, 2007). This is important, as it is often not obvious how the realization of the alternative design may affect the structure and behavior of the system at runtime, and therefore influence other system quality attributes.…”

“…As part of our research on the evolvability of large softwareintensive systems (van de Laar et al, 2007), we observed that suitable architectural views are indispensable assets to improve and sustain the evolvability of systems (Muller, 2004(Muller, , 2009. Such views help practitioners to understand the existing system, to plan and evaluate intended changes, and to communicate them to others efficiently.…”