A use case is a set of instructions that an individual in a process completes to go through one single step in that process. It describes what the user does to interact with a system.
To understand how a user is aided by a system when completing a specific task.
1. IDENTIFY A PROCESS AND A SCENARIO within that process (the use case) to be analyzed.
2. IDENTIFY STAKEHOLDERS AND KEY PLAYERS in the use case.
3. DETERMINE THE GOAL(S) to be achieved from the analysis. Generally the goals of the use case revolve around identifying event triggers, alternate scenario paths or extensions, or simply just to understand the process and scenario better.
4. COLLECT RELEVANT DATA that will aid in achieving the goals of the use case identified in the previous step.
5. ORGANIZE THE COLLECTED DATA in a manner which best supports the use case goals.
6. SUMMARIZE AND FORMULATE CONCLUSIONS.
Can reveal requirements that might be missed in approaches that are not a specific.
Can be completed without a team.
Reduces the case to a sequence of steps allows you to create an effective interaction prior to application design.
Clinical background is necessary for good results in health care settings.
Scheele K. Improving patient results tracking in a multi-specialty clinic. 2007 Society for Health Systems Conference; 2007; New Orleans, LA; 2007.
Sharp A, McDermott P. Requirements modeling with use cases and services. Workflow modeling: tools for process improvement and applications development. 2nd ed. Boston: Artech House; 2009. p. 375-422.