Humberto Cervantes is a professor at Universidad Autónoma Metropolitana Iztapalapa in Mexico City. His primary research interest is software architecture design process tool development methods. He holds the Software Architecture Professional and ATAM Evaluator certificates from the SEI.  Rick Kazman is the Danny and Elsa Lui Distinguished Professor of Information Technology Management at the University of Hawaii. He was involved in creating the ATAM (Architecture Tradeoff Analysis Method) and the Titan and DV8 tools for architecture analysis.

• Preface    xiAcknowledgments    xiiiAbout the Authors     xv  CHAPTER 1: Introduction     11.1 Motivations     11.2 Software Architecture     21.3 The Role of the Architect     61.4 A Brief History of ADD     71.5 Summary     81.6 Further Reading      81.7 Discussion Questions      9  CHAPTER 2: Architectural Design      112.1 Design in General      112.2 Design in Software Architecture      122.3 Why Is Architectural Design So Important?       162.4 Architectural Drivers      172.5 Summary      262.6 Further Reading      262.7 Discussion Questions      27  CHAPTER 3: Making Design Decisions      293.1 Making Design Decisions      293.2 Design Concepts: The Building Blocks for Creating Structures      323.3 Design Concepts to Support Performance      393.4 Design Concepts to Support Availability      413.5 Design Concepts to Support Modifiability      463.6 Design Concepts to Support Security      493.7 Design Concepts to Support Integrability      533.8 Summary      573.9 Further Reading      573.10 Discussion Questions      58  CHAPTER 4: The Architecture Design Process      594.1 The Need for a Principled Method      594.2 Attribute-Driven Design 3.0      604.3 Applying ADD to Different System Contexts      664.4 Identifying and Selecting Design Concepts      704.5 Producing Structures      744.6 Defining Interfaces      774.7 Creating Preliminary Documentation During Design      814.8 Tracking Design Progress      854.9 Summary      874.10 Further Reading      884.11 Discussion Questions      89  CHAPTER 5: API-centric Design      915.1 Business Agility      915.2 API-centric Design      935.3 API-centric Design and ADD      1075.4 Summary      1105.5 Further Reading      1105.6 Discussion Questions      111  CHAPTER 6: Designing for Deployability      1136.1 Deployability Principles and Architectural Design      1136.2 Design Decisions to Support Deployability      1196.3 Deployability and ADD      1286.4 Summary      1296.5 Further Reading      1306.6 Discussion Questions      130  CHAPTER 7: Designing Cloud-Based Solutions      1337.1 Introduction to the Cloud      1337.2 Drivers and the Cloud      1367.3 Cloud-Based Design Concepts      1397.4 ADD in the Design of Cloud-Based Solutions      1477.5 Summary      1487.6 Further Reading      1487.7 Discussion Questions      149  CHAPTER 8: Case Study: Hotel Pricing System      1518.1 Business Case      1518.2 System Requirements      1538.3 Development and Operations Requirements 1     568.4 The Software Design Process      1588.5 Summary      1888.6 Further Reading      1898.7 Discussion Questions      189  CHAPTER 9: Case Study: Digital Twin Platform      1919.1 Business Case      1929.2 System Requirements      1939.3 The Design Process      1959.4 Summary      2239.5 Further Reading      2249.6 Discussion Questions      225  CHAPTER 10: Technical Debt in Architectural Design      22710.1 Technical Debt      22710.2 The Roots of Technical Debt in Design      22810.3 Refactoring and Redesign      23110.4 Technical Debt and ADD      23310.5 Summary      23510.6 Further Reading      23610.7 Discussion Questions      237  CHAPTER 11: Analysis in the Design Process      23911.1 Analysis and Design      23911.2 Why Analyze?       24211.3 Analysis Techniques      24311.4 Tactics-Based Analysis      24411.5 Reflective Questions      24611.6 Scenario-Based Design Reviews      24711.7 Summary      25011.8 Further Reading      25111.9 Discussion Questions      251  CHAPTER 12: The Architecture Design Process in the Organization      25312.1 Architecture Design and the Development Life Cycle      25312.2 Architecture Design and the Organization      26312.3 Summary      26812.4 Further Reading      26912.5 Discussion Questions      270  CHAPTER 13: Final Thoughts      27313.1 On the Need for Methods      27313.2 Future Directions      27513.3 Next Steps      27613.4 Further Reading      27713.5 Discussion Questions      277  Appendix Tactics-Based Questionnaires      279Index      301

Humberto Cervantes is a professor at Universidad Autónoma Metropolitana Iztapalapa in Mexico City. His primary research interest is software architecture design process tool development methods. He holds the Software Architecture Professional and ATAM Evaluator certificates from the SEI.  Rick Kazman is the Danny and Elsa Lui Distinguished Professor of Information Technology Management at the University of Hawaii. He was involved in creating the ATAM (Architecture Tradeoff Analysis Method) and the Titan and DV8 tools for architecture analysis.

• Preface    xiAcknowledgments    xiiiAbout the Authors     xv  CHAPTER 1: Introduction     11.1 Motivations     11.2 Software Architecture     21.3 The Role of the Architect     61.4 A Brief History of ADD     71.5 Summary     81.6 Further Reading      81.7 Discussion Questions      9  CHAPTER 2: Architectural Design      112.1 Design in General      112.2 Design in Software Architecture      122.3 Why Is Architectural Design So Important?       162.4 Architectural Drivers      172.5 Summary      262.6 Further Reading      262.7 Discussion Questions      27  CHAPTER 3: Making Design Decisions      293.1 Making Design Decisions      293.2 Design Concepts: The Building Blocks for Creating Structures      323.3 Design Concepts to Support Performance      393.4 Design Concepts to Support Availability      413.5 Design Concepts to Support Modifiability      463.6 Design Concepts to Support Security      493.7 Design Concepts to Support Integrability      533.8 Summary      573.9 Further Reading      573.10 Discussion Questions      58  CHAPTER 4: The Architecture Design Process      594.1 The Need for a Principled Method      594.2 Attribute-Driven Design 3.0      604.3 Applying ADD to Different System Contexts      664.4 Identifying and Selecting Design Concepts      704.5 Producing Structures      744.6 Defining Interfaces      774.7 Creating Preliminary Documentation During Design      814.8 Tracking Design Progress      854.9 Summary      874.10 Further Reading      884.11 Discussion Questions      89  CHAPTER 5: API-centric Design      915.1 Business Agility      915.2 API-centric Design      935.3 API-centric Design and ADD      1075.4 Summary      1105.5 Further Reading      1105.6 Discussion Questions      111  CHAPTER 6: Designing for Deployability      1136.1 Deployability Principles and Architectural Design      1136.2 Design Decisions to Support Deployability      1196.3 Deployability and ADD      1286.4 Summary      1296.5 Further Reading      1306.6 Discussion Questions      130  CHAPTER 7: Designing Cloud-Based Solutions      1337.1 Introduction to the Cloud      1337.2 Drivers and the Cloud      1367.3 Cloud-Based Design Concepts      1397.4 ADD in the Design of Cloud-Based Solutions      1477.5 Summary      1487.6 Further Reading      1487.7 Discussion Questions      149  CHAPTER 8: Case Study: Hotel Pricing System      1518.1 Business Case      1518.2 System Requirements      1538.3 Development and Operations Requirements 1     568.4 The Software Design Process      1588.5 Summary      1888.6 Further Reading      1898.7 Discussion Questions      189  CHAPTER 9: Case Study: Digital Twin Platform      1919.1 Business Case      1929.2 System Requirements      1939.3 The Design Process      1959.4 Summary      2239.5 Further Reading      2249.6 Discussion Questions      225  CHAPTER 10: Technical Debt in Architectural Design      22710.1 Technical Debt      22710.2 The Roots of Technical Debt in Design      22810.3 Refactoring and Redesign      23110.4 Technical Debt and ADD      23310.5 Summary      23510.6 Further Reading      23610.7 Discussion Questions      237  CHAPTER 11: Analysis in the Design Process      23911.1 Analysis and Design      23911.2 Why Analyze?       24211.3 Analysis Techniques      24311.4 Tactics-Based Analysis      24411.5 Reflective Questions      24611.6 Scenario-Based Design Reviews      24711.7 Summary      25011.8 Further Reading      25111.9 Discussion Questions      251  CHAPTER 12: The Architecture Design Process in the Organization      25312.1 Architecture Design and the Development Life Cycle      25312.2 Architecture Design and the Organization      26312.3 Summary      26812.4 Further Reading      26912.5 Discussion Questions      270  CHAPTER 13: Final Thoughts      27313.1 On the Need for Methods      27313.2 Future Directions      27513.3 Next Steps      27613.4 Further Reading      27713.5 Discussion Questions      277  Appendix Tactics-Based Questionnaires      279Index      301