arti/Estonian-ID-card-mobile-authenticator-POC
1
0
Fork 0
mirror of https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC.git synced 2024-11-22 05:41:00 +02:00
Code Packages Releases Wiki Activity

Updated use cases 1, 5

Henrik Lepson 2021-12-03 20:24:00 +02:00
parent dd623a493b
commit bddc2ec361
1 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
Use-Cases.md

@ -10,12 +10,12 @@ The UI layout that asks the user for CAN is active.
User
**Main success scenario:**
1. The application asks the user to insert a valid CAN.
2. The user enters CAN into the provided input field and then clicks on the “next” button.
3. The system checks the length of the entered CAN to make sure that its length equals 6.
2. The user enters CAN into the provided input field.
3. The system checks if the length of the entered CAN is 6.
4. The CAN is automatically saved.
**Extensions:**
 3. The length of the CAN entered by the user is not 6.
  a. The system cancels the action triggered by the next button so the user can change the entered CAN.
No extensions
**Related tasks:**
[MOB-37](https://tvp-mobile-authentication.atlassian.net/browse/MOB-37), [MOB-39](https://tvp-mobile-authentication.atlassian.net/browse/MOB-39), [MOB-40](https://tvp-mobile-authentication.atlassian.net/browse/MOB-40)
@ -40,12 +40,12 @@ The UI layout that asks the user for PIN1 input is active.
User
**Main success scenario:**
1. The application asks the user to insert a valid PIN1.
2. The user enters PIN1 into the allocated input field and then clicks on the “next” button.
2. The user enters PIN1 into the allocated input field and then clicks on the “continue” button.
3. The system checks the length of the entered PIN1 to make sure that its length is an integer in the range [4, 12].
**Extensions:**
 3. The length of the PIN1 that the user entered in the input field is not an integer in the range [4, 12].
  a. The system cancels the action triggered by the next button so the user can change the entered PIN1.
  a. The system cancels the action triggered by the "continue" button so that the user can change the entered PIN1.
**Related tasks:**
[MOB-37](https://tvp-mobile-authentication.atlassian.net/browse/MOB-37), [MOB-40](https://tvp-mobile-authentication.atlassian.net/browse/MOB-40)
@ -124,23 +124,23 @@ The user has a valid Estonian ID-card with NFC interface.
**Primary actor:**
User
**Main success scenario:**
1. The user clicks the “begin” button on the home screen of the authentication application to start the process.
2. The application asks the user to enter the CAN of the ID card (includes Use Case #1) if it is not saved to the application.
3. The application tells the user to touch the smartphone with the ID card in the given 90 second time window.
4. The user puts the ID card against the smartphone.
5. The application notifies the user that the ID-card has been detected and establishes a PACE connection with the ID card using the CAN provided by the user previously in the step 2.
6. The application retrieves the first name, the last name and the national identification number of the ID card owner from the ID card.
7. The application notifies the user that reading the information from the ID card is completed.
8. The application displays the retrieved information to the user in a formatted way.
1. The application asks the user to save the CAN of the ID card (includes Use Case #1) if it is not saved to the application.
2. The application tells the user to touch the smartphone with the ID card.
3. The user puts the ID card against the smartphone.
4. The application notifies the user that the ID-card has been detected and establishes a PACE connection with the ID card using the CAN provided by the user previously in the step 1.
5. The application retrieves the first name, the last name and the national identification number of the ID card owner from the ID card.
6. The application notifies the user that reading the information from the ID card is completed.
7. The application displays the retrieved information to the user in a formatted way.
**Extensions:**
 4. The user fails to put the ID card against the smartphone in the 90 second time window.
  a. The system cancels the process and returns the user to the home screen of the application.
 5a. The CAN provided by the user does not match the CAN on the ID card.
 3. The user fails to put the ID card against the smartphone.
  a. The system keeps waiting for the card as long as the application is active.
 4a. The CAN provided by the user does not match the CAN on the ID card.
  a. The application fails to establish a secure connection with the ID card over the NFC connection.
  b. The application notifies the user that the CAN provided was not valid and returns the user to the home screen.
 5b. The ID card is moved away from the smartphone NFC range before the information exchange between the smartphone and the ID card is completed.
  a. The application notifies the user that the connection to the ID card was lost and returns the user to the home screen.
  c. The application deletes the saved CAN.
 4b. The ID card is moved away from the smartphone NFC range before the information exchange between the smartphone and the ID card is completed.
  a. The application notifies the user that the connection to the ID card was lost and gives user the option to try again.
**Related tasks:**
[MOB-10](https://tvp-mobile-authentication.atlassian.net/browse/MOB-10), [MOB-16](https://tvp-mobile-authentication.atlassian.net/browse/MOB-16), [MOB-18](https://tvp-mobile-authentication.atlassian.net/browse/MOB-18), [MOB-37](https://tvp-mobile-authentication.atlassian.net/browse/MOB-37), [MOB-39](https://tvp-mobile-authentication.atlassian.net/browse/MOB-39), [MOB-40](https://tvp-mobile-authentication.atlassian.net/browse/MOB-40), [MOB-52](https://tvp-mobile-authentication.atlassian.net/browse/MOB-52), [MOB-53](https://tvp-mobile-authentication.atlassian.net/browse/MOB-53)