ACKOWLEDGEMENT

We would like to express our deepest gratitude to all those who provided us the facilities
to complete this report. A special gratitude to our respected Head of the Department Prof V. B.
Hunagund and external guide prof V. C. Kagawade, whose contribution is tremendous in
completing this project.

Furthermore, we would also like to acknowledge our project guide Prof. R. S.

Wadawadagi for guiding us through the course of the project by giving suggestions and
encouragement.
 ABSTRACT
The main objective of this project is to design and create a data management system for a
bike rental system. This enables admin to manage vehicle that can be used by any customer and
it also allow the renter to leave their bikes on rent by registering with bike details and owner
information through the admin.

This application has a very user friendly interface.

 Contents

Sl. No Topics Page. No

1 Introduction to the area.
2 Literature survey.
2.1 Existing System.
2.2 Problems in existing system.
2.3 Available solution and their features.
2.4 Proposed solution.
2.5 Advantages of proposed solution.
3 Problem Definition.
3.1 Problem Definition.
3.2 Proposed solution.
3.3 Development process.
4 Software requirement specification.
4.1 Purpose.
4.2 Scope.
4.3 Functional requirement.
4.4 Performance requirement.
4.5 Exception handing.
4.6 Acceptance criteria.
4.7 Design hints and guidelines.
4.8 Glossary of terms.
 4.9 Technology requirement.
5 Detailed design.
5.1 High level design.
5.1.1 ER model/DFD.
5.2 Low level design.
6.2.1 Relation mode/Pseudo code/source code.
6 Implementation.
7 Testing &Result.
8 Conclusion.
9 Future Enhancement.
10 Reference books sites and other resources.
11 Index.
12 Appendices.
12.1 User manual.
12.2 About tools/technology.
 Introduction to the area
This system is named as Bike Rental Management System and it is a web based
application. This system is designed to help the customers to take bikes or two-wheelers on rent.
When we go on any trip outside the town or country we want to be free of time so instead of
going through metros and taxis we prefer to have our own vehicle for rent.

Using this system vehicle owner can register and customers who want to take bikes on
rent can register themselves as renters and can take any bike on rent. The customer should
provide some proofs to take the bike on rent.

Proofs like license, address and phone number are compulsory so that no one could run
taking the bike. Any customer whose proofs are not uploaded and are not valid will not be
allowed to take any bike on rent.

This system has one admin account who verifies and the recording user information. This
system has only one admin account and cannot have any other users account.
 2. Literature survey.

2.1 Existing System

An existing Bike rental management System can be provide the customer details are store
in the manually paper work. Till now there was no clear web base user interface to help the user
to rent vehicle. They had to manually rent the vehicle throw their office. It was difficult to task to
manage rental vehicle. Keeping track all the rental vehicle problem.

2.2 Problems in existing system.

 Repetitive process increases work load.

 Existing system do not support to get fast and accurate recall of customer
information.
 Redundancy of data.
 Difficult in checking vehicle status whether the vehicle is being used or available
for rental.
 Client does not know the detailed information about the bike that they had rent.
 Mistake in giving vehicle to the correct client due to data redundancies that
occurred because of manual way are high.
 Difficulties in refereeing to the previous data had been recorded since all the
checking is done manually.

2.3 Available solution and their features.

Automated system for Bike Rental Management System reduces work of the user and
also support quick decisions while renting the bike to the customer and performs fast operation
data. Thus the proposed system can over came problem of the existing system.
2.4 Proposed Solution

Automate the manual system. This system will enable the user to rent a bike. The admin
shall login to the system and check for availability for bikes and the user specific type of bike
and the journey data and time. System shall check for the availability of the bike and rent the
bike to the customer.

2.5 Advantages of proposed solution.

 Admin can add the new bike details along with receptive owner details.
 Admin can keep track the customers by storing the customer information.
 It provides security to the data by allowing user to login through username and password.
 Less paper work.
 System will allow the outside customer to leave there bikes on rent, by registering.
 System will allow generating daily/weekly report.
 3. Problem Definition.

Bike Rental Management System process maintained through the application with
automation of some basic modules.

3.1 Proposed Solution

Automate the manual system. This system will enable the user to rent a bike. The admin
shall login to the system and check for availability for bikes the user specific type of bike and the
journey data and time. System shall check for the availability of the bike and rent the bike to the
customer.

3.2 Development process

 4. Software Requirement Specification

4.1 Purpose

This system is named as Bike Rental Management System. This system is designed to
help the customers to take bikes or two-wheelers on rent. When we go on any trip outside the
town or country we want to be free of time so instead of going through metros and taxis we
prefer to have our own vehicle for rent.

4.2 Scope
It is more efficient and convenient for bike rental management system. It reduces the
manpower needed perform administrative tasks by reducing paper works. If estimated work is
done by computer there will be decreased in workload we can see.

4.3 Functional requirement

The Bike Rental Management System is capable of supporting following Modules

1. Customer
2. Bike owner
3. Bike
4. Transaction
5. Report Generation
Administrative Module :

The administrator is responsible for managing the data like creating customer details,
bike owner details, respective bikes details and all transaction data should be maintain for more
usages, like report generating for particular customers based on their engage date and return date
of bike.

Customer:
Customer information has to be maintained so that tracking can be done based on the
stored data of each customer. The information like customer first name last name, resident
address, license number and currently active phone number.

Bike owner
Bike owner can leave there bikes on rent by providing the some essential information like his /
her first and last name, current address, active phone number and their respective bike registration
number.

Bike:
Bike details has to be maintained so that ease to handle or chick the availability of bikes
and engaged bikes by storing the information like bike registration number, bike model, bike
number, bike color, bike type, bike registered date, engaged date and return date etc by this
stored information we can easily track the bike by whom.

Transaction:
Transaction details have been stored on the database for managing the customer and bike date and
knowing the availability of bikes and tracking the customers. In this transaction table stores the data like
customer license number and respective bike registration number taken by the customer.

Report Generation:
 Generating the report is done based on the number of transactions done in a particular
date to present date. In this report it consisting the customer details along with the bike details
and paid amount by the customer.

4.4 Performance requirement:

The performance requirement is measured in terms of the how well the application
performs. How efficient is organized and other related factors?

In this application with respect to database design, at least third normal form is accepted.
Further, the communication between client and server should be observed only when the
appropriate format of the data is been submitted.

4.5 Date store requirement

The data store requirement in this application is regarding the following entities.

Admin Login: Admin must log in by registered with user name and password for maintaining
information of customers, bike owners and their associated bikes information and for generating
the weekly transactions reports.

User Login: User must log in by registered with user name and password for storing information
of customers, bike owners and their associated bikes information.

4.6 Exception handling

An exception is a difficulty so as to occur during the execution of a program. An
exception for many different reasons, including the following:
 If the mobile number exceeds 10 digits, it shows the error message.
 Admin and Data Admin should log in with proper user name and password if they are
entering wrong cannot be login.
  From date and to date must be valid, if to date is less than from date then an exception
occurs.
 In the name fields, the user must be entered alphabets only.

4.7 Acceptance criteria

Before accommodating the developed application the developer has to show the proper
functioning of the system.
The developer software product must address the customer's requirements.

4.8 Design Hints and Guidelines

“Design associated among requirement specification and final solution for satisfying the
requirements. The design of the system is basically a blueprint or a plan for the system”
These can be worn to create a customer responsive GUI ( Graphical User Interface ) for
this the application which involves the code for ever single fields for designing a application
form using the PHP along with HTML scripts.
The forms are designed using labels, text boxes, buttons, images, data grid views etc.
 Text box: It is used to read input from user. It enables to add alphanumeric values
with a length of respective data type of fields, for example varchar data type it
will holds up to 255 characters.
 Label: Labels are the tokens of a user interface which are used to indicate the
heading and labels. The design can make more pleasant by adding different colors
to it, which will provides a good look and feel for user.

4.9 Glossary of terms

 Customer:
It involves the customers’ information.
 Bike owner:
It involves the bike owners’ details like owner first and last name, address, phone
number etc.
  Bike :
It involves the respective bike owner id along with all bike details like bike
model, bike type, bike color etc.

 Report:
It involves the respective customer details with rented bike details, amount paid
for the respective bike and there feedbacks from customers which are stored in the
database. It also involves the engaged date and returned date of bike by the customer.

4.10Technology requirements
Software requirements
The software requirement of the project are summarized in the following table.

Software Required

Programming PHP

Database MySQL

Operating System Microsoft Windows 10pro

Browser Used Google chrome

Hardware requirements
The hardware requirement of the project are summarized in the following table.

Hardware Required

RAM 1GB
 Hard Disk 100GB

Processor Core i3

5. System Design

5.1 Use Case Model

1) Use case diagram for admin login

Admin

Figure: - Use case diagram for admin.

 In this use case admin should be login and they can view the all transactions of bike, view
the customer details, bike owner details, bike details and he can generate a report for customers
and for owners of bike.

2) Use case diagram for user login

User
 Figure : - Use case diagram for user

In this use case diagram user should login to the system and they can add the customer
details, bike owner details and bike details of respective owner, and user can manipulate the all
dates of customer, bike owner and bikes details which are stored in the data base.

6. Detailed Design

6.1 High level design

6.1.1 ER model

1
1
6.1.2 DFD design

Login to system Check Roles of

access Manage Customer
Admin details

Manage Bike Owner

User details
Check credentials Manage modules

Manage Bike details

Change Password

Manage Transaction
details

Manage Payment details

Manage Report
6.2 Low level Design

 Customer

 Bike

 Bike Owner
  Transaction

6.1.2 Pseudo code

Admin Login Page

Step1: Read username and password
Step2: Verify username and password
Step3: Whether Admin account exit
if found then
Print “Successful login”
Else
Print “Invalid username and password”
Step4: View the bike, customer, bikeowner, transactions, report details
Update the bike, customer and bikeowner information
Generate various report related to bike
Logout
Step5: Stop

User Login Page

Step1: Read username and password
Step2: Verify username and password
Step3: Whether Admin account exit
if found then
Print “Successful login”
Else
Print “Invalid username and password”
Step4: View the bike, customer, bikeowner, transactions, report details
Update the bike, customer and bikeowner information
Generate various report related to bike
Logout
Step5: Stop

Source Code

<?php

if(isset($_POST["submit"])){
if(!empty($_POST['username']) && !empty($_POST['pass'])) {
$user=$_POST['username'];
$pass=$_POST['pass'];
 $type=$_POST['usertype'];
$con=mysql_connect('localhost','root','') or die(mysql_error());
mysql_select_db('bike') or die("cannot select DB");
$query=mysql_query("SELECT * FROM login WHERE (username='".$user."' AND
password='".$pass."'and usertype='".$type."')");
$numrows=mysql_num_rows($query);
if($numrows!=0)
{
while($row=mysql_fetch_assoc($query))
{
$utype=$row['usertype'];
$dbusername=$row['username'];
$dbpassword=$row['password'];
}
if($user == $dbusername && $pass == $dbpassword)
{
session_start();
$_SESSION['sess_user']=$user;
echo $utype."<br/>".$type;
if($utype=="Admin"){
header("Location:carrental/index.html");
}
else {
header("Location:carrental/customer.php?id=$utype");
}
} else {
echo "Invalid username or password!";
}
} else {
echo "All fields are required!";
}
 }
?>

7 Implementations
Following the steps involved in creating Data base
 Open the MySQL-front
2. In local host select the database by its name.
3. Select add new connection; the database connection form will be opened.
4. Connect to the database using database administrator credentials.
5. In data source Select MySQL-front.

Table Description

1) Add bike table

2) Bike owner

3) Add customer
4) Transactions

5) Login