Название: Facilitating Software Architecture: Empowering Teams to Make Architectural Decisions
Автор: Andrew Harmel-Law
Издательство: O’Reilly Media, Inc.
Год: 2025
Страниц: 570
Язык: английский
Формат: epub
Размер: 10.1 MB

The software architect role is evolving. As systems and their interactions with the teams that build, run, and evolve them become more complex, it's often impossible for those playing the traditional architect roles to be everywhere they need to be. There's simply too much architecture to be done, and the situation has reached a breaking point.

There's a better way. Author Andrew Harmel-Law shows you how architects and development teams can collaborate to create and evolve more efficient architectures for their systems. Techniques in this book will help you learn how to create a mindset that allows everyone to practice architecture and build the best systems they've ever experienced.

What is software architecture? For Grady Booch, “Software architecture represents the set of significant design decisions that shape the form and the function of a system, where significant is measured by cost of change.” Martin Fowler has a similar take that can be paraphrased as software architecture being those decisions that are both important and hard to change.

I like these two definitions because not only do they encompass what software architecture is, they also highlight the greatest difficulty with the concept of “software architecture.” Booch’s definition leans toward the end result while Fowler’s leans more toward the practice. In fact, the term software architecture can refer to one or the other, or both at the same time. Rather confusingly, we tend to use the meanings interchangeably when we talk about the software we build. For any software system to be successful, both the end result and the practice are essential.

With this book, you will:

Understand the new dynamics that affect modern software delivery
Learn a methodology that brings software architecture and development together
Nurture the fundamental interplay of decisions, advice, architecture, and feedback from running systems
Initiate practices that maximize benefits and mitigate risks
Create an approach tuned to architecture, everyone's skills, and your organization's culture

Who Should Read This Book:
This book is primarily aimed at the two groups I am trying to bring together: developers looking to take steps into architectural accountability and architects learning to add facilitation skills to their repertoire.