Software Architecture in Practice
If I could rewrite the title, I would put it as "Introduction to Software Architecture" because everything looks like theory lessons in school, not practical. The writing is kinda daunting: lengthy, jargon and duplication.
By the time I’m writing this, I have about eight years of experience in software engineering. For a big part of it, software architecture has been a major concern for me. One of the earliest questions I pondered was the difference between software architecture as it’s practiced by the community and described in the canon and just developing some proper OOP. This distinction, although it started to clear early on, remained a bit vague for me. One of the longest-standing questions was the relation...more
How to elicit and prioritize architecturally significant requirements (ASRs), e.g. Utility tree method
How to address these requirements with architectural tactics and patterns
How to document architecture using various views, e.g. module view (source code model), run time view (components and connectors model), ...more
Was far heavier on the how to gather user requirements than how to determine which design pattern will fit the user's requirements than I was expecting.
Overall, It was a good book for the course.
I think myself as a Junior Solutions Architect and that's why I decided to read it.
I must say that this book covered a lot of my Software Engineering courses in the University (this is a good thing as these things tend to be forgotten).
Overall I would suggest this book for every aspiring Developer that wants to go in the Architects career path.
Thanks to this book, I am at least equipped to handle architecture oriented discussions within and around organization.
This is probably the best formal book you can read on architecture. If you are an architect, or want to be an architect, this had better be on your shelf.
Some ideas are good but explanations are overly long. It could be much shorter, maybe a medium-sized blog post. I had a feeling that authors tried to cram into it everything they find useful about architecture. Links to aerospace standards (who need them in a book like this?), clumsy discussion of product lines (an entire chapter is useless) and many more. Authors use “Source of stimulus - Stimulu ...more
If you're designing complex, distributed systems and you want to avoid discovering fundamental architectural problems very late or post release, then this book will show you how to think about, document, and evaluate your architectures in enough detail to avoid repeating painful mistakes.
Goodreads is hiring!
Learn more »