book

Software Architecture in Practice, 4th Edition

by Len Bass, Paul Clements, Rick Kazman

August 2021

Intermediate to advanced

464 pages

14h 24m

English

Addison-Wesley Professional

Read now

Unlock full access

1.1 What Software Architecture Is and What It Isn’t1.2 Architectural Structures and Views1.3 What Makes a “Good” Architecture?1.4 Summary1.5 For Further Reading1.6 Discussion Questions

2.1 Inhibiting or Enabling a System’s Quality Attributes2.2 Reasoning about and Managing Change2.3 Predicting System Qualities2.4 Communication among Stakeholders2.5 Early Design Decisions2.6 Constraints on Implementation2.7 Influences on Organizational Structure2.8 Enabling Incremental Development2.9 Cost and Schedule Estimates2.10 Transferable, Reusable Model2.11 Architecture Allows Incorporation of Independently Developed Elements2.12 Restricting the Vocabulary of Design Alternatives2.13 A Basis for Training2.14 Summary2.15 For Further Reading2.16 Discussion Questions
3.1 Functionality3.2 Quality Attribute Considerations3.3 Specifying Quality Attribute Requirements: Quality Attribute Scenarios3.4 Achieving Quality Attributes through Architectural Patterns and Tactics3.5 Designing with Tactics3.6 Analyzing Quality Attribute Design Decisions: Tactics-Based Questionnaires3.7 Summary3.8 For Further Reading3.9 Discussion Questions
4.1 Availability General Scenario4.2 Tactics for Availability4.3 Tactics-Based Questionnaire for Availability4.4 Patterns for Availability4.5 For Further Reading4.6 Discussion Questions
5.1 Continuous Deployment5.2 Deployability5.3 Deployability General Scenario5.4 Tactics for Deployability5.5 Tactics-Based Questionnaire for Deployability5.6 Patterns for Deployability5.7 For Further Reading5.8 Discussion Questions
6.1 Energy Efficiency General Scenario6.2 Tactics for Energy Efficiency6.3 Tactics-Based Questionnaire for Energy Efficiency6.4 Patterns6.5 For Further Reading6.6 Discussion Questions
7.1 Evaluating the Integrability of an Architecture7.2 General Scenario for Integrability7.3 Integrability Tactics7.4 Tactics-Based Questionnaire for Integrability7.5 Patterns7.6 For Further Reading7.7 Discussion Questions
8.1 Modifiability General Scenario8.2 Tactics for Modifiability8.3 Tactics-Based Questionnaire for Modifiability8.4 Patterns8.5 For Further Reading8.6 Discussion Questions
9.1 Performance General Scenario9.2 Tactics for Performance9.3 Tactics-Based Questionnaire for Performance9.4 Patterns for Performance9.5 For Further Reading9.6 Discussion Questions
10.1 Safety General Scenario10.2 Tactics for Safety10.3 Tactics-Based Questionnaire for Safety10.4 Patterns for Safety10.5 For Further Reading10.6 Discussion Questions
11.1 Security General Scenario11.2 Tactics for Security11.3 Tactics-Based Questionnaire for Security11.4 Patterns for Security11.5 For Further Reading11.6 Discussion Questions
12.1 Testability General Scenario12.2 Tactics for Testability12.3 Tactics-Based Questionnaire for Testability12.4 Patterns for Testability12.5 For Further Reading12.6 Discussion Questions
13.1 Usability General Scenario13.2 Tactics for Usability13.3 Tactics-Based Questionnaire for Usability13.4 Patterns for Usability13.5 For Further Reading13.6 Discussion Questions
14.1 Other Kinds of Quality Attributes14.2 Using Standard Lists of Quality Attributes—Or Not14.3 Dealing with “X-Ability”: Bringing a New QA into the Fold14.4 For Further Reading14.5 Discussion Questions
15.1 Interface Concepts15.2 Designing an Interface15.3 Documenting the Interface15.4 Summary15.5 For Further Reading15.6 Discussion Questions
16.1 Shared Resources16.2 Virtual Machines16.3 VM Images16.4 Containers16.5 Containers and VMs16.6 Container Portability16.7 Pods16.8 Serverless Architecture16.9 Summary16.10 For Further Reading16.11 Discussion Questions
17.1 Cloud Basics17.2 Failure in the Cloud17.3 Using Multiple Instances to Improve Performance and Availability17.4 Summary17.5 For Further Reading17.6 Discussion Questions
18.1 Energy18.2 Network Connectivity18.3 Sensors and Actuators18.4 Resources18.5 Life Cycle18.6 Summary18.7 For Further Reading18.8 Discussion Questions
19.1 Gathering ASRs from Requirements Documents19.2 Gathering ASRs by Interviewing Stakeholders19.3 Gathering ASRs by Understanding the Business Goals19.4 Capturing ASRs in a Utility Tree19.5 Change Happens19.6 Summary19.7 For Further Reading19.8 Discussion Questions
20.1 Attribute-Driven Design20.2 The Steps of ADD20.3 More on ADD Step 4: Choose One or More Design Concepts20.4 More on ADD Step 5: Producing Structures20.5 More on ADD Step 6: Creating Preliminary Documentation during the Design20.6 More on ADD Step 7: Perform Analysis of the Current Design and Review the Iteration Goal and Achievement of the Design Purpose20.7 Summary20.8 For Further Reading20.9 Discussion Questions
21.1 Evaluation as a Risk Reduction Activity21.2 What Are the Key Evaluation Activities?21.3 Who Can Perform the Evaluation?21.4 Contextual Factors21.5 The Architecture Tradeoff Analysis Method21.6 Lightweight Architecture Evaluation21.7 Summary21.8 For Further Reading21.9 Discussion Questions
22.1 Uses and Audiences for Architecture Documentation22.2 Notations22.3 Views22.4 Combining Views22.5 Documenting Behavior22.6 Beyond Views22.7 Documenting the Rationale22.8 Architecture Stakeholders22.9 Practical Considerations22.10 Summary22.11 For Further Reading22.12 Discussion Questions
23.1 Determining Whether You Have an Architecture Debt Problem23.2 Discovering Hotspots23.3 Example23.4 Automation23.5 Summary23.6 For Further Reading23.7 Discussion Questions
24.1 The Architect and the Project Manager24.2 Incremental Architecture and Stakeholders24.3 Architecture and Agile Development24.4 Architecture and Distributed Development24.5 Summary24.6 For Further Reading24.7 Discussion Questions
25.1 Competence of Individuals: Duties, Skills, and Knowledge of Architects25.2 Competence of a Software Architecture Organization25.3 Become a Better Architect25.4 Summary25.5 For Further Reading25.6 Discussion Questions
26.1 Single Qubit26.2 Quantum Teleportation26.3 Quantum Computing and Encryption26.4 Other Algorithms26.5 Potential Applications26.6 Final Thoughts26.7 For Further Reading

Content preview from Software Architecture in Practice, 4th Edition

About the Authors

Len Bass is an award-winning author who has lectured widely around the world. His books on software architecture are standards. In addition to his books on software architecture, Len has also written books on User Interface Software and DevOps. Len has over 50 years’ experience in software development, 25 of those at the Software Engineering Institute of Carnegie Mellon. He also worked for three years at NICTA in Australia and is currently an adjunct faculty member at Carnegie Mellon University, where he teaches DevOps.

Dr. Paul Clements is the Vice President of Customer Success at BigLever Software, Inc., where he works to spread the adoption of systems and software product line engineering. Prior to this, he was a senior ...