CAR RENT AND ONLINE RESERVATION

SYSTEM

Use cases (Fully Dressed Format)

Use Case UC1: Search Car

Scope: Car Rent and Online Reservation System
Level: user goal Primary
Actor: Customer and staf
Stakeholder and Interest:
CUSTOMER: The customer wants to search car from the car list
in order to display. The customer wants a car as he desired or
fulfill his/her budget or requirements for rented car.
Staff: The staf also wants to search car from the car list in order
to display.
Pre-condition: This use case helps to register rental
information of the customers and the car that the customer rents.
Customers wants to reserve and make schedule for renting car,
based on the availability of the CAR.

Success Guarantee (or Post-conditions):

Display the cars and information.

Main Success Scenario (or Basic Flow):

1. The staf or Customers clicks on search CAR BUTTON.
2. The system should displays combo box to select search for a
car.
3. The staf or customers select one of the following option from
the combo Boxcar Brand, Car Type, Car Model or default is all.
Clicks on search button
4. Then the system display all information about the car based on
selected option

Exceptions (or Alternative Flows):

4a. If any lists are not selected from the combo box system goes
back or returns to step 3 to select must option from the combo
box.

Special Requirements:
Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of
the system as a whole.

Usability:
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security:

The system provides username and password to prevent the

system from unauthorized access. The stafs password must be
greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
Should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:

The system should always be available for access at 24 hours, 7

days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Use Case UC2: Manage Car

Create/Add car
Scope: Car Rent and Online Reservation System
Level: user goal Primary
Actor: ADMIN
Stakeholder and Interest:
The admin should have want to add car information.
Pre-condition: The admin should have login and wants to add
cars information.

Success Guarantee (or Post-conditions):

Successfully add car information.

Main Success Scenario (or Basic Flow):

1. The Administrator logs onto the System.
2. The Administrator selects Tools from the Menu Bar.
3. The Administrator selects Add Car Information.
4. The System will display the list of all cars.
5. The Administrator shall click on add a car information button to
add a new car information.

6. After clicking the add button, a window will pop up showing

information to be input in the appropriate fields
7. The system will add all the information of the car created by
the Administrator.

Exceptions (or Alternative Flows):

*a. At any time, System fails:
1. To support the recovery admin restart the system and request
for prior system state.

1a. The user name and password cannot be verified

1. Admin re-enter the username and password and again request
for login.

1b. The system tells the user that username does not exist in
database.
1. Admin request for the recovery of previous account/create new
account.

Special Requirements:
Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of
the system as a whole.

Usability
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security

The system provides username and password to prevent the

system from unauthorized access. The stafs password must be
greater than eight characters.

Performance

The system response time for every instruction conducted by the

user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

View Car:
Scope: Car Rent and Online Reservation System
Level: user goal Primary
Actor: Customer and staf
Stakeholder and Interest:

Customer and Staff: This use case allows staf and

customers to view or display all cars with their complete detail
and description about the car.
Pre-condition: The customer wants to see car Rent, Reserve
car for their need or full fills his/her requirements.

Success Guarantee (or Post-conditions):

Views all available cars.

Main Success Scenario (or Basic Flow):

1. The staf or Customer wants to view car.
2. The staf or customer click on view cars button.
3. The system retrieves all information about the cars.

Extensions (or Alternative Flows):

3a. If in the database no matched car available or empty the
system should have display the message "this car is not available
sorry".

Special Requirements:

Non-functional requirements, such as performance, security, or

availability, usually specify or constrain characteristics of
the system as a whole.

Usability:
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security:
The system provides username and password to prevent the
system from unauthorized access. The stafs password must be
greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous

Update car
Scope: Car Rent and Online Reservation System
Level: user goal Primary
Actor: ADMIN
Stakeholder and Interest:
Admin: The admin should have want to update or modify car
information.

Pre-condition: The admin should have login and wants to

update cars information.

Success Guarantee (or Post-conditions):

Successfully update car information.

Main Success Scenario (or Basic Flow):

1. The admin wants to update car information.
2. Search car by its plate number because every car has unique
number plate.
3. The system should have display the all information about the
car.
4. The admin enters update information of car which he wants to
update.
5. The admin click on update button after successfully update the
information of required car.
6. The system should have successfully updates information in to
the database of the system.

Extensions (or Alternative Flows):

3a. If car is not found back to the step no 2.
Special Requirements:
Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of
the system as a whole.

Usability: The system provides a help and support menu in all

interfaces for the user to interact with the system. The user can
use the system by reading help and support.

Security:
The system provides username and password to prevent the
system from unauthorized access. The stafs password must be
greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and

should be able to provide response within a short time span

usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week .Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Delete/Remove Car

Scope: Car Rent and Online Reservation System

Level: user goal Primary
Actor: ADMIN
Stakeholder and Interest:
Admin: The admin should have want to delete car information.
Pre-condition: The admin should have login and wants to
delete cars information.

Success Guarantee (or Post-conditions):

Successfully delete car information.

Main Success Scenario (or Basic Flow):

1. The Administrator logs onto the System.
2. The Administrator selects Tools from the Menu Bar.
3. The Administrator selects car information.
4. The System will display the list of all cars.
5. The Administrator shall click on delete car button to delete car
information.
6. After clicking the delete button, a window will pop up showing
information to be input in the appropriate fields.
7. The system will delete all the information of the car entered by
the Administrator.

Exceptions (or Alternative Flows):

*a. At any time, System fails:
1. To support the recovery admin restart the system and request
for prior system state.
1a. The user name and password cannot be verified
1. Admin re-enter the username and password and again request
for login.

1b. The system tells the user that username does not exist in
database.
1. Admin request for the recovery of previous account/create new
account.

Special Requirements:
Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of
the system as a whole.

Usability:
The system provides a help and support menu in all interfaces for
the user tointeract with the system.The user can use the system
by reading help and support.

Security: The system provides username and password to

prevent the system from unauthorized access. The stafs
password must be greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

USE CASE UC3: Reserve Car

Scope: Car Rent and Online Reservation System
Level: user goal Primary
Actor: Customer

Stakeholders and Interests:

-Customer: The customer wants a car as he desired. This is
Customers to reserve and make schedule for renting vehicle,
Based on the availability of the vehicle.
-Staff: Allow staf to view or display customer
reservation. This IS to register rental information of the
customers and the vehicle that the customer rents. This is to
register rental information of the customers and the vehicle that
the
customer rents
-Manager: Allow Manager of the organization to generate a
report about the renting information of a month.

Pre-conditions: Customer wants to reserve a vehicle and

reservation
details that customer should have to entered.

Success Guarantee (or Post-conditions): information of

customer is saved.
customer have reserved the car. The staf see the reservation
detail
about the customer. payment is charged by customer and
notification of
successfully showed by customer.

Main Success Scenario (or Basic Flow):

1. The customer wants to reserve a car.
2. The customer clicks reservation page.
3. The system prompts the customer to fill a reservation form
4. The customer enters the following information
Customer (full name, ID no, City, Mobile number and selects
Vehicle plate number, Pickup date & return date)
5. The customer clicks reserve button to reserve.
6. The system checks all required information had been filled and
the date entered dates are valid
7. The system presents information to accept or decline the
rental Agreement.
8. The customer accepts the reservation terms and condition and
clicks
Accept.

Extensions (or Alternative Flows):

1a.The system promotes the customer to fill a reservation form.
If the customer enters invalid date and time, the system goes
back to
reserve button for reservation.
1b. The system checks all required information have been filled
and the
date entered dates are valid.
If the customer fills invalid information, the system goes back to
reserve button for reservation.
2a. The customer wants a car that is not available in this case

system should have to respond the choosen car is not available in

this date.The respond
3a.The system presents information to accept or rejects the
rental
Agreement.
If the customer rejects the agreement, the system displays a
message
that reservation cancelled.else The customer shows the
reservation
successfully.

Special Requirements:

Non-functional requirements, such as performance, security, or

availability, usually specify or constrain characteristics of
the system as a whole.
-Customers registration: The system should allow new users
to register
online.
- Online reservation of cars: Customers should be able to use
the
system to make booking and online reservation.

Usability:
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security: The system provides username and password to

prevent the system from unauthorized access. The stafs
password must be greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Use Case UC4: Rent Registration

Scope: Car Rent and Online Reservation System
Level: User Goal Primary
Actor: Staf
Stakeholder and Interests:
Customer: The customer wants to take the reserved vehicle.
Staff: A staf Member open rent page and than A staf Member
Enters the Details about the Costumer
System: The system displays a form to be filled out for renting
the vehicle than system verifies that basic fields have been filled
out and the system displays successful rent summary
Pre-conditions: The Staf Want To Enter the Rent Registration
Details of the Customers
Success Guarantee (or Post-conditions): Information
about the Costumer Is Save in System, The Customer Get the Car
and the Staf See Anytime Record of the Customer

Main Success Scenario (or Basic Flow):

1. The customer wants to take there served vehicle.
2. The staf open rent page
3. The system displays a form to be filled out for renting the
vehicle
4. The staf enters Full name, Nationality, Country, City,
Identification Number, Phone, Plate No, Down Payment, Daily
Price, Rent Date, Return Date, Total Rent Day, Total Payment, and
Refund
5. The system prompts to enter the following information.
6. The staf clicks on rent button.
The system displays successful rent

Extensions (or Alternative Flows):

1a: The Staf Member Want To Enter New Rent Registration Of
The New Costumer Who Want A Car On Rent
2a: The system displays a form to be filled out for renting the
vehicle.
3a: The Staf member Enter All Details Which Is required of the
costumer

4a: The If The Staf Member Cannot Fill Any Field Or Enter Invalid
( Name , Date , Payment Detail etc ) Than The System Show Error
To The Staf member That He enter the wrong details
4b: than staf member fill again the form with true details than
system check if everything is true than system accept the form
and save in database all details
Special Requirements: Non-functional requirements, such as
performance, security, or availability, usually specify or constrain
characteristics of the system as a whole.
If More Than 1 Staf member Want to Enter the Rent Registration
of Customers than the system allow more than 1 member for fill
form at the same time the recorded of the customer save in
database only staf members are able to edit or changed it

Special Requirements: Non-functional requirements, such

as performance, security, or availability, usually specify
or constrain characteristics of the system as a whole.

Usability:
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security: The system provides username and password to

prevent the system from unauthorized access. The stafs
password must be greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:

The system should always be available for access at 24 hours, 7

days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Use Case UC5: Update Rent

Scope: Car Rent and Online Reservation System

Level: User Goal Primary

Actor: Staf
Stakeholder and Interests:
Customer: The customer wants to get vehicle For More Days.
Staff: If Customer Want Vehicle For More Days Than A staf
Member open rent page and than A staf Member Update The
Rent Of The Costumer Or If The Staf member Enter Wrong
Payment Than He Edit The Payment
System: The system displays The Pervious Record of the
Customer form The Data base Than Staf Member Update the
Rent of the Selected Customer
Pre-conditions: The Staf Want To Update the Rent Details of
the Customers
Success Guarantee (or Post-conditions): The Rent
Details of the Customer Is Update Successful.

Main Success Scenario (or Basic Flow):

1: Staf wants to update rent
2: The Staf Member Open the Customers Detail page
3: Than Staf Member Search by unique ID which is give to
customer during rent.
4: The Staf Member updates the information
5: Click on update button.

Extensions (or Alternative Flows):

1a: The Staf Member Want To Update the Customer Rent
2a: The Staf Member Click on the Customers Details Button
3a: The Staf member Enter the unique ID which is give to
customer during Fill rent Page and the system displays the rent
information.
4a: The Staf member Update the Selected User Rent Information
5a: System Check That Every Field Is Fill No One Filed Is Empty
And Also Check Again its Valid If Its Cannot Valid Of Staf
member Empty Any Field System Show Error To The Staf Member
5b: Staf member Enter the Details Again System Check Again If
Its Valid Than Show The message Of Update

Special Requirements:

Non-functional requirements, such as performance, security, or

availability, usually specify or constrain characteristics of
the system as a whole.
The System Update The User Rent Also Increase / Decrease It In
Totals Of Customer And Total Of Company Payment.

Usability:
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security: The system provides username and password to

prevent the system from unauthorized access. The stafs
password must be greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Use Case UC6: View Reservation

Scope: Car Rent and Online Reservation System
Level: User Goal Primary
Actor:
Staf
Stakeholder and Interests:
Staff: This use case allows to staf wants to view or display
customer reservation.

Pre-conditions:
The staf should have login to view the reservation.

Success Guarantee (or Post-conditions):

Display all reservations of the cars.

Main Success Scenario (or Basic Flow):

1. The staf wants to view reservation of the cars.
2. The staf requests the reservation Page to view the reserve
cars.
3. The system responds the requested page.
4. Then on reservation page the employee clicks view button.
5. The system puts on view or displays all reservation information
to the employee.

Exceptions (or Alternative Flows):

5a. if reservation not found system goes to step no 2. If the again
reservation not found in this case system should have displays
the message this is not found".

Special Requirements:
Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of
the system as a whole.

Usability:
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security: The system provides username and password to

prevent the system from unauthorized access. The stafs
password must be greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Use Case UC7: Cancel Reservation

Scope: Car Rent and Online Reservation System
Level: User goal Primary
Actor: Customer
Stakeholder and Interests:
Customers: If the customer wants to cancel a reservation
because of some personal reasons or any other problem occurs
that time, or customer have an emergency.
Pre-condition: Customer already has reserved car which he
wants and wants to cancel the reservation of the car because of
some reasons.

Success Guarantee (or Post-conditions):

Customer successfully cancel a reservation of the car.

Main Success Scenario (or Basic Flow):

1. The customer wants to cancel reservation
2. The customer opens reservation page and clicks cancel
reservation link
3. The system displays a form
4. The customer enters reservation confirmation number and
clicks cancel reservation button
5. The system verifies the field has been filled out correctly and
checks validity of confirmation number, then popup a message to
verify the canceling
6. Are you sure you want to cancel, the customer clicks Yes
button.
7. The system cancels the reservation and display a message the
reservation is canceled.

Extensions (or Alternative Flows):

5a. if the customer enters invalid number system goes back or

returns to step 4. To fill invalid or the empty field again.
6a. If the customer clicks NO reservation canceling will be
terminated.

Special Requirements:
Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of
the system as a whole.

Usability:
The system provides a help and support menu in all interfaces for
the user to interact with the system. The user can use the system
by reading help and support.

Security: The system provides username and password to

prevent the system from unauthorized access. The stafs
password must be greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The

system should have high performance rate when executing users

input and
Should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Use Case UC8: Generate Report

Scope: Car Rent and Online Reservation System
Level: User Goal Primary
Actor: Manager
Stakeholder and Interests:
Manager: The Manager wants see the Monthly / Weakly Report
of Renting

System: The system only displays Report to the Manager

Pre-conditions: Manager wants to see the report Of the
Business

Success Guarantee (or Post-conditions): Generate

Report Information and show it to the manger

Main Success Scenario (or Basic Flow):

1:
2:
3:
4:

The
The
The
The

Manger
Manger
Manger
Manger

Want To See the Report

Login in His Account
Click on the View Reports Button
Download the Reports

Extensions (or Alternative Flows):

1a: The Manager wants to generate report.
2a: Manger Click On Manger login Button And Enter His User
name And Password If Its True Manger Go To His Account
Otherwise System Show Error Message To The Manger And Show
Form Again TO Fill if its true than manger login in his account
3a: The Manager clicks On Reports Button
3b: The system responds the requested page
3c: Then on the Reports page the Manager specifies the month
and then clicks on the generate button.
4a: The Manger See the Report If He Want to Download It than He
Clicks On Download Report Button and Report Is Download

Special Requirements: Non-functional requirements, such

as performance, security, or availability, usually specify
or constrain characteristics of the system as a whole.
The system only show The Reports to The Manger No one Else
And the manager is able to select the month which Report he
want to see.

Usability: The system provides a help and support menu in all

interfaces for the user to interact with the system. The user can
use the system by reading help and support.

Security: The system provides username and password to

prevent the system from unauthorized access. The stafs
password must be greater than eight characters.

Performance:
The system response time for every instruction conducted by the
user must not exceed more than a minimum of 10 seconds. The
system should have high performance rate when executing users
input and
should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25
seconds for less complicated task.

Availability:
The system should always be available for access at 24 hours, 7
days a week. Also in the occurrence of any major system
malfunctioning, the system should be available in 1 to 2 working
days, so that business process is not severely afected

Frequency of Occurrence: Could be nearly continuous.

Use Case UC9: Login

Scope: Car Rent And Online Reservation System
Level: User Goal Primary
Actor: Customer, Staf
Stakeholders and Interests:
Customer: The Customer Wants A car So He / She Login In The
Account And Reserve A Car And See The Rates Of The Car .
Staff: Staf Can See the Customer Records and See How Many
Cars Are Reserved So Staf members Login In There Account And
See

Pre-conditions: The Customer First Login Into Account To

Reserve A Car And See Reservation Or Rates of Cars .
Success Guarantee (or Post-conditions): When Any
User Login In TO The Account Then They Can Reserve Any Car
And Its Record Save In DATA Base And the Staf members Can
Also Check The Details Of Customers .
The Payment Is Charged By The Customer And Notification Of
Successfully Showed In The customer Account.

Main Success Scenario (or Basic Flow):

1.The staf is on the home page to login to the system.

2. The system promotes the staf toenter Username, Password

3. The staf enters username and password, Click on LoginButton.
4. The system verifies that all thefilled have been filled out and
valid
5. The system successfully logged inthe system

Extensions (or Alternative Flows):

1a.The system promotes the customer to fill a Login form.
If the customer enters invalid Email Or Password the system Show
Error Of Invalid Email Or Password )
1b. The system checks all required information have been filled
and The Email And Password Is Valid Then User Enter In There
Account If the customer fills invalid information, the system goes
back to
The Login Page With Error Message .
2a. If The Customer Forget His Email Or Password Then HE / She
Click On The Forget Email Or Password Button Then He / She Goes
To The Recovery Page And Enter His User Name If Its Exsits In The
DB Than His Login Details Send To The User Email
3a. If The User Click On The Keep me Login Then System Save His
Browser And When He Open The Site He Is Automatically Login In
His Account Untill He Clear His Browser Cookie .
Frequency of Occurrence: Could be nearly continuous.