-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add system use case with retry as alternate flow
- Loading branch information
1 parent
49c4dad
commit 4e6c28e
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
### Use case: Enroll contactless card to receive transit benefit | ||
|
||
**Primary Actor**: Transit rider | ||
**Systems**: Benefits app, payment processor | ||
|
||
**Preconditions**: | ||
|
||
- Transit rider has confirmed their eligibility with the Benefits app | ||
- Transit rider has their contactless card information available | ||
- Benefits app is able to contact the payment processor | ||
|
||
**Trigger**: Transit rider initiates the enrollment process | ||
|
||
**Basic flow**: | ||
|
||
1. Transit rider enters their contactless card information | ||
2. Benefits app passes that information to the payment processor to enroll the card | ||
3. Payment processor successfully enrolls card | ||
|
||
**Alternate flows**: | ||
|
||
- 3a. Payment processor returns with one of the following errors: address verification failed, token is invalid, or general server error | ||
- 3a1. Transit rider chooses to retry, starting back at initiating the enrollment process | ||
- 3b1. Transit rider leaves the Benefits app | ||
|
||
**Postconditions**: | ||
|
||
- Transit rider's contactless card is enrolled to receive the transit benefit |