Evaluating Software Architectures: Methods and Case Studies (Hardcover)

Paul Clements, Rick Kazman, Mark Klein

Evaluating Software Architectures: Methods and Case Studies (Hardcover)
  • 出版商: Addison Wesley
  • 出版日期: 2001-10-22
  • 售價: $2,475
  • 貴賓價: 9.5 折 $2,351
  • 語言: 英文
  • 頁數: 368
  • 裝訂: Hardcover
  • ISBN: 020170482X
  • ISBN-13: 9780201704822
  • 相關分類: 軟體架構

    • 立即出貨 (庫存=1)

買這商品的人也買了...

商品描述

Table of Contents

List of Figures.
List of Tables.
Preface.
Acknowledgments.
Reader's Guide.
1. What Is Software Architecture?

Architecture as a Vehicle for Communication among Stakeholders.
Architecture and Its Effects on Stakeholders.
Architectural Views.
Architecture Description Languages.

Architecture as the Manifestation of the Earliest Design Decisions.
Architectural Styles.

Architecture as a Reusable, Transferable Abstraction of a System.
Summary.
For Further Reading.
Discussion Questions.


2. Evaluating a Software Architecture.

Why Evaluate an Architecture?
When Can an Architecture Be Evaluated?
Who's Involved?
What Result Does an Architecture Evaluation Produce?
For What Qualities Can We Evaluate an Architecture?
Why Are Quality Attributes Too Vague for Analysis?
What Are the Outputs of an Architecture Evaluation?
Outputs from the ATAM, the SAAM, and ARID.
Outputs Only from the ATAM.

What Are the Benefits and Costs of Performing an Architecture Evaluation?
For Further Reading.
Discussion Questions.


3. The ATAM—A Method for Architecture Evaluation.

Summary of the ATAM Steps.
Detailed Description of the ATAM Steps.
Step 1: Present the ATAM.
Step 2: Present the Business Drivers.
Step 3: Present the Architecture.
Step 4: Identify the Architectural Approaches.
Step 5: Generate the Quality Attribute Utility Tree.
Step 6: Analyze the Architectural Approaches.
Step 7: Brainstorm and Prioritize Scenarios.
Step 8: Analyze the Architectural Approaches.
Step 9: Present the Results.

The Phases of the ATAM.
Phase 0 Activities.
Phase 1 Activities.
Phase 2 Activities.
Phase 3 Activities.

For Further Reading.
Discussion Questions.


4. The Battlefield Control System—The First Case Study in Applying the ATAM.

Preparation.
Phase 1.
Step 1: Present the ATAM.
Step 2: Present the Business Drivers.
Step 3: Present the Architecture.
Step 4: Identify the Architectural Approaches.
Step 5: Generate the Quality Attribute Utility Tree.
Step 6: Analyze the Architectural Approaches.

Phase 2.
Step 7: Brainstorm and Prioritize Scenarios.
Step 8: Analyze the Architectural Approaches.
Step 9: Present the Results.

Results of the BCS Evaluation.
Documentation.
Requirements.
Sensitivities and Tradeoffs.
Architectural Risks.

Summary.
Discussion Questions.


5. Understanding Quality Attributes.

Quality Attribute Characterizations.
Performance.
Availability.
Modifiability.
Characterizations Inspire Questions.

Using Quality Attribute Characterizations in the ATAM.
Attribute-Based Architectural Styles.
Summary.
For Further Reading.
Discussion Questions.


6. A Case Study in Applying the ATAM.

Background.
Phase 0: Partnership and Preparation.
Phase 0, Step 1: Present the ATAM.
Phase 0, Step 2: Describe Candidate System.
Phase 0, Step 3: Make a Go/No-Go Decision.
Phase 0, Step 4: Negotiate the Statement of Work.
Phase 0, Step 5: Form the Core Evaluation Team.
Phase 0, Step 6: Hold Evaluation Team Kick-off Meeting.
Phase 0, Step 7: Prepare for Phase 1.
Phase 0, Step 8: Review the Architecture.

Phase 1: Initial Evaluation.
Phase 1, Step 1: Present the ATAM.
Phase 1, Step 2: Present Business Drivers.
Phase 1, Step 3: Present the Architecture.
Phase 1, Step 4: Identify Architectural Approaches.
Phase 1, Step 5: Generate Quality Attribute Utility Tree.
Phase 1, Step 6: Analyze the Architectural Approaches.
Hiatus between Phase 1 and Phase 2.

Phase 2: Complete Evaluation.
Phase 2, Step 0: Prepare for Phase 2.
Phase 2, Steps 1-6.
Phase 2, Step 7: Brainstorm and Prioritize Scenarios.
Phase 2, Step 8: Analyze Architectural Approaches.
Phase 2, Step 9: Present Results.

Phase 3: Follow-Up.
Phase 3, Step 1: Produce the Final Report.
Phase 3, Step 2: Hold the Postmortem Meeting.
Phase 3, Step 3: Build Portfolio and Update Artifact Repositories.

For Further Reading.
Discussion Questions.


7. Using the SAAM to Evaluate an Example Architecture.

Overview of the SAAM.
Inputs to a SAAM Evaluation.
Outputs from a SAAM Evaluation.

Steps of a SAAM Evaluation.
Step 1: Develop Scenarios.
Step 2: Describe the Architecture(s).
Step 3: Classify and Prioritize the Scenarios.
Step 4: Individually Evaluate Indirect Scenarios.
Step 5: Assess Scenario Interactions.
Step 6: Create the Overall Evaluation.

A Sample SAAM Agenda.
A SAAM Case Study.
ATAT System Overview.
Step 1: Develop Scenarios, First Iteration.
Step 2: Describe the Architecture(s), First Iteration.
Step 1: Develop Scenarios, Second Iteration.
Step 2: Describe the Architecture(s), Second Iteration.
Step 3: Classify and Prioritize the Scenarios.
Step 4: Individually Evaluate Indirect Scenarios.
Step 5: Assess Scenario Interactions.
Step 6: Create the Overall Evaluation—Results and Recommendations.

Summary.
For Further Reading.
Discussion Questions.


8. ARID—An Evaluation Method for Partial Architectures.

Active Design Reviews.
ARID: An ADR/ATAM Hybrid.
The Steps of ARID.
Phase 1: Rehearsal.
Phase 2: Review.

A Case Study in Applying ARID.
Carrying Out the Steps.
Results of the Exercise.

Summary.
For Further Reading.
Discussion Questions.


9. Comparing Software Architecture Evaluation Methods.

Questioning Techniques.
Questionnaires and Checklists.
Scenarios and Scenario-Based Methods.

Measuring Techniques.
Metrics.
Simulations, Prototypes, and Experiments.
Rate-Monotonic Analysis.
Automated Tools and Architecture Description Languages.

Hybrid Techniques.
Software Performance Engineering.
The ATAM.

Summary.
For Further Reading.
Discussion Questions.


10. Growing an Architecture Evaluation Capability in Your Organization.

Building Organizational Buy-in.
Growing a Pool of Evaluators.
Establishing a Corporate Memory.
Cost and Benefit Data.
Method Guidance.
Reusable Artifacts.

Summary.
Discussion Questions.


11. Conclusions.

You Are Now Ready!
What Methods Have You Seen?
Why Evaluate Architectures?
Why Does the ATAM Work?
A Parting Message.


Appendix A: An Example Attribute-Based Architectural Style.

Problem Description.
Stimulus/Response.
Architectural Style.
Analysis.
Reasoning.
Priority Assignment.
Priority Inversion.
Blocking Time.

For Further Reading.


References.

商品描述(中文翻譯)

目錄


圖表清單。
表格清單。
前言。
致謝。
讀者指南。
1. 什麼是軟體架構？


架構作為利害關係人之間的溝通工具。

架構及其對利害關係人的影響。
架構視圖。
架構描述語言。



架構作為最早設計決策的體現。

架構風格。



架構作為系統的可重用、可轉移的抽象。
摘要。
進一步閱讀。
討論問題。



2. 評估軟體架構。


為什麼要評估架構？
何時可以評估架構？
誰參與其中？
架構評估產生什麼結果？
我們可以評估哪些品質屬性？
為什麼品質屬性對分析來說太模糊？
架構評估的輸出是什麼？

ATAM、SAAM和ARID的輸出。
僅ATAM的輸出。



進行架構評估的成本和效益是什麼？
進一步閱讀。
討論問題。



3. ATAM——一種架構評估方法。


ATAM步驟摘要。
ATAM步驟的詳細描述。

步驟1：介紹ATAM。
步驟2：介紹業務驅動因素。
步驟3：介紹架構。
步驟4：識別架構方法。
步驟5：生成品質屬性效用樹。
步驟6：分析架構方法。
步驟7：腦力激盪並優先考慮情景。
步驟8：分析架構方法。
步驟9：呈現結果。



ATAM的階段。

階段0活動。
階段1活動。
階段2活動。
階段3活動。



進一步閱讀。
討論問題。



4. 戰場控制系統——應用ATAM的第一個案例研究。


準備工作。
第1階段。

步驟1：介紹ATAM。
步驟2：介紹業務驅動因素。
步驟3：介紹架構。
步驟4：識別架構方法。
步驟5：生成品質屬性效用樹。
步驟6：分析架構方法。



第2階段。

步驟7：腦力激盪並優先考慮情景。
步驟8：分析架構方法。
步驟9：呈現結果。



戰場控制系統評估的結果。

文件。
需求。
敏感性和權衡。
架構風險。



摘要。
討論問題。



5. 理解品質屬性。


品質屬性特徵。

性能。
可用性。
可修改性。
特徵啟發問題。



在ATAM中使用品質屬性特徵。
基於屬性的架構風格。
摘要。
進一步閱讀。
討論問題。



6. 應用ATAM的案例研究。


背景。
階段0：合作夥伴關係和準備工作。

階段0，步驟1：介紹ATAM。
階段0，步驟2：描述候選系統。
階段0，步驟3：做出前進/不前進的決策。
階段0，步驟4：協商聲明。



結果。

類似商品