A use case describes how a user uses a capability to accomplish a desired outcome. A use case defines how the features are to be implemented and also any errors that may be encountered.
Use cases define interactions between actors and the system to attain particular outcomes. There are three basic elements that make up a use case:
- Actors: Actors are the type of users that interact with the system.
- System: Use cases capture functional requirements that specify the intended behavior of the system.
- Outcomes: Use cases are typically initiated by a user to fulfill outcomes. The activities and variants involved in attaining the outcome are also defined.
Characteristics associated with use cases are:
- Organizing functional requirements
- Detailing the outcomes of the system
- Describing the actions and exceptional flow of events
The steps in designing use cases are:
- Identify the users of the system.
- For each category of users, create a persona.
- Identify significant outcomes associated with each role to support the system.
- Create use cases for every outcome associated with a feature and maintain.
- Review and validate the use cases
In Catalio after you have created your capability and a feature, you have the ability to add multiple use cases to one feature. To add a new use case to feature, open a Feature and click the button “New Use Case" towards the top right.