Sciweavers

Share
ICSE
1999
IEEE-ACM

Experience with Performing Architecture Tradeoff Analysis

8 years 11 months ago
Experience with Performing Architecture Tradeoff Analysis
Software architectures, like complex designs in any field, embody tradeoffs made by the designers. However, these tradeoffs are not always made explicitly by the designers and they may not understand the impacts of their decisions. This paper describes the use of a scenario-based and model-based analysis technique for software architectures—called ATAM—that not only analyzes a software architecture with respect to multiple quality attributes, but explicitly considers the tradeoffs inherent in the design. This is a method aimed at illuminating risks in the architecture through the identification of attribute trends, rather than at precise characterizations of measurable quality attribute values. The ATAM is illustrated in this paper via an example where we analyzed a U.S. Army system for battlefield management. Keywords Architecture analysis, quality attribute models, architectural styles 1 WHY ARCHITECTURE TRADEOFF ANALYSIS? At the Software Engineering Institute (SEI), we have bee...
Rick Kazman, Mario Barbacci, Mark Klein, S. Jeromy
Added 04 Aug 2010
Updated 04 Aug 2010
Type Conference
Year 1999
Where ICSE
Authors Rick Kazman, Mario Barbacci, Mark Klein, S. Jeromy Carrière, Steven G. Woods
Comments (0)
books