Basic flow Steps
1 The use case begins when the user selects
“Book Car”.
2 The system prompts the user to enter the customer’s file number.
3 The user enters the customer’s file number and clicks “OK”.
A1: Add Customer.
A2: Search Customer.
A3: Modify Customer.
A4: View Customer.
4 The system displays the booking screen along with the discount offer.
A5: The user entered an invalid file number.
5 The user selects the type of car in the checkbox that contains:
o Sports car.
o SUV.
o Station wagon.
o Other car types.
The user enters the start/end date of car rental.
6 The system displays cars available with the faire per period.
A6: No cars available.
requests.
8 The system displays a confirmation screen that contains:
The car rented.
The start/end date.
The amount the customer has to pay.
The discount offered.
9 The user confirms the criteria.
10 The use case ends.
Alternate Flow: A1 (Add Customer)
1 The “Add Customer” use case is executed.
2 The flow goes to step 4 of the primary flow.
Alternate Flow: A2 (Search Customer)
1 The user selects “Search Customer”
2 The “Search Customer” use case is executed.
3 The flow goes to step 4 of the primary flow.
Alternate Flow: A3 (Modify Customer)
1 The “Modify Customer” use case is executed.
2 The flow goes to step 4 of the primary flow.
Alternate Flow: A3 (View Customer)
1 The “View Customer” use case is executed.
2 The flow goes to primary flow, step 4.
Alternate Flow: A5 (Invalid File Number)
1 The system displays a message that the entered file doesn’t exist.
2 The user confirms the message.
3 The flow returns to step 3 of the primary flow.
Alternate Flow: A6 (No Cars Available)
1 The system displays a message that there are no cars available.
2 The user confirms the message.
3 The flow returns to step 5 of the primary flow.
Page 26 2. Modify Booking
Use Case Number 2
Use Case Name Modify Booking Author/Source Abdulaziz Alamoudi Date of Creation November 17, 2009
Precondition(s) A valid booking must exist in the customer’s file.
Successful Post Condition - The return date of the booked car is changed.
- The car booked might be changed.
Actors Receptionist
Priority Medium.
Related Use Cases 4. Search Booking
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user selects
“Modify Booking”.
2 The system prompts the user to enter the customer’s booking number.
A1: Search Booking.
3 The user enters the booking number and clicks “View”.
A2: Invalid Booking Number.
4 The system displays the booking profile.
5 The user changes the required information:
Return date.
Car rented.
6 The system generates a confirmation message.
7 The user confirms the message.
8 The use case ends.
Alternate Flow: A1 (Search Booking)
1 The “Search Booking” use case is executed.
2 The flow goes to the basic flow, step 3.
Alternate Flow: A2 (Invalid Booking Number)
1 The system displays a message that the entered booking number doesn’t exist.
2 The user confirms the message.
3 The flow returns to the basic flow, step 2.
3. Cancel Booking
Use Case Number 3
Use Case Name Cancel Booking Author/Source Abdulaziz Alamoudi Date of Creation November 17, 2009
Precondition(s) - The car must be booked.
- The receptionist must enter the booking number.
Successful Post Condition The car booking is canceled.
Actors Receptionist
Priority Medium.
Related Use Cases 4. Search Booking
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user enters the customer’s booking number.
A1: Search Booking.
2 The system displays the booking profile.
A2: The booking number doesn’t exist.
3 The user cancels the booking.
4 The system generates a confirmation message.
5 The user confirms the message.
6 The use case ends.
Alternate Flow: A1 (Search Booking)
1 The “Search Booking” use case is executed.
2 The flow goes to the basic flow, step 2.
Alternate Flow: A2 (The booking number doesn’t exist) 1 The system displays a message that the
entered booking number doesn’t exist.
2 The user confirms the message.
3 The flow returns to the basic flow, step 1.
Page 28 4. Search Booking
Use Case Number 4
Use Case Name Search Booking Author/Source Abdulaziz Alamoudi Date of Creation November 17, 2009
Precondition(s) In the case that the customer lost the booking number, the receptionist needs to enter the customers name or mobile number in the required field.
Successful Post Condition The booking file is viewed.
Actors Receptionist
Priority Low.
Related Use Cases 2. Modify Booking.
3. Cancel Booking.
Flow of Events Basic Flow
Step Number Steps
1 The system prompts the user to enter:
Customer’s phone number.
Customer’s driving license number.
Customer’s name.
2 The user enters the required information.
3 The system displays the profile.
The booking doesn’t exist.
4 The use case ends.
Alternate Flow: A1 (The booking doesn’t exist)
1 The system displays a message that the booking doesn’t exist.
2 The user confirms the message.
3 The flow goes to the basic flow, step 1.
5. Add Customer
Use Case Number 5
Use Case Name Add Customer Author/Source Abdulaziz Alamoudi Date of Creation November 10, 2009
Precondition(s) When a customer wants to book a car and he doesn’t have a previous instantiated account, then the receptionist adds a customer.
Successful Post Condition The customer is added to the system.
Actors Receptionist
Branch Manager
Priority High.
Related Use Cases 1. Book Car.
6. Modify Customer.
7. View Customer.
8. Search Customer.
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user clicks
“Add Customer”.
2 The system displays the “New Customer”
screen and prompts the user to enter the required information:
Name.
National ID.
Driving License.
Offered Discount.
Address.
Occupation (Job).
Company.
3 The user enters the required information.
4 The system displays a confirmation message to confirm the criteria.
A1: The user missed a required area.
A2: The information already exists.
5 The user confirms the message.
6 The use case ends.
Alternate Flow: A1 (The user missed a required area) 1 The system prompts the user that he didn’t
enter required information.
2 The user enters the information.
3 The flow returns to the basic flow, step 4.
Alternate Flow: A2 (The information already exists) 1 The system displays a message that the
Page 30
information already exists.
2 The user confirms the message.
3 The system displays the duplicated information.
4 The user might change the information.
A3: Search Customer.
5 The flow returns to the basic flow, step 2.
Alternate Flow: A3 (Search Customer)
1 The “Search Customer” use case is executed.
2 The use case ends.
6. Modify Customer
Use Case Number 6
Use Case Name Modify Customer Author/Source Abdulaziz Alamoudi Date of Creation November 10, 2009
Precondition(s) When the customer requests to book a car, he might want to change some of the information existing in his file like a mobile phone or an address.
Successful Post Condition The customer file is modified and the old data is updated.
Actors Receptionist
Branch Manager
Priority Low.
Related Use Cases 1. Book Car
8. Search Customer
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user clicks
“Modify Customer” and enters the customer’s file number.
A1: Search Customer.
2 The system displays the customer’s profile.
3 The user changes the required information and clicks”OK”.
4 The system displays a confirmation message.
5 The user confirms the message.
6 The use case ends.
Alternate Flow: A1 (Search Customer)
1 The “Search Customer” use case is executed.
2 The use case ends.
Page 32 7. View Customer
Use Case Number 7
Use Case Name View Customer Author/Source Abdulaziz Alamoudi Date of Creation November 10, 2009
Precondition(s) When the customer requests to book a car, the user might want to view the customer’s file to validate specific
information.
Successful Post Condition The customer’s file is displayed to the user.
Actors Receptionist
Priority Low.
Related Use Cases 1. Book Car
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user clicks
“View Customer” in the booking screen.
2 The system displays the customer’s file.
3 The user clicks “OK” when he finishes checking the file.
4 The use case ends.
8. Search Customer
Use Case Number 8
Use Case Name Search Customer Author/Source Abdulaziz Alamoudi Date of Creation 10 November, 2009
Precondition(s) When the customer requests booking a car in the case that the customer forgot his file number the user will search using the customer’s phone number or name.
Successful Post Condition The system displays the customer’s file to the user.
Actors Receptionist
Branch Manager
Priority High
Related Use Cases 1. Book Car.
5. Add Customer.
6. Modify Customer.
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user selects
“Search Customer”.
2 The system displays a search engine screen that contains the fields:
Name.
Driving License.
National ID.
Phone Number.
2 The user enters the customer’s searching information name and clicks “Search”.
3 The system displays a message that the file was found.
A1: The file is not found.
4 The user clicks on the file icon.
5 The system displays the file.
6 The user clicks “OK”.
7 The use case ends.
Alternate Flow: A1 (The file is not found)
1 The system displays a message that the file is not found.
2 The user confirms the message.
3 The flow returns to basic flow, step 2.
Page 34 9. Receive Payment
Use Case Number 9
Use Case Name Receive Payment Author/Source Abdulaziz Alamoudi Date of Creation 17 November, 2009
Precondition(s) The customer pays the accountant the amount of money required.
Successful Post Condition The accountant issues a coupon for the customer and settles the bill afterwards.
Actors Accountant
Priority High
Related Use Cases 10.Transfer Fund.
11. Settle Bill.
12. Issue Coupon.
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