Professional Documents
Culture Documents
1. Register
Table 1: Use Case - Register
Use-case UC-01
Number
Use-Case Name Register a user.
Priority High
Actor Customer
Description This use case describes how Customers to Register into the Pheonix
online booking System.
Precondition None.
Post-condition If the use case was successful, the actor is now Registered into the
Pheonix online booking system. If not, the system state is unchanged.
Basic course of User Action System Response
Action 1. The user is on the home page to 2. The system promotes the user to
Register to the system. enter User’s Name,Father
Name,Birthdate,Contact No.
3. The User’s enter his/her ,Occupation,Address, Email
Name,FatherName,Birthdate, account and Password.
Contact No. ,Occupation, 4. The system verifies that all the
filled have been filled out and
Address, Email account and valid.
Password , Click on Register 5. The system successfully Register
Button. in the system.
6. Use case Exit
Alternate course 6.1 If all fields are not filled out the system notifies the actor a message
of Action please fill out the blank field and then goes back or returns to step 4 of
basic course of Action to enter again.
2. Login
Table 2: Use Case - Login
Use-case UC-01
Number
Use-Case Name Log in
Priority High
Actor Staff,customer
Description This use case describes how Staffs and customers to login into the online
booking System.
Precondition The user/staff must be registered.
Post-condition If the use case was successful, the actor is now logged into the online
booking system. If not, the system state is unchanged.
Basic course of User Action System Response
Action 3. The user is on the home page to 4. The system promotes the user to
login to the system. enter Username, Password.
7. The system verifies that all the
3. The user enters username and filled have been filled out and
password, Click on Login valid.
Button. 8. The system successfully logged in
the system.
9. Use case Exit
Alternate course 6.1 If all fields are not filled out and not matched to the username and
of Action password the system notifies the actor a message Invalid Username or
Password and then goes back or returns to step 4 of basic course of
Action to enter again.
3. Reserve Vehicle
Table3: Use Case - Reserve Vehicle
Use-case UC-03
Number
Use-Case Name Reserve vehicle
Priority High
Actor Customer
Description This use case permits customers to reserve and make schedule for
renting vehicle, based on the availability of the vehicle.
Precondition Customer wants to reserve a vehicle and reservation details about
customer have to be entered.
Post-condition Customers reserve successfully
Basic course of User Action System Response
Action 1. The customer wants to reserve 3. The system prompts the
a vehicle. customer to fill a reservation
2. The customer clicks reservation form .
page. 6. The system checks all required
4. The customer enters the information had been filled and
following information customer the date entered dates are valid
(full name, ID/Passport No, 7. The system presents information
Country, Mobile number and to accept or decline the rental
selects vehicle plate number, Agreement.
Pickup date & drop date),Drop 9. The system shows the customer
off location. that the reservation has been
5. The customer clicks reserve completed, and presents the
button to reserve. customer a reservation
8. The customer accepts the confirmation number.
reservation and clicks Accept. 10. Use case ends.
Alternate course 6.1 If the customer enters invalid date and time, the system goes back to
of Action step 4 to enter the valid date and time.
6.1 If the customer fills invalid information, the system goes back to
step 4 to enter the invalid field again.
7.1 If the customer declines the agreement, the system displays a
message that reservation canceled.
4. Payment Registration
Table 4: Use Case - Payment Registration
7. Update Vehicle
Table 7: Use Case - Update Vehicle
Use-Case Number UC-07
Use-Case Name Update Vehicle
Priority High
Actor Staff
Description This use case permits staff to update or modify vehicle information.
Precondition UC-1, UC-6
Post-condition updated vehicle information
Basic course of User Action System Response
Action 1. The user wants to update vehicle 3. The system will display all
information. information about the vehicle.
2. Search vehicle by plate number. 6. The system successfully updates
4. The staff enters update information in to database.
information of vehicle. 7. Use case Ends.
5. The employee click on update
button.
Alternate course of 3.1 If vehicle is not found back to basic course of action 2
Action
8. View Vehicle
9. Update Rent
Table 3: Use Case - Update Rent
Use-Case Number UC-08
Use-Case Name Update Rent
Priority High
Actor Staff
Description This use case permits employee to update or modify Rent information
incase when there is a need for editing
Precondition Need to Change information
Post-condition Successful Update Message
Basic course of User Action System Response
Action 1. Staff wants to update rent. 4. The system displays the rent
2.Open the rent page information.
3. Search by unique attribute which 7. The system validates updated
is give to customer during rent. information and saves updated
5.The Staff update the information information in to database.
6. Click on update button. 8. Exit use case.
Alternate course of 4.1 If match is not found go back to basic course of action 3.
Action 7.1if the entered information is invalid the system back to basic course
of action 5
10. Cancel Reservation
Table 10: Use case - Cancel Reservation
Use-Case UC-10
Number
Use-Case Name Cancel a Reservation
Priority Medium
Actor Customer
Description This use case permits a customer to cancel a reservation.
Precondition Customer already has reserved and wants to cancel the reservation
Post-condition Customer successfully cancel a vehicle
Basic course of User Action System Response
Action 1. The customer wants to cancel 3.The system displays a form
reservation 5. The system verifies the field
2. The customer opens reservation has been filled out correctly and
page and clicks cancel reservation checks validity of confirmation
link number, then popup a message to
4. The customer enters reservation verify the canceling.
confirmation number and clicks 7. The system cancels the
cancel reservation button. reservation and display a message
6. Are you sure you want to cancel, the reservation is canceled.
the customer clicks “Yes” button. 8.use case Exit
Alternate course 5.1 If the customer enters invalid number system goes back or returns to
of Action step 4 of basic course of Action. To fill invalid or the empty field again.
6.1 If the customer clicks “NO” reservation canceling will be terminated.
Use-Case UC-11
Number
Use-Case Name View Reservation
Priority Medium
Actor Staff
Description These use case allow staff to view or display customer reservation.
Precondition UC-1
Post Condition Display all reservations
Basic Course of User Action System Response
Action 1. The staff wants to view 3. The system responds the requested
reservation. page.
2. The staff requests the 5. The system puts on view or
reservation Page. displays all reservation
4. Then on reservation page the information to the employee.
employee clicks view button. 6. Use case ends
Alternate course of 5.1 If reservation not found system goes to basic course of action 6.
Action
13. Logout
Table13: Use Case – Logout
Group Members:
Mujtaba Ali (27027) (Team leader).
Qazi Arsalan (28511)
Ghafoor shah (23781)
Zeeshan Ahmed (27645)
Abdul Wali shahid (25658)
Information System diagram :
Register Login
Electronic-
Devices
Search Vehicle
View Vehicle
Update Vehicle
OS
Internet
Reserve Vehicle
Payment Registration
Admin
Employee Vehicle Registration
Customers
Guest
Cancel Reservation
Generate Report
Employee data
Customer data
Admin data Log out
Guest data
UseCase diagram :
Register
Login
Manage Booking
Manage Data
Update Data
Client Information
Record Keeping
procurements
Employee