mirror of
https://github.com/TanelOrumaa/Estonian-ID-card-mobile-authenticator-POC.git
synced 2024-11-22 13:51:00 +02:00
Separated use cases visually
parent
8f50370d48
commit
4ae6b935e7
33
Use-Cases.md
33
Use-Cases.md
@ -1,6 +1,6 @@
|
||||
_NB! Use cases #1, #2 and #3 are only used in the include relationships with other use cases. These three use cases are not independent, but are duplicated in most of the other use cases so extracting them was necessary to avoid repetition, keep the use cases as concise as possible and improve readability._
|
||||
|
||||
**Use Case #1**
|
||||
# **Use Case #1**
|
||||
**Use Case Title:**
|
||||
Entering CAN (Card Authentication Number) of the ID card
|
||||
**Preconditions:**
|
||||
@ -19,7 +19,7 @@ User
|
||||
b. The user is allowed to change the entered CAN.
|
||||
|
||||
|
||||
**Use Case #2**
|
||||
# **Use Case #2**
|
||||
**Use Case Title:**
|
||||
Entering PIN 1 of the ID card
|
||||
**Preconditions:**
|
||||
@ -37,7 +37,8 @@ User
|
||||
a. The action triggered by the next button is cancelled.
|
||||
b. The user is allowed to change the entered PIN 1.
|
||||
|
||||
**Use Case #3**
|
||||
|
||||
# **Use Case #3**
|
||||
**Use Case Title:**
|
||||
Entering PIN 2 of the ID card
|
||||
**Preconditions:**
|
||||
@ -55,7 +56,8 @@ User
|
||||
a. The action triggered by the next button is cancelled.
|
||||
b. The user is allowed to change the entered PIN 2.
|
||||
|
||||
**Use Case #4**
|
||||
|
||||
# **Use Case #4**
|
||||
**Use Case Title:**
|
||||
Saving the CAN number of the ID card on the phone
|
||||
**Preconditions:**
|
||||
@ -72,7 +74,8 @@ User
|
||||
**Extensions:**
|
||||
None
|
||||
|
||||
**Use Case #5**
|
||||
|
||||
# **Use Case #5**
|
||||
**Use Case Title:**
|
||||
Displaying the public information of the ID card in the authentication application
|
||||
**Preconditions:**
|
||||
@ -101,8 +104,7 @@ User
|
||||
a. The application notifies the user that the connection to the ID card was lost and the user is returned to the home screen.
|
||||
|
||||
|
||||
|
||||
**Use Case #6**
|
||||
# **Use Case #6**
|
||||
**Use Case Title:**
|
||||
Using biometric authentication to enter PIN 1 during the authentication process
|
||||
_NB! Biometric authentication does not replace the need to use PIN 1 for the authentication process, but it is a convenience feature that makes entering PIN 1 faster as it is done automatically when fingerprint is used, thus saving the user a few seconds of time each time they use the application for authentication._
|
||||
@ -130,7 +132,8 @@ User
|
||||
b. The user is notified that the PIN 1 entered was not valid and the authentication process is cancelled.
|
||||
c. The biometric authentication mode is automatically turned off by the application in the settings menu until a new PIN 1 is saved to this feature in order to avoid future use of this feature with an invalid PIN 1.
|
||||
|
||||
**Use Case #7**
|
||||
|
||||
# **Use Case #7**
|
||||
**Use Case Title:**
|
||||
Application automatically closes itself at the end of the authentication process
|
||||
**Preconditions:**
|
||||
@ -147,7 +150,8 @@ The authentication application
|
||||
3. The authentication application fails to close itself automatically.
|
||||
a. The user closes the application manually.
|
||||
|
||||
**Use Case #8**
|
||||
|
||||
# **Use Case #8**
|
||||
**Use Case Title:**
|
||||
Using the authentication application to log into a website
|
||||
**Preconditions:**
|
||||
@ -185,7 +189,8 @@ User
|
||||
b. The user is notified that the provided PIN 1 was not correct.
|
||||
c. The authentication process is canceled and the user is directed back to the website without a result.
|
||||
|
||||
**Use Case #9**
|
||||
|
||||
# **Use Case #9**
|
||||
**Use Case Title:**
|
||||
Using the authentication application to give a signature on a website
|
||||
**Preconditions:**
|
||||
@ -218,8 +223,9 @@ User
|
||||
7c. The NFC connection between the ID card and the smartphone is lost during the communication.
|
||||
a. The application fails to retrieve information from the ID card.
|
||||
b. The process is canceled and the user is returned to the website without a result.
|
||||
|
||||
**Use Case #10**
|
||||
|
||||
|
||||
# **Use Case #10**
|
||||
**Use Case Title:**
|
||||
Using the authentication application to log into a mobile application running on the same smartphone.
|
||||
**Preconditions:**
|
||||
@ -258,7 +264,8 @@ User
|
||||
b. The user is notified that the provided PIN 1 was not correct.
|
||||
c. The authentication process is canceled and the user is returned to the initial application without a result.
|
||||
|
||||
**Use Case #11**
|
||||
|
||||
# **Use Case #11**
|
||||
**Use Case Title:**
|
||||
Using the authentication application to give a signature on a mobile application
|
||||
**Preconditions:**
|
||||
|
Loading…
Reference in New Issue
Block a user