Rental Car Management System

Independent University, Bangladesh

CSC-445 Software Engineering

Spring- 2016

1|Page
Rental Car Management System Final Project -CSC445
 Submitted by:

M. Rashed Mahamaud Rayhan Sardar Tipu

ID: 1320156 ID: 1330418
Project lead Bachelor in Computer Science & Engineering
Bachelor in Computer Science

Mir Noor-UL-Haque Pias Abdul Munim

ID: 1210168 ID: 1621738
Bachelor in Computer Science Masters in Software Engineering

Golam Rakib
ID: 1621707
Masters in Software Engineering

Submitted to:

Dr. Mahady Hasan

Department of Computer Science & Engineering
Table of Contents

Overall operational concept of the system..............................................................................................................5

Introduction.............................................................................................................................................................5
Currently available Systems.....................................................................................................................................5
Problem and difficulties in the current system.........................................................................................................6
The need of improved distributed services..............................................................................................................6
Proposed Envisioned Distributed system with Rich picture.................................................................................7
Benefit of the Envisioned/proposed system.........................................................................................................8
Analyze the detail requirement and Develop functional and non-functional requirements....................................8
Functional Requirement.......................................................................................................................................8
Reservation.......................................................................................................................................................8
Vehicle..............................................................................................................................................................9
Rent.................................................................................................................................................................. 9
Non-Functional Requirements.............................................................................................................................9
Usability............................................................................................................................................................9
Security...........................................................................................................................................................10
Performance...................................................................................................................................................10
Availability......................................................................................................................................................10
Architectural design and evaluate benefits as well as liabilities.............................................................................10
Detailed description...........................................................................................................................................13
Advantages.........................................................................................................................................................13
Liability...............................................................................................................................................................13
End to end Quality Control Process........................................................................................................................13
Test Plan.............................................................................................................................................................13
Introduction........................................................................................................................................................13
Project Name..................................................................................................................................................13
Project Leads:.................................................................................................................................................14
Test Project Task.............................................................................................................................................14
Defect Tracking and reporting System................................................................................................................14
Testing Synopsis.................................................................................................................................................15
Items to be tested Items.................................................................................................................................15
 Items not to be Tested...................................................................................................................................16
Test Environment/System Requirements...........................................................................................................16
HARDWARE INTERFACE REQUIREMENTS.......................................................................................................16
SOFTWARE INTERFACE REQUIREMENTS........................................................................................................16
COMMUNICATIONS INTERFACE REQUIREMENTS...........................................................................................17
Standards/Reference material........................................................................................................................17
Testing Scope.....................................................................................................................................................17
Unit Testing....................................................................................................................................................17
Smoke Testing................................................................................................................................................17
Feature level testing.......................................................................................................................................17
Functional Tests..............................................................................................................................................18
Integration Testing.........................................................................................................................................18
System Testing................................................................................................................................................18
Security Testing..............................................................................................................................................18
Test Schedule and Resources.............................................................................................................................18
Major Activities Schedule:..............................................................................................................................18
Test Phases and Completion criteria..................................................................................................................18
Issues and Risks..................................................................................................................................................19
Test Cases Functional.............................................................................................................................................19
Work Breakdown Structure of the Rental Car Management System.....................................................................24
Critical Path............................................................................................................................................................25
Gantt Chart of the Rental Car Management System..............................................................................................26
Overall operational concept of the system.

Introduction

This chapter of the project document which provides a general introduction about the Rental Car Management
system project. The chapter contains and describes about background of the organization, existing system
functions and problems.

This chapter also describes about the proposed system, objective including the general and specific objectives of
the project.

Currently available Systems

Prime Car Rental (PRC) organization gives car rental service for both foreign and local customers. This
organization carries out its daily work by providing; their service to the customers using manually system. The
organization uses a manual system for reserving, renting, register and to keep record of all the rental activities and
customer information. The detailed existing system functions are listed as follows: -

 During vehicle reservation the customers reserve a vehicle by making a phone call to the
organization; otherwise he/she is expected to go to the organization to make reservation.
 During renting a vehicle the customer personal information, payments status and rent
agreements are filled in the car rent agreement form; in order to hold legal contract between the
customer and organization for renting the vehicle.
 The organization normal work time schedule is from 8:00am – 11:00pm; therefore the
organization gives services for fifteen hours a day.
The organization makes a general report about the rented vehicles once at the end of the month and generates
a report.
Problem and difficulties in the current system

The existence system has a number of problems in the working procedure for the organization and customers.
These problems are: -

1. During reservation a customer reserve a vehicle on phone or expected to go to the organization for
reserving. This has its own problem in the business sector.
 The organization phone may be busy or may not work when customer is calling to make
reservation.
 It may be difficult to customers to get the phone number or the location of the organization.
 The customers may be resulted to unnecessary extra expense and waste their time.
 Their may accrue duplicated reservation of the same vehicle.
 The organization may not be able to serve many customers.
 The customers may not get service of the organization 24/7 ( twenty four hours a day and seven
days a week).

2. During renting a vehicle, the customer information and contract made between them are filled in a
form.
 The contract form made between the customer and organization may be difficult to find incase
of misplacing or disappearing due to massive collection of data.

3. During generating monthly report.

 When generating report, it takes time and it may not be easy to manage and analysis the monthly
work due to massive collection of data and the generated report may not be accurate.

The need of improved distributed services

Following is the need of improved distributed services,

 The new system is totally computerized system.
 A new system provides features like time efficiency to show car details, user profiles and
whatever the customer will give the feedback to the admin.
 This system provides tourism and traveling facilities.
 An inquiry is easily done by user in the system.
 It is the most software application for managing online car rental business.
 Proposed Envisioned Distributed system with Rich picture

Proposed Envisioned Distributed system with Rich picture

7|Page
Rental Car Management System Final Project -CSC445
 Benefit of the Envisioned/proposed system
First of all it would be a growth-oriented car rental organization by efficiently serving value-conscious customers
for all of their car rental occasions.

Secondly it will consistently deliver a quality product, friendly service and great value that make customers
confident that Budget is their best car rental choice.

Analyze the detail requirement

and non-functional and Develop functional
requirements

Functional Requirement

Functional requirements these are statements of services the system should provide, how the system should react
to particular inputs, and how the system should behave in particular situations. It specifies the software
functionality that the developers must build into the product to enable users to accomplish their tasks.

Reservation

1. The system must allow the customer to register for reservation.

2. The system shall allow the customer to view detail description of particular vehicle.
3. The system must notify on selection of unavailable vehicles while reservation.
4. The system shall present an option for advanced search to limit the vehicle search to specific categories of
vehicles search. E.g. By Brand, Type and Model.
5. The system must view list of available vehicles during reservation.
6. The system shall allow the customers to cancel reservation using reservation confirmation number.
7. The system shall allow the employee to update reservation information.
8. The system shall allow the employee to view reservations made by customers.
9. The system must be able to provide a unique reservation conformation number for all successfully
committed reservations.
10. The system must be able to display reservation summary for successfully committed reservation.

8|Page
Rental Car Management System Final Project -CSC445
 Vehicle

11. The system should allow staff to register new vehicles.

12. The system shall allow staff to update information of the vehicle in need of modification.
13. The system shall allow staff to display all lists of vehicle.
14. The system shall allow staff to display all available vehicle.
15. The system shall allow staff to display all rented vehicle.
16. The system shall allow staff to display all off duty vehicles.

Rent

17. The system shall allow staff to register customers into rental list.
18. The system shall allow staff to update about customer rent record details in the rental list.
19. The system shall allow staff to display customers, who rent vehicles.
20. The system must provide printable summary for successful committed rent.

Non-Functional Requirements

Introduction
Non-functional requirements, as the name suggests, are requirements that are not directly concerned with the
specific services delivered by the system to its users. They may relate to emergent system properties such as
reliability, response time, and store occupancy. Alternatively, they may define constraints on the system
implementation such as the capabilities of I/O devices or the data representations used in interfaces with other
systems. 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 staffs’ 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 user’s 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 affected.

Architectural design and evaluate benefits as well as

liabilities

Here we will use Three-tier architecture. Three-tier architecture is a client–server software architecture pattern
in which the user interface (presentation), functional process logic ("business rules"), computer data storage and
data access are developed and maintained as independent modules, most often on separate platforms.
 Data services
Master DB Data warehouse

Primary Slave DB DB

Sync
Scheduler

DB cluster manager
O
L
A
P

p
r
o
v
i
d
e
r
s

Data Provider Bus (DPS)

Agent Directory Pro R Vehicle profile

vid e
er s
pro e
file r
v
a
ti
o
n

Local Local
A Local Pro Local Vehicle
g vid
e er Reser
n vatio
t
n
DB DB DB DB
services services

ser ser
vic vic
es es

Enterprise System Bus (ESB)

11Ag|enPt Agent 1 customers Agent 2 customer Agent 2 customers Agent 3 customers Agent 3 customers
1 acugstoemers Rental Car Management System Final Project -CSC445
 Agent UI services

services

Car rent providers

Servers

Load balancer Load balancer

Car
rent
pro
vide
rs

A A Agent 3
g

Local DB Local DB Local DB

A A A
g g g
e
n
t

F
r
o
n
t

e
n
d

11Ag|enPt Agent 1 customers Agent 2 customer Agent 2 customers Agent 3 customers Agent 3 customers
1 acugstoemers Rental Car Management System Final Project -CSC445
12 | P a g e
Rental Car Management System Final Project -CSC445
 Detailed description
Central car rental system allows agents to plug-in to the system and allows agents to reserve, look-up, follow-up,
track any vehicle associated with the agent. Agent system consumes core UI services for all functional
requirements and allows agents create them on application on top of the enterprise stack.

Individual providers are also provided with a portal to register and hire-out cars to agents. Provider portal uses
core UI services in the ecosystem.

Core UI services is loosely coupled in the enterprise stack and only loads the Façade component from enterprise
service bus. Enterprise service bus is responsible to handle the downstream system and it only knows which
component to consume and interact for certain functionality in the functional requirements.

Downstream components i.e. Agent directory, provider profile, vehicle etc. are behind the enterprise system bus
and they are loaded in the enterprise stack loosely within the container.

Data provider bus encapsulates the data providers and data access are provided by services which only provides
CRUD operations.

OLAP cubes are created from DB by administrator and synchronized to OLAP cubes periodically.

Advantages
 Enterprise grade solution
 Very loosely coupled and allows components to be removed and plugged in easily
 New agents can consume exposed API and get connected to global car rental ecosystem.
 System designed to handle hundred thousands of requests.
 Properly designed to encapsulate functional requirement defined for each component.

Liability
 Requires extensive expertise to alter system architecture.
 Ecosystem is expensive to incorporate in the first phase.
 Infrastructure is not designed to multi-region and require significant changes to the system design.

End to end Quality Control Process

This chapter of the project document provides end to end Quality Control Process.

Test Plan

Introduction
Project Name
Rental Car Management System
13 | P a g e
Rental Car Management System Final Project -CSC445
Project Leads:
1.1.1. Project Manager: A. M. Rashed Mahamud
1.1.2. Development Lead: Md. Golam Rakib
1.1.3. Test Manager: Mir Noor-UL-Haque Pias

Test Project Task

1.1.4. Test case design: Mir Noor-UL-Haque Pias
1.1.5. Test personnel:
1.1.5.1. For manual tests: Mir Noor-UL-Haque Pias, Rayhan Sardar Tipu

1.1.6. Documentation reviews: A.M. Rashed Mahamud

Defect Tracking and reporting System

1.1.7. Defects will be tracked by using Black Box method.
1.1.8. The Defect Tracking method will be accessible by all the members of project
development team and test team.
1.1.9. Unit test of each module will be done by developer and the unit test report will be
shared with test team.
1.1.10. The testing will be start middle of the development that means after develop some
features/module we start testing till to end of the UAT according to the testing
schedule.
1.1.11. Bug fixing will be start from 7th April, 2016 and continue till end of the testing.
1.1.12. Without fixing the bug of any particular module/feature testing will not be completed.
1.1.13. All test cases will be prepared before start of the testing.
1.1.14. Test manager review and approved the test cases.
1.1.15. Test cases may be added during test conducted.
1.1.16. System test will be performing after full development.
1.1.17. Test environment, hardware and testable feature/module need to be ready before
testing in the test server.
1.1.18. Test report will be provided after end of the full testing in tracking method.
1.1.19. If any changes are made to the requirements, design and schedule then immediately
need to be informed to the test manager
 Testing Synopsis
Items to be tested Items

Reservation

1. Customer to register for reservation.

2. View description of particular vehicle.
3. Notify on selection of unavailable vehicles while reservation.
4. Advanced search E.g. By Brand, Type and Model.
5. Select specific vehicle using different search category while reservation.
6. List of available vehicles during reservation.
7. Customers reservation cancel.
8. Update reservation information.
9. Viewing reservations made by customers.
10. Their daily costs, and requests from customer.
11. Displaying reservation summary for successfully committed reservation.

Vehicle

12. Allow staff to register new vehicles.

13. Allow staff to select vehicles in the list.
14. Allow customer to select vehicles in the list.
15. Allow staff to Search vehicles by specific record.
16. Allow customer staff to Search vehicles by specific record.
17. Allow staff to update information of the vehicle in need of modification.
18. Allow staff to display all lists of vehicle.
19. Allow staff to display all available vehicle.
20. Allow customer to display all available vehicle.
21. Allow staff to display all rented vehicle.
22. Allow staff to display all off duty vehicles.

Rent

23. Allow staff to register customers into rental list.

24. Allow staff to update about customer rent record details in the rental list.
25. Able to save all changes made on the customer rent list.
26. Allow staff to select customer rent record by specific search category.
27. Allow staff to search rent record of customers using specific categories.
28. Allow staff to display customers, who rent vehicles.
29. Allow staff to display all customers rent record
30. Provide printable summary for successful committed rent.
 Items not to be Tested
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 staffs’
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 user’s 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 affected.

Test Environment/System Requirements

HARDWARE INTERFACE REQUIREMENTS
ID # Hardware Component
HI-1 DMZ Server (for Public
Interface / Web Server)
HI-2 Internal Box (Service API, DB
& Others)
HI-3 GP SIM or Test MSISDN
Requirement
2 CPU, 8 GB Memory
2 CPU, 8GB Memory, 500 GB
storage
Several SIM or Test MSISDNs
for testing the APIs &
application.

SOFTWARE INTERFACE REQUIREMENTS

ID # Software Component Requirement
SI-1 Java Development Kit Java SE 8
(JDK)
SI-2 Database Server MySQL Community server 5.7
 ID # Software Component Requirement
SI-3 Web Server Glassfish 3.1
SI-4 Server Host OS Windows 8.1
SI-5 Sandbox/Commercial Any open source Rest API Testing
terminal tool or need to develop for testing
SI-6 API load testing Any open source Rest API load testing
tool

COMMUNICATIONS INTERFACE REQUIREMENTS

ID # Communication Requirement
CI-1 Windows Internet Explorer for Admin GUI

Standards/Reference material
1.1.20. The followings are the Test deliverables/documents
1. Test Plan
2. Test Cases.
3. Reviewed/Revised copy of Test cases.
4. Test Report and Defect Report.

Testing Scope
Unit Testing
The goal of unit testing is to isolate each part of the program and show that the individual parts
are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a
result, it affords several benefits. The test team take 5 to 10 minute to test a single module. Most
of the test case are done by the unit testing method.

Smoke Testing

This is a set of acceptance criteria—conditions that must be met before testing can begin. A smoke
test should represent the bare minimum of acceptance testing. If any particular, specialized test
cases listed in other test case document can be used here. The test manager done it he first lists
down all the test case and he decided to which test case are doing and which tools are using for the
test case.

Feature level testing

The test case is on the same side or like same the functional test are the same kinds of test as like the non-
functional test case are same. So the featured level testing is:
 Functional Tests
The test cases will be designed from requirements to test the functionalities with both positive
and negative scenarios. Test team are doing their work in a big amount of time to functional
tests. They take almost time of testing for functional tests.

Integration Testing
All the components which are selected for testing. first of the test team are check those components for if there
some are defected the test are not being done well.

System Testing
All features will be tested to ensure that all elements of the integrated system function properly.

Security Testing
Security must be ensured using HTTPS mechanism.

Test Schedule and Resources

Major Activities Schedule:
Activities Start Date End Date Responsible Deliverables
Ensure Test Environment - 15/04/2016 Md.Abdul Munim Test Server
Test plan 10/04/2016 12/04/2016 Rayhan Sardar Tipu Test Plan

Test Cases Design 7/04/2016 13/04/2016 Mir Noor-UL-haque Test Cases

Pias

Identify Additional testers - 7/04/2016 Mir Noor-UL-haque

Pias and Golam Rakib

Testing Conducted (1st cycle + 8/04/2016 17/04/2016 1. Mir Noor-UL-haque Test Report
2nd cycle + system testing + Pias
bug fixing of all cycle) 2.Rayhan Sardar Tipu

Test Phases and Completion criteria

1.2. Planned Test cycles and Phases:
 Before testing any features / module developers will must finish unit testing
 Integration, system, load testing will be done for the features of every delivered testable
component in each first cycle testing.
 Any blocker issue for a feature will be taken care of immediately before testing the next
one.
 The testing of the modules will be completed when the defects are fixed and re-tested.

1.3. The severity of found defects will be assessed and the priorities on resolving them will be set
by collaborating with the developer(s), project managers and the system analyst on this.
1.4. The criteria that must be fulfilled before each stage of testing can be considered complete are:
  The Blocker, Critical, Major issues and Minor issues (according to point 2) will
be fixed.
 The Known issues (if any) will be listed and notified to clients in release notes.

Issues and Risks

1.5. Identify issues that have yet to be decided as of this draft of the plan. Note these as risks to
the schedule, scope, or quality of the test effort.
1.6. Identify other risks that may have an impact on the success of the plan. Use the risks outlined
in the course book and the attached speaker notes as a guideline to identifying common risks.
Eg:
 These are risks to the schedule, scope, or quality of the test effort:
 The feedback (issue fixing/not fixing) from developers on Test and defect report needs
to be well communicated. If not, testing schedule may be hampered.
 Bug fixing and retesting part needs to be very interactive and well communicated among
developers and testers. Otherwise there is risk to ensure bug density minimization.
 The same risk is there for Smoke test at the end (only one cycle of testing is planned).
 If planned/allocated resources are not available the functional test, retest and regression
test may hamper.

Test Cases Functional

Test Test Case Purpose Precondition Test Steps Expected Results

Case Name
No.

01 Register for Enable customer Customer has Click register button. Customer will be
reservation to register in the valid email id. Provide required registered in the
system information such as, system.
name, email, phone
no.
Verify email provided
by using verification
link sent to email.

02 View vehicle Enable customer Customer is Click to see the Detailed

description to view detailed logged in the vehicles of the description of all
description of system company. vehicles in the
 particular vehicle Click on a particular system are
vehicle. displayed upon
Detailed description of request.
that vehicle will be
displayed.

03 Notify selection Notify customer Customer is Click on reserve Notification is

of unavailable that selected logged in the vehicle. displayed for all
vehicle while vehicle is system. Get notification that unavailable
reservation unavailable for Customer has vehicle is unavailable. vehicles in the
reservation attempted to system upon
reserve a vehicle. attempt of
reservation.

04 Advanced Enable customer Customer is Select advanced All available search

search by to limit search of logged in the search. parameters display
vehicle vehicle by brand, system. Select category of appropriate results.
category type and model. search.
Result will be
displayed according to
the parameters set.

05 Display list of Enable customer Customer is Click on the button All vehicles
available to view the list of logged into the available vehicles available for
vehicle for vehicles available system A list of vehicles reservation will be
reservation for reservation available for on the list.
reservation will be
displayed

06 Cancel Enable customer Customer is Select cancel Customer will

reservation to cancel logged in the reservation. receive a
reservation of system. Provide reservation notification of
vehicle Customer has a confirmation number. successful
vehicle reserved Reservation cancelation of
confirmation number reservation.
will be verified by the If failed, show
system. error message.
Notification of
successful/failed
cancelation will be
displayed.

07 Update Enable employee Employee is Select update Updated

reservation to update logged in the reservation information will be
information reservation system. information saved and
information Employee has Make necessary displayed.
clearance to changes.
update Save changes
information

08 View list of Enable employee Employee is Select reservations List of reservations

reservations to view logged in the made will be
reservations made system. displayed.
by customers Employee has
 clearance to view
reservations

09 Provide unique Enable Reservation has Generate reservation Generate unique

reservation identification of been made number. numbers for all
number reservations Verify its uniqueness reservations made

10 Display Enable customer Customer is Select view summary Summary of

reservation to view a logged in the reservation will be
summary summary of a system displayed.
committed Customer has
reservation made a successful
reservation

11 User log in Enable Users to User has required Input username If verified, grant
log in to the credentials to log Input password access to the
system in Select user type system.
(customer, manager, If not, show error
employee) message.
Verify username,
password and type

12 Create new Enable new Customer has Click sign up button. Customer will be
customer customers to use valid email id Provide required registered in the
account the system information such as, system after
name, email, phone verification.
no.
Verify email provided
by using verification
link sent to email.

13 Create new Enable manager Manager has Click register new Employee will be
employee to register required employee button registered in the
account employees in the information of Provide required system after
system employee information such as, verification.
name, email, phone
no.
Verify email provided
by using verification
link sent to email.

14 User log out Enable user to log User is logged in Click log out button. User will be logged
out of the system out

15 Change Allow user to User exists in the Click forgot password Log in credentials
password change password system in log in page or will be updated
change password in with new
account settings. password.
If forgot password,
then recovery link will
be sent to email.
After clicking link,
input new password,
save password.
 If from account
settings, input current
password, input new
password, save
password.

16 Register new Enable Employee is Input information of New vehicle

vehicle registration of logged in vehicle. information will be
new vehicle in the Employee has Add picture. saved and vehicle
system clearance to Save roster will be
register new updated.
vehicle

17 Update vehicle Enable employees Employee is Select vehicle Updated

information to update vehicle logged in Make necessary information will be
information to Employee has changes to the saved and
current status clearance to information of vehicle. displayed.
update vehicle Save changes.
information

18 View vehicle Enable employees Employee is Select view all List of all vehicles
list to view list of all logged in vehicles of the company
vehicles will be displayed

19 View available Enable employees Employee is Select view available List of vehicles
vehicle list to view list of logged in vehicles available for
available vehicles reservation will be
displayed

20 View rented Enable employees Employee is Select view rented List of vehicles
vehicle list to view list of logged in vehicles currently rented
rented vehicles will be displayed

21 View off duty Enable employees Employee is Select view off duty List of off duty will
vehicle list to view list of off logged in vehicles be displayed
duty vehicles

22 Register Enable employee Employee is Open registration Rental list will be

customer into to register logged in form. updated.
rental list customer into Employee has Input customer and
rental list clearance to vehicle information.
register customer Save records.
into rental list

23 Update Enable employee Employee is Open rental list Updated record

customer rent to rent record logged in Select record to details will be
record details details in rental Employee has update. saved in the rental
list clearance to Make necessary list.
update rent record changes.
details in rental Save records.
list

24 Search rent Enable employee Employee is Select search by Search result

records by to search rent logged in category. matching input
 specific records by Employee has Input desired category. categories will be
category specified clearance to view displayed.
parameters rent records If no such records
exist, then error
message will be
displayed.

25 Display list of Enable employee Employee is Open list of customers A list of customers
customers who to see which logged in who rented vehicles. who rent vehicles
rented vehicles customers have Employee has will be displayed.
rented vehicles clearance to view
customer list

26 Display Enable employee Employee is Select view customer Rent records of that
customer rent to see rent records logged in rent records. specific customer
records of customers Employee has will be displayed.
clearance to view This will be true
customer rent for all customers in
records the system

27 Print summary Enable user to User is logged in. Open summary of System will print
of successfully print a summary User has clearance successfully the summary of
committed rent of successfully to print summary committed rent. successfully
committed rent of successfully Click print committed rent.
committed rent
Work Breakdown Structure of the Rental Car
Management System
Critical Path
Gantt Chart of the Rental Car Management System