You're reading from Becoming an Agile Software Architect Strategies, practices, and patterns to help architects design continually evolving solutions

Product type Paperback

Published in Mar 2021

Publisher Packt

ISBN-13 9781800563841

Length 372 pages

Edition 1st Edition

Tools

JIRA

Concepts

Agile

Author (1):

Rajesh R V

View More author details

Table of Contents (19) Chapters

Preface

1. Section 1: Understanding Architecture in the Agile World

2. Chapter 1: Looking through the Agile Architect's Lens FREE CHAPTER

3. Chapter 2: Agile Architecture – The Foundation of Agile Delivery

4. Section 2: Transformation of Architect Roles in Agile

5. Chapter 3: Agile Architect – The Linchpin of Success

6. Chapter 4: Agile Enterprise Architect – Connecting Strategy to Code

7. Chapter 5: Agile Solution Architect – Designing Continuously Evolving Systems

8. Section 3: Essential Knowledge to Become a Successful Agile Architect

9. Chapter 6: Delivering Value with New Ways of Working

10. Chapter 7: Technical Agility with Patterns and Techniques

11. Chapter 8: DevOps and Continuous Delivery to Accelerate Flow

12. Chapter 9: Architecting for Quality with Quality Attributes

13. Chapter 10: Lean Documentation through Collaboration

14. Chapter 11: Architect as an Enabler in Lean-Agile Governance

15. Section 4: Personality Traits and Organizational Influence

16. Chapter 12: Architecting Organizational Agility

17. Chapter 13: Culture and Leadership Traits

18. Other Books You May Enjoy

Applying architecture trade-offs

Architecture trade-off analysis is an extremely important activity for evaluating solutions against quality goals to make informed decisions. Implementing quality requires compromise as achieving everything is not possible. This trade-off is similar to what the CAP theorem states: a distributed database system can only guarantee two qualities out of consistency, availability, and partition tolerance. Some quality attributes may be cost-prohibitive, some may exponentially increase complexity, and some may have strong interdependencies with another quality attribute where improving one may bring the other down.

Vasa, a Swedish warship, is a classic example of building too much quality into a product without trade-offs. In the 1620s, Poland-Lithuania and Sweden were at war. The Swedish king wanted to show off their power and naval superiority by building a gun platform on a large, heavily armed ship that could also transport soldiers. The engineers...