Just Enough Software Architecture: A Risk-Driven Approach

Needed a book on software architecture and this just suited me - my perspective is C++, desktop applications and this book seems pretty background neutral compared to another that got sent back. Good overview of the different basic architectures. It should allow me to argue over the coming weeks during our Scrum project where we are doing big upfront design - doesn't make sense to me either.

A really good book on architecture.

This is the most comprehensive description of of both the hows and whys of architectural modelling I have ever read, period. The notion of risk-driven architecture is the first systematic way I have seen that actually helps you answer the question when you are finished architecting. And chapter 4 should be given to every software engineering student as an example of architectural reasoning. But the book as a whole is quite demanding and I would recommend it to a software professional who wants to improve the knowledge about how to develop better software from an architectural perspective, instead of a student textbook. I think you must have some experience in software development as well as several exemplars of software that you use for you own designs to benefit from everything in this book. On the other hand you could just pick a few things and those in isolation would make you a better software developer. I thought the book was a hard read, the book really challenged me to put together everything I know about software design and modelling into a single comprehensive package. It is like an architecture master class for software developers. I recommend the book to every professional I know that is interested in architecture and want to improve their game.

Completely different focus on architecture method - Risk based. In today's design risk of failure or security breaches etc are very high. This book helps in identifying them through risk based design methods.

I rarely write reviews but really enjoyed this book! I thought it was so useful that we're using it as part of an internal book club at our company. Here's what I found useful for me and why I think it will be more useful if more people have read it (at our company). * It's an introduction to software architecture principles that many people without formal computer science backgrounds don't get without a lot of experience, it doesn't give you all of the answers but it highlights what you don't know and acts as a starting point for further research. WHY should we model and WHAT should we model. * It gives a really comprehensive look at architecture and modeling from a high level. It highlighted for me relevant concepts and terms that I've consistently encountered (and partially understood) in a very accessible way. * It offers an introduction to thinking about WHEN modeling makes sense. It gives you license to think about modeling on a spectrum, when I'd often thought of it as binary ("to model" or "not to model"). * Finally, for our team it further standardizes our vocabulary. It helps get people thinking and speaking on the same page, which is huge when you're frequently getting new hires (especially if they're not from standard comp sci backgrounds). This helps us get closer to understanding HOW modeling can improve our product and company.

As a software architecture learner, this book is very good for the purpose.

Até que ponto discutir a arquitetura de um sistema? Onde começa o "design"? Esse tipo de questão atormenta os profissionais da área. A pressão para se começar o trabalho de execução de um sistema conflita com a necessidade de estudar o problema o suficiente para tomar boas decisões macro que permitam uma execução tranquila. O autor sugere um modelo que basicamente pode ser resumido a: invista em arquitetura nos projetos de maior risco. Os primeiros capítulos, onde o autor define o seu modelo, são bons. A parte onde ele tenta exemplificar com um estudo de caso, nem tanto. É uma boa tentativa para um assunto onde os livros normalmente são muito genéricos. Eu trabalho com isso, tenho um grande conhecimento tácito adquirido, mas acho muito difícil colocar no papel regras que fundamentem o que eu penso. Então entendo a dificuldade dos autores. Mas ainda não achei o livro definitivo sobre o assunto.

One of the best books about software architecture. The content is very rich and easy to follow.