Rating: 
Summary: Best book for the Java Design
Review: First of all it defines the UML through the view of Java language and it emphasizes the UML that most of the architects and developers would use.
It has a little bit too much of why the developers should use UML and if it is an individual versus team aproach but other than that it cleary defines the class and packages principles. The whole book is guided by these.
Definitely a book to buy.
Rating:
Summary: AGILE application of Objects, UML, and Process
Review: I came across this book after reading The Elements of UML Style's Bibliography by Scott W. Ambler who is a founder and thought leader on the Agile Modeling methodology. I thought it might explain a different way to do OOAD using UML compared to books written by Craig Larman. Not really.But the surprise to me was how agile it made the use of OO, UML, and process. The title should be: Agile Java Design Objects, UML, and Process. This only the book that I have read that made me feel confident about using RUP and how it's use should not slow down the process. While I have read other UML modeling books, none of them made it clear to not get hung up on every detail in each iteration. The book is shorter some of other UML OO books and this adds to its agility. It directs you to get through the process more quickly and to not lose sight of the end goal. Here's a nugget: "However, even more important is satisfying use requirements in the allotted time frame. Don't spend a lot of time trying to find the best solution the first time. Instead, find something that works and continue to refine and improve that system throughout the development effort." Also, the book has numerous best practices and best-of-breed technologies on object-oriented analysis and design that I have not read in any other books. For example, while it emphasizes that architecture plays a key role, it says it is advantageous to use UML to obtain feedback from peers and mentors, and to develop throwaway prototypes as Frederick Brooks recommended in the Mythical Man-Month to contribute to a more resilient, robust, and flexible final product. The bottom-line surprise was that this book helped me guage the appropriate level of detail for an software architecture document and tells why reverse-engineering source is inappropriate for this. As Kirk writes, "We should be cautious when producing detailed, low-level diagrams because they risk becoming outdated as our internal code structure changes. Instead, higher-level, architecturally signficant diagrams should be created that communicate our architecture and solve complex architectural challenges. In general, our golden rule should be to produce any artifact only if it contributes positively to the development of better software."
Rating:
Summary: AGILE application of Objects, UML, and Process
Review: I came across this book after reading The Elements of UML Style's Bibliography by Scott W. Ambler who is a founder and thought leader on the Agile Modeling methodology. I thought it might explain a different way to do OOAD using UML compared to books written by Craig Larman. Not really. But the surprise to me was how agile it made the use of OO, UML, and process. The title should be: Agile Java Design Objects, UML, and Process. This only the book that I have read that made me feel confident about using RUP and how it's use should not slow down the process. While I have read other UML modeling books, none of them made it clear to not get hung up on every detail in each iteration. The book is shorter some of other UML OO books and this adds to its agility. It directs you to get through the process more quickly and to not lose sight of the end goal. Here's a nugget: "However, even more important is satisfying use requirements in the allotted time frame. Don't spend a lot of time trying to find the best solution the first time. Instead, find something that works and continue to refine and improve that system throughout the development effort." Also, the book has numerous best practices and best-of-breed technologies on object-oriented analysis and design that I have not read in any other books. For example, while it emphasizes that architecture plays a key role, it says it is advantageous to use UML to obtain feedback from peers and mentors, and to develop throwaway prototypes as Frederick Brooks recommended in the Mythical Man-Month to contribute to a more resilient, robust, and flexible final product. The bottom-line surprise was that this book helped me guage the appropriate level of detail for an software architecture document and tells why reverse-engineering source is inappropriate for this. As Kirk writes, "We should be cautious when producing detailed, low-level diagrams because they risk becoming outdated as our internal code structure changes. Instead, higher-level, architecturally signficant diagrams should be created that communicate our architecture and solve complex architectural challenges. In general, our golden rule should be to produce any artifact only if it contributes positively to the development of better software."
Rating:
Summary: Full of Helpful Principles
Review: I found this book tremendously helpful. It is full of programming principles which immediately helped me with a project I was working on.
I thought the approach of the book was excellent. The well-written merging of Java design topics put me in a beneficial mind-set. I believe I avoided several architectural mistakes because of this book.
I took a Systems Analysis and Design class a year ago. I feel this book helped me make several connections between that course work and the books I have read that cover just the basics of Java syntax.
Rating:
Summary: The author has got it just right
Review: I've just finished reading this book (in 3 days!) and it has been extremely helpful. I'm a relatively inexperienced OO programmer, but this book has vastly improved my design skills. It is the first book I've actually read about OO, I only decided to read it because I needed help designing my simulation project for school. The author focuses on the main principles of OO (which I was naive to before reading), and only uses the UML and specific software processes when appriopriate. He emphasizes that new technologies and design patterns should only be used if it truly brings benefit to your project, and ultimately it is the final product that is most important. Everything I was reading I kept trying to relate to my current project, and I've already started to see my system's architecture improve. Highly recommended!
Rating:
Summary: For programmers who has mastered the basics of Java
Review: Java Design: Objects, UML, And Process by software is consultant and Java expert Kirk Knoernschild a comprehensive computer programmer's reference for the creation of high quality, useful, reusable, and long-lasting software designs. Individual chapters cover the basics of UML, modeling strategies, analyzing problems, designing subsystems and much more. Java Design: Objects, UML, And Process is a superbly organized and presented reference for programmers who has mastered the basics of Java and are ready to broaden their applied skills and expertise in the robust, highly practical, and increasingly popular computer language of Java.
Rating: 
Summary: The content of the book is the same as others
Review: May be I am too serious in this book.
But tell the truth,the author just
only show his "word game" like some
other authors.
In his writing style,he never gives
a consideration to his readers' reading
ability. What he want to do is to display
how a great philologist he is.
So when you buy the book you will get a
good writing skill , not software
technical skill.
Rating:
Summary: The content of the book is the same as others
Review: May be I am too serious in this book.
But tell the truth,the author just
only show his "word game" like some
other authors.
In his writing style,he never gives
a consideration to his readers' reading
ability. What he want to do is to display
how a great philologist he is.
So when you buy the book you will get a
good writing skill , not software
technical skill.
Rating:
Summary: Excellent Book on Java Design and OO Design in general
Review: The first chapter alone was worth the price. Though I've been involved in Java and OO for sometime, the academics of it have escaped me. This book enabled me fill the holes in the OO/Java fundamentals necessary to build resilient systems. The author does a nice job tying in the first chapter to the rest of the book and reiterating the important elements. Don't expect an easy read! This material is pretty heavy stuff. However, when you've finished, you will have learned (instead of just read) some important OO concepts in the context of Java.
Rating:
Summary: Be prepared to improve your system!
Review: The first chapter alone was worth the price. Though I've been involved in Java and OO for sometime, the academics of it have escaped me. This book enabled me fill the holes in the OO/Java fundamentals necessary to build resilient systems. The author does a nice job tying in the first chapter to the rest of the book and reiterating the important elements. Don't expect an easy read! This material is pretty heavy stuff. However, when you've finished, you will have learned (instead of just read) some important OO concepts in the context of Java.
| 
