( 4 reviews )
-
( 2 of 2 found this review helpful ) Posted: May 24 2002
You are already into various Java technologies likeServlets, JDBC, EJBs and can put together asmall to medium application/project using those.You somehow implemented the project/app to satisfy the requirements but you are thinkingthat there has to be a better way of going froma set of requirements to a design (from which the leap to actual coding is smooth) without feeling likesome vague unrepeatable 'magic' was being done.You want to formalize the process of jumping from the'analyze' phase to a 'Object oriented design' phase (thatresults in sequence/collaboration diagrams etc) butwithout being encumbered by an elaborate and complexmethodology.You want this process to be small, easy to understandand flexible so that you can adapt it to your needs.If the above applies, you should seriously considerinvesting in this book.The Authors use the often used bookstore example to drive home the process which starts with writing usecases and ends with a detailed design that satisfies all theuser's requirements.A list of 10 common mistakes made during each step ofthe process can be used as a reference when you aredone understanding the process and are actually applyingit in your projects.Paul Reed's Application Development with Java and UMLmakes a good complement to this book, thoughConallen uses a modified but still complex enough form of Rational Unified Process (RUP) in his book.
-
( 4 of 8 found this review helpful ) Posted: Jan 16 2002
I was excited about this book when I bought it online. Now that I read it, I am not very happy. The authors could have drilled deeper into some examples of how to implement the application using some wide spread technology like Java or ASP and COM. Giving concrete examples of what a Boundary Object should be, or what classes make sense to implement to interact with databases, just to mention a few, would have been very helpful. I also found "the top ten error" method very tiresome (I often skipped it and went straight to the right ways of doing things). The book was helpful though in providing a guide of what steps to follow in the design process as well as giving us a good idea on how to break the project into objects and diagrams.
-
( 17 of 17 found this review helpful ) Posted: Aug 3 2001
Okay. I became interested in the lightweight Iconix process after a series of 5 articles in Software Development magazine, so I went out and bought the first book "Use case driven object modeling with UML - a practical approach". I design community based web portal applications. Our applications are medium-sized, but complex. So RUP is too big, and XP is too small. The Iconix process presented here is about right for most of our applications, and to satisfy client expectations for design.The first book is more theoretical. This one has better, more complete, illustrative examples. There is some repetition between the two, but no pages are taken up by code. Like the first book, it is easy to read.If you work in web development, read Conallen's "Building web applications with UML" also. The books complement each other well. (See my review)
