scispace - formally typeset
Open AccessDOI

SEI Architecture Analysis Techniques and When to Use them

TLDR
The purpose of this technical note is to describe, using a hypothetical example, the alignment, combination, and uses of the two methods for analyzing system and software architectures, the Quality Attribute Workshop and the Architecture Tradeoff Analysis MethodSM.
Abstract
The Software Engineering Institute (SEI) has developed two methods for analyzing system and software architectures—the Quality Attribute Workshop (QAW) and the Architecture Tradeoff Analysis Method (ATAM). These techniques, which are described in detail in various SEI technical reports and on the SEI Web site, can be used in combination to obtain early and continuous benefits. Designed to complement the ATAM, the QAW provides a method for analyzing a conceptual architecture or a system architecture against a number of critical quality attributes—such as availability, performance, security, interoperability, and modifiability—before the software architecture is fully developed. Once the software architecture is developed, the ATAM can be used to reveal how well the architecture satisfies particular quality attribute requirements and the risks, sensitivities, and tradeoffs involved in satisfying the requirements. The purpose of this technical note is to describe, using a hypothetical example, the alignment, combination, and uses of the two methods.

read more

Citations
More filters

Quality Attribute Workshops (QAWs), Third Edition

TL;DR: This report describes the newly revised QAW and describes potential uses of the refined scenarios generated during it.
Proceedings ArticleDOI

Architecture classification for SOA-based applications

TL;DR: Using this architecture classification scheme, several well-known SOA-based applications are reviewed including the architectures proposed and adopted by major computer companies and standard organizations.
Journal ArticleDOI

An architectural pattern for non-functional dependability requirements

TL;DR: This work proposes an architectural pattern that allows requirements engineers and architects to map dependability requirements into three corresponding types of architectural components, general enough to work with existing requirements techniques and existing software architectural styles, including enterprise and product-line architectures.

Towards Modeling Non-Functional Requirements in Software Architecture

TL;DR: This position paper introduces the early research, which proposes a grouping mechanism, similar to the separation of concerns achieved in Aspect-Oriented Programming (AOP), to model NFRs in software architectures directly and explicitly.
Journal ArticleDOI

An architectural pattern for non-functional dependability requirements

TL;DR: An architectural pattern is proposed that allows requirements engineers and architects to map the three types of dependability requirements into three corresponding types of architectural components, general enough to work with existing requirements techniques and existing software architectural styles, including enterprise and product-line architectures.
References
More filters
Book

Evaluating Software Architectures: Methods and Case Studies

TL;DR: The ATAM-A Method for Architecture Evaluation focuses on using Quality Attribute Characterizations in the ATAM to evaluate Architecture as a Reusable, Transferable Abstraction of a System.
ReportDOI

Quality Attribute Workshops

TL;DR: Quality attribute workshops (QAW) provide a method for evaluating the architecture of a software-intensive system during the acquisition phase of major programs against a number of critical quality attributes, such as availability, performance, security, interoperability, and modifiability.
ReportDOI

Use of Quality Attribute Workshops (QAWs) in Source Selection for a DoD System Acquisition: A Case Study

TL;DR: A case study of how a DoD organization used QAW architecture analysis and evaluation in a major system acquisition, early on, to reduce program risk is presented in this paper, where the authors describe the system, the motivation for including architecture evaluation in the acquisition, and the QAW approach.
Related Papers (5)