Applying Use Case Driven Object Modeling with UML: An Annotated E-Commerce Example

by Kendall Scott and Doug Rosenberg

Book Overview

Applying Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example is a practical, hands-on guide to putting use case methods to work in real-world situations. This workbook is a... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0201730391
• ISBN13: 9780201730395
• Release Date: January 2001
• Publisher: Addison-Wesley Professional
• Length: 176 Pages
• Weight: 1.50 lbs.
• Dimensions: 0.4" x 8.1" x 9.9"

Customer Reviews

An expense that can be justified.

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.

A practical follow-up

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)

Learn object modeling by example with solution

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.