I’m attempting to drill this Detailed Use Case Narrative into my brain (but I know I just need the vibe- still, every bit helps) by blogging it- something about using both hands to type seems to engage the brain more.
- Use Case Name: Fairly obvious.
- Scenario: Maybe we’re using the same use case in slightly different situations, such as a web order and a phone order
- Triggering Event: what starts the use case
- Brief Description: Can be taken from your original brief Use Case description
- Actors: People or external systems involved
- Related Use Cases: What other use cases might be involved?
- Stake-holders: perhaps departments that need to provide information/stuff
- Pre-conditions: What must exist for this use case to happen
- Post-conditions: What will be created/changed at the end of this use case
- Flow of Activities:
- Actor: what the actor does (numbered)
- System: what the system does in response (1.1, 1.2, 2.1, etc)
- Exception Conditions: what happens if something doesn’t work right: maybe an item is not in stock.
So that’s a detailed use case description.
Edit: perhaps the sign of a tired mind, but here’s a fun saying to help remember them:
Uncle Sam Tells Big Dog About (Really Something Pretty Preposterous): Flying Elephants.