Draw.io
Kumu.io
lucidchart.com
4.*.* Description of Environment (brief)
4.*.* Use Case
Name
Description<
Primary Actor<
Supporting Actors<
Stakeholders and Interests
Pre-Conditions
Post Conditions
Success condition
Failure condition:
Minimal Guarantee
Trigger
Main Success Scenario
Extensions
Variations
Frequency:
Assumptions
Special Requirements
Issues
Outcome
4.*.* Recommendations
- Identity, Interactions, Regulations and Governance
TEMPLATE
Use Case: Name <Enter Use Case name here>
...
<The event that starts this Use Case.
Main Success Scenario
- <Enter steps here>
- <Enter steps here>
- <Enter steps here>
...
<Enter the Main flow of events. i.e. The steps narrating/illustrating the interaction between Actors and the System. Describe Actor’s actions/stimuli and how the system responds to those stimuli. Describe the ‘happy path/day’ scenario, meaning the straight and simple path where everything goes ‘right’ and enables the primary actor to accomplish his or her goal. Main flow/path should always end with a success end condition.>
Extensions
<Enter Extensions and their steps here>
<Enter any extensions here. Extensions are branches from the main flow to handle special conditions. They also known as Alternate flows or Exception flows. For each extension reference the branching step number of the Main flow and the condition which must be true in order for this extension to be executed.
Variations
<Enter variations here>
<Enter any data entry or technology variations such as – different methods of data input, screen/module invocation, etc.
...
<Enter any assumptions, if any, that have been made while writing this Use Case.
Special Requirements
<Enter any special requirements such as Performance requirements, Security requirements, User interface requirements.Examples::
Performance
User Interface
Security
Issues
<List any issues related to the definition of the use case.