Enjoy fast, FREE delivery, exclusive deals and award-winning movies & TV shows with Prime
Try Prime
and start saving today with Fast, FREE Delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Instant streaming of thousands of movies and TV episodes with Prime Video
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
$31.99$31.99
FREE delivery:
Tuesday, July 11
Ships from: Amazon.com Sold by: Amazon.com
Buy used: $15.88
Other Sellers on Amazon
+ $3.99 shipping
84% positive over last 12 months
Usually ships within 2 to 3 days.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required. Learn more
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the Author
OK
Design of Design, The: Essays from a Computer Scientist 1st Edition
| Price | New from | Used from |
- Kindle
$20.99 Read with Our Free App - Paperback
$15.88 - $31.9914 Used from $9.60 7 New from $31.99
Purchase options and add-ons
Effective design is at the heart of everything from software development to engineering to architecture. But what do we really know about the design process? What leads to effective, elegant designs? The Design of Design addresses these questions.
These new essays by Fred Brooks contain extraordinary insights for designers in every discipline. Brooks pinpoints constants inherent in all design projects and uncovers processes and patterns likely to lead to excellence. Drawing on conversations with dozens of exceptional designers, as well as his own experiences in several design domains, Brooks observes that bold design decisions lead to better outcomes.
The author tracks the evolution of the design process, treats collaborative and distributed design, and illuminates what makes a truly great designer. He examines the nuts and bolts of design processes, including budget constraints of many kinds, aesthetics, design empiricism, and tools, and grounds this discussion in his own real-world examples—case studies ranging from home construction to IBM's Operating System/360. Throughout, Brooks reveals keys to success that every designer, design project manager, and design researcher should know.
- ISBN-100201362988
- ISBN-13978-0201362985
- Edition1st
- PublisherAddison-Wesley Professional
- Publication dateMarch 22, 2010
- LanguageEnglish
- Dimensions1.1 x 6.1 x 9.1 inches
- Print length448 pages
Frequently bought together

What do customers buy after viewing this item?
- Most purchased | Highest ratedin this set of products
Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable SystemsPaperback
Mythical Man-Month, The: Essays on Software Engineering, Anniversary EditionFrederick Brooks Jr.Paperback
Software Fundamentals: Collected Papers by David L.ParnasDaniel M./ David M. Hoffman / WeissPaperback
Editorial Reviews
From the Back Cover
Making Sense of Design
Effective design is at the heart of everything from software development to engineering to architecture. But what do we really know about the design process? What leads to effective, elegant designs? The Design of Design addresses these questions.
These new essays by Fred Brooks contain extraordinary insights for designers in every discipline. Brooks pinpoints constants inherent in all design projects and uncovers processes and patterns likely to lead to excellence. Drawing on conversations with dozens of exceptional designers, as well as his own experiences in several design domains, Brooks observes that bold design decisions lead to better outcomes.
The author tracks the evolution of the design process, treats collaborative and distributed design, and illuminates what makes a truly great designer. He examines the nuts and bolts of design processes, including budget constraints of many kinds, aesthetics, design empiricism, and tools, and grounds this discussion in his own real-world examples―case studies ranging from home construction to IBM’s Operating System/360. Throughout, Brooks reveals keys to success that every designer, design project manager, and design researcher should know.
About the Author
Frederick P. Brooks, Jr., is Kenan Professor of Computer Science at the University of North Carolina at Chapel Hill. He is the recipient of the National Medal of Technology, for his work on IBM’s Operating System/360, and the A. M. Turing Award, for his “landmark contributions to computer architecture, operating systems, and software engineering.” He is the author of the best-selling book The Mythical Man-Month, Anniversary Edition (Addison-Wesley, 1995).
Product details
- Publisher : Addison-Wesley Professional; 1st edition (March 22, 2010)
- Language : English
- Paperback : 448 pages
- ISBN-10 : 0201362988
- ISBN-13 : 978-0201362985
- Item Weight : 1.34 pounds
- Dimensions : 1.1 x 6.1 x 9.1 inches
- Best Sellers Rank: #432,457 in Books (See Top 100 in Books)
- #161 in Computer Systems Analysis & Design (Books)
- #1,013 in Software Design, Testing & Engineering (Books)
- #1,266 in Computer Software (Books)
- Customer Reviews:
About the author

Frederick P. Brooks, Jr., is Kenan Professor of Computer Science at the University of North Carolina at Chapel Hill. He was an architect of the IBM Stretch and Harvest computers. He was Corporate Project Manager for the System/360, including development of the System/360 computer family hardware and the decision to switch computer byte size from 6 to 8 bits. He then managed the initial development of the Operating System/360 software suite: operating system, 16 compilers, communications, and utilities.
He founded the UNC Department of Computer Science in 1964 and chaired it for 20 years. His research there has been in computer architecture, software engineering, and interactive 3-D computer graphics (protein visualization graphics and "virtual reality"). His best-known books are The Mythical Man-Month (1975, 1995); Computer Architecture: Concepts and Evolution (with G.A. Blaauw, 1997); and The Design of Design (2010).
Dr. Brooks has received the National Medal of Technology, the A.M. Turing award of the ACM, the Bower Award and Prize of the Franklin Institute, the John von Neumann Medal of the IEEE, and others. He is a member of the U.S. National Academies of Engineering and of Science, the American Academy of Arts and Sciences, the Royal Academy of Engineering (U.K.) and of the Royal Netherlands Academy of Arts and Sciences.
He became a Christian at age 31 and has taught an adult Sunday school class for 35 years. He chaired the Executive Committee for the 1973 Research Triangle Billy Graham Crusade. He and Mrs. Nancy Greenwood Brooks are faculty advisors to a graduate student chapter of InterVarsity Christian Fellowship. They have three children and nine grandchildren.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The book contains six parts and is about 400 pages thick. The first part of the book called "Models of Designing" dives (again) in the Waterfall Model and explains that it doesn't work, cannot work, and has never ever worked. He compares the Waterfall model to the Rational Model of design (from Simon) which has been criticized as being overly simplistic. Brooks still spends about 50 pages diving in Waterfall model and concludes this with: "The waterfall model is wrong and harmful; we must outgrow it"
The second part is about collaboration and tele-collaboration. To me, this was the weakest part of the book. In this part, Brooks argues that a good design always comes from one designer and cannot be developed by a group or a team. This is contrary to my own experiences and also, according to his notes, contrary to some of the reviewers experiences. Yet he keeps stressing this point throughout his book. The subject of tele-collaboration was covered only minimally.
The third part is probably the best part of the book and names design perspectives. Each chapter is a separate essay about one aspect of design. I especially enjoyed chapter 13 where Brooks argues we'll need more examplars of good software developers we can build on. Good design is build on good examples, but in software development... good examples are rarely studied (even though they are nowadays frequently Open Sourced)
The fourth and most of the sixth part of the book were uninteresting to me. The fourth part discusses a design that Brooks made with his team to design a dream system for architects for designing houses. It was mainly a description of the design decisions he made. Chapter six consists of case studies. Most of these case studies are Brooks amateur (physical) architecture studies where he, in he free time, extended his house and build a beach house. The cases aren't strongly linked to the design perspectives and design model he described earlier and it made them rather uninteresting to me (a software developer first). Chapter six also has cases about the IBM 360 system and operating system. I was more interested in these chapters, especially from a historical perspective. (Brooks his beach house might be beautiful, it had no impact on the world other than Family Brooks' enjoyable life at the beach).
The fifth part is short and names Great Designers. It contains two chapter "Great Designs come from Great Designers" and "Where do Great Designers Come From?". I enjoyed these chapters as a reminder of the impact of people and talent on the result of a project. And the question, which is unfortunately not a common discussion, how to actually teach great design (which he then links back to the examplars).
Overall, I enjoyed reading The Design of Design, yet I expected more. I was particularly disappointed by the old-ness (and perhaps obsoleteness) of the examples. Nearly all examples came again from the IBM 360 project. As programming language examples with a good design, Brooks doesn't talk about Ruby or Haskell... no he mentions APL. There is no example about modern design (in software that is) or any suggestion that Fred Brooks has been involved in a software development project after the IBM 360 project. This did not make his writing less entertaining, nor his insights less insightful, yet... I had expected more. Oh, and the case studies about his amateur architecture projects could probably be skipped.
Anyways, as mentioned, I still enjoyed reading it. The writing was good and the lessons were still valid. I thought of rating it 3 or 4 stars and decided to still go with a 4 star rating. However, if you are unfamiliar with Fred Brooks work, I'd recommend to read "The Mythical Man Month" instead.
In the first few chapters the book stresses the point that design is iterative process, that it is not possible to get the design right from the very beginning. Then he mentions several cases of how the design of complex system was done in a wrong way. For example, designing a military chopper without consulting with pilots. Therefore, even during early design stage it is important that users be taken into consideration. And this is indeed why open-source systems are so successful - because they are driven by users of the product.
Brooks mentions that previously the designers were actually the users of the product: think of Wright brothers, Ford who rode on the car that he designed, etc. But as the time goes by this happens to change: do you think that space rocket designers are same people as astronauts? Obviously no. And this is going to happen to the software as well, Brooks claims.
As the library of software components gets bigger and bigger, the process of building software becomes more like that in assembly factory: take piece labeled S1 and S2, connect them together, wrap them into S3, etc. In such a scenario the designer might not even know how to program, and this is the good part. The drawback is that such software can have bad design.
In further chapters of the book Brooks delves into philosophy - empiricism and rationalism. He mentions that abstract math was generated by French philosophers who were mostly into rationalism, whereas applied science was created by Brits who are into empiricism. Brooks claims that software engineering is totally empirical, that is, requires constant verification, and so is the design of software.
Then Brooks sheds light on what are the characteristics of a good design, in his opinion. The major design principles are: orthogonality, propriety, and generality. But those are just general principles. When you design something, you have to make thousands of micro-decisions and the way you make them is called style. How to achieve good style? Brooks mentions the importance of copying other people's styles. Even great composers such as J. S. Bach spent considerable amount of time studying other people's works.
So, design is a complicated iterative process. As always, documentation plays a very important role. So how can one document the design trajectories? For that tools are needed. Brooks cites a few tools available online, but I cannot say they are mainstream. On the other hand, he fails to mention Mind Maps, a recent tool which is hugely popular among engineers.
To summarize, this book is a message from a successful engineer of previous generation of computer programmers. Can the youngsters learn something from this book? Definitely yes. On the other hand, the book will not fix the problems in existing products, but it can help prevent further mistakes.
Top reviews from other countries
What interested me was the idea of deliberating training oneself to be a great designer. This is a new concept. I have just fallen into design. There has been no conscious decision to do design. And then to actively study design.
Up to now, I have not designed any real database systems. I have designed small subsystems mainly to do with searching music titles, storing financial transactions for credit cards, etc. All really conceptually uninteresting, but very challenging in physical implementation. I was more of a carpenter rather than an architect.
Once one has made the decision to become a designer, Brooks suggests that one seek out the best in the field and study their designs. This is extremely difficult to do in the database field because all database designs are hidden away. I know of no published database designs. There are books on database designs but these are recipe books not a diary of what was done and why.
In studying design, Brooks says to concentrate on the constraints the designer worked under, and try to find out what was the conceptual vision they were working towards.
From database designs I have seen to date, not all of the design is in the database. By this, I mean that the rules about object behaviour is sometimes encoded in the application itself not in the constrints explicated in the data dictionary. Some constraints may even be in user behaviour.
Even if you don't always agree with the author, it's worth reading because it will make you think.
[I had a research fellowship for 5 years working in an aspect of design theory, and was a visiting prof at the CMU NSF Engineering Design Centre in 1990 as well as working with the EDC in my own department and visiting MIT and Stanford. So I think I had a pretty broad spread of understanding of the field.]
This book includes case studies you won't find elsewhere on Brooks' house extensions, but these are pretty pallid stuff. I fear it is showing his age in that the disturbing and insightful author of the Mythical Man Month is not in evidence.
One for absolute beginners in studying design process, otherwise something that any decent library should have but few people will read.










