BIKE RENTAL SYSTEM USING WEB

A Mini-project Report submitted

in partial fulfilment for the award of the Degree of

Bachelor of Technology in
Computer Science and Engineering

ADDAGARLA BHAVANI SANKAR U21CS008

AVINASH RAJ U21CS052

BALAGAMSETTY SHASHANK U21CS062

BALUSU SIVATEJA U21CN145

Under the guidance of

Dr. K. Bala

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

SCHOOL OF COMPUTING

BHARATH INSTITUTE OF HIGHER EDUCATION AND

RESEARCH
(Deemed to be University Estd u/s 3 of UGC Act, 1956)

CHENNAI 600 073, TAMILNADU, INDIA

November/ December, 2024
 Batch No. F6

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

BONAFIDE CERTIFICATE

This is to Certify that this Mini-Project Report Titled “BIKE RENTAL

SYSTEM USING WEB” is the Bonafide Work of A.BHAVANI SANKAR
(U21CS008), AVINASH RAJ(U21CS052), B.SHASHANK(U21CS062), B.SIVATEJA

(U21CS065) who carried out the mini project work under my supervision.
Certified further, that to the best of my knowledge the work reported here in
does not form part of any other project report or dissertation on basis of which
a degree or award conferred on an earlier occasion by any other candidate.

PROJECT GUIDE HEAD OF THE DEPARTMENT

Dr. K. Bala Dr. S. Maruthuperumal

Professor Professor
Department of CSE Department of CSE
BIHER BIHER

Submitted for Semester Mini-Project viva-voce examination held

on

INTERNAL EXAMINER EXTERNAL EXAMINER

 DECLARATION

We declare that Mini-project report titled BIKE RENTAL SYSTEM

USING WEB submitted in partial fulfillment of the degree of B. Tech in
(Computer Science and Engineering) is a record of original work carried
out by us under the supervision of Dr. K. Bala, and has not formed the basis
for the award of any other degree or diploma, in this or any other Institution
or University. In keeping with the ethical practice in reporting scientific
information, due acknowledgements have been made wherever the
findings of others have been cited.

ADDAGARLA BHAVANI SANKAR

(U21CS008)

AVINASH RAJ
(U21CS052)

BALAGAMSETTY SHASHANK
(U21CS062)

BALUSU SIVATEJA
(U21CS065)

Chennai
Date :
 ACKNOWLEDMENTS

We express our heartfelt gratitude to our esteemed Chairman, Dr.S. Jagathrakshakan,

M.P., for his unwavering support and continuous encouragement in all our academic
endeavors.
We express our deepest gratitude to our beloved President Dr. J. Sundeep Aanand
President, and Managing Director Dr. E. Swetha Sundeep Anand for providing us the
necessary facilities to complete our project.
We take great pleasure in expressing sincere thanks to Dr. K. VijayaBaskar Raju Pro-
Chancellor, Dr. M. Sundararajan Vice Chancellor (i/c), Dr. S. Bhuminathan Registrar
and Dr. R. Hariprakash Additional Registrar, Dr. M. Sundararaj Dean Academics for
moldings our thoughts to complete our project.
We thank Dr. S. Neduncheliyan Dean, School of Computing for his encouragement
and the valuable guidance.
We record indebtedness to our Head, Dr. S. Maruthuperumal, Department
of
Computer Science and Engineering for his immense care and encouragement towards
us throughout the course of this project.
We also take this opportunity to express a deep sense of gratitude to our Supervisor Dr.
K. Bala and our Project Co-Ordinator Mr. K. Sivaraman for their cordial support,
valuable information, and guidance, they helped us in completing this project
throughvarious stages.
We thank our department faculty, supporting staff and friends for their help and
guidance to complete this project

ADDAGARLA BHAVANI SANKAR U21CS008

AVINASH RAJ U21CS052
BALAGAMSETTY SHASHANK U21CS062
BALUSU SIVATEJA U21CS065
 ABSTRACT

The development of a bike rental system using web

technologies offers a seamless and efficient way for users to rent bikes,
contributing to urban mobility solutions. This system leverages a web
interface to provide real-time bike availability, easy reservations, secure
payments, and GPS tracking, allowing users to rent bikes in an eco-
friendly and cost-effective manner. The core components of the system
include a user-friendly frontend, robust backend, and integration with
external services such as payment gateways and GPS tracking for
enhanced functionality. The system addresses common challenges in
traditional bike rental methods, such as lack of real-time data,
inefficiencies in payment processing, and the absence of automated user
management. Through careful design and the integration of modern web
technologies like HTML, CSS, JavaScript, and server-side tools such as
Node.js. The bike rental system achieves scalability, security, and
convenience for both users and administrators. This system has been
tested for performance and reliability, showing high user satisfaction,
ease of use, and operational efficiency. The primary focus of this project
is to solve urban transportation issues by providing an alternative to
congested roads and high vehicle emissions. By offering a web-based
platform for bike rentals, the system promotes sustainable transportation
and encourages healthier lifestyles.
 TABLE OF CONTENTS

DESCRIPTION PAGE NUMBER

1. INTRODUCTION 1
2. ANALYSIS 5
1. Existing System 6
2. Need For The New System 6
3. Main Objective Of The New System 6
3. SYSTEM REQUIREMENT STUDY 8
4. Hardware Requirements 9
5. Software Requirements 9
6. PHP Language 9
7. Common Uses Of PHP 10
8. Characteristics Of PHP 10
4. FUNCTIONAL SPECIFICATIONS 11
9. Modules 12
10. Module Specifications 12
5. SYSTEM DESIGN 15
11. Feasibility Study 16
12. Economic Feasibility 16
13. Operational Feasibility 17
14. Behavioral Feasibility 17
15. Technical Feasibility 17
16. System Design Process 18
17. Design Tools 18
6. DATAFLOW DIAGRAM 19
1. Data Flow Chart 20
1. Data Flow Diagram 20
7. ER DIAGRAM 21
2. ER Diagram 22
8. USE CASE DIAGRAM 24
3. Use case Diagram 25
4. Use case Diagram For Admin 25
5. Use case Diagram For User 26
6. Activity Diagram For Admin 27
7. Activity Diagram For User 28
9. TESTING 30
8. Types Of Testing 30
1. Acceptance Testing
31
2. System Testing
31
3. Integration Testing
31
4. Unit Testing 32
9. Methods Of Software Testing
32
10. Testing Principles
33
11.Error Handling 33

10. SYSTEM VALIDATION AND VERIFICATION 34

11. DATABASE DESIGN 37
12. SCREENSHOTS 43
12. Admin Modules 44
1. Admin Login
2. Dashboard
 3. Change Password
4. Manage Brands
5. Post A vehicle
6. Manage Vehicles
7. Manage Bookings
8. Registered Users
2. User Modules 48
1. Sign Up
2. Login
3. Home Page
4. Profile
5. Update Password
6. My Booking
7. My Testimonial
8. Vehicles Details
9. List Of Vehicles
10. About Us
13. CODING 53
14. FUTURE ENHANCEMENT 96
15. CONCLUSION 98
16. BIBLIOGRAPHY 100
 ABREVIATIONS/ NOTATIONS/ NOMENCLATURE

HTML:- HTML is the standard markup language for creating Web

pages. HTML describes the structure of a Web page.

CSS :- Cascading Style Sheets is a style sheet language used for

specifying the presentation and styling of a document written in a
markup language such as HTML

JS :- JS stands for JavaScript. It is a text-based, lightweight, cross-

platform, and interpreted scripting programming language

Enthusiastic:- A person who is interested in a particular item.

E-Commerce :- E-commerce (electronic commerce) is the buying and

selling goods and services, or the transmitting of funds or data.

Website :- A website is a collection of files accessed through a web

address, covering a particular theme or subject, and managed by a
particular person or organization.
 CHAPTER – 1
INTRODUCTION

1
 CHAPTER 1
INTRODUCTION

1.1 About the project

Bike rental project using PHP is a web-based application. It is a system design
especially
for large, premium and small bike rental business. The bike rental system provides
complete functionality of listing and booking bike.

Bike rental system (CRS) is a web-based system for a company that rents out bikes.

This system enables the company to make their services available to the public
through

the internet and also keep records about their services. This is a company that rents
automobiles for a short period of time for a few days or week bike rental companies
operate by purchasing or leaning a number of a fee. To make this service more popular

and accessible to the public it has been transform into a web base system and
connected

to the internet were everyone can be able to have access to it. To develop a web-based
system that will help manage the business transactions of bike renting Rental fleets
can

be structured in several ways they can be owned outright, they can be leased, or they
can be owned under a guaranteed buy-back program arranged directly through a
manufacturer or manufacturer's financial arm.

This Bike Rental System project is designed to aid the bike rental company to enable
renting of bikes through an online system. It helps the users to search for available
bikes

view profile and book the bikes for the time period. It has a user-friendly interface
which helps the user to check for bikes and rent 2them for the period specified. They
2
could also make payment online. The rental bikes shall be categorized into economy,
premiums
type of bike etc. Also, it will need an identification number. Using these details, the
tool shall help the customer to book a bike for the journey.

1.2 Problem Statement

The problem with some of the current system is that, Based on observations, some
small companies already have a bike rental system which is not a web-based
system application. This is a limitation that gives them capability to stores customer's
details, but at the same time they cannot make their services more available to the
public through the internet they rather make use of posters to advertise their
services to the public. These types of companies can overcome these problems by
switching to the web base application of their type of system. They also make use of
phone call reservations which is also limited to many features as compared to a web
base system.

1.3 Previous work

In old times, there were no facilities of computerized system. Nowadays, there are
many facilities of computerized system. People can rent bike for short- and long-term
period and there are many companies that offer opportunities for people who cannot
afford to buy a bike as well as for those who need bike for some period of time.

1.4 Objectives

The objectives of this project are:

•To develop a web-based system that will help manage the business transactions of
bike renting.

•It is a system design especially for large, premium and small bike rental business
The bike rental system provides complete functionality of listing and booking bike.
In this system, Tourism and Travelling facilities also provide.

3
1.5 Specific Project Goals

In this bike rental system, we are going to introduce online booking of bike rent will
be available. So, the Burdon of the customer will be reduced. Our Aim is to design
and create a data management System for a bike rental company. This enables admin
can rent a vehicle that can be used by a customer by paying the money during a
Specified Period of time. This system increases customer retention and simplify
vehicle and staff Management in an efficient way.

•This software Bike Rental System has a very user-friendly interface. Thus, the
users will feel very easy to work on it. By using this system admin can manage their
rental, payment, employment issues and vehicle issues such as and insurance.
The bike information can be added to the system by admin.

•And admin will decide the money for bike rent-it bases on the day.
Vehicle replacement is available if any problem that occurs in the vehicle.

1.6 Scope of the Project

The scope of this project is as follows:

• The bike rental system to keep detail records of both the bikes and the

customers, the duration they rent bike as well as the type of bike they rent.

• The system will be mainly design for small a company that renders it bike
rental services to customers.
• The system will have the ability to generate and print invoice for each
successful transaction.
• The system will have two levels of access:
1. The administrator
2. Customer

4
1.7 Project Overview Statement
To develop a system of BIKE RENTAL PORTAL by completely focusing on
customer, our employees, growth, innovation and efficiency. All of these elements
will drive us toward success. The process on searching the client's details is slow if it
uses manual system and there are thousands of clients. Besides that, staffs have to
record the booking manually and it is difficult to improve a monthly report or an
annual report. However, this project has strategic backup system for any eventually.
Vehicles are well maintained and tested for delivering optimum and uninterrupted
performance.

4
CHAPTER –2
ANALYSIS

5
 CHAPTER 2
ANALYSIS

2.1 Existing System

• An existing system can provide manually
paper work.
• The user has to go in the office where user can get the BIKE on rent and book
their BIKE.
• In the existing system you cannot provide feedback of the user to the admin
online.

2.2 Need for the New System

• The new system is totally computerized system.
• A new system provides features like time efficiency to show BIKE details, user
• profiles and whatever the customer will give the feedback to the admin.
• This system provides tourism and travelling facilities.
• An inquiry is easily done by user in the system. It is the most software
application for managing online BIKE rental business.

2.3 Main objective of the new system

• Fast and Efficient: As compared to existing system, in new system

the user can get the information fast, easily and efficiently from the

software,

• Reliable and accurate: As in new system, the information is stored and

processed in computers so that data will be more reliable and accurate.
• Centralized Data: In the existing system, data records are kept under file
maintenance system due to this system the placement of the data is not at one
particular place. But in new system, each and every record is maintained 6on
computer, which leads to the centralization of data.
• Non-Redundant Information: - As in proposed system data is maintained on
the computers so inconsistency does not occur which will never lead to problem
like duplication of data.
• Easy to Access: -As compared to existing system, in new system the users can
easily and efficiently accesses the information from the computer.
• No Documentation: -As everything is stored on the computer, so there is no
need of documents or maintaining the files.

7
 CHAPTER – 3

SYSTEM REQUIREMENT STUDY

8
 CHAPTER 3

SYSTEM REQUIREMENT STUDY

3.1 Hardware Requirements

RAM : 8GB

Hard disk : 20GB

Processor : AMD Ryzen 5 3250U

Graphics : Radeon Graphics 2.60 GHz

Quality : 64 Bit Screen

Resolution : 1366 768

Mouse : Standard Optical

3.2 Software Requirements

Web Server : APACHE

Language : PHP

Database : MYSQL

Web Browser : Google Chrome or any compatible browser

Operating System : Windows or any equivalent OS

3.3 PHP Language

PHP started out as a small open-source project that evolved as more and more people
found out how useful it was. Rasmus Lerdorf unleashed the first version of PHP way
back in 1994.

 PHP is a recursive acronym for "PHP: Hypertext Preprocessor".

9
  It is integrated with a number of popular databases, including MySQL,
PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server.
 PHP is a server side scripting language that is embedded in HTML. It is used to
manage dynamic content, databases, session tracking, even build entire e-
commerce sites.
 PHP is pleasingly zippy in its execution, especially when compiled as an
Apache module on the Unix side. The MySQL server, once started, executes
even very complex queries with huge result sets in record-setting time.
 PHP is forgiving: PHP language tries to be as forgiving as possible.
 PHP Syntax is C-Like.

3.4 Common uses of PHP

 PHP performs system functions, i.e., from files on a system it can create, open,
read, write, and close them.
 PHP can handle forms, ie, gather data from files, save data to a file, through
email you can send data, return data to the user.
 You add, delete, modify elements within your database through PHP.
 Using PHP, you can restrict users to access some pages of your website.
 It can encrypt data.

3.5 Characteristics of PHP

Five important characteristics make PHP's practical nature possible-

 Simplicity
 Efficiency
 Security
 Flexibility
 Familiarity

10
 CHAPTER – 4
FUNCTIONAL SPECIFICATIONS

11
 CHAPTER 4
FUNCTIONAL SPECIFICATION

4.1 Modules

 Admin
 User
1. Admin:
Admin can add a BIKE, manage booking BIKE and rent and also
view feedback and enquiry
2. User:
User can view information of available BIKE, booking BIKE, easily get
the BIKE on rent and also give feedback and can enquiry

4.2 Module Specification

1. User

View Available Bikes:

It is a system design especially for large, premium and small BIKE rental
business.

The user can view Available BIKEs and user can book for that bike.

Booking Bike:

The user can view Available BIKEs and user can book for that bike.

Easily Get the Bike on Rent:

The Customer can easily get the bike whenever they need to on the rent
with use of this system.

12
 Give Feedback:

The customer will give the feedback to the admin

Enquiry:

The inquiry can easily do by user.

4.2.2 Admin

Dashboard:

In this section admin can view the overview of the bike rental (Like total
vehicles, total booking, brands enquiry)

Vehicle Brand:

Admin can create/edit/delete vehicle brands

Vehicles:

The admin can add the bike so that the user can see the available BIKEs and
book the bike..

Admin can also edit and delete the bikes.

Bookings:

Admin can manage the bookings (confirm and cancel the booking)

Manage testimonials:

Admin can manage the testimonials (Active and Inactive the testimonials).

Manage Contact us query:

Admin can manage Contact us query.

View Feedback:

13
The admin easily views the feedbacks and solve the query.

Registered users:

Admin can view the registered users.

Manage pages:

Admin can update the pages data information.

Contact info:

Admin can update the contact info.

Manage Subscribers:

Admin can manage subscribers.

14
 CHAPTER – 5
SYSTEM DESIGN

15
 CHAPTER 5
SYSTEM DESIGN

5.1 Feasibility Study

Feasibility study is a test of a system proposal according to its workability, impact on

the organization, ability to meet user needs, and effective use of resources. The
feasibility study is to serve as a decision document; it must answer the following
questions

 What are the user's demonstrable needs?

 Is the problem worth solving?
 How can the problem be solved?

All the successful projects are not necessarily the biggest but rather those that truly
meet the user expectations. Three key considerations involved in the feasibility
analysis are economic, operational and technical.

5.2 Economic Feasibility

Economic feasibility is the most frequently used method for evaluating the
effectiveness of a candidate system. The procedure is to determine the savings and the
benefits from the candidate system and compare with costs. If the benefits outweigh
the costs, then it is decided to go ahead with the projects. Otherwise, further
justification or alterations in the proposed system will have to be made if it is to have a
chance of being approved. This is an on-going effort that improves in accuracy at
each phase of the system life cycle.

16
5.3 Operational Feasibility

People are resistant to change and computers have been known to facilitate change.
An estimate should be made of how strong a reaction of the user staff is likely to
have an impact towards the development of a computer system. It is common
knowledge that computer installations have a lot to do with turnovers, transfers,
retaining and changes to employee job status. Therefore, it's understandable that
the production of the candidate system requires special effort to educate and train
the staff on the new way of doing the job. But since ultimately the introduction of a
new system will only reduce the staff's workload, they may have no objection to
install a computerized system, and of course will be eager to extend their cooperation.

5.4 Behavioral Feasibility

It relates human behavior in the organization and political aspects. Here we focus

on What organizational structures are disturbed?

What new skills will be required?

What changes will be brought with the system

Do the existing members have these skills? If not, can they be trained in due course of
time? It also includes social and managerial aspects that is whether the proposed
project will be acceptable to the customer and the management, along with the
determination of whether the proposed project considers Act, Status as well as
pending Legislations as a part of the legal feasibility

5.5 Technical Feasibility

Technical feasibility centers on the existing system and to what extent it can support
the proposed system. This involves financial considerations to accommodate
technical enhancements. If the budget is a serious constraint, then the project is
judged not

17
feasible. Now considering the proposed system, our client has been maintaining the
records manually at the present. So, he has to purchase new computer systems for the
automation of the concern The owner having realized the advantages, benefits and
economic feasibility of the new system is ready to afford the expenses for the
satisfaction of all the hardware and software requirements.

5.6 System design process

A computer procedure is a series of operations designed to manipulate data to produce

outputs from a computer system. The procedure may be a single program or a series
of programs. The detail design of the computer procedure follows acceptance
by management of an outline design proposal. The aim now is to design
procedures at lower levels of detail, which will define the detailed steps to be taken
to produce the specified computer output. When complete, these procedure
definitions together with data specifications are organized for programmers from
which the required programs can be written.

5.7 Design Tools

Various tools are being used by system analysis to specify computer procedures. Not
all of them are used here to design this project. Some of the important tools that have
been made use of are

5.8 Data validation

Computer input procedures must also be designed to detect errors in the data at a
lower level of detail which is beyond the capability of the control procedures.
These are combined with the design of the input process itself.

The validation procedure must be designed to check each record, data item, field
against certain criteria specified by the system analyst or the programmer.

18
 CHAPTER – 6
DATAFLOW DIAGRAMS

7
19
 CHAPTER 6
DATA FLOW DIAGRAM

6.1 Data flow Diagram

Figure 6.1

20
6.1.2 Data flow Diagram

Figure 6.2

21
CHAPTER – 7
ER DIAGRAM

22
 CHAPTER 7
ER DIAGRAM

The Entity-Relationship (ER) model was originally proposed by Peter in 1976

[Chen76] as a way to unify the network and relational database views Simply stated
the ER model is a conceptual data model that views the real world as entities and
relationships. A basic component of the model is the Entity-Relationship diagram
which is used to visually represent data objects. Since Chen wrote his paper the
mode has been extended and today it is commonly used for database design for the
database designer, the utility of the ER model is:

 It maps well to the relational model. The constructs used in the ER model can
easily be transformed into relational tables.
 It is simple and easy to understand with a minimum of training. Therefore, the
model can be used by the database designer to communicate the design to the
end user.
 In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.

All notational styles represent entities as rectangular boxes

and relationships as lines connecting boxes. Each style uses a special set of symbols to
represent the BIKEdinality of a connection. The notation used in this document is
from Martin. The symbols used for the basic ER constructs are:

 Entities are represented by labelled rectangles. The label is the name of the
entity. Entity names should be singular nouns
 Relationships are represented by a solid line connecting two entities. The name
of the relationship is written above the line. Relationship names should be
verbs
23
  Attributes, when included, are listed inside the entity rectangle. Attributes
which are identifiers are underlined. Attribute names should be singular nouns.
 BIKEdinality of many is represented by a line ending in a crow's foot. If the
crow's foot is omitted, the BIKEdinality is one.

Existence is represented by placing a circle or a perpendicular bar on the line.

Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the
entity that is optional.

7.1 ER Diagram

Figure 7.1

24
 CHAPTER – 8
USE CASE DIAGRAM

25
 CHAPTER 8

USE CASE DIAGRAM

8.1 Use Case Diagram

A Use case is a description of set of sequence of actions. Graphically it is rendered as

an ellipse with solid line including only its name. Use case diagram is a behavioural
diagram that shows a set of use cases and actors and their relationship. It is an
association between the use cases and actors. An actor represents a real-world object
Primary Actor-Sender, Secondary Actor Receiver.

8.2 Use Case diagram for admin

Login

Manage
booking

View
Enquriy

Check
Rent

Add
bike
details

Logout

Figure 8.2 26
8.3 Use Case diagram for user

Figure 8.3

27

21
8.4 Activity diagram for admin

Figure 8.4

28
8.5 Activity diagram for user

Figure 8.5

29

23
CHAPTER – 9
TESTING

30
 CHAPTER 9
TESTING

Software Testing is evaluation of the software against requirements gathered from

users and system specifications. Testing is conducted at the phase level in
software development life cycle or at module level in program code. Software testing
comprises of validation and verification.

9.1 Types of Testing

1. Acceptance Testing

It is a formal testing according to user needs, requirements and business processes

conducted to determine whether a system satisfies the acceptance criteria or not and to
enable the users, customers or other authorized entities to determine whether to accept
the system or not.

2. System Testing
System Testing is a type of software testing that is performed on a complete integrated
system to evaluate the compliance of the system with the corresponding
requirements. In system testing, integration testing passed components are taken as
input.

3. Integration Testing
Integration testing (sometimes called integration and testing, abbreviated 1&T) is the
phase in software testing in which individual software modules are combined and
tested as a group Integration testing is conducted to evaluate the compliance of a
system or component with specified functional requirements.

31
9.1.4 Unit Testing

Unit testing is a software development process in which the smallest testable parts of
an application, called units, are individually and independently scrutinized for
proper operation. This testing methodology is done during the development process
by the software developers and sometimes QA staff.

9.2 Methods for Software Testing

There are mainly two widely used methods for software testing, one is White box
testing which uses internal coding to design test cases and another is black box
testing which uses GUI or user perspective to develop test cases.
 White box testing
 Black box testing

System testing falls under Black box testing as it includes testing of the external
working of the software Testing follows user's perspective to identify minor defects.

System Testing includes the following steps:

 Verification of input functions of the application to test whether it is producing

the expected output or not.
 Testing of integrated software by including external peripherals to check the
interaction of various components with each other.
 Testing of the whole system for End-to-End testing.
 Behaviour testing of the application via a user's experience.

32
9.3 Testing Principles

All tests should be traceable to customer

requirements. Test should be planned long before

testing begins.

The testing should begin in the small and progress towards testing "in the

large”. Exhaustive testing is not possible.

To be most effective, testing should be conducted by an independent third party.

 Characteristics of a Good Test

 A good test has a high probability of finding an error.
 A good test is not redundant
 A good test should be best of breed.
 A good test should be neither too simple nor too complex.

This section deals with the details of the classes of tests which must be
conducted to validate the functions, performance, and the constraints. This
is achieved basically by the means of testing which plays a vital role in the
development of the software.

9.4 Error Handling

Error handling refers to the anticipation, detection, and resolution of
programming, application, and comications errors Specialized programs, called
error handlers, are available for some applications. The best programs of this
type forestall errors, if possible recover from them when they occur
without terminating the application, or if alleles fail) gracefully terminate an
affected application and save the error information to a log file.

33
 CHAPTER – 10
SYSTEM VALIDATION AND
VERIFICATION

34
 CHAPTER 10
SYSTEM VALIDATION AND VERIFICATION

10.1 System Validation and Verification

System Validation and Verification is an important aspect of software
engineering. Verification refers to the set of activity that ensures that software
correctly implemented a specific function. Validation refers to a different set of
activity that ensures that the software that has been built is traceable to
customer requirement.

 Verification "Are we building the project, right?"

 Validation "Are we building the right product?"

The definition of validation and verification encompasses many of the activity

that we have referred to as software quality assurance (SQA).

Verification and validation encompass a wide array of SQA activity that include
formal technical review, quality and configuration audit, performance
monitoring simulation, feasibility study, documentation review,
algorithm analysis, development testing, qualification testing and installation
test.
10.2 System Verification and Validation Defined

Once the design is baselined, the design is transformed, via build, code, buy, or
reuse, into the system of interest. Similar to the discussion for the design
process, most organizations have a set of guidelines or "golden rules" that guide
the build (manufacture or code) process. These include workmanship and
quality control requirements for the organization.

After the system has been built or coded, there will be a gate review where the
system is both verified and validated. At this stage of the system lifecycle, the
35
concepts of system verification and system validation take on a more formal
meaning. Thus, the Systems Engineering (SE) lifecycle processes include the
processes of System Verification and System Validation. Each process represents a
set of activities (test, demonstration, inspection, analysis) that cumulate with one
or more gate reviews associated with the acceptance of the system by the
customer.
System Verification: a process done after design and build or coding, making
sure the designed and built or coded system meets its requirements. The focus is
on the built or coded system and how well it meets the agreed-to requirement set
that drove the design and fabrication. Methods used for system verification
include test, demonstration, inspection, or analysis "Did we build the thing right?"
Also included in system verification is a determination that the team responsible
for building or coding the system of interests followed the organization's rules.
guidelines, and best practices associated with manufacturing and coding. The
focus is on the manufacturing or coding processes. "Did we follow our
organizations guidelines for manufacturing or coding correctly?"

System Validation: a process that occurs after system verification that makes
sure the designed, built, and verified system meets its intended purpose in its
operational environment The focus is on the completed system and how well it
meets stakeholder expectations (needs) that were defined during the scope
definition phase that should have occurred at the beginning of the project "Did
we build the right thing?”

System verification and system validation processes are directly related to the
contractual obligation concept for a requirement statement and set of
requirements. It is through these process activities that we prove we have met
both the agreed-to needs of entities who are the source of our own them.

36
 CHAPTER – 11
DATABASE DESIGN

37
 CHAPTER 11
DATABASE DESIGN

The data in the system has to be stored and retrieved from database. Designing
the database is part of system design. Data elements and data structures to be
stored have been identified at analysis stage. They are structured and put
together to design the data storage and retrieval system.

A database is a collection of interrelated data stored with minimum redundancy

to serve many users quickly and efficiently. The general objective is to make
database access easy, quick, inexpensive and flexible for the user. Relationships
are established between the data items and unnecessary data items are removed.
Normalization is done to get an internal consistency of data and to have
minimum redundancy and maximum stability. This ensures minimizing
data storage required, minimizing chances of data inconsistencies and
optimizing for updates. The MS Access database has been chosen for
developing the relevant databases.

11.1 Admin

Table Name Admin

Description This table is store information about
Admin
Primary Key id
Foreign Key -

Table 11.1

38
Sl.No. Field Name Data Type(Size) Constraints
1. Id (Primary) int (11) Primary key
2. UserName Varchar (100) Not Null
3. Password Varchar (100) Not Null
4. UpdationDate timestamp Not Null

Table 11.2
11.2 User Registration

Table Name tblusers

Description This table is providing the information
about user regisration
Primary Key Id
Foreign Key -

Table 11.3
Sl.No Field Name Data type(Size) Constraints
1. Id(Primary) int(11) Primary Key
2. FullName varchar(120) Null
3. EmailId varchar(100) Null
4. Password varchar(100) Null
5. ContactNo char(11) Null
6. DOB varchar(100) Null
7. Address varchar(255) Null
8. City varchar(100) Null
9. RegDate Timestamp Current_timestrap
10. UpdationDate Timestamp Null

Table 11.4

39
11.3 Brands Table

Table Name tblbrands

Description This table is providing the information
about Bike brands
Primary Key Id
Foreign Key -

Table 11.5
Sl.No. Field Name Data Type(Size) Constraints
1. Id (Primary) int (11) Primary key
2. BrandName Varchar (120) Not Null
3. CreationDate timestamp Current_
4. UpdationDate timestamp Not Null

Table 11.6
11.4 Contact Us Details Table

Table Name tblcontctusinfo

Description This table is provide the contact
information at website.
Primary Key Id
Foreign Key -

Table 11.7
Sl.No. Field Name Data Type(Size) Constraints
1. Id int Primary key
2. Address Tinytext Null
3. EmailId Varchar(255) Null
4. ContactNo Char(11) Null

Table 11.8
40
11.5 Vehicles Info Table

Table Name tblvehicles

Description This table is provide the information
about Bikes.
Primary Key Id
Foreign Key -

Table 11.9
Sl.No Field Name Data type(Size) Constraints
1. id(primary) int(11) Primary Key
2. VehiclesTitle varchar(150) Null
3. VehiclesBrand int(11) Null
4. VehiclesOverview Longtext Null
5. PricePerDay int(11) Null
6. FuelType varchar(100) Null
7. ModelYear int(6) Null
8. SeatingCapacity int(11) Null
9. Vimage1 varchar(120) Null
10. Vimage2 varchar(120) Null
11. Vimage3 varchar(120) Null
12. Vimage4 varchar(120) Null
13. BrakeAssist int(11) Null
14. LeatherSeats int(11) Null
15. RegDate Timestamp Null
16. UpdationDate timestamp Null

Table 11.10

41
11.6 Booking Table

Table Name tblbooking

Description This table is provide the information
about booking.
Primary Key Id
Foreign Key -

Table 11.11
Sl.No Field Name Data type(Size) Constraints
1. id(primary) int(11) Primary Key
2. BookingNumber bigint(12) Null
3. UserEmail varchar(100) Null
4. VehicleId int(11) Null
5. FromDate varchar(20) Null
6. ToDate varchar(20) Null
7. Message varchar(255) Null
8. Status int(11) Null
9. PostingDate timestamp Null

Table 11.12

42
CHAPTER – 12
SCREENSHOTS

43
 CHAPTER 12
SCREENSHOTS

12.1.1 Admin Modules

1. Admin Login

Figure 12.1
12.1.2 Dashboard

Figure 12.2
44
12.1.3 Change Password

Figure 12.3

12.1.4 Manage Brands

Figure 12.4

45
12.1.5 Post a Vehicle

Figure 12.5

12.1.6 Manage Vehicles

Figure 12.6

46
12.1.7 Manage Bookings

Figure 12.7

12.1.8 Registered Users

Figure 12.8

47
12.2.1 User Modules

1. Sign Up

Figure 12.9

12.2.2 Login

Figure 12.10

48
12.2.3 Home Page

Figure 12.11

12.2.4 Profile

Figure 12.12

49
12.2.5 Update Password

Figure 12.13

12.2.6 My Booking

Figure 12.14

50
12.2.7 My Testimonial

Figure 12.15

12.2.8 Vehicles Details

Figure 12.16

51
12.2.9 List Of Vehicles

Figure 12.15

12.2.10 About Us

Figure 12.16

52
CHAPTER – 13
CODING

53
 CHAPTER 13
CODING

13.1 Index Page

<?php
session_start();
include('includ
es/
config.php');
error_reporting
(0);

?>

<!DOCTYPE
HTML>
<html
lang="en">
<head>
<meta http-
equiv="Conten
t-Type"
content="text/
html;
charset=utf-
8">
<meta http-
equiv="X-UA-
Compatible"
content="IE=e
dge">
<meta
name="viewp
ort"
content="widt
h=device-
width,initial-
scale=1">
<meta
name="keywo 54
rds"
content="">
<meta
 <link rel="alternate stylesheet" type="text/css"
href="assets/switcher/css/green.css" title="green" media="all" />
<link rel="alternate stylesheet"
type="text/css"
href="assets/switcher/css/purple.css" title="purple"
media="all" />
<link rel="apple-touch-icon-precomposed" sizes="144x144"
href="assets/images/favicon-icon/apple-touch-icon-144-precomposed.png">
<link rel="apple-touch-icon-precomposed" sizes="114x114"
href="assets/images/favicon-icon/apple-touch-icon-114-
precomposed.html">
<link rel="apple-touch-icon-precomposed" sizes="72x72"
href="assets/images/favicon-icon/apple-touch-icon-72-precomposed.png">
<link rel="apple-touch-icon-precomposed"
href="assets/images/favicon-icon/apple- touch-icon-57-precomposed.png">
<link rel="shortcut icon"
href="assets/images/favicon-icon/24x24.png">
<link href="https://fonts.googleapis.com/css?
family=Lato:300,400,700,900" rel="stylesheet">
</head>
<body>

<!-- Start Switcher -->

<?php include('includes/colorswitcher.php');?>
<!-- /Switcher -->

<!--Header-->
<?php include('includes/header.php');?>
<!-- /Header -->

<!-- Banners -->

<section id="banner" class="banner-section">
<div class="container">
<div class="div_zindex">
<div class="row">
<div class="col-md-5 col-md-push-7">
<div class="banner_content">
<h1>Online Bike Rental Management</h1>
<p>We have more than a thousand bikes for you to
choose. </p>
<a href="#" class="btn">Read More <span class="angle_arrow"><i class="fa
fa-angle-right" aria-hidden="true"></i></span></a> </div>
</div>
</div> 55
</div>
</div>
 <link rel="alternate stylesheet" type="text/css"
href="assets/switcher/css/pink.css" title="pink" media="all" />
<link rel="alternate stylesheet"
type="text/css"
href="assets/switcher/css/green.css" title="green"
media="all" />
<link rel="alternate stylesheet" type="text/css"
href="assets/switcher/css/purple.css" title="purple" media="all" />

</div>
<ul class="coustom-breadcrumb">
<li><a href="#">Home</a></li>
<li>Bike Listing</li>
</ul>
</div>
</div>
<!-- Dark Overlay-->
<div class="dark-overlay"></div>
</section>
<!-- /Page Header-->

<!--Listing-->
<section class="listing-page">
<div class="container">
<div class="row">
<div class="col-md-9 col-md-push-3">
<div class="result-sorting-wrapper">
<div class="sorting-count">
<?php
//Query for Listing count
$sql = "SELECT id from tblvehicles";
$query = $dbh -> prepare($sql);
$query->bindParam(':vhid',$vhid,
PDO::PARAM_STR);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$cnt=$query->rowCount();
?>
<p><span><?php echo htmlentities($cnt);?>
Listings</span></p>
</div>
</div>

<?php $sql = "SELECT tblvehicles.*,tblbrands.BrandName,tblbrands.id56

as bid from tblvehicles join tblbrands on tblbrands.id=tblvehicles.VehiclesBrand";
<script src="assets/js/slick.min.js"></script>
<script src="assets/js/owl.carousel.min.js"></script>

</body>
</html>
<?php } ?>

13.2 Contact Us

<?php
session_start();
error_reporting(0);
include('includes/
config.php');
if(isset($_POST['s
end']))
{
$name=$_POST['f
ullname'];
$email=$_POST['e
mail'];
$contactno=$_PO
ST['contactno'];
$message=$_POS
T['message'];
$sql="INSERT INTO tblcontactusquery(name,EmailId,ContactNumber,Message)
VALUES(:name,:email,:contactno,:message)";
$query = $dbh->prepare($sql);
$query->bindParam(':name',$name,PDO::PARAM_STR);
$query->bindParam(':email',$email,PDO::PARAM_STR);
$query->bindParam(':contactno',$contactno,PDO::PARAM_STR);
$query->bindParam(':message',$message,PDO::PARAM_STR);
$query->execute();
$lastInsertId = $dbh->lastInsertId();
if($lastInsertId)
<!DOCTYPE HTML>
<html lang="en">
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=utf-8">
<meta http-equiv="X-UA-
Compatible" content="IE=edge">
57
<meta name="viewport"
content="width=device-
width,initial-scale=1">
<link rel="stylesheet" href="assets/css/bootstrap.min.css" type="text/css">
<!--Custome Style -->
<link rel="stylesheet" href="assets/css/styles.css" type="text/css">
<!--OWL Carousel slider-->
<link rel="stylesheet" href="assets/css/owl.carousel.css" type="text/css">
<link rel="stylesheet" href="assets/css/owl.transitions.css" type="text/css">
<!--slick-slider -->
<!-- SWITCHER -->
<link rel="stylesheet" id="switcher-css" type="text/css"
href="assets/switcher/css/switcher.css" media="all" />
<link rel="alternate stylesheet" type="text/css"
href="assets/switcher/css/red.css" title="red" media="all" data-default-color="true" />
<link rel="alternate stylesheet" type="text/css"
<link rel="apple-touch-icon-precomposed" sizes="144x144"
href="assets/images/favicon-icon/apple-touch-icon-144-precomposed.png">
<link rel="apple-touch-icon-precomposed" sizes="114x114"
<style>
.succWrap{ padd
ing: 10px;
margin: 0 0 20px
0;
background: #fff;
border-left: 4px
solid #5cb85c;
-webkit-box-
shadow: 0 1px
1px 0
rgba(0,0,0,.1);
box-shadow: 0
1px 1px 0
rgba(0,0,0,.1);
}
</style>
</head>
<body>

<<!-- Start
Switcher -->
<?php
include('includes/
colorswitcher.php
');?>
<!-- /Switcher --
> 58

<!--Header-->
 <title>Bike Rental Portal | Admin Create Brand</title>
<!-- FoOt awesome -->
<link rel="stylesheet" href="css/font-awesome.min.css">
<!-- Sandstone Bootstrap CSS -->
<link rel="stylesheet" href="css/bootstrap.min.css">
<!-- Bootstrap Datatables -->
<
<script src="js/jquery.min.js"></script>
<script src="js/bootstrap-select.min.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/jquery.dataTables.min.js"></script>

<script src="js/chartData.js"></script>
<script src="js/main.js"></script>
</body>
</html>
<?php } ?>

13.3 Log Out

<?php
session_start();
$_SESSION =
array();
if
(ini_get("sessi
on.use_cookies
")) {
$params = session_get_cookie_params();
setcookie(session_name(), '', time() - 60*60,
$params["path"], $params["domain"],
$params["secure"], $params["httponly"]
);
}
unset($_SESSION['login']);
session_destroy(); // destroy session
header("location:index.php");
?>

59
CHAPTER – 14
CONCLUSION

60
 CHAPTER 14
CONCLUSION

In comparison to previous experiences, when every activity related to the vehicle

rental business was restricted to a physical place alone, the bike rental industry has
emerged with new delicacies

Even if the physical location has not been completely eliminated, the internet's power
has altered the nature of functions and how these tasks are accomplished Customers
may now book vehicles online, rent automobiles online, and have the bike delivered
to their home if they are a registered member, or they can travel to the office to pick
up the bike.
From web based portal, we can say that bike rental portal can be more helpful and
saves lot of time with more some advantages:

 Fully funtional and flexible.

 Can book a bike with/without driver.
 Local booking or outstation booking
 With insurance or without insurance.
 It saves lot of time money and labour.
 Can operate 24x7.
 Use of least paper work.

61
 CHAPTER – 15

FUTURE ENHANCEMENT

62
 CHAPTER 15
FUTURE ENHANCEMENT

 Add new bike is representing the bike list.

 The User payment for the current receiptof the payment.
 Add the current project for booking easy.
 System that allows users to track the availability of bikes in real-time.
 Users can reserve bikes in advance.
 Adding a loyalty program to incentivize users to continue renting
bikes.

63
 CHAPTER -16
BIBILOGRAPHY

64
 CHAPTER 16
BIBILOGRAPHY

The following books were referred during the analysis and execution phase of
the Project.

16.1 Books Referred:

 BEGINNING PHP5 - DAVE MERCER

 BLACK BOOK HTML - -WILEY DREAMTECH
 PHP AND MYSQL WEB DEVELOPMENT-LUKEWELLING LAURA
 MICROSOFT SQL SERVER 2000--RANKIN, PAUL & JENSEN
 SQL SERVER-2000 - DUSAN PETKOVIC
 PHP IN A NUTSHELL -PAUL HUDSON

16.2 Websites Referred:

 https://www.mysql.com/
 https://www.apachefriends.org/download.html
 https://www.php.net/
 https://www.sitepoint.com/php/
 http://www.projectworlds in

65