Use Cases Document Template (BEA)
- On the 1st iteration, let's keep it simple. I suggest we capture a use case with a very simple, even text-only (diagrams optional) format, by: (BEB)
- 1. Naming the Use Case (BEC)
- 2. identifying its "Goal" and "Primary Actor(s)" (BED)
- 3. describing its primary scenario (successful end) as a sequence of numbered steps; (BEE)
- 4. describe alternative scenarios (including failed end) and others, as variations on the above sequence; (BEF)
- 5. optionally, make a top-level use case diagram. (BEG)
this should be a short (1 page) draft just to quickly document the ideas and to ensure top level alignment of the interpretation of those ideas among the parties involved. This follows the example shown on Figure 3-1 (p.40) of Martin Fowler's "UML Distilled (2nd Edition)" (see UseCasesSimpleTextExample) (BEH)
- On the 2nd iteration, may I suggest we will follow the framework set out in Alistair Cockburn's Sample Requirements Document Chapter 2. (BEI)
Iteration-1: Quick Capture of the Draft Use Cases (BEK)
- Use Case Name: (BEL)
- Goal: (BEM)
- Primary Actors: (BEN)
- Primary Scenario (successful end): (BEO)
- Alternative Scenario-n (failed end): (BES)
- step nn. (BET)
- Alternative Scenario-n (failed end): (BEU)
- step nn. (BEV)
- Use Case Diagram (optional) (BEW)
Iteration-2: Documenting the Use Cases (BEX)
- Name the Primary Use Case (BEY)
2a. The Primary Actors and their General Goals (BEZ)
- List Actors, along with a breif description of the roles of each of them. (BF0)
2b. The Business Use Cases (BF1)
- Tabulate Outermost Goals, with the following columns: (BF2)
- Tabulate Task Level Goals, with the following columns: (BF7)
2c. The System Use Cases (BFC)
- Use Case 1: name primary use case (BFD)
- Use Case Diagram(s) (BFU)
- Use Case n: name use case (BGL)
- Use Case n: name use case (BGV)