SPECIAL OFFERS
Keep up with new releases and promotions. Sign up to hear from us.
Register your product to gain access to bonus material or receive a coupon.
In this first-ever use case workbook, proven authors Doug Rosenberg and Kendall Scott help developers and analysts put their use case knowledge to the test, in real-world projects. A perfect companion to the authors' breakthrough Use Case Driven Modeling with UML -- or any other introductory guide to use cases -- this book offers systematic hands-on practice in implementing use cases, based on the authors' unparalleled experience in teaching working developers. This workbook dissects the design of an Internet bookstore, step-by-step, in exceptional detail -- showing common mistakes in building use cases, and how the models look once they've been corrected. The authors provide hands-on practice with every aspect of use case development with UML, including requirements review, domain modeling, use case modeling, preliminary design review, robustness analysis, sequence diagrams, critical design review, and more. The book also contains five valuable "Top 10" lists, including lists of errors in robustness analysis and sequence diagramming. For all systems analysts, software architects, software engineers, and developers interested in working with UML or strengthening their current UML skills.
Click below for Sample Chapter related to this title:
rosenbergch16.pdf
Preface.
Practice.
The Premise.
Acknowledgments.
A Walk (Backwards) through the ICONIX Process.
Key Features of the ICONIX Process.
Process Fundamentals.
The Process in a Nutshell.
Requirements List for The Internet Bookstore.
The Key Elements of Domain Modeling.
The Top 10 Domain Modeling Errors.
Exercises.
Bringing the Pieces Together.
The Key Elements of Use Case Modeling.
The Top 10 Use Case Modeling Errors.
Exercises.
Bringing the Pieces Together.
The Key Elements of Requirements Review.
The Top 10 Requirements Review Errors.
The Key Elements of Robustness Analysis.
The Top 10 Robustness Analysis Errors.
Exercises.
Bringing the Pieces Together.
The Key Elements of Preliminary Design Review.
The Top 10 PDR Errors.
The Key Elements of Sequence Diagrams.
Getting Started with Sequence Diagrams.
The Top 10 Sequence Diagramming Errors.
Exercises.
Bringing the Pieces Together.
The Key Elements of Critical Design Review.
The Top 10 CDR Errors.
In our first book, Use Case Driven Object Modeling with UML, we suggested that the difference between theory and practice was that in theory, there is no difference between theory and practice, but in practice, there is. In that book, we attempted to reduce OOAD modeling theory to a practical subset that was easy to learn and pretty much universally applicable, based on our experience in teaching this material to people working on hundreds of projects since about 1993.
Now, two years after hitting the shelves, that book is in its fifth printing. But even though our work has been favorably received, it seems like the job isn't all the way done yet. "We need to see more use case and UML modeling examples" is a phrase we've been hearing fairly often over the last couple of years. And, as we've used the first book as the backbone of training workshops where we apply the theory to real client projects, it has become clear that the process of reviewing the models is critically important and not well understood by many folks.
So, although we present a fairly extensive example in our first book, we convinced Addison-Wesley to let us produce this companion workbook, in which we dissect the design of an Internet bookstore, step-by-step, in great detail. This involves showing many common mistakes, and then showing the relevant pieces of the model with their mistakes corrected. We chose an Internet bookstore because it's relevant to many of today's projects in the Web-driven world, and because we've been teaching workshops using this example and, as a result, had a rich source of classroom UML models with real student mistakes in them.
We collected some of our favorite mistakes--that is, the kind of mistakes we saw getting repeated over and over again--and built this workbook around those models. And then we added three new chapters about reviews--one on requirements reviews, one on preliminary design reviews, and one on critical design reviews.
What really makes this book unique, though, is the fact that you, the reader, get to correct the mistakes.
After we give you an overview of the ICONIX process in Chapter 1, four of the seven subsequent chapters address the four key phases of the process in some detail. The format of each of these chapters is as follows:
The following aspects are common to each set of exercises:
Your task is to write corrections on each "bad" exercise page before you flip it over to see the "good" exercise diagram.
To summarize: Chapter 2 presents classes used by the ten sample use cases. Chapter 3 presents fragments from all of those use cases. Chapters 5 and 7 present diagrams connected with five of the use cases. The idea is that you'll move from a partial understanding of the use cases through to sequence diagrams that present full text, and some of the associated elements of the detailed design, for each use case.
What about the other three chapters, you ask?
All three of these review chapters offer overviews, details, and top 10 lists, but we don't make you work any more exercises. What these reviews have in common is the goal of ensuring consistency of the various parts of the model, as expressed on the "good" exercise diagrams.
The Appendix contains a report that summarizes the model for the bookstore; you can download the full model from http://www.iconixsw.com/WorkbookExample.html. The Appendix contains all of the diagrams that appear in the body of the book, but the full model includes design details for the other five use cases. This allows you to go through these use cases as further exercises, and then compare your results to ours; we highly recommend that you do this.
Cool premise, isn't it? We're not aware of another book like this one, and we're hoping you'll find it useful in your efforts to apply use case driven object modeling with UML.
Doug would like to thank his intrepid crew at ICONIX, especially Andrea Lee for her work on the script for the Inside the ICONIX Process CD, which we borrowed heavily from for Chapter 1, along with Chris Starczak, Jeff Kantor, and Erin Arnold. Doug would also like to thank Kendall for (finally) agreeing that yes, this would make the book better, and yes, we do have time to add that, and yes, the fact that R comes before S does mean that Mr. Rosenberg has more votes than Mr. Scott. Co-author's note to self: Get name legally changed to Scott Kendall before the next book comes out. That'll teach him.
Doug and Kendall would like to thank Paul Becker and all the fine folks at Addison-Wesley (including Ross Venables, who's no longer there but who got this project off the ground) who somehow managed to compress the production schedule to compensate for the delays in the writing schedule (which are all Kendall's fault). We'd also like to thank the reviewers of the manuscript, especially Mark Woodbury, whose incisive comments about "defragmenting" the example gave us the push we needed to get it the point where we think it's really, really cool as opposed to just really cool. And, we'd like to thank Greg Wilson, who reviewed our first book for Dr. Dobbs' Journal, liked it, and suggested that we write a companion workbook. Specifically, he said: "The second criticism of this book is one that I thought I'd never make: It is simply too short. Having finally found a useful, readable, and practical description of a design-centered development methodology, I really wanted a dozen or more examples of each point to work through. If the authors were to produce a companion workbook, I can promise them that they'd have at least one buyer."
Finally, Kendall would like to thank Doug for raising the art of snarkiness to a level that makes Kendall look like a paragon of good cheer in comparison to Doug.
Santa Monica, CaliforniaHarrison, Tennessee
dougr@iconixsw.comkendall@usecasedriven.com
http://www.iconixsw.comhttp://www.usecasedriven.com