Car Rental Management System Contents

Kevin Kline
Jon Rose
Jeff Vannini
Matt McCoy
Oakland Community College CIS 2111 Systems Analysis and Design

Contents
1.0 Introduction................................................................................................................................ 3
1.1 System Purpose....................................................................................................................... 3
1.2 System Scope.......................................................................................................................... 3
1.3 System Overview..................................................................................................................... 3
1.3.1............................................................................................................................................... 3
1.3.2 System Functions.................................................................................................................. 3
1.3.3............................................................................................................................................... 4
1.3 Definitions............................................................................................................................... 4
2.0 Requirements............................................................................................................................. 4
2.1 External Interfaces.................................................................................................................. 4
2.1.1 Hardware Interfaces.......................................................................................................... 4
2.1.2 System Interfaces.............................................................................................................. 4
2.1.3 User Interfaces.................................................................................................................. 4
2.2 Functions................................................................................................................................. 4
2.2.1 Case Diagram Charts........................................................................................................ 5
2.2.2 Functional Requirements................................................................................................... 5
2.2.3 Use Case Tables.................................................................................................................... 7
2.3 Performance Requirement....................................................................................................... 7
2.4 Design Constraints.................................................................................................................. 7
3.0 Appendices................................................................................................................................. 7
Appendix A – Case Diagram Charts................................................................................................... 7
CRMS Case Diagram 1................................................................................................................... 8
CRMS Case Diagram 2................................................................................................................... 9
CRMS Case Diagram 3................................................................................................................. 10
CRMS Case Diagram 4................................................................................................................. 10
CRMS Case Diagram 5................................................................................................................. 11
1.1.1 Appendix B – Use Cases..................................................................................................... 11
Use Case 1................................................................................................................................... 11
Use Case 2................................................................................................................................... 11
Use Case 3................................................................................................................................... 11
Use Case 4................................................................................................................................... 12
Use Case 5................................................................................................................................... 12
Use Case 6................................................................................................................................... 12
Use Case 7................................................................................................................................... 13
Use Case 8................................................................................................................................... 13
Use Case 9................................................................................................................................... 13

Use Case 10................................................................................................................................. 14
Use Case 11................................................................................................................................. 14
Use Case 12................................................................................................................................. 14
Use Case 13................................................................................................................................. 15
Use Case 14................................................................................................................................. 15
Use Case 15................................................................................................................................. 15
Use Case 16................................................................................................................................. 15
Use Case 17................................................................................................................................. 16
Use Case 18................................................................................................................................. 16
Use Case 19................................................................................................................................. 16
Use Case 20................................................................................................................................. 16
Use Case 21................................................................................................................................. 17
Use Case 22................................................................................................................................. 17
Use Case 23................................................................................................................................. 17
Use Case 24................................................................................................................................. 17
Use Case 25................................................................................................................................. 18

1.0Introduction
1.1 System Purpose
The company wants to find a solution to reduce its operating costs. The system being
developed is a system to handle the business needs of renting out vehicles to customers,
maintaining records and data on vehicle fleet, operating the customer portal website, and
reporting the state of the system to the company. The system does not fulfill any other
needs of the business.
1.2 System Scope
The functional scope of the system is represented in four different aspects of the system:
Customer Service Module (CS), Web Portal Module (WP), Fleet Management Module (FM)
and Reports and Analytics Module (RA).
1.2.1 The scope of the Fleet Management module is keeping track of the rental vehicle
fleet. This module’s purpose will be to contain the data on the vehicle fleet and
information about the specific vehicles. The Fleet Management module will not handle the
renting of the vehicles.
1.2.2 The scope of the Customer Web Portal is to rent vehicles to customers online in the
absence of an employee. The module will interface with the fleet management module but
will not perform any of that module’s duties. The same goes for the Customer Service
module.
1.2.3 The scope of the Customer Service Module is to provide a clear and easy to use
layout for employees and customers to follow along with as they work out a rental. As
mentioned above the module will interface with the fleet management module but will not
perform any of that module’s duties.
1.2.4 The scope of the Reports and Analytics Module is to provide a predetermined spot
that will contain all of the reports made from employees on car rentals. It will help the
store managers and corporate office when they need to file reports and check on rentals.
1.3 System Overview
1.3.1 System Context
The system has been designed with four modules in mind. These modules are the
customer service module, the web portal module, the fleet management module, and the
reports and analytics module. These four modules will make up the structure of the
system. The customer service module will be the part of the system that is supposed to
provide the employee with everything they need to perform their duties. The web portal
module will be the part of the system that handles the website where the customers will
be able to go through an automated process to rent cars. The fleet management module
will do as its name suggests and manage the rental fleet. The reports and analytics
module will be the part of the system that will be used to generate reports from the
remaining three modules for the purpose organizing the data on the status of the
company. The system will be able to interact with outside systems to process payment on
behalf of the company.

1.3.2 System Functions
The system will be able to rent out vehicles. The system will be able to accept payments.
The system will keep track of the rental fleet. The system will generate reports for the
employees.
1.3.3 User Characteristics
The users will be customers which can include traveling business people, out of town
visitors, and local residents in need of a car. Other users of the system will be the
employees both at the store level and a headquarters. The employees will all be using
windows desktops to conduct their business on the system but the system will need to
accommodate the variety of devices that the customers will have. The customers will have
mobile devices running several different operating software including android, iOS, and
blackberry. The full website also must accommodate these different operating systems.
1.3 Definitions
Car Rental Management System: CRMS
1. Customer Service Module: CS
2. Customer Web Portal: WP
3. Fleet Management: FM
4. Reports and Analytics: RA
Actors
1. Employee: Emp
2. Manager: Man
3. Customer: Cus
2.0Requirements
2.1 External Interfaces
2.1.1 Hardware Interfaces
R1: The system will have 3 terminals per store, with each one having a touch screen
monitor, keyboard, credit card scanner and a cash register.
R2: The system will have a 45 minute battery backup at each terminal.
R3: The system will have a 2 hour battery backup at the server at headquarters.
2.1.2 System Interfaces
R4: The system will interact with the banking network for the purpose of processing
payments.
R5: The systems data needs will be supported by a connection to the headquarters server.

2.1.3 User Interfaces
R6: The System will consist of Four (4) modules; Customer Service, Customer Portal
Website, Fleet Management, Reports & Analytics.
2.2 Functions
2.2.1 Case Diagram Charts
See Appendix A
2.2.2 Functional Requirements
R7: The System will contain a Customer Service module that will allow Store and
Corporate employees to provide information to customers
R8: The System will contain a Customer Service module that will allow Store and
Corporate employees’ access to the system for the purpose of Creating "Rental
Agreements"
R9: The System will contain a Customer Service module that will allow Store and
Corporate employees to collect payments
R10: The System will contain a Customer Portal Website that will provide information to
the public and customers about the company and operations of the company.
R10.1: This information will include Locations, Hours of operation, contact information,
available rental vehicles, rental packages, price estimate, and any other information
deemed necessary by the company.
R11: The customer portal website will provide the customer with the closest location to
their zip code and up to the next five (5) closest locations in addition to hours of
operations, contact info and directions.
R12: The System will generate an inventory capacity report for the desired time and
location.
R13: The System will allow for new vehicles to be added to the inventory of the company.
R14: The Fleet management module will allow the system to track vehicle maintenance.
Maintenance will be tracked through mileage and or time as decided by the company.
R15: The System will contain a Report and Analytics Module that will serve the purpose of
generating reports on the operations of the company.
R16: The System will contain a Report and Analytics Module that will be capable of
generating reports for items such as sales, maintenance, vehicle history, operations,
rentals, and insurance.
R17: The System will contain a Report and Analytics Module that will be capable of
generating reports for a desired time and location