Sunteți pe pagina 1din 12

Use-case Description :

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

Use-case Number UC-04


Use-Case Name Payment Registration
Priority High
Actor Staff
Description This use case permits to register payment information of the customers
and the vehicle that the customer rents.
Precondition UC-3
Post-condition Customer rent information
Basic course of User Action System Response
Action 1. The customer wants to take the 3. The system displays a form
reserved vehicle. to be filled out for renting the
2. The staff open rent page. vehicle.
4.The staff enters Full name, 4. The system prompts to enter
Nationality, Country, City, the following information.
Identification Number, Phone, Plate 6. The system verifies that
No, Down Payment, Daily Price, Rent basic fields have been filled
Date, Return Date, Total Rent Day, out.
Total Payment, Refund 7. The system displays
5. The staff clicks on rent button. successful rent summary
8. Use case Exit.
Alternate course 6.1 If Full name, Nationality, country, City, Id/Passport, Phone, Truck
of Action Plate No, Down Payment, Price/day, Rent Date, Return date and Total
Payment this fields are not filled out system goes back or returns to step
4 of basic course of Action. To fill invalid field.
5. Vehicle Registration

Table5: Use Case - Vehicle Registration

Use-Case Number UC-04


Use-Case Name Vehicle Registration
Priority High
Actor Staff
Description These use case permits staff to register New Vehicles to the system with
detail descriptions about the Vehicle such as condition, Model number,
fuel type, size and amount of price per day.
Precondition New vehicle Purchased
Post-condition New Vehicle information stored successfully.
Basic course of User Action System Response
Action 1. The staff wants to add a new 3. The system response or
vehicle displays a form to be filled out
2. The staff requests add new vehicle for vehicle registration.
form page. 6. The system verifies that the
4. The staff enters the following fields have been filled out
information in the form. correctly.
Vehicle Brand, Vehicle Type, Vehicle 7. The system displays a
Model, Fuel Type, Plate Number, successfully stored message to
Size, Condition, Price per day,price per the employee.
week. 8. Use case Exit
5. The staff clicks or presses on the
save or insert button.
Alternate course 6.1 If all fields are not filled out the system goes back or returns to step
of Action 4 of basic course of Action. To fill the invalid or the empty field.
6. Search Vehicle
Table 6: Use Case - Search Vehicle
Use-Case UC-06
Number
Use-Case Name Search Vehicle
Priority Medium
Actor Staff and customer
Description This use case permits staff and customer to search vehicle from the
vehicle list in order to display.
Precondition UC-1,UC-2
Post-condition Display
Basic course of User Action System Response
Action 1. The staff or Customers clicks on 2.The system displays combo box
search vehicle link. to select search to a vehicle.
3. The staff or customers select one 4. Then the system display all
of the following lists from the information about the vehicle based
combo Box, Vehicle Size,Vehicle on selected list.
Type. Vehicle num. or default is All. 6. Use case End.
Clicks on search button.
Alternate course 4.1 If any lists are not selected from the combo box system goes back or
of Action returns to step 3 of basic course of Action to select from the combo box.

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

Table 8: Use Case – View Vehicle


Use-Case Number UC-07
Use-Case Name View Vehicle
Priority Medium
Actor Staff and customer
Description This use case allows staff and customer to view or display all vehicles
with their detail description about the vehicle.
Precondition Vehicle Rent, Reserve
Post-condition Views all vehicles
Basic course of User Action System Response
Action 1. The staff or Customer wants 3. The system retrieves all
view vehicle. information about the vehicles.
2. The staff or customer click on 4. Use case exit.
view vehicles button.
Alternate course of 3.1 If in the database no matched vehicle available or empty go to
Action Basic course action of 4.

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.

11. View Reservation

Table11: Use Case - View Reservation

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

12. Generate Report

Table 4: Use Case - Generate Report


Use-Case Number UC-12
Use-Case Name Generate Report
Priority High
Actor Manager
Description These use case allow Manager of the organization to generate a report
about the renting information of a month.
Precondition Manager wants to see report
Post Condition Generate monthly Report Information
Basic Course of User Action System Response
Action 1. The Manager wants to generate report. 3. The system responds
2. The Manager clicks rent pages. the requested page.
5. Then on the rent page the Manager specifies 7. Use case ends
the month and then clicks on the generate
button.
Alternate course of 7.1 If the reservation information is empty or not found go to 8.
Action

13. Logout
Table13: Use Case – Logout

Use-Case Number UC-13


Use-Case Name Log out
Priority High
Actor Staff , Customer and Manager
Description These use case allow Staff and Customer to log out from the
system at a time of accomplishing their work.
Precondition UC-1
Post Condition System logs out
Basic Course of User Action System Response
Action 1. The Staff or 3. The system responds to the requested
manager wants to action.
log out 4. The system displays a message that the
2. The Staff , Staff ,Customer or Manager logged out
Customer or from the system.
Manager clicks the 5. Use case Ends
log out button
“INTRODUCTION TO SOFTWARE ENGNEERING”

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

View Available Vehicle

Customer Confirm Booking

Manage Data

Update Data

Vehicle Information Admin

Client Information

Record Keeping

procurements
Employee