Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user enters the booking number.
2 The system displays the booking file along with the payment.
A1: Settle Bill.
A2: Issue Coupon.
Alternate Flow: A1 (Settle Bill)
1 The “Settle Bill” use case is executed.
2 The use case ends here.
Alternate Flow: A2 (Issue Coupon)
1 The “Issue Coupon” use case is executed.
2 The use case ends here.
10. Transfer Fund
Use Case Number 10
Use Case Name Transfer Fund Author/Source Abdulaziz Alamoudi Date of Creation 10 November, 2009
Precondition(s) The customer might use a credit card for the payment.
Successful Post Condition The funds are transferred to the bank account.
Actors Bank Server
Priority Medium
Related Use Cases 9. Receive Payment
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user establishes a connection with the bank server.
E1: There is no connection.
2 The user enters the account number and the payment amount.
3 The system validates the information and sends it to the bank server.
A1: Invalid Account Number.
4 The bank server receives the information.
5 The funds are transferred.
6 The bank server sends a confirmation message.
7 The user confirms the message.
8 The use case ends.
Alternate Flow: A1 (Invalid Account Number)
1 The system displays a message that the account number doesn’t exist.
2 The flow returns to primary flow step 2.
Error Flow: E1 (There is no connection)
1 The system displays a message that there is no connection with the bank server.
2 The user confirms the message.
3 The use case ends in this position.
Page 36 11. Settle Bill
Use Case Number 11
Use Case Name Settle Bill
Author/Source Abdulaziz Alamoudi Date of Creation 17 November, 2009
Precondition(s) The customer must pay the remaining payment when returning the car.
Successful Post Condition The bill is settled and the customer’s file is legally cleared from any additional payment.
Actors Accountant.
Priority High
Related Use Cases 9. Receive Payment 10. Transfer Fund.
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user selects
“Settle Bill”.
2 The system prompts the user to enter the booking number.
3 The user enters the booking number.
4 The system displays the remaining payment.
A1: There is no additional payment.
5 The user confirms the bill.
6 The bill is printed.
7 The use case ends.
Alternate Flow: A1 (There is no additional payment) 1 The system displays a message that there is
no additional payment.
2 Te user confirms the message.
3 The flow goes to basic flow, step 5.
12. Issue Coupon
Use Case Number 12
Use Case Name Issue Coupon Author/Source Abdulaziz Alamoudi Date of Creation November 17, 2009
Precondition(s) The payment of must be received.
Successful Post Condition The coupon is issued.
Actors Accountant
Priority High
Related Use Cases 9. Receive Payment
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user clicks
“Issue Coupon” after receiving the payment.
2 The system displays the coupon containing the information regarding the rental:
Car rented.
3 The user clicks “Print Coupon”.
4 The coupon is printed.
5 The use case ends.
Page 38 13. Receive Car
Use Case Number 13
Use Case Name Receive Car Author/Source Shaeq Khan Date of Creation December 5, 2009
Precondition(s) Fleet Inspection has approved the car’s usage by customers.
Successful Post Condition The information about the car’s availability is updated.
Actors Dispatch Department
Priority Medium
Related Use Cases 15. Update Record 16. Issue Form
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user clicks
“Receive Car”.
2 The system prompts the user to enter the customer ID and booking number.
3 The user enters the required information.
A1: Information entered is invalid.
A2: Update record for the car
A3: Customer does not exist.
A4: Invalid Booking number.
4 The system displays a confirmation message.
5 The user confirms the message.
- A5: Customer requests for a copy of the form
6 The use case ends.
Alternate Flow: A1 (Information entered is invalid) 1 The system displays a message that the
information entered by the user is not of the same type of information accepted by the info field.
2 The user confirms the message.
3 The flow goes back to basic flow, step 2 Alternate Flow: A2 (Update Record for the car)
1 The use case 15 Update Record is executed 2 The flow goes back to basic flow, step 4 Alternate Flow: A3 (Customer does not exist)
1 The system displays a message that the customer with the entered ID does not
2 The user confirms the message.
3 The use case 8 Search Customer is executed
4 The flow goes back to basic flow, step 2 Alternate Flow: A4 (Invalid Booking number)
1 The system displays a message that the booking number entered is invalid.
2 The user confirms the message.
3 The flow goes back to basic flow, step 2 Alternate Flow: A5 (Customer requests for a copy of the form)
1 The use case 16 Issue Form is executed 2 The use case ends.
Page 40 14. Dispatch Car
Use Case Number 14
Use Case Name Dispatch Car Author/Source Shaeq Khan Date of Creation December 5, 2009
Precondition(s) Fleet Inspection has approved the car’s usage by customers.
Successful Post Condition The car has been handed over to the customer.
Actors Dispatch Department
Priority High
Related Use Cases Issue Form
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user clicks
“Dispatch Car”.
2 The system prompts the user to enter the customer ID and booking number.
3 The user enters the required information.
A1: Information entered is invalid.
4 The system displays a confirmation message for a valid booking.
A2: Customer does not exist.
A3: Invalid Booking number.
5 The user confirms the message.
6 Use case number 16 Issue form is executed.
7 The use case ends.
Alternate Flow: A1 (Information entered is invalid) 1 The system displays a message that the
information entered by the user is not of the same type of information accepted by the info field.
2 The user confirms the message.
3 The flow goes back to basic flow, step 2 Alternate Flow: A2 (Customer does not exist)
1 The system displays a message that the customer with the entered ID does not exist in the system.
2 The user confirms the message.
3 The flow goes back to basic flow, step 2 Alternate Flow: A3 (Invalid Booking number)
1 The system displays a message that the booking number entered is invalid.
2 The user confirms the message.
3 The flow goes back to basic flow, step 2
15. Update Record
Use Case Number 15
Use Case Name Update Record Author/Source Shaeq Khan Date of Creation December 5, 2009
Precondition(s) The dispatch department has received the car from the fleet inspection department.
Successful Post Condition The availability status of the car has been updated.
Actors Dispatch Department
Priority Medium