Use Case
Use cases have a well-defined set of components (description, actor, preconditions, postconditions, main scenario, alternate/exception scenarios), so it is possible to make use cases look very similar across the organizations and projects.
Components description:
| Part | Note |
|---|---|
| Actor | Always included. Retrieved from the association between actor and use case. |
| Preconditions | Filled in Confluence, only if needed for the particular case |
| Postconditions | Filled in Confluence, only if needed for the particular case |
| Description | Describes the purpose of the use cases and the rationale. It should give enough context to understand not only what value it provides to the user but also the motivation and relationships to other parts of the system. |
| Scenarios | Filled in Confluence. Includes either only one main scenario or a separate section for each scenario type - main flow, alternate flows, exception flows. |
Everything except the name and actor is entered manually. The individual parts of the use case specification are optional, so keep use cases concise and include only the parts which add value and omit parts that are not needed.
Scenarios
If the use case also contains alternate or exception scenarios, a separate section for each scenario is included:
