Enhanced descriptions from Syndetics:

Applied Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example provides a practical, hands-on guide to putting use case methods to work in real-world situations. This companion workbook to Use Case Driven Object Modeling with UML bridges the gap between the theory presented in the authors' first book, and the practical issues involved in the development of an internet/e-commerce application.

Uniquely conceived as a workbook, featuring an e-commerce system for an on-line bookstore as a running example, the book dissects its design in detail, demonstrates the most common design mistakes, and reveals the correct solutions. The hands-on exercises give you the opportunity to detect, identify, and correct critical errors on your own, before reviewing the solutions provided in the book.

The workbook is structured around the proven ICONIX Process, a streamlined approach to UML modeling designed to avoid analysis paralysis without skipping analysis and design. It presents the four key phases of this minimalist approach to use case driven design: domain modeling; use case modeling; robustness analysis; and sequence diagramming. For each of these topics, the book provides an overview, detailed discussion, top 10 mistakes, and a set of exercises for honing object modeling and design skills.

Another unique aspect of this book is the three chapters on reviews. The authors devote a chapter each to requirements review; preliminary design review; and critical design review. This focus on "designing quality in" by teaching how to review UML models fills a major gap in the published literature.

The book shows you, by example, how to avoid more than 70 specific design errors as shown in the "Top 10" error lists on the inside covers and within each chapter. With the information, examples, and exercises in this book, you will develop the knowledge and skills you need to apply use case modeling more effectively to your next application.

0201432897B04302001

Table of contents provided by Syndetics

• Figures (p. ix)
• Analysis Paralysis Alerts (p. xi)
• Top 10 Lists (p. xiii)
• Preface (p. xv)
• Chapter 1 The ICONIX Unified Object Modeling Approach (p. 1)
• Background (p. 3)
• Introduction to the Approach (p. 5)
• Thoughts on Methodology (p. 8)
• Process Fundamentals (p. 9)
• The Approach in a Nutshell (p. 11)
• Chapter 2 Domain Modeling (p. 15)
• Discover Classes (p. 17)
• Build Generalization Relationships (p. 21)
• Build Associations Between Classes (p. 23)
• Develop Association Classes (p. 26)
• Mine Your Legacy Documentation for Domain Classes (p. 27)
• Draw an Analysis-Level Class Diagram (p. 32)
• Continue to Iterate and Refine (p. 33)
• Chapter 3 Use Case Modeling (p. 37)
• Use Cases, Actors, and Use Case Diagrams (p. 38)
• Analysis-Level and Design-Level Use Cases (p. 40)
• Writing Use Cases (p. 40)
• Working Inward from a GUI to Identify Use Cases (p. 41)
• Mining Your Legacy User Manuals for Use Cases (p. 45)
• Refining Use Cases (p. 46)
• Basic and Alternate Courses of Action (p. 47)
• Factoring Out Commonality in Usage (p. 49)
• Constructs from the UML and OML (p. 49)
• Back to Our Example (p. 51)
• Use Case Packages (p. 55)
• Use Cases and Requirements (p. 56)
• Wrapping Up Use Case Modeling (p. 57)
• Chapter 4 Robustness Analysis (p. 61)
• Key Roles of Robustness Analysis (p. 63)
• Sanity Check (p. 63)
• Completeness Check (p. 64)
• Object Identification (p. 65)
• Preliminary Design (p. 65)
• More About Robustness Analysis Object Types (p. 66)
• Performing Robustness Analysis (p. 67)
• Updating Your Domain (Static) Model (p. 74)
• Wrapping Up Robustness Analysis (p. 78)
• Chapter 5 Interaction Modeling (p. 81)
• Goals of Interaction Modeling (p. 82)
• Sequence Diagrams (p. 84)
• Getting Started (p. 85)
• Putting Methods on Classes (p. 93)
• Examples (p. 96)
• Updating Your Static Model (p. 100)
• Finalizing Attributes and Methods (p. 101)
• Ensuring Quality (p. 102)
• Adding Infrastructure (p. 103)
• Patternizing Your Design (p. 104)
• Back to the Example (p. 104)
• Completing Interaction Modeling (p. 105)
• Chapter 6 Collaboration and State Modeling (p. 109)
• When Do We Need Collaboration Diagrams? (p. 110)
• State Diagrams (p. 113)
• How Many State Diagrams Do We Need? (p. 113)
• Activity Diagrams (p. 116)
• Extending Interaction Modeling (p. 117)
• Chapter 7 Addressing Requirements (p. 121)
• What Is a Requirement? (p. 122)
• The Nature of Requirements, Use Cases, and Functions (p. 123)
• Requirements Traceability (p. 126)
• Extending a Visual Modeling Tool to Support Requirements (p. 128)
• Requirements and the ICONIX Approach (p. 129)
• Getting Ready to Code (p. 130)
• Chapter 8 Implementation (p. 135)
• Project Staffing Issues (p. 136)
• Project Management (p. 137)
• Revisiting the Static Model (p. 138)
• Allocating Classes to Components (p. 139)
• Code Headers (p. 139)
• Testing (p. 142)
• Metrics (p. 143)
• Tracking Use Case Driven Development (p. 146)
• Wrapping Up (p. 147)
• Appendix: "Uses" vs. "Extends" (p. 149)
• Bibliography (p. 157)
• Index (p. 159)

Excerpt provided by Syndetics

Theory, in Practice 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's 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. The Premise 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 first part describes the essence of domain modeling (Chapter 2), use case modeling (Chapter 3), robustness analysis (Chapter 5), or sequence diagrams (Chapter 7), and places the material in the context of the "big picture" of the process. The next section describes the key elements of the given phase. Each of these sections is basically a condensed version of an associated chapter in Use Case Driven Object Modeling with UML, with some new information added within each chapter. The following section describes the top 10 mistakes that our students tend to make during workshops where we teach the process. We've added five new Top 10 lists in this book: Top 10 robustness analysis errors, Top 10 sequence diagramming errors, and Top 10 mistakes to avoid for each of the three "review" chapters. The final section presents a set of five exercises for you to work, to test your knowledge of the material in the chapter. The following aspects are common to each set of exercises: There's a red box, with a red label, at the top of each right-hand page. For the domain modeling and use case exercises, this label takes the form Exercise X; for the robustness analysis and sequence diagram exercises, the label takes the form of a use case name. (We'll explain the significance of this soon.) There are three or four mistakes on each right-hand page. Each mistake has a "Top 10" logo next to it that indicates which rule is being violated. The left-hand page on the flip side of each "red" page has a black box, with a black label, at the top. Corrections to the errors presented on the associated "bad" page are explicitly indicated; explanations of the mistakes appear at the bottom of the page. Your task is to write corrections on each "bad" exercise page before you flip it over to see the "good" exercise diagram. Chapter 2 presents classes used by 10 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? Chapter 4 describes how to perform requirements review, which involves trying to ensure that the use cases and the domain model work together to address the customers' functional requirements. Chapter 6 describes how to perform preliminary design review (PDR), which involves trying to ensure that robustness diagrams exist for all use cases (and are consistent with those use cases), the domain model has a fairly rich set of attributes that correspond well with whatever prototypes are in place (and all of the objects needed by the use cases are represented in that model), and the development team is ready to move to detailed design. Chapter 8 describes how to perform critical design review (CDR), which involves trying to ensure that the "how" of detailed design, as shown on sequence diagrams, matches up well with the "what" that the use cases specify, and that the detailed design is of sufficient depth to facilitate a relatively small and seamless leap into code. All three of these 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 wraps things up in a nice bow by offering a report that shows the "good" model in its entirety--all of the class diagrams, use case text, robustness diagrams, and sequence diagrams represented in the body of the book, plus some other stuff too. 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. 0201432897P04302001 Excerpted from Use Case Driven Object Modeling with UML: A Practical Approach by Doug Rosenberg, Kendall Scott All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Author notes provided by Syndetics

Doug Rosenberg, founder and president of ICONIX, has been teaching use case driven object modeling using a Unified Jacobson/Booch/Rumbaugh approach since 1992, several years before the advent of UML. His acclaimed CD-ROM tutorials, including "Complete CORBA," "Mastering UML with Rational Rose," and "A Unified Object Modeling Approach" are in widespread use in more than 40 countries. He has taught object modeling using UML at dozens of companies including Boeing, Duke Power, Hughes, JC Penney, Lockheed-Martin, Lucent, Motorola, NASA, and Philip Morris. He has also written numerous articles for a variety of publications, including Object Magazine, Software Development, and Rose Architect.
Kendall Scott, the supporting author of the award-winning book UML Distilled (with Martin Fowler, Addison-Wesley, 1997), is a technical writer who specializes in writing about financial and accounting applications. He is the principal of Software Documentation Wizards.