This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book descri
Just Enough Software Architecture: A Risk-Driven Approach
โ Scribed by George Fairbanks
- Publisher
- Marshall & Brainerd
- Year
- 2010
- Tongue
- English
- Leaves
- 378
- Category
- Library
No coin nor oath required. For personal study only.
โฆ Synopsis
This book teaches risk-driven architecting and describes a way to do just enough architecture. It avoids the one-size-fits all process tarp pit with advice on how to tune your design effort based on the risks you face. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes. This book focuses on the technical parts of software development and what developers do to ensure the system works-not the job titles or processes. 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 learn specialized techniques in more detail. 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.
๐ SIMILAR VOLUMES
<p><i>Software Engineering: Architecture-driven Software Development</i> is the first comprehensive guide to the underlying skills embodied in the IEEE's Software Engineering Body of Knowledge (SWEBOK) standard. Standards expert Richard Schmidt explains the traditional software engineering practices
Section 1. Software Engineering Foundations -- Introduction to Software Engineering -- Generic Software Development Framework -- The Software Architecture -- Coping with Project Complexity -- Integrated Product and Process Development -- Section 2. Specifying Software Requirements -- Understanding S
<p><i>Economics-driven Software Architecture</i> presents a guide for engineers and architects who need to understand the economic impact of architecture design decisions: the long term and strategic viability, cost-effectiveness, and sustainability of applications and systems. Economics-driven soft