Rating: 
Summary: This book is for college students, not for professionals !
Review: The book is pretty well structured and written for somebody having a little exposure to design. I personally felt I lost my time reading it since I already have some experience in design in another OO language. The book is definitely too much like a school text book. In particular, the chapter on database access with Java concentrates on relational db concepts instead of providing useful design and architectural hints on how to develop a multi tiers application using JDBC !
Rating:
Summary: All about the applet
Review: This book has some good things to say, and it does a fair job explaining some basic designs, but the whole book is based on applets. Every example, every line of code refers to applets. If you're not insterested in applets, or are not interested in applying the applet-based examples to actual real-world code, don't buy this book. If you're into applets and want to know more about basic design patterns this book is for you.
Rating:
Summary: All about the applet
Review: This book has some good things to say, and it does a fair job explaining some basic designs, but the whole book is based on applets. Every example, every line of code refers to applets. If you're not insterested in applets, or are not interested in applying the applet-based examples to actual real-world code, don't buy this book. If you're into applets and want to know more about basic design patterns this book is for you.
Rating: 
Summary: If you are even vaguely familiar with OOAD &Java, forget it!
Review: This book is inaccurate, too simple and does not address patterns in a realistic way at all, essential to successful oo design in my opinion. Just authors out to make a quick buck with a poor quality hardback book and a cd.These days I find it harder and harder to find books as good as the o'reilly series. Whatever you want, you can find much more of it there, than here.
Rating:
Summary: This is anything but a design book
Review: This book tries to be all things, but not Object-Oriented Design in Java. Even some of the examples requires you to download a library from a third party company. Save your money. I recommend you buy "applying UML and Patterns" that will lead you into "Design Patterns" by the gang of 4. P.S. I felt that two starts is being kind.
Rating:
Summary: This is anything but a design book
Review: This book tries to be all things, but not Object-Oriented Design in Java. Even some of the examples requires you to download a library from a third party company. Save your money. I recommend you buy "applying UML and Patterns" that will lead you into "Design Patterns" by the gang of 4. P.S. I felt that two starts is being kind.
Rating: 
Summary: An absolute must-have for serious Java developers
Review: This is a witty, well-organized, thorougly researched and informative work. Not only do the authors do an excellent job of presenting the concepts of software design using solid OO techniques, their introduction to Java (in a chapter only somewhat facetiously titled "Teach Yourself Java in 21 Minutes") is almost certainly the most concise and understandable introduction to the language that I've seen. Every chapter is focused and the flow of material is really excellent. I found myself, as someone who has had years of OO design and development experience, nodding my head repeatedly. And the end of each chapter contains a quiz, some suggested exercises, and a section on where to go for more depth on the subjects covered. As a result, this book would be outstanding for a college-level course or an informal workshop of Java developers who want to learn serious OO design and analysis.
Rating: 
Summary: Add this book to your library.
Review: This is an extremely easy book to read and comprehend. The examples are great. An excellent book for someone wanting to learn OOD.
Rating:
Summary: The BEST book for learning Object-Oriented Design!
Review: This is the best book I have seen yet that truly encapsulates the whole design process in an easy to digest format. The important thing to emphasize is that the design principles that are conveyed here can be applied to anything. I thought I really knew what Object-Oriented Design was until I got this book. This book explains in detail all the requisite information on techniques and tools in implementing good design decisions. This is a 'must-have' book for your reference library.
Rating:
Summary: Not up to snuff
Review: Way too superficial for such a fat book. I don't understand the authors' refusal to use UML. They only use it to illustrate the few design patterns they cover. But my favorite chapter is 14 where they discuss databases. After a micro-blurb on what JDBC is, the authors tell us that a description of using that interface is out of scope of the book. They then proceed to teach us all about relational DB concepts, the building of E-R diagrams, and all about normalization. Somehow, they think that these things are within the scope of OO Design in Java.
| 
