Shop Ani- May
$40.12 with 33 percent savings
List Price: $59.75
FREE Returns
FREE delivery Saturday, May 24 to Nashville 37217
Or Prime members get FREE delivery Wednesday, May 21.
In Stock
$$40.12 () Includes selected options. Includes initial monthly payment and selected options. Details
Price
Subtotal
$$40.12
Subtotal
Initial payment breakdown
Shipping cost, delivery date, and order total (including tax) shown at checkout.
Ships from
Amazon.com
Amazon.com
Ships from
Amazon.com
Sold by
Amazon.com
Amazon.com
Sold by
Amazon.com
Returns
30-day refund/replacement
30-day refund/replacement
This item can be returned in its original condition for a full refund or replacement within 30 days of receipt.
Read full return policy
Payment
Secure transaction
Your transaction is secure
We work hard to protect your security and privacy. Our payment security system encrypts your information during transmission. We don’t share your credit card details with third-party sellers, and we don’t sell your information to others. Learn more
Kindle app logo image

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.

Read instantly on your browser with Kindle for Web.

Using your mobile phone camera - scan the code below and download the Kindle app.

QR code to download the Kindle App

Follow the author

George Fairbanks
Follow
Something went wrong. Please try your request again later.

Just Enough Software Architecture: A Risk-Driven Approach 1st Edition

by George H. Fairbanks (Author)
4.3 out of 5 stars 78 ratings
{"desktop_buybox_group_1":[{"displayPrice":"$40.12","priceAmount":40.12,"currencySymbol":"$","integerValue":"40","decimalSeparator":".","fractionalValue":"12","symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"dv%2F07ydt%2FgZJZja3uA%2FxmF2qBj0Zf30M1NSWxoIpXe2xWsPMH3KKnSyf3aZRWSLttmdGeo4bdxMLGH%2BZp2I39iwjIe0E6jFZlLH6iJVE0VA4gU4P9QFWVaNZibsD%2BGx7TEkr%2FRxpz%2BA%3D","locale":"en-US","buyingOptionType":"NEW","aapiBuyingOptionIndex":0}]}

Purchase options and add-ons

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 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 design effort based on the risks you face.

It democratizes architecture. 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, and how seemingly small changes can affect a system's properties.

It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts.

It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not 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 can learn specialized techniques in more detail.

It provides practical advice. Software design decisions influence the architecture and vice versa. 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.

Read more
Previous slide of product details
  1. ISBN-10
    0984618104
  2. ISBN-13
    978-0984618101
  3. Edition
    1st
  4. Publisher
    Marshall & Brainerd
  5. Publication date
    August 30, 2010
  6. Language
    English
  7. Dimensions
    7.3 x 1.1 x 9.3 inches
  8. Print length
    376 pages
Next slide of product details

Frequently bought together

Just Enough Software Architecture: A Risk-Driven Approach
This item: Just Enough Software Architecture: A Risk-Driven Approach
$40.12
Get it as soon as Saturday, May 24
In Stock
Ships from and sold by Amazon.com.
+
Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems
$41.84
Get it May 30 - Jun 4
In Stock
Ships from and sold by MyPrepbooks.
+
Fundamentals of Software Architecture: An Engineering Approach
$43.99
Get it as soon as Saturday, May 24
In Stock
Ships from and sold by Amazon.com.
Total price: $00
To see our price, add these items to your cart.
Details
Added to Cart
These items are shipped from and sold by different sellers.
Show details Hide details
Choose items to buy together.

Editorial Reviews

Review

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

Product details

  • Publisher ‏ : ‎ Marshall & Brainerd
  • Publication date ‏ : ‎ August 30, 2010
  • Edition ‏ : ‎ 1st
  • Language ‏ : ‎ English
  • Print length ‏ : ‎ 376 pages
  • ISBN-10 ‏ : ‎ 0984618104
  • ISBN-13 ‏ : ‎ 978-0984618101
  • Item Weight ‏ : ‎ 2.06 pounds
  • Dimensions ‏ : ‎ 7.3 x 1.1 x 9.3 inches
  • Customer Reviews:
    4.3 out of 5 stars 78 ratings

About the author

Follow authors to get new release updates, plus improved recommendations.
George Fairbanks

George Fairbanks

Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.

Dr. George Fairbanks has been teaching software architecture and object-oriented design for over a decade for companies including Kinetium, Valtech, and Platinum Technology. In the Spring of 2008 he was the co-instructor for the graduate software architecture course at Carnegie Mellon University.

He holds a Ph.D. in Software Engineering from Carnegie Mellon University, advised by David Garlan and Bill Scherlis. His dissertation introduced design fragments, a new way to specify and assure the correct use of frameworks through static analysis. He has publications on frameworks and software architecture in selective academic conferences, including OOPSLA and ICSE.

He has written production code for telephone switches, plugins for the Eclipse IDE, and everything for his own web dot-com startup. He maintains a network of Linux servers in his spare time.

George has been a program committee member for the Working International Conference on Software Architecture (WICSA), the International Conference on Software Maintenance (ICSM), and the European Conference on Software Architecture (ECSA). He has been a referee for IEEE Transactions on Software Engineering (TSE) and IEEE Software.

Customer reviews

4.3 out of 5 stars
78 global ratings

Review this product

Share your thoughts with other customers
Write a customer review

Customers say

Customers appreciate the book's architecture development concepts in practice. The vocabulary receives mixed feedback, with one customer highlighting relevant concepts and terms, while another finds it wordy towards the end.

AI-generated from the text of customer reviews

Select to learn more

6 customers mention "Architecture"6 positive0 negative

Customers appreciate the book's coverage of architecture development concepts in practice, with one customer highlighting its risk-driven approach and another noting its high-level modeling techniques.

"...It's an introduction to software architecture principles that many people without formal computer science backgrounds don't get without a lot of..." Read more

"...makes it easier to understand the topics and see architecture development concepts in practice...." Read more

"...I really appreciate the non-dogmatic approach to architecture...." Read more

"...specific and valuable evidence on the need and on the value of having appropriate architecture...." Read more

9 customers mention "Vocabulary"6 positive3 negative

Customers have mixed opinions about the vocabulary in the book, with some finding it helpful for understanding concepts and terms, while others find it wordy and repetitive.

"...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. *..." Read more

"...The book contains examples or case studies that makes it easier to understand the topics and see architecture development concepts in practice...." Read more

"...The author was a bit wordy towards the end, but given that those chapters were meant as a reference, I guess that's ok...." Read more

"...It's a very thoughtful and thought provoking look at the design process." Read more

Top reviews from the United States

  • luke tucker
    5.0 out of 5 stars Great Intro to Architecture and Modeling Concepts
    Reviewed in the United States on February 5, 2018
    Verified Purchase
    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.
    11 people found this helpful
    Helpful
     Report
  • Eric G.
    4.0 out of 5 stars solid book on risk-driven architecture
    Reviewed in the United States on May 4, 2011
    Verified Purchase
    I thought overall that the book was pretty good. The author did a good job of laying the groundwork for how to determine when to stop designing your architecture and how to effectively accomplish the design with a special ear towards quality attributes.

    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!
    6 people found this helpful
    Helpful
     Report
  • justenough_reviewer1
    5.0 out of 5 stars Review of Just enough architecture
    Reviewed in the United States on February 20, 2012
    Verified Purchase
    So far I have read the first 7 chapters of the book. By what I have seen so far the book contents are interesting and relevant for architecture development. The book contains examples or case studies that makes it easier to understand the topics and see architecture development concepts in practice.

    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.
    8 people found this helpful
    Helpful
     Report
  • Charles E Rider
    5.0 out of 5 stars Fantastic. Talking sense to anxiety.
    Reviewed in the United States on March 20, 2013
    Verified Purchase
    Pragmatism, thy name is software. I really appreciate the non-dogmatic approach to architecture. The simple premise that the more danger you are in the more tightly one wants to predict the outcome is simple. To those who build software every day it is a lovely antidote to those who value process over results and a lovely reality check to wave at those who value "organic" over everything else.
    Thanks
    5 people found this helpful
    Helpful
     Report
  • Grown Up Geek
    4.0 out of 5 stars Just Enough is Plenty
    Reviewed in the United States on September 3, 2012
    Verified Purchase
    Designing good software architecture is, in my opinion, undervalued. "Just Enough Software Architecture" gives specific and valuable evidence on the need and on the value of having appropriate architecture. Rather than the blind "document it all" attitude, it gives insight into how to decide what to architect and what to ignore.

    It's a very thoughtful and thought provoking look at the design process.
    5 people found this helpful
    Helpful
     Report

Top reviews from other countries

Translate all reviews to English
  • SaM
    5.0 out of 5 stars must have book to learn risk-based architecting
    Reviewed in India on September 11, 2015
    Verified Purchase
    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.
    Report
  • gfarfanb
    5.0 out of 5 stars Good book
    Reviewed in Mexico on May 22, 2023
    Verified Purchase
    As a software architecture learner, this book is very good for the purpose.
    Report
  • Eduardo Vieira
    4.0 out of 5 stars Abordagem de custo-benefício a Arquitetura de Software
    Reviewed in Brazil on July 24, 2016
    Verified Purchase
    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.
    Report
  • Hadi Elmougy
    5.0 out of 5 stars Great book
    Reviewed in Germany on November 19, 2018
    Verified Purchase
    One of the best books about software architecture. The content is very rich and easy to follow.
    Report
  • まっこう
    5.0 out of 5 stars Just enoughが素敵！
    Reviewed in Japan on October 27, 2012
    Verified Purchase
    リスクに応じたJusｔ　Enoughなソフトウェアアークテクチャというコンセプトが素敵です。
    アーキテクトは普段からこういうことを無意識に意識しているんじゃないかと思うのですが、
    これを読みながら今一度　自分の中のアーキテクト的な思考回路を整理できました。
    なぜアーキテクト（本書ではもっと広くデベロパーと位置付けていますが）はアーキテクチャを意識するべきなのか。
    アーキテクチャがシステム全体の中で果たす役割は何なのか。が明瞭に述べられています。
    アジャイル、ウォータフォールといった特定の開発プロセスに依存しないレベルで語られているため
    読む人にとっては抽象的過ぎるという印象を持たれるかもしれません。よって経験の少ない初心者向けとは言えません。
    また実際のソフトウェア開発の現場で使える即効薬ではありません。ソフトウェア開発プロジェクト全体を通しての
    リスクとは何なのかをそれぞれの当事者が深く考えるきっかけにする第一歩に過ぎないかもしれません。
    しかし、書かれている内容はとても本質的なのでシステム開発に関わる全ての人に読んでほしいと思います。
    Report