Use Case 2.6 Change remote PIN
Overview
Aspect |
Description |
---|---|
Summary |
The user changes their PIN by first entering the current one, then choosing and confirming a new PIN that meets policy requirements. |
Goal |
Changing the remote PIN. |
Preconditions |
|
Postconditions |
|
Triggered by |
|
Additional Documentation |
|
Possible errors |
|
Logical Test Cases |
Flow
# |
Description |
Next |
---|---|---|
1 |
PRIMARY SCENARIO |
|
1.1 |
System executes partial flow PF2.4 Confirm a protected action
|
|
1.1a |
Result: Confirm |
1.2 |
1.1b |
Result: Back |
Back |
1.2 |
Displays screen ‘Choose new PIN’
|
|
1.2a |
User enters PIN |
1.3 |
1.2b |
User selects Back |
Back |
1.2c |
Error: No internet |
Error flow: No internet |
1.2d |
Error: Server unreachable |
Error flow: Server unreachable |
1.3 |
System validates entered PIN against PIN policy
|
|
1.3a |
Case: PIN matches PIN policy |
1.4 |
1.3b |
Case: PIN does not match PIN policy |
2 |
1.4 |
System displays screen ‘Repeat PIN’
|
|
1.4a |
User enters PIN |
1.5 |
1.4b |
User selects Back |
Back |
1.5 |
System validates PINs match
|
|
1.5a |
Case: PINs match |
1.6 |
1.5b |
Case: PINs do not match first time |
3 |
1.5c |
Case: PINs do not match second time |
4 |
1.5d |
Error: No internet |
Error flow: No internet |
1.5e |
Error: Server unreachable |
Error flow: Server unreachable |
1.6 |
System displays screen ‘PIN change success’
|
|
1.6a |
User selects Dashboard |
|
1.6b |
User selects Settings |
End |
2 |
WHEN PIN DOES NOT SATISFY POLICY (TOO SIMPLE) |
|
2.1 |
System displays PIN too simple message
|
|
2.1a |
User selects OK |
1.2 |
3 |
WHEN PINs ARE NOT EQUAL (FIRST TIME) |
|
3.1 |
System displays PIN is different message
|
|
3.1a |
User selects Try again |
1.4 |
4 |
WHEN PINs ARE NOT EQUAL (SECOND TIME) |
|
4.1 |
System displays PIN is different message
|
|
4.1a |
User selects Choose New Pin |
1.2 |