Deriving Architectural Tactics: A Step Toward Methodical Architectural Design

Bachmann, Felix; Bass, Len; Klein, Mark

doi:10.21236/ada413701

Cited by 84 publications

(69 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Bachman et al [1] describe steps for deriving architectural tactics. These steps include identifying candidate reasoning frameworks which include the mechanisms needed to use sound analytic theories to analyze the behavior of a system with respect to some quality attributes [2].…”

Section: Add First Iterationmentioning

confidence: 99%

Exploring How the Attribute Driven Design Method Is Perceived

Alí

Solís²

2014

Relating System Quality and Software Architecture

View full text Add to dashboard Cite

Abstract.A method for designing software architecture based on achieving quality attributes is the Attribute Driven Design (ADD) method. This method has not been explored in terms of users' perception on its usefulness and easiness of use. Our goal is to study the perceptions that software engineers with no or little experience industrially in designing software architecture using the ADD. In this paper, we describe an empirical study that we conducted on master students to measure their perceptions of the ADD after using it. We performed two experiments; one with students enrolled in the Software Architecture module in 2010 and repeated it with the students of the same module in 2011. Our main findings are that the subjects perceive ADD method as useful, and that there is a relationship between its usefulness and willingness of use. However, the subjects' opinion was that they did not agree that the ADD method is easy to be used. We also discuss several problems that the subjects faced when using ADD.

show abstract

Section: Add First Iterationmentioning

confidence: 99%

Exploring How the Attribute Driven Design Method Is Perceived

Alí

Solís²

2014

Relating System Quality and Software Architecture

View full text Add to dashboard Cite

show abstract

“…Having multiple views helps to separate the concerns and as such support the modeling, understanding, communication and analysis of the software architecture from the perspective of different concerns of various stakeholders. In addition to architectural views, architectural tactics (Bachman et al 2003) and architectural patterns (Buschmann et al 1996) are utilized to ensure that the architecture meets the required quality concerns. In the last decade, the software engineering community has witnessed the proposal of an increasing number of architectural patterns that are also applied in practice.…”

Section: Related Workmentioning

confidence: 99%

Optimizing decomposition of software architecture for local recovery

2011

View full text Add to dashboard Cite

The increasing size and complexity of software systems has led to an amplified number of potential failures and as such makes it harder to ensure software reliability. Since it is usually hard to prevent all the failures, fault tolerance techniques have become more important. An essential element of fault tolerance is the recovery from failures. Local recovery is an effective approach whereby only the erroneous parts of the system are recovered while the other parts remain available. For achieving local recovery, the architecture needs to be decomposed into separate units that can be recovered in isolation. Usually, there are many different alternative ways to decompose the system into recoverable units. It appears that each of these decomposition alternatives performs differently with respect to availability and performance metrics. We propose a systematic approach dedicated to optimizing the decomposition of software architecture for local recovery. The approach provides systematic guidelines to depict the design space of the possible decomposition alternatives, to reduce the design space with respect to domain and stakeholder constraints and to balance the feasible alternatives with respect to availability and performance. The approach is supported by an integrated set of tools and illustrated for the open-source MPlayer software.

show abstract

“…One missing step in our proposed framework is the linkage between risk model and quality-attribute model such as performance and reliability models, which determines how quality requirements can be derived with respect to mitigation actions chosen. The SEI has recently proposed a quality-attribute reasoning framework [5] that unifies various quality attribute models. We anticipate that incorporation of this reasoning framework into our scheme will be possible.…”

Section: Second Iterationmentioning

confidence: 99%

Managing Architectural Design Decisions for Safety-Critical Software Systems

Kelly

2006

Quality of Software Architectures

View full text Add to dashboard Cite

Abstract. In this paper, we propose a negative scenario framework along with a mitigation action model as the linkage between safety quality attribute and architecture definition. The scenario framework provides an effective means of formulating safety concerns. The mitigation action model facilitates exploitation and codification of existing safety-critical system design knowledge. Finally, we present a series of steps that enable the justification of architectural design decisions that refine both requirements and architectures. We demonstrate and discuss the application of our framework by means of a case study.

show abstract

Deriving Architectural Tactics: A Step Toward Methodical Architectural Design

Cited by 84 publications

References 1 publication

Exploring How the Attribute Driven Design Method Is Perceived

Exploring How the Attribute Driven Design Method Is Perceived

Optimizing decomposition of software architecture for local recovery

Managing Architectural Design Decisions for Safety-Critical Software Systems

Contact Info

Product

Resources

About