Use this template to create a user story, a use case, or a user journey to describe something that needs to be addressed in the PEMC.
Description (User Story)
Enter a high-level (elevator pitch) description of the use case. This can be phrased as a user story or stories. A user story describes a type of user, what they want, and why. This is typically a simple sentence or two like, "As <description of user>, I want <functionality> so that <benefit>.
Narrative
The user wants to be able to carry a collection of credentials with them that can give then access to physical locations as well as digital assets.
Secondary Use Case (optional)
Actors
| Actor | Role in the use case |
|---|---|
| Holder | The human user of the mobile credentials. |
| Device | A smart phone or other mobile computing device including the operating system (OS) software. |
| Wallet | An application running on the OS that has access to protected storage on the device. Often called a native app. |
| Issuer | of a mobile credential. |
| Verifier | of one or more mobile credentials. |
User Stories
| Element | Detail | Notes |
|---|---|---|
| As a, | human user | |
| I want | access | |
| so that | complete my task | |
| Acceptance Criteria | ||
| Given | <how things begin> | |
| When | <action taken> | |
| Then | <outcome of taking action> | |
Prerequisites / Assumptions
Use Case Details
Privacy
Data Provided
Data Retained
Diagram
Steps
Primary Use Case
The anticipated normal sequence
| # | Step | Description |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 |
Secondary Use Case(s)
Alternate or variant sequences
| # | Step | Description |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 |
Sequence Diagram
End State
Describe what measures or signifies the end of the case
Success
Markers or metrics that indicate success
Failure
Markers or metrics that indicate failure
References
Champion / Stakeholder
List of the people that created the use case
Related Material
Resources and Links