Rating: 
Summary: Strong OOAD & UML
Review: The OOAD & UML content of this book is excellent! The chapters on requirement gathering, use case driven analysis are very good, as well as the discussion of technology selection and software architecture approach. The user's approach is very systematic and practical, showing in-depth understanding and solid experience from real world projects.However, the J2EE technology discussion are relatively light, with some material slightly outdated. Also, there is no discussion of JSP - an important J2EE presentation tier technology - at all. Considering the book is published well after JSP was released, this is definitely a major pitfall. Overall, the book is worth reading, even just for the requirement and analysis part!
Rating:
Summary: A powerful case for analysis/design before coding
Review: The two strengths of this book are showing object-oriented analysis and design - UML centered - for a simple enterprise problem and making powerful cases for doing analysis and design using use cases, sequence diagrams and class diagrams before jumping into the code. The diagrams have value for explaining a software system to people who are not proficient in the implementation language.
The UI piece of the problem is handled by a clever abstract factory solution instead of using JSP. It seems the modern movement is toward prototyping by business analysts using Frontpage or Dreamweaver, or such, and then refactoring the pages with JSP. I'm not sure everyone would want to abstract the HTML the way the book does.
It seems that publishers are getting a little lazy; there are some typographical problems that a person who passed high school English should catch. There are some phrases that are repeated too much and should have been re-worded or removed as well.
Although it is not an easy subject, this book will point the developer down the right direction and give her or him plenty to think about.
Rating: 
Summary: An excellent UML-centric resource for Java architects
Review: This book is an excellent resource for advanced Java architects and developers trying to learn the UML paradigm. It weeds out the UML that you dont want to know and concentrates on Java-applicable UML. As the title itself specifies, this is neither for non-Java readers nor for those Enterprise Java developers who don't need UML. All technologies related to Enterprise Java are here: EJB, XML, CORBA, RMI-IIOP and Servlets.
Rating:
Summary: Excellent.... but... no jsp
Review: This book is excellent for modelling Enterprise Java with UML. I am still a student and my experience (or lack thereof) is still all theoretical but I found the introduction to object modelling (chapter 4) VERY USEFUL and somewhat better than my classes on the same topic! This title however, does not cover JSP (JavaServer Pages) and as such the presentation tier is mostly focussed on servlets and has a lot of information (possibly obsolete now) on HTTP production classes. I found the modelling methods/guides for EJBs extremely useful and still haven't found the same information elsewhere. Overall an easily read and understood book.
Rating:
Summary: Good book with a few errors.
Review: This book is fairly good to treat J2EE and UML. However, there are some mistakes in the book: 1)Page 11, * should mean 0 or more. So, "Each person object may be associated with several Car objects" is wrong, should be " 0 or more Car objects". According to the OMG UML 1.4 specificaiton ..., seciton 3.44: "If the multiplicity specification comprises a single star (*), then it denotes the unlimited nonnegative integer range, that is, it is equivalent to 0..* (zero or more)." 2) Page 52, fig 3.2 is WRONG! It has only join, no fork. In an UML diagram, the fork and join must be paired! According to Rational Rose 2002 help: "Every fork that appears on an activity diagram should ideally be accompanied by a corresponding join. ". Besides these errors, I think it is a good book. Thanks, David Zuo.
Rating: 
Summary: Bad definitions but good case study.
Review: This book is very weak in defining basic UML and OO concept in the first chapter. It has bad definition for concepts such as "classes and relationships". Its definition of some of OO concept is hard to grasp for new comers to this field. At first I was going to use this book for some of the in house classes that I teach. Now I have decided to use it in conjunction with other books, since I am very pleased with its case study. If we fail to have a good basic definition and miss points in definitions of such concepts as Relationships between objects, then we cannot really provide a book that can be exclusively used for learning a concept such OO and the UML in enterprise Java. My suggestion to the writer is to omit the first chapter or rewrite it.
Rating:
Summary: Excellent Book for OO Analysis
Review: This book takes you through the development of an application from proposal to implementation. In alternating chapters the authors explain the use of UML for a particular step in the development lifecycle and then demonstrate what they just explained to develop a sample timecard system. The best part of the book, which is not significantly different than the first edition, is the first half in which the authors discuss requirements gathering and object oriented analysis. The book is worth the price for this first part alone. The second half of the book has been expanded to discuss new J2EE technologies. The chapters on evaluating technologies are good as far as discussing how to evaluate technologies but the actual analysis is weak as they ignore candidate technologies such as Struts in favor of their own homegrown HTML production framework. They also fail to explain why EJBs are a better choice for their sample application than simply using Servlets/JSPs/JDBC. The final section on design gets bogged down with too many pages of code listings and not enough explanations for the code. Arrington and Rayhan have done a very good job explaining UML although some familiarity with UML notation (or at least a handy manual) would be helpful. If you already own the first edition then you can ignore this edition. If you don't own it then you will definitely want to read this book. This is a must have book for any Java architect/developer doing OOAD.
Rating:
Summary: Excellent Book for OO Analysis
Review: This book takes you through the development of an application from proposal to implementation. In alternating chapters the authors explain the use of UML for a particular step in the development lifecycle and then demonstrate what they just explained to develop a sample timecard system. The best part of the book, which is not significantly different than the first edition, is the first half in which the authors discuss requirements gathering and object oriented analysis. The book is worth the price for this first part alone. The second half of the book has been expanded to discuss new J2EE technologies. The chapters on evaluating technologies are good as far as discussing how to evaluate technologies but the actual analysis is weak as they ignore candidate technologies such as Struts in favor of their own homegrown HTML production framework. They also fail to explain why EJBs are a better choice for their sample application than simply using Servlets/JSPs/JDBC. The final section on design gets bogged down with too many pages of code listings and not enough explanations for the code. Arrington and Rayhan have done a very good job explaining UML although some familiarity with UML notation (or at least a handy manual) would be helpful. If you already own the first edition then you can ignore this edition. If you don't own it then you will definitely want to read this book. This is a must have book for any Java architect/developer doing OOAD.
Rating:
Summary: One niggle
Review: This is a good introductory book for UML in general. My one complaint is in the handling of the diagrams. Whoever put the book together was loathe to put any diagrams in the middle of pages, so they are all at the top or bottom of a page; consequently they are sometimes in the wrong place - in the middle of a previous section, on another page, or some other odd place.
Rating:
Summary: Great first UML book for a Java developer
Review: This is a very good book for someone who has a worked with java at the developer level and is thinking about making the jump to the architect level. Arrington is an experienced teacher and his teaching proficiency shows all along the book. His style is very clear and sometimes repetitive, but that makes sure you get the idea through.
Being a "hands on type of guy" I like the fact that the book explains the theory in the context of developing and example application.
The UML & Object Oriented Analysis section of the book is truly outstanding, while the implementation part leaves a bit to be desired. It is also outdated as it still uses HTML production classes inside Servlets and not JSP. The second edition should fix this.
Overall the best book on UML for a Java developer I have read so far.
| 
