Just Enough Software Architecture: A Risk-Driven Approach

When the author started developing software, there were books on languages and books on object-oriented programming, but few books on design. Knowing the features of the C++ language does not mean you can design a good object-oriented system, nor does knowing the Unified Modeling Language (UML) imply you can design a good system architecture.

Setting it apart from other books about software architecture, Just Enough Software Architecture: A Risk-Driven Approach a ]

Teaches risk-driven architecting
The book describes a way to do just enough architecture. It avoids the "one size fits all" process tar pit with advice on how to tune your architecture and design effort based on the risks you face.

Democratizes architecture
The book seeks to make architecture relevant to all software developers, not just architects.

Cultivates declarative knowledge
The book will make you more aware of what you have been doing and provide names for the concepts.

Emphasizes the engineering
The book focuses on the technical parts of software development and deals with what developers do to ensure the system works. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium- to large-sized problems and points out where you can learn specialized techniques in more detail.

Provides practical advice
The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.