A Software On

Rental Car Management System

Under Guidance Of

Mr. Adrish Bhattacharya

Introduction
The project Rental Car Management System,

has been developed keeping in mind to provide the various cars to the customers at a different times. The project has been designed with the help of Software Net Beans 6.5.1 and Ms Access 2003. The software is designed in such a way that in such case in favor of the user demands to modify the software, it can be done in an easy way by the designers of the software.

Its market relevance

The Rental Car Management System software is more

reliable to access & easy to operate. This software is more efficient to handling as well as maintain. Customers satisfaction is the prime concern for us. It makes the business have an edge above the competitors. It provides the needful quality services to the clients in order to their requirements. The owner of this software would be interested in the latest development and the real time status of the company.

Advantages
The Rental Car Management System software saves a

lot of time, money & labor. This software increases the efficiency of the management at offering quality services to the customers. This software provides custom features development & support.

Drawback
This Rental Car Management System software

only can access via offline not by the online. This software can accessed by the single user access mode only at a time.

System Analysis & Design

In this section, we present the requirement specification,

s/w & h/w requirements for both system developers & system users. In the Functional Requirements define the functions that are define by the projects. Different functions are needed by different system users. A non register customers can only visit the availability site and search the rest of car information. A register customers may have two choice i.e., they can hire Book/Hr & Book/Km.

Iterative Waterfall Model

Feasibility study

Requirement analysis and specification

Design

Coding and Unit Testing

Integration Testing

Maintenance

System Analysis & Design

Functional Requirements for Book/Hour customers : 1.BOOKIE NAME 2.BOOK ID 3.ADDRESS 4.PHONE NO. 5.BOOKING DATE 6.TIME 7.CAR TYPE 8.CAR NO 9.HOURS 10.COST Functional Requirements for Book/KM customers : 1.BOOKIE NAME 2.BOOK ID 3.ADDRESS 4.PHONE NO. 5.BOOKING DATE 6.TIME 7.CAR TYPE 8.CAR NO 9.HOURS 10.KILOMETERS

Software & Hardware Requirements

Software Requirements

Hardware Requirements

We have used

Microsoft Access Database

Java technology jre

Pentium 4 RAM-256 MB Hard Disk-1 GB Operating SystemWindows XP with Service Pack 2

Context Level :
Admin
1. LOGIN 2. AVAILABILITY 3. CAR LIST 4. INSERT CAR INFO 5. DELETE CAR 6. UPDATE RENT 7. INSERT NEW RENT 8. CREATE EMPLOYEE 9. DELETE EMPLOYEE

Car Rent Management

1. Login 2. Booking 3. Availability 4. Car List

Employee

Use Case Diagram

LOGIN BOOKING AVAIALABILITY

LOGIN INSERT CAR INFO DELETE CAR UPDATE RENT INSERT NEW RENT CREATE EMPLOYEE DELETE EMPLOYEE

CAR LIST

Employee

Administrator

Username, password

EMPLOYEE

Login

Verification type

EMPLOYEE

Availability

Car list Booking

RENT

Check Availability

CAR

BOOKING

LEVEL 1 DFD for EMPLOYEE

User Name

User Name

ADMIN

Password

Login

Password

EMPLOYEE

Delete Employee

CAR

Car No.
Create Employee

RENT
Booking
Car Type

RENT

BOOKING

Availability Check

Date

Level -1 DFD for ADMIN

ADDRESS

PHONE

DATE

TIME

BOOKING NAME

CAR NO

BOOKING ID

CAR TYPE

ER-DIAGRAM

BOOKING
N 1 1 N NAME 1 PASSWORD
CONDITIONAL UPDATE VIEW

N
HAS

CAR NO CAR TYPE

MAKE

CAR
ADDRESS PHONE HAS A

EMPLOYEE
USER NAME

TYPE

11

CONDITIONAL INSERT UPDATE & VIEW

RENT/HOUR

CAR TYPE

RENT

RENT/KM

Snapshots

Splash Window

Snapshots : Login Window & After Login Window

Snapshots : BOOKING

Snapshots : AVAILABLITY

Snapshots : CAR LIST

Snapshots : INSERT CAR INFO

Snapshots : DELETE CAR

Snapshots : UP DATE RENT

Snapshots : INSERT NEW RENT

Snapshots : CREATE EMPLOYEE

Snapshots : DELETE EMPLOYEE

Testing
The Test Plan specifies the objective of testing for e.g. to
achieve error-free operation under stated condition for a stated period of time. There are different types of test that a software product must satisfy:1. Unit Testing 2. System Testing 3. Integrating Testing

Unit testing works Test the module. System testing depend upon the system. Integrating testing test the total system.

Future Prospects.
Reusability is possible as and when require this
application. We can update it in next version. Reusable software reduces design, coding & testing cost by amortizing over several design. The method is understandable to someone other than the creator of the method can understand the code. It cost is under the budget and make within given time period. It is desirable to aim for a system within a minimum cost.

Conclusion
While making the system, an eye has been kept on making
it as user-friendly, as cost-effective and as flexible as possible. As such one may hope that the system will be acceptable to any user and will adequately meet his/her needs. It can be safely concluded that the product is a highly efficiently GUI base component. The system has reached a steady state where almost bugs have been eliminated. This component can be easily plugged in many others systems.