Book description
Developers who effectively employ use cases deliver better applications--on time and under budget. The concept behind use cases is perhaps as old as software itself; they express the behavior of systems in terms of how users will ultimately interact with them. Despite this inherent simplicity, the use case approach is frequently misapplied, resulting in functional requirements that are confusing, cumbersome, or redundant.
In Use Case Modeling, experienced use case practitioners Kurt Bittner and Ian Spence share their tips and tricks for applying use cases in various environments. They delve into all aspects of use case modeling and management, demonstrating how development teams can capitalize on the approach's simplicity when modeling complex systems.
In this ready reference, readers will discover how to
Introduce a development team to use cases and implement a use case approach
Identify the key elements of a use case model, including actors; and the components of a use case, including basic flow, preconditions, post-conditions, sub-flows, and alternate flows
Master the objectives and challenges of creating detailed descriptions of use cases
Improve their descriptions' readability and consistency
Prevent and remedy common problems arising from the misuse of include, extend, and generalization use case relationships.
Organize and conduct a review of a use case model to realize the best possible approach
The book draws extensively on best practices developed at Rational Software Corporation, and presents real-life examples to illustrate the considerable power of use case modeling. As such, Use Case Modeling is sure to give development teams the tools they need to translate vision and creativity into systems that satisfy the most rigorous user demands.
0201709139B08062002
Table of contents
- Copyright
- Foreword
- Preface Why Bother with Use Cases?
-
I. Getting Started with Use-Case Modeling
- 1. A Brief Introduction to Use-Case Modeling
-
2. Fundamentals of Use-Case Modeling
- The Use-Case Model
- The Basic Building Blocks of a Use-Case Model
- Supporting Artifacts
- Summary
-
3. Establishing the Vision
- Introducing Stakeholders and Users
- Involving Stakeholders and Users in Your Project
- Creating a Shared Vision
- Bringing It All Together: The Vision Document
- Do You Really Need to do All of This?
- Summary
-
4. Finding Actors and Use Cases
-
Finding Actors
- Start by Identifying the Primary Actors
- Work from the Specific to the General
- Don’t Forget the Supporting Actors
- Consider All Existing Requirements Information
- Remember That Actors Are Not Always People
- Focus on the System Boundary
- Don’t Preempt the Design
- Don’t Confuse the Actors with the Devices They Use
- When You Can’t Find the Actors, Start with the Use Cases
- Focus First on the Familiar
- Evolve the Set of Actors Alongside the Set of Use Cases
- Documenting Actors
-
Finding Use Cases
- Start by Identifying the Actor Goals
- Consider the Information Needs of the System and Its Users
- Don’t Worry About Commonality (at least at first)
- Don’t Confuse Use Cases with “Functions”
- Focus on Value
- Derive the Use Cases from the System’s Vision
- Don’t Forget the Supporting and Operational Use Cases
- Evolve the Set of Use Cases Alongside the Set of Actors and the Supplementary Specification
- Documenting Use Cases
- Summary
-
Finding Actors
- 5. Getting Started with a Use-Case Modeling Workshop
-
II. Writing and Reviewing Use-Case Descriptions
- 6. The Life Cycle of a Use Case
- 7. The Structure and Contents of a Use Case
-
8. Writing Use-Case Descriptions: An Overview
- Who Writes Use-Case Descriptions?
- How Long Does it Take to Write a Use Case?
- Getting Started
-
Managing Detail
- Good Use-Case Models Have No “Levels”
- Adapt the Description to Your Intended Audience
- Use the Glossary and Domain Model to Capture Definitions
- Capture Business Rules in a Domain Model
- Use Subflows to Simplify Complex Descriptions
- Use Alternative Flows to Capture Unusual or Complex Behavior
- Don’t Fill Your Use Cases with CRUD
- Don’t Be Afraid of Capturing the Detail
- Summary
-
9. Writing Use-Case Descriptions: Revisited
- How Much Detail is Enough?
- Describing Preconditions
- Describing Postconditions
- Writing the Flow of Events
- Using the Glossary and the Domain Model
- Writing “Named” Subflows
-
Writing Optional, Alternative, and Exception Flows
- Identifying Alternative Flows
- Representing Alternative Flows in Separate Sections
- Naming Alternative Flows
- Using Extension Points to Target Alternative Behavior
- Describing Alternative Flows That Can Occur Anywhere in the Use Case
- Resuming the Use Case After the Alternative Flow Completes
- Alternative Flows for Alternative Flows and Named Subflows
- Writing Special and Supplementary Specifications
- Capturing Use-Case Scenarios
- Summary
- 10. Here There Be Dragons
- 11. Reviewing Use Cases
- 12. Wrapping Up
- Appendix Examples
- Glossary
- Bibliography
Product information
- Title: Use Case Modeling
- Author(s):
- Release date: August 2002
- Publisher(s): Addison-Wesley Professional
- ISBN: 9780201709131
You might also like
book
Patterns for Effective Use Cases
Use cases have become an integral part of modeling software requirements, but many software developers are …
book
Advanced Use Case Modeling: Software Systems
"This book isn't just another introduction to use cases. The authors have used their wealth of …
book
The Unified Modeling Language User Guide, 2nd Edition
For nearly ten years, the Unified Modeling Language (UML) has been the industry standard for visualizing, …
book
UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition
Would you like to understand the most important elements of Class diagrams? (See page 35.) Do …