For both templates, it is appropriate to number individual use cases, either in ascending order or including the package number to which the use case belongs. Attach the Use Case diagram itself for a better understanding of the relationships between authors and use cases.
The basic template contains the most important fields for the Use Case.
- Use case - Identification and name of the use case.
- Brief description - briefly describe what the use case is about.
- Actors - a list of actors associated with a use case
- Basic flow - description of the basic flow of use cases, as an interaction between the actuator and the system from the operator's point of view.
- Alternative flow - description of other alternative flows of interaction between the actor and the system.
- Conditions for starting - if any, describe the conditions that must occur for starting the basic flow.
- Conditions for completion - conditions that must occur for completion
- Special requirements - state special requirements related to use cases.
- Additional information - important for further development or specifying an area.
- Realized requirements - If you record system requirements, state which of them are realised using the use case.
The template provides more information on the use case.
- Use Case - Identification and name of the use case.
- Included in a phase - a number or other identification of the development phase in which the use case is included
- Version - simple versioning of use case changes.
- Date of change - Date of the last change of the use case
- Last Modified - The name of the author of the last modification of the use case
- Purpose - description of the purpose of the use case
- Occurrence Frequency - an auxiliary use case frequency classifier - can be used to prioritize development
- Actors- a list of authors with the possibility of describing user rights
- Trigger - a specific event triggering a basic flow
- Pre-conditions - Optional conditions that must occur to start the base stream
- Successful Completion - A clear and concise description of the successful completion of the base stream
- Baseline scenario - a description of the use case scenario as an interaction between the actuator and the system from the operator's point of view
- Extensions and alternative scenarios - description of other alternative flows of interaction between the actor and the system. Describe alternative scenarios separately.
- Related Use Cases and other entities - optionally complete related use cases or other entities, including a description of the context.
- Realized requirements - if you record system requirements, state which of them are implemented using the use case.
- Open topics and notes - add topics, notes or points to be resolved in the context of this use case
- Add-ons and attachments - complete everything that will help in the correct understanding of use cases.