<< 1 >>
Rating: 
Summary: Impudently clear!
Review: A developer who doesn't know a process, doesn't know what he/she is missing. A developer who doesn't know UML risks to be relegated to fill rows of code on a structure of classes and methods designed by others.
This book teaches a simple and effective process, and indirectly UML too. UML is like any other languages: one cannot learn it without using it in practice.
The authors are teachers, and this gives a big edge to the book, for their ability to anticipate reader's difficulties and common errors.Even if I actually use Catalisys process, tailored for components (see UML Components, Cheesman and Daniels), simply I can't immagine to be where I am without having read this book at the beginning.
Rating:
Summary: Learn object modeling by example with solution
Review: All of the different jobs found in software development are learned in two ways. Either through trial and error on the job or by working through examples. The first is the most effective, but by far the most expensive. While the second is less thorough, it is cheaper and reduces the cost when you make the inevitable move to the first. Since object modeling is always open to many differing interpretations, learning how to create and use them has a slow learning curve. The best approach to learning how to model objects is to find and plow through detailed, complete examples, which of course presupposes that such examples exist. Well, they do and some of the best are found in this book.
The approach is one that maximizes the teaching effectiveness. An Internet bookstore project is created from the beginning. It is large enough to be instructive yet not so large that it becomes unwieldy. The authors then take you through the sequence of steps:
1) Domain Modeling, 2) Use Case Modeling, 3) Requirements Review, 4) Robustness Analysis, 5) Preliminary Design Review, 6) Sequence Diagrams, and 7) Critical Design Review.
What is different about this book is that after the explanation of the development stage, there is a top ten list of common errors made in that stage followed by an example described in UML. The UML diagram includes some of the errors in the list and they are pointed out and explained. This really drives the point of the error home.
The book is a distillation of the experience of the authors as they built a comparable system. They documented the complete process via videotape and then distilled their actions, including errors, down to the material in the book. This has led to some very good examples of how to model development at all stages and will certainly help you avoid some of the most common pitfalls as you make the treacherous, exhaustive and gratifying move from idea to product.
Rating: 
Summary: Pricey for what it provides
Review: 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.
Rating:
Summary: A practical follow-up
Review: 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)
Rating: 
Summary: An expense that can be justified.
Review: You are already into various Java technologies like
Servlets, JDBC, EJBs and can put together a
small to medium application/project using those. You somehow implemented the project/app to
satisfy the requirements but you are thinking
that there has to be a better way of going from
a set of requirements to a design (from which the leap to
actual coding is smooth) without feeling like
some vague unrepeatable 'magic' was being done. You want to formalize the process of jumping from the
'analyze' phase to a 'Object oriented design' phase (that
results in sequence/collaboration diagrams etc) but
without being encumbered by an elaborate and complex
methodology. You want this process to be small, easy to understand
and flexible so that you can adapt it to your needs. If the above applies, you should seriously consider
investing 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 the
user's requirements. A list of 10 common mistakes made during each step of
the process can be used as a reference when you are
done understanding the process and are actually applying
it in your projects. Paul Reed's Application Development with Java and UML
makes a good complement to this book, though
Conallen uses a modified but still complex enough form
of Rational Unified Process (RUP) in his book.
<< 1 >>
| 
