Gilberto Flores V said
When we introduce students in the complex world of modeling application with java and UML, we need a material that shows the students how to do the things in an applicable and real way. I can tell that this book is the book that all the java software Engineriers must have. In this book we find the anwers of how we can obtain good requirements using use cases, we understand the basics of the architecture of any application, and we can map the UML concepts with the the Java technology.
Thomas Paul said
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.
Riccardo Audano said
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.
Anonymous said
The flow is good.
Has been written in real layman terms which is good.
I read it in one sitting at a store before and then bought it.
(took me 4 hrs to read...)
Like one reviewer said there are a few mistakes...
But that doth not make this book bad at all.
An excellent buy....it will be a ref for a loooong time to come.
David Zuo said
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.
Comments