Ninguno

ATAM: Method for Architecture Evaluation

Rick Kazman Mark Klein Paul Clements

August 2000

TECHNICAL REPORT CMU/SEI-2000-TR-004 ESC-TR-2000-004

Pittsburgh, PA 15213-3890

ATAM:SM Method for Architecture Evaluation
CMU/SEI-2000-TR-004 ESC-TR-2000-004

Rick Kazman Mark Klein Paul Clements

August 2000
Product Line Systems

Unlimited distribution subject to the copyright.This report was prepared for the SEI Joint Program Office HQ ESC/AXS 5 Eglin Street Hanscom AFB, MA 01731-2116 The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. FOR THE COMMANDER

Norton L. Compton, Lt Col., USAF SEI Joint Program Office

This work is sponsored by the U.S.Department of Defense. The Software Engineering Institute is a federally funded research and development center sponsored by the U.S. Department of Defense. Copyright © 2000 by Carnegie Mellon University. Requests for permission to reproduce this document or to prepare derivative works of this document should be addressed to the SEI Licensing Agent.

NO WARRANTY THIS CARNEGIE MELLON UNIVERSITYAND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITHRESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. This work was created in the performance of Federal Government Contract Number F19628-95-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The Government of the United States has a royalty-free governmentpurpose license to use,duplicate, or disclose the work, in whole or in part and in any manner, and to have or permit others to do so, for government purposes pursuant to the copyright license under the clause at 52.227-7013. Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder. For information about purchasing paper copies of SEI reports, please visit thepublications portion of our Web site (http://www.sei.cmu.edu/publications/pubweb.html).

Table of Contents

Abstract 1 Introduction 1.1 2 3 4 5 What is the Purpose of the ATAM?

vii 1 2 5 7 9 13 13 16 16 18 19 21 21 22 23 23 25 25 26 27 29 29

The Underlying Concepts A Brief Introduction to the ATAM Quality Attribute Characterizations Scenarios 5.1 5.2 5.3 5.4 Types of Scenarios Eliciting andPrioritizing Scenarios Utility Trees Scenario Brainstorming

6 7

Attribute-Based Architectural Styles Outputs of the ATAM 7.1 7.2 7.3 7.4 Risks and Non-Risks Sensitivity and Tradeoff Points A Structure for Reasoning Producing ATAM’s Outputs

8

The Steps of the ATAM 8.1 8.2 8.3 8.4 8.5 Step 1 - Present the ATAM Step 2 - Present Business Drivers Step 3 - Present Architecture Step 4 - IdentifyArchitecture Approaches Step 5 - Generate Quality Attribute Utility Tree

CMU/SEI-2000-TR-004

i

8.6 8.7 8.8 8.9 9

Step 6 - Analyze Architecture Approaches Step 8 - Analyze Architecture Approaches Step 9 - Present Results

29 36 37 39 39 40 41 42 45 45 46 59 59 59 60 60 63 65 67 67 68 69

Step 7 - Brainstorm and Prioritize Scenarios 33

The Two Phases of ATAM 9.1 9.2 9.3 9.4 Phase 1Activities Phase 2 Activities ATAM Steps and Their Associated Stakeholders A Typical ATAM Agenda

10 A Sample Evaluation: The BCS 10.1 10.2 Phase 1 Phase 2

11 Results Of The BCS ATAM 11.1 11.2 11.3 11.4 Documentation Requirements Architectural Risks Reporting Back and Mitigation Strategies

12 Conclusions Bibliography Appendix A Attribute Characteristics A.1 Performance A.2 Modifiability...