Use Case 1.2 Open the app
Overview
Aspect |
Description |
---|---|
Summary |
The user opens the app manually or follows a universal link. The system checks the app version is valid, or forces the user to update. |
Goal |
Opening the app. |
Preconditions |
|
Postconditions |
None |
Triggered by |
|
Additional Documentation |
|
Possible errors |
|
Logical test cases |
Flow
# |
Description |
Next |
---|---|---|
1 |
PRIMARY SCENARIO |
|
1.1 |
System determines app startup state |
|
1.1a |
Case: App launches (iOS) or starts cold or warm (Android)1 |
2 |
1.1b |
Case: App resumes (iOS) or starts hot (Android)2 |
3 |
2 |
WHEN APP LAUNCHES |
|
2.1 |
System displays screen ‘Splash screen’ |
|
2.1a |
Event: 1 second passes |
2.2 |
2.2 |
System executes partial flow PF1.4 Apply update policy |
|
2.2a |
Result: App version is allowed |
2.3 |
2.3 |
System determines whether remote PIN is set up |
|
2.3a |
Case: User has setup a remote PIN |
Go to: UC2.3 Unlock the app |
2.3b |
Case: User has not setup a remote PIN |
Go to: UC1.1 Introduce the app |
3 |
WHEN APP RESUMES |
|
3.1 |
System determines whether remote PIN is set up |
|
3.1a |
Case: User has setup a remote PIN |
3.2 |
3.1b |
Case: User has not setup a remote PIN |
Resume3 |
3.2 |
System determines whether app is locked |
|
3.2a |
Case: Wallet is unlocked |
3.3 |
3.2b |
Case: Wallet is locked |
Go to: UC2.3 Unlock the app |
3.3 |
System determines whether user has obtained PID |
|
3.3a |
Case: User has obtained PID |
3.4 |
3.3a |
Case: User has not obtained PID |
Resume3 |
3.4 |
System executes partial flow PF2.7 Resolve a universal link |
|
3.4a |
Result: No (valid) universal link |
Resume3 |