The Use Case template...
I recommend having a list of use cases titles and, if necessary, definitions of key "actors" - ie a system or a role a person might take in interacting with a system. Actors interact with one another to accomplish a goal (which is the use case). The word template is also available.
USE CASES
ACTORS
Actor 1 | Description |
Actor 2 | Description |
Use case title
Author
Organization
ID | An ID unique within this working group |
|---|---|
Title | Title that summarizes the user's goal in the use case, for example, "Searching for learning at the point of care." |
Actors | List the actors involved in this use case. An actor is a system or a role a person might take in interacting with a system. For example, a physician learner could be an actor, or a learning management system. |
Trigger event | If there is an event that precedes and triggers this use case, list it here. For example, the trigger event for a point of care learning experience would be "A clinician has a clinical question at the point of care." |
Sucess end condition | If the user's goal is accomplished, what is the end result? For example, "The clinician accesses learning that addresses her clinical questions." |
Assumptions | If there are any assumptions or prerequisite action that must be taken, list them here. The user having logged in successfully may be an assumption. |
Description | Write a step by step narrative description of how the user and system interact to achieve the end goal. This doesn't have to be technical, it just describes what you want the technology to do for you. |
Transaction | What are the important system to system transactions that might require standards? |
Exceptions | What happens if things go wrong? |
Potential Standards | If a particular transaction points to the need for a data exchange standard, give a general title for that standard here. |