Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ $3.75 shipping
+ Free Shipping
Just Enough Software Architecture: A Risk-Driven Approach Hardcover – August 30, 2010
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
The presentation is brisk, and the examples are frequent and interesting. This is a worthy book, a joy to read, and one I wish I had earlier in my career --- to help me avoid making so many mistakes! It is deserving of a place on your shelf if you want become a better software designer. --Dr. Timothy J. Halloran, Director of Engineering at SureLogic Inc.
If you're going to read only one book on software architecture, start with this one. --Michael Keeling, professional software engineer
This book reflects the author's rare mix of deep knowledge of software architecture concepts and extensive industry experience as a developer. If you're an architect, you will want the developers in your organization to read this book. If you're a developer, do read it. --Paulo Merson, Visiting Scientist, Software Engineering Institute
The Risk-Driven Model approach described in George Fairbanks' Just Enough Software Architecture has been applied to the eXtensible Information Modeler (XIM) project here at the NASA Johnson Space Center (JSC) with much success. It is a must for all members of the project, from project management to individual developers. In fact, it is a must for every developer's tool belt. The Code Model section and the anti-patterns alone are worth the cost of the book!--Christopher Dean, Chief Architect, XIM, Engineering Science Contract Group
This book shows how software architecture helps you build software instead of distracting from the job; the book lets you identify and address only those critical architectural concerns that would otherwise prevent you from writing code. --Dr. Kevin Bierhoff, professional software engineer
All in all, this book is easy to read, concise, yet rich with references -- a well-architected and finely-designed book! --Dr. Shang-Wen Cheng, flight software engineer
This book presents a unique view on software architecture that makes it both accessible and practical. The concepts of just enough architecture and risk-driven design are breakthrough ideas developed by Fairbanks. This book demonstrates how architectural principles can be effectively used to solve real world applications. I found it extremely useful and a must read for anyone working in software development. --Dr. Marcus Fontoura, Principal Research Scientist & Architect, Yahoo! Research.
This book [is] a uniquely practical and approachable contribution to the field of software architecture. For anyone who must create innovative software systems, for anyone who is faced with tough decisions about design tradeoffs, for anyone who must find an appropriate balance between agility and discipline -- in short, for almost any software engineer -- this is essential reading. --Dr. David Garlan, Professor, School of Computer Science, Carnegie Mellon University
From the Author
This is the book I wish I'd had when I started developing software. At the time, there were books on languages and books on object-oriented programming, but few books on design. Knowing the features of the Java or C++ language does not mean you can design a good object-oriented system, nor does knowing the Unified Modeling Language (UML) mean you can design a good system architecture.
Like many books, this is a book about software architecture, but this one is for developers. In it, you'll find not only advice on how to think about design, but also hard-won advice from real projects.
This is not a book specifically about Agile Architecture, but it is fully compatible with Agile processes. It shows you how to build up your conceptual model of architecture rather than shelves of documentation.
I hope you enjoy it. --George Fairbanks
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.
The book has hardcover and seems to be a book that will last long if well taken care of. This book will definitely reside on my bookshelf of books of reference.
The author was a bit wordy towards the end, but given that those chapters were meant as a reference, I guess that's ok. You really only need to read the first part of the book to understand the methodology. For a deep dive into the concepts introduced in the first part, the second part is where it's at. It would have been nice if the author had used a single over-arching example throughout the book. The examples he gave, like the Yinzer system (a job-advertising social network), felt incomplete to me. For example, he started the Yinzer example to include the domain and design models, but switched to a new example, an email processing system, for the code model.
In any case, after reading the book, I'm finding myself thinking about work projects at a higher level now. I'm definitely recognizing and applying architectural styles more consciously, instead of by accident. So, I would consider that a success in my mind and would recommend it to others!
The goal of this book is to analyze Edo Japan's sustainable practices and apply them to modern life. It does this by taking a fictionalized journey through the country, starting at a farming village and ending at the home of a lower-level Edo Samurai. As we travel with the narrator, the story points out various things we'd notice and what they mean. Between chapters different levels of society and locations are analyzed for useful lessons.
Thus you'll read about the energy-saving virtue of pickling, the value of latrine outputs, the life of traveling city pottery repairman, and samurai who farm on their small estates. It's actually a bit dizzying, and the author packs in a lot - almost a bit too much to be frank, but he's got a lot to cover.
This human-level look at a sustainable culture, why it evolved, and what it means is very intriguing and has high impact. Backed by illustrations and research, giving these fictionalized but historical examples of efficiency, good construction, food production, etc. helps one understand what we can learn and apply to our lives. This varies from ethical/personal approaches to serious thoughts about material usage and land.
The book will make you think, will help you see the value of history, and will give you ideas.
Despite it's many triumphs of stability, efficiency, and literacy, the book doesn't set the Edo period as something to emulate entirely. The Edo period was also a time of social immobility for most, high taxes for farmers, the practice of infanticide for some, and a samurai class whose comparative wealth were constrained by propriety and social policy. The author clearly admires the Edo period, and perhaps in one or two cases praises it more than I feel it deserved, but he also acknowledges its many flaws. He regards these issues with a kind of sad affection, blots on a period that he feels shows important virtues, but blots nonetheless.
Do I consider this a book worth reading? I do - for the right audience.
Ecology/Sustainability: If you're interested in sustainability in a historical context, this book will definitely be for you.
Those Interested in Japan: If you're into Japanese food, culture, or history, then you'll probably adore this book. This might also be a great gift for anyone interested in period anime and manga because of the wealth of details.
Writers: This books way of using fiction, illustration, and analysis is actually very interesting from a pure level of literature. As a writer or instructional designer, if this book sounds at least mildly interesting to you, you may want to get it as a study of a useful instructional writing style.
So there you have it. The book's not for everyone, but it's quite a good book for the right people.
Most recent customer reviews
very interesting, havent read it all but cant wait to really get in to it.