Home Page Icon
Home Page
Table of Contents for
Structure: The Scenario
Close
Structure: The Scenario
by Andy Pols, Alistair Cockburn, Paul Bramble, Steve Adolph
Patterns for Effective Use Cases
Copyright
Dedication
Structure: The Use Case Set
Structure: The Use Case
Structure: The Scenario
Structure: The Step
Foreword
Preface
Audience
Organization
How to Use This Book
What about UML?
Why Don't We Use a Single Use Case Template for the Examples?
The Agile Software Development Series
Pattern Language Heritage
Acknowledgments
1. What Is a Quality Use Case?
1.1. Why Use Cases at All?
1.2. What's So Hard about Telling Good Stories?
1.3. Why a Use Case Pattern Language?
1.4. What Are Patterns?
1.5. How Should I Use This Pattern Language?
1.6. What Is the Use Case Pattern Form?
Stepping through a Sample Pattern
The Name
A Picture
The Context
The Problem Statement
The Metaphoric Story
The Forces Affecting the Problem
The Solution
The Examples
1.7. Organization of the Pattern Language
Development Patterns
The Team
The Process
Editing
Structural Patterns
Use Case Sets
Use Cases
Scenarios and Steps
Relationships
1.8. Supplement: A Brief Tutorial on Writing Use Cases
2. The Team
2.1. Team Organizational Issues
2.2. SmallWritingTeam
Examples
Facilitating Large Groups: No Design without Representation
Large Groups and Frequent Checkpoints
2.3. ParticipatingAudience
Examples
The Job Flow Engine
Making Movies
To the Moon
2.4. BalancedTeam
Examples
Lack of Diversity
2.5. Trade-offs and Collaborations
3. The Process
3.1. BreadthBeforeDepth
Examples
3.2. SpiralDevelopment
Examples
Wings Over the World
A More Literary Example
3.3. MultipleForms
Examples
Batch Job Distribution
Purchasing for a Business
3.4. TwoTierReview
Examples
Wings Over the World (Continued)
The Programmer Who Cried Review
3.5. QuittingTime
Examples
Wings Over the World (Continued)
3.6. WritersLicense
Examples
Wings Over the World (Continued)
3.7. Trade-offs and Collaborations
4. The Use Case Set
4.1. SharedClearVision
Examples
Wings Over the World
Automated Railway Signaling
Mobile Dispatching
4.2. VisibleBoundary
Examples
Wings Over the World: Context Diagrams
4.3. ClearCastOfCharacters
Examples
Centre A: The Museum for Contemporary Asian Art
The Pharmacy Receptionist
4.4. UserValuedTransactions
Examples
Wings Over the World and UserValuedTransactions
Wings Over the World and Avoiding Form-Focus
The Cruddy Mortgage Origination System
4.5. EverUnfoldingStory
Examples
Wings Over the World and Use Case Levels
Centre A: The Museum for Contemporary Asian Art
4.6. Trade-offs and Collaborations
5. The Use Case
5.1. CompleteSingleGoal
Examples
Wings Over the World
5.2. VerbPhraseName
Examples
Insurance Claims
Use Case Naming Horrors
Good Use Case Names
5.3. ScenarioPlusFragments
Examples
Auto Insurance Claim Handling
5.4. ExhaustiveAlternatives
Examples
E-mail Access
5.5. Adornments
Examples
Wings Over the World with Adornments
5.6. PreciseAndReadable
Examples
Wings Over the World: Readable but Imprecise
Wings Over the World: Precise but Unreadable
5.7. Trade-offs and Collaborations
6. Scenarios and Steps
6.1. DetectableConditions
Examples
The ATM JAD Session
Wings Over the World
6.2. LeveledSteps
Examples
A Long and Tedious Use Case for an On-line Store
A Use Case with Excessively Large Steps for an On-line Store
A Use Case That Mixes Large and Small Steps for an On-line Store
6.3. ActorIntentAccomplished
Examples
The Actor-less ATM
6.4. ForwardProgress
Examples
Wings Over the World: A Diversionary Scenario
Insurance Claim: Not Enough Forward Progress
6.5. TechnologyNeutral
Examples
File Accident Claim: Tied to Technology
6.6. Trade-offs and Collaborations
7. Use Case Relationships
7.1. CommonSubBehavior
Examples
Wings Over the World and Includes
7.2. InterruptsAsExtensions
Examples
Wings Over the World and Extensions
Extensions and UML Extension Points
7.3. PromotedAlternative
Examples
Wings Over the World
Using Extends
7.4. Trade-offs and Collaborations
7.5. CapturedAbstraction—A Pattern for Applying UML Generalization, by Dan Rawsthorne
Examples
Wings Over the World
8. Editing Existing Use Cases
8.1. RedistributeTheWealth
Examples
Call Processing
8.2. MergeDroplets
Examples
Call Processing
8.3. CleanHouse
Examples
Hospital Claim
8.4. Trade-offs and Collaborations
References
Photo Credits
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Search in book...
Toggle Font Controls
Playlists
Add To
Create new playlist
Name your new playlist
Playlist description (optional)
Cancel
Create playlist
Sign In
Email address
Password
Forgot Password?
Create account
Login
or
Continue with Facebook
Continue with Google
Sign Up
Full Name
Email address
Confirm Email Address
Password
Login
Create account
or
Continue with Facebook
Continue with Google
Prev
Previous Chapter
Structure: The Use Case
Next
Next Chapter
Structure: The Step
Structure: The Scenario
DetectableConditions
Include only detectable conditions. Merge conditions that have the same net effect on the system.
LeveledSteps
Keep scenarios to three to nine steps. Ideally, the steps are all at similar levels and at a level of abstraction just below the use case goal.
Add Highlight
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click
here
login for view all page.
Day Mode
Cloud Mode
Night Mode
Reset