کاربرد موارد استفاده: راهنمای عملی (ویرایش دوم)

Use case analysis is a methodology for defining the outward features of a software system from the user's point of view. Applying Use Cases, Second Edition, offers a clear and practical introduction to this cutting-edge software development technique. Using numerous realistic examples and a detailed case study, you are guided through the application of use case analysis in the development of software systems. This new edition has been updated and expanded to reflect the Unified Modeling Language (UML) version 1.3. It also includes more complex and precise examples, descriptions of the pros and cons of various use case documentation techniques, and discussions on how other modeling approaches relate to use cases. Applying Use Cases, Second Edition, walks you through the software development process, demonstrating how use cases apply to project inception, requirements and risk analysis, system architecture, scheduling, review and testing, and documentation. Key topics include: Identifying use cases and describing actors Writing the flow of events, including basic and alternative paths Reviewing use cases for completeness and correctness Diagramming use cases with activity diagrams and sequence diagrams Incorporating user interface description and data description documents Testing architectural patterns and designs with use cases Applying use cases to project planning, prototyping, and estimating Identifying and diagramming analysis classes from use cases Applying use cases to user guides, test cases, and training material An entire section of the book is devoted to identifying common mistakes and describing their solutions. Also featured is a handy collection of documentation templates and an abbreviated guide to UML notation. You will come away from this book with a solid understanding of use cases, along with the skills you need to put use case analysis to work. Cover......Page 1 Contents......Page 6 Foreword......Page 12 Preface to Second Edition......Page 14 Preface......Page 16 Chapter 1 Getting Started......Page 18 An Iterative Software Process......Page 19 An Example Project......Page 20 The Project Description......Page 21 Starting Risk Analysis......Page 23 Chapter Review......Page 27 Chapter 2 Identifying System Boundaries......Page 28 Identifying Actors......Page 29 Identifying Use Cases......Page 31 Describing Actors and Use Cases......Page 34 Handling Time......Page 38 Potential Boundary Problems......Page 39 Scoping the Project......Page 40 Chapter Review......Page 41 The Basic Use Case......Page 44 Pre-and Postconditions......Page 45 Flow of Events......Page 46 Guidelines for Correctness and Completeness......Page 48 Presentation Styles......Page 49 Handling Complex Use Cases......Page 51 The Basic Path......Page 52 Alternative Paths......Page 54 Detailing Significant Behavior......Page 57 Documenting Alternatives......Page 59 Adding Direction to the Communicates Association......Page 64 Chapter Review......Page 65 Include......Page 68 Extend......Page 70 Inheritance......Page 75 Interfaces......Page 76 Chapter Review......Page 82 Activity Diagrams......Page 84 Simple Sequence Diagrams......Page 90 Diagramming the User Interface......Page 92 Chapter Review......Page 94 Determining the Level of Detail......Page 96 Traceability between Use Cases......Page 101 Use Cases for Business Processes......Page 102 Chapter Review......Page 104 Documentation Templates......Page 106 Other Documents......Page 108 Tool Support for Documents......Page 111 Documenting Login......Page 112 Documenting CRUD......Page 115 Chapter Review......Page 116 Review for Completeness......Page 118 Review with End Users......Page 120 Reviewers......Page 121 Adding Flexibility to Your System......Page 122 Work Flow on a Use Case Diagram......Page 124 Use Cases Too Small......Page 125 Screens as Use Cases......Page 129 Using Vague Terms......Page 132 Business versus Technical Requirements......Page 137 Chapter Review......Page 139 Architectural Patterns......Page 140 Three-Tier Architectural Pattern......Page 141 Pipe and Filter Architectural Pattern......Page 142 Order-Processing Architecture Example......Page 143 Testing the Architecture with Use Cases......Page 146 Defining Interfaces between Subsystems......Page 150 Subordinate Use Cases......Page 153 Creating Subsystem Documentation......Page 157 Subordinate versus Alternative versus Include......Page 158 Chapter Review......Page 159 Planning the Project......Page 160 Build versus Buy Decisions......Page 166 Prototyping......Page 167 Weighting Actors......Page 168 Weighting Use Cases......Page 169 Weighting Technical Factors......Page 170 Project Estimate......Page 174 Chapter Review......Page 175 Key Abstractions of the Domain......Page 176 Identifying Key Abstractions in Use Cases......Page 177 Diagramming Scenarios with Key Abstractions......Page 178 Diagramming Key Abstractions......Page 180 Use Case versus Subsystem View......Page 181 The Iteration Schedule......Page 183 Delivery and Beyond......Page 184 Use Cases After Delivery......Page 185 Chapter Review......Page 186 Final Wrap-Up......Page 187 Appendix A: Resources......Page 188 System or Subsystem Documents......Page 192 Use Case Document......Page 193 Appendix C: UML Notation......Page 196 Appendix D: Sending Results of the Use Case Estimator......Page 202 Appendix E: Order-Processing System......Page 204 Risk Factors......Page 205 System-Level Use Cases......Page 206 Architecture......Page 207 A......Page 256 D......Page 257 I......Page 258 P......Page 259 S......Page 260 U......Page 261 W......Page 262 Use cases allow software developers to identify exactly what features will be required by every user of a software system, and describe these features in terms that allow for rapid, cost-effective, successful development. Applying Use Cases is the most practical, simple, and gentle introduction to use cases. This edition is even better, with more real-world examples, more insight into the pitfalls of use case development, and thorough updating for UML 1.3 and RUP 2000. Leading mentors and consultants Geri Schneider and Jason Winters cover every phase of the process, in the context of a start-to-finish, realistic case study. Learn how to identify both primary and secondary scenarios for the usage of a proposed system; how to diagram use cases; and how to architect and organize large systems, define interfaces between components, and document your use cases Use case analysis is a methodology for defining the features of a software system from the user's point of view. This work offers an introduction to this software development technique. It guides you through the application of use case analysis in the development of software systems, and reflects the Unified Modeling Language (UML) version 1.3.