Now available - a companion
Use-Case Driven Object Modeling with UML - An Annotated E-Commerce
"If you liked 'Object
Oriented Software Engineering', you'll like this book." -- Ivar Jacobson
Today, software practitioners are faced with the cold, hard reality that there is seldom enough time to properly model an impending project. Even with the widespread acceptance of the Unified Modeling Language (UML), proper modeling is often not completed because aggressive schedules make this practice difficult. The book presents a streamlined approach to UML modeling that includes a minimal but sufficient set of diagrams and techniques that you can use to get from use cases to code quickly and efficiently.
Read a review of the book from Dr. Dobbs.
I got a copy of "Use Case Drive Object Modeling." I will be buying several more copies for my team. As the project leader, I have been looking for a "Process" that we can follow, evaluate, and later tune if need be. The process described in "Use Case Driven Object Modeling with UML" looks like what we will follow." -- Charlie Wilson, Staff Software Engineer, Sequent Computer Systems
"Use Case Driven Object Modeling with UML" provides practical guidance that will allow developers to produce UML models quickly and effeciently, while maintaining the important traceability from user requirements through detailed design and coding. The authors borrow from extensive industry experience to present proven methods to drive the object modeling process forward from use cases in a simple and straightforward manner.
Click here to view the Table of Contents
Click here to view the Preface
Click here to view a list of Figures
Click here to view the Top 10 Lists
Click here to view the Analysis Paralysis Alerts
Click here to download the Rose Model example
"The authors have presented a process for developing applications using object oriented technologies that is as close as possible to a 'cookie cutter' recipe as you'll find. The 'cookie cutter' process is the Holy Grail of development processes, destined never to be achieved, yet it drives us in the direction of even more predictable software development." -- Jim Conallen, CTO, Clarity Development, LLC.
Comments from Doug Rosenberg
Comments from Kendall Scott