Verify a mobile credential
- John Wunderlich
Owned by John Wunderlich
Page Status: DRAFT
Priority: P2
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
What happens during the use case.
Secondary Use Case (optional)
Actors
| Actor | Role in the use case |
|---|---|
| Alice | |
| Bob | |
| etcetera |
User Stories
| Element | Detail | Notes |
|---|---|---|
| As a, | <description of user> | |
| I want | <functionality> | |
| so that | <benefit> | |
| 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
Page Tasks
- Type your task here, using "@" to assign to a user and "//" to select a due date