Use Cases
- Tags
- soft-eng
Is a [see page 4, collection] of scenarios depicting how an actor interacts with a system.
A use case is a sequence of related transactions between an actor and a system that yields a result of measurable value... use-cases represent business tasks, not system actions. They must have a measurable business-level objective.
- [see page 6, Jacobson, 1994].
To get started [see page 10, documenting] use cases:
- Describe the required system functionality in detail.
- Collect the different scenarios incrementally.
- Document the main success scenario (main flow), variant flows diverging from the main flow can come later.
- Write each scenario as a sequence of events and style as a dialogue between the actor and the system.
In the case of [see page 16, overlapping] use cases you can create a partial base case and include it in the event-flow of a derived case. You can also [see page 18, inherit] actors.