
Select transaction type
Use case ID: 1
Description
Description
The user selects the duration of the parking time and the method of payment
Actors
Actors
User
Assumptions and constrains
Assumptions and constrains
Pre-condition: The machine is not disabled
Post-condition: The user has selected the duration and method of payment
Steps to achieve the goal
Steps to achieve the goal
1. The user selects the duration (see use case 2)
2.
The user selects the method of payment (see use case 3)
Related non-functional requirements
The system shall correctly respond to a button press within 0.25s
Error cases
Error cases
a. Selecting the duration or method of payment is aborted
1. The system shows the welcome message
2. The use case is repeated
__________________________________________
Select parking duration
Use case ID: 2
Description
Description
The user selects the duration of the parking time
Actors
Actors
User
Assumptions and constrains
Assumptions and constrains
Pre-condition: The machine is not disabled
Post-condition: The user has selected the duration
Steps to achieve the goal
Steps to achieve the goal
1. User presses the GET TICKET button
2. The system shows a list of duration options: ½, 1, 2, and 4 hours
3. User presses a button corresponding to one of the options
Related non-functional requirements
The system shall correctly respond to a button press within 0.25s
Error cases
Error cases
a. There is not enough free parking places after User presses the GET TICKET button
1. The system shows the message “No parking spaces left”
2. The use case is aborted.
b. There has been more than 30 seconds without user's activity
2. The use case is aborted.
__________________________________________
Select payment method
Use case ID: 3
Description
Assumptions and constrains
Description
The user selects the payment method
Actors
Actors
User
Assumptions and constrains
Pre-condition: The user has selected the duration
Post-condition: The user has selected the Credit card payment method
Steps to achieve the goal
Steps to achieve the goal
1. The system shows a list of payment options: “Credit card” and “Phone”
2. User presses a button corresponding to one of the options
Related non-functional requirements
The system shall correctly respond to a button press within 0.25s
Error cases
Error cases
a. User selects a button that does not correspond to one of the choices on the list
1. The system shows the message “Invalid choice, please try again”
2. Go back to step 1 of the use case.
b. There has been more than 30 seconds without user's activity
2. The use case is aborted.
__________________________________________
Select payment by phone
Use case ID: 4
Extends Use Case 3
Description
Description
The user selects the Phone payment method
Actors
Actors
User
Steps to achieve the goal
1-2 same as in Use Case 3
3. The system displays its phone number and phone-payment instructions.
Related non-functional requirements
The system shall correctly respond to a button press within 0.25s
No comments:
Post a Comment