ONLINE CAR RENTAL SYSTEM

Project Report

Submitted By
GURU PRASATH.N
Reg.No:16BCA025

Under the Guidance of

Mr.R.SURESH MCA,M.Phil

In partial fulfillment of the requirements for the Award of the Degree of

Bachelor of Computer Application

Department of Computer Science

Dr. G. R. Damodaran College of Science (Autonomous)

(Autonomous, affiliated to the Bharathiar University and recognized by UGC)
Re-accredited at the ‘A’ Grade level by the NAAC
An ISO 9001:2008 Certified Institution
Coimbatore 641-014.

MARCH-2019
 Department of Computer Science

Dr. G. R. Damodaran College of Science (Autonomous)

(Autonomous, affiliated to the Bharathiar University and recognized by UGC)
Re-accredited at the ‘A’ Grade level by the NAAC
An ISO 9001:2008 Certified Institution
Coimbatore 641-014.

Certificate

This is to certify that this project report entitled

ONLINE CAR RENTAL SYSTEM

is a bonafide record of project work done by

GURU PRASATH.N
Reg. No:16BCA025

Submitted in partial fulfillment of the requirements for the degree of

BACHELOR OF COMPUTER APPLICATION.

_____________ _____________
___________________

Faculty Guide Head of the Department

Submitted for Viva-Voce Examination held on ____________________

_______________ ______________

Internal Examiner External Examiner

DECLARATION
 DECLARATION
I hereby declare that the project entitled “ONLINE CAR RENTAL SYSTEM” submitted to
Dr.G.R.Damodaran college of Science (Autonomous affiliated to the Bharathiar University)
in partial fulfillment of the requirements for the award of the Degree of BACHELOR OF
COMPUTER APPLICATION is a record work done by me under the guidance of
Mr.R.Suresh MCA, M.Phil, Assistant professor, Department of ComputerScience.

Reg.No :16BCA025 GURU PRASATH.N

DATE:
 TABLE OF CONTENTS

Chapter No TITTLE Page No

ACKNOWLEDGEMENT

SYNOPSIS

1 INTRODUCTION
1.1 Organization Profile
1.2 Module description

2 SYSTEM ANALYSIS
2.1 Existing system
2.2 Proposed system

3 SYSTEM SPECIFICATIONS
3.1 Hardware Requirements
3.2 Software Requirements
3.3 Software feature

4 SYSTEM DESIGN

4.1 Input Design

4.2 Output Design
4.3 Database Design

5 SYSTEM TESTING & IMPLEMENTATION

5.1 System Testing
5.2 System Implementation

6 SYSTEM MAINTENANCE

7 CONCLUSION& FUTURE ENHANCEMENT

8 BIBLIOGRAPHY

9 APPENDIX
ACKNOWLEDGEMENT
 ACKNOWLEDGEMENT
I thank almighty God for providing me Knowledge, Strength and all vital facility
to complete the project.

In deep sense of gratitude, I express my sincere thanks to our beloved

Dr.T.SANTHA, Principal of Dr.G.R.Damodaran College of Science, Coimbatore for
extending his valuable support in allowing me to undertake this project.

I extend my sincere thanks to Dr.G.RADHAMANI, Director of Department of

Computer Science, Dr.G.R.Damodaran College of Science, Coimbatore for her
encouragement and valuable support throughout my project.

I cordially express my thanks to Dr.S.SUJATHA, Head of

Department,Department of Computer science Dr.G.R.Damodaran College of Science,
Coimbatore for her constant guidance.

I extend my heartfelt thanks to my respected guide, Mr.R.SURESH, MCA,

M.Phil Assistant professor, who helped me to complete my project with constant support
and guidance. My sincere thanks to all the staff members of my department too, for their
encouragement and suggestions.

I extend my sincere thanks to GOMATHI ENGINEERING WORKS

Coimbatore for being my industry guide and helping me in all possible means during the
course of this project.

At last not the least with love and affection, I would like to thank my family for
their prayers, support and advice, which guided me always.

GURU PRASATH.N
(16BCA025)
 SYNOPSIS
This project titled as “ONLINE CAR RENTAL SYSTEM” is concerned with
the enquiry and process of booking cars. This package helps the user of renting cars to
view their reports according to their requirements.
The system developed on Asp.Net has a strong database

support in M.S SQL Server the powerful form designer Asp.Net as contain all features

that marks it as a powerful GUI. The speed and ability to process a large database add its

efficiency.

I developed this project to book a car on rent at the fare charges.

In present system all booking work done manually and it takes very hard work to

maintain the information of booking and cars. If you want to find which vehicle is

available for booking then it takes a lot of time. It only makes the process more difficult

and hard. This aim of the project is to automate the work performed in the car rental

management system like generating daily bookings, records of car or cab available for

booking, record of routes available, rental charges for cars for every rout, store record of

the customer.Online Car rental system is a car booking software that provides a complete

solution to all your day-to-day car booking office running needs. This system helps you

to keep the information of Customer online. You can check your customer information

any time by using this system. Online Car rental system is a unique and innovative

product. Using this this you can also keep the information of number of bookings in

current month or in last 6 month or in last year. Based on this information you can take

decision regarding your business development.

The most important feature of the project, it is user friendly i.e.

it is very easy to use for a person who has no deep knowledge in computer
 1. INTRODUCTION

1.1 ORGANIZATION PROFILE

Gomathi Engineering Works is a leading Manufacturer & supplier of

Wooden , Aluminium , Arialdite pattern and dies in CNC , VMC or Manual

manufacturer in Coimbatore. The foundation stone of Coimbatore , Tamilnadu, India

based Gomathi Engineering Works was laid in the year 1990, under the guidance of

Industry-experience. Experienced management the company has witnessed great height

and still flourishing at a rapid pace. They are procuring high grade aluminium metal and

high quality pattrens. Company is located in Vadamadurai, Coimbatore, Tamilnadu, India.

Gomathi Engineering Works deals in various types of Textile machinery and Industrial

spares that includes shafts, brackets & various hubs, studs, flutted rollers, roller stands

&bottom roller slides and many more. These products are manufactured at vendor’s end

with the perfect blend of latest technology and well trained manpower.

KEY FACTS ABOUT ORGANIZATION:

 Ethical business practices

 Industry leading price

 Knowledgeable professionals

 Time bounded delivery

 100% customer centric approach

1.2 MODULE DESCRIPTION

The modules of the project are as follows, each module has their own
function.
CUSTOMER:

This module maintains the detailed profile of the customer and their purchase

along with the details. The customer will be given with a customer code. And the last

transaction made by the customer will be listed. Some discounts are given to the

customer according to the number of purchase he made with the concern.

CARS DETAILS:

This module maintains the entire item sold in the past along with their discounts
car rates, total price etc. Here the rental of the items is listed according to the date of the
rental and the customer code. The new rental order can also be added to the system.

BOOKING DETAILS:

This module maintains the detailed profile of the car rental details. The customer
will be given with a customer code. Customer can select different cars like maruthi, alto,
nison, tata sumo and more then models. Rent can different to model of cars. This module
store the details in hiring table.

PAYMENTS:
This module contains the details about the rental payment. The details such as
invoice number, invoice date, rental amount, and total amount are maintained in this
module
 2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

The system, which is followed at present, is an manual system, which has

elaborated function for every process, now the system is done by manually.

In manual system nearly six members are needed and is maintain in different
register each for production, sales etc. Any person can see the details easily. More time is
needed to do work. The existing system’s security is poor.

LIMITATIONS OF EXISTING SYSTEM

 In manual system maintain number of not books for each department.

 Time takes is more and transactions are slow.
 Absence of multitasking.
 Modification of any correction and anything is very difficult and errors
occur frequently.
 Manual work takes more man power.
 In manual work followed by many functions so calculations and transaction
details are difficult to maintain.
 Security of the processing system is very low.
2.2 PROPOSED SYSTEM

The proposed system makes the management of the details easier which is

far better than the existing system. In our system the need for maintaining large, written

information is reduced. The way in which the data stored is very efficient. This helps in

easy entry, editing, storing the data as well as retrieving the data.

Separate tables for purchases, sales, and returns for both are maintained. The

database is carefully designed to facilitate the easy, accurate retrieval and also to

consolidate the information.

The some of the benefits of the proposed system are,

 It reduces the volume of documents stored if maintained manually.

 Easy entry, editing, deletion, and extraction of information.

 Quick retrieval of the wanted information.

 Immediate information of the present stock, needs etc.

 3. SYSTEM SPECIFICATION

3.1 HARDWARE SPECIFICATION

Hardware specification of the system that is used in this project are ,

Processor : Intel Core 2 Duo 2.66 GHz

RAM : 2 GB

Hard disk : 500 GB

3.2 SOFTWARE SPECIFICATION

Software specification of the system that is used in this project is,

Operating System : WINDOWS 8

Front End : ASP.Net

Back End : MS – SQL Server

3.3 SOFTWARE FEATURE

FRONT-END: ASP.NET

In this day of business-to-business and business-to-consumer e-commerce, slow

Web applications can waste resources and drive customers away from your company.
Web site performance is an extremely important issue for the developer writing code and
for the system administrator maintaining applications.

Fortunately, ASP.NET incorporates a variety of features and tools that allow you
to design and implement high-performance Web applications. These features include the
following:

 An improved process model

 Compilation of requested pages and automatic storage on the server
 ASP.NET-specific performance counters
 Web application testing tools

ASP.NET gives you the ability to create Web applications that meet the demands
that arise when they must process large numbers of requests simultaneously. Describes
how to use the performance counters that are delivered with the .NET Framework, as
well as how to create your own Performance Counter objects to customize the way in
which you monitor your applications, services, and drivers.
Creating ASP.NET Web Applications
ASP.NET is a unified Web development platform that provides the services
necessary for you to build enterprise-class Web applications. While ASP.NET is largely
syntax compatible with Active Server Pages (ASP), it provides a new programming
model and infrastructure that allow you to create a powerful new class of applications.
ASP.NET is part of the .NET Framework and allows you to take full advantage of the
features of the common language runtime, such as type safety, inheritance, language
interoperability, and versioning.
This section provides you with conceptual information about how ASP.NET
works and procedural topics that show you how to write code that takes full advantage of
the power of this new platform.

Introduction to ADO.NET
ADO.NET is the latest in a long line of database access technologies that
began with the open database connectivity (ODBC) application-programming interface
(API). With .NET Microsoft offers a general-purpose framework—the Framework class
library that covers all the existing windows API and more. In particular, it includes a
number of frequently used libraries now available through separate COM objects.
Among these, we find that XML and ADO object models have been integrated in a sub
tree of classes called ADO.NET. ADO.NET turns out to be the substrate that will form
the foundation of data-aware .net applications. ADO.NET gathers all the classes that
allow data handling. Such classes represent data container objects that feature typical
database capabilities –indexing, sorting, and views.
The success of web applications changed the face of the typical distributed
system. Now most distribution systems are n-tier. Systems characterized by a high, and
still growing, demand for scalability and interoperability. As a result, data disconnection
and XML became best practices and gained a wide acceptance from the industry.
ADO.NET tries to unify some of today’s best practices under the umbrella of .NET. The
overall programming model for data access is comprehensive and incredibly powerful.
ActiveX Data Objects (ADO):
This is a programming model that eliminates the need to choose from
among DAO and RDO and all other data access methods. It is designed to provide a
common bridge between different databases, file systems
and e-mail servers.
ADO Commandobject:
The ADO Command object is used to execute commands against a data
source. This object can apply changes through manipulation command such as insert,
update and delete; it is presently limited to read-only, forward-only access to the Result
set through the ADO Data Reader.
ADO Data Reader:
If the user wants to perform a sequential, read-only pass through a query
result, the dataset command can be used to establish a reader object. The properties and
methods included in the ADO Data Reader helps the user to scan through the query
result.

Back-End: MS SQL SERVER (Structured Query Language)

SQL Server is a relational database management system that’s capable of handling

large amounts of data and many concurrent users while preserving data integrity and
providing many advanced administration and data distribution capabilities.
The SQL Server component acts as a gateway between the clients and the
physical data. No client applications have direct access to the data.

The features of the SQL Server

 It is a client-server architecture and not shared-file application as Access.
 Symmetric Multiprocessing (SMP) supports up to 32 simultaneous processors.
 It can have database up to 1 terabyte (1024 GB) in size.
 It can handle up to 32,767 simultaneous user connections.
 A language used to insert, retrieve, modify, and delete data in a relational
database. SQL also contains statements for defining and administering the objects in a
database. SQL is the language supported by most relational databases, and is the subject
of standards published by the International Standards Organization (ISO) and the
American National Standards Institute (ANSI). SQL Server 2000 uses the SQL language
called Transact-SQL.

SQL server Query Analyzer is a graphical toll that allows you to:

 Edit and SQL scripts queries.

 View a graphical representation of a query’s (estimated) execution plan.
 Return query results to grid or text.
 Perform index analysis.
 Retrieve Transact-SQL syntax help
 View statistic information about an executed query.
 4. SYSTEM DESIGN

SYSTEM DESIGN
System design is described as a process of planning a new business system or

more to replace or to complement an existing system. The system design states how a

system will meet the requirements identified during the system analysis.

System design focuses mainly on four distinct attributes. They are data structure,

software architecture, interface representation and algorithmic details.

It describes a solution of approaching to the creation of new system. System

design is a transmission from a user-oriented document to a document oriented to

programmers.

4.1 INPUT DESIGN

Input design is a part of overall system design, which requires very careful
attention. Often the collection of input data is the most expensive part of the system, in
terms of both the equipments used and the number of people involved; it is the point of
most contact for the users with the computer system, and it is prone to error. If data going
into the system is incorrect, then the processing and output will magnify these errors and
thus the designer has number of clear objectives in input design.
 To produce a cost effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.
In this system input screen is designed carefully so that no inaccurate data will
enter into the database. The data is made as easy as possible. For simplifying the data
entry, many facilities are given. The branch, class can easily be selected through option
buttons to facilitate easy selection. The attendance entries can also be entered with the
help of these buttons. It provides user friendly interface and reduces strain.
4.2 OUTPUT DESIGN

An output from computer system requires primarily communicating the results of

processing to the users. They also provide a permanent hard copy of these results for later
consultations. The various types of outputs required by the system are given below.
 External outputs, whose destination is outside the concern, require special
attention, because the project is the image of the concern.
 Internal inputs whose destination is within the concern and which requires careful
design because they are the user’s main interface within the computer.
 Operation outputs, whose use is purely within the computer department, for
example, program listing, usage statistics, etc.,
 Interactive outputs, which involves the user in communicating directly with the
computers.
4.3 DATABASE DESIGN

Database design includes the contents of all the tables in a report manner.

It enters the details about each table. Database design is the process of converting the

user originated inputs into a computer based format. The goal of the design is to make

the data entry easier, logical and error free.

The data in the system is stored and retrieved from the database. Designing
the database is a part of the 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. The general theme behind the database is to handle the
information as an integrated whole. When designing a database, we have to make
decisions regarding how best to make some systems in the real world and model it as
database.

The goal of database design is to generate a set if relations that allows storing
information easily. The database is designed in relational model in which the data are
organized into entries and relation between them.
In our data flow diagrams, we have given names to data flows, process and data
stores. Although the names are descriptive of the data, they do not give details. So the
following DFD gives the details of the fields used. A data dictionary has many advantage
in improving analyst of user communication by establishing consistent definitions of
terms elements and procedures.
 5. SYSTEM TESTING AND IMPLEMENTATION

5.1 SYSTEM TESTING

The purpose of system testing is to identity and current errors in the
candidate system. As important as this phase is, it is one that is frequently compromised.
Typically, the project the schedule or the user is eager to go directly to conversion.

TESTING METHODOLOGIES
The system testing includes unit testing, integration testing and validation
testing. Each one is described as follows.

MODULETESTING
Unit testing focuses the verification effort on the smallest unit of software
design, which is the module. The unit testing is always white box oriented and the steps
can be conducted in parallel for the modules. The organization of the testing activity
should in some way reflect the organization of the design activity. Taking into account
this viewpoint the modules were tested individually to assure that they function properly
as a unit. Both White-Box testing and Black –Box testing strategies were used.

WHITE-BOX TESTING
The test cases were chosen to ensure that
 The loop conditions certainly evaluate to false, there by
avoiding infinite loops
 The loops get executed only the required number of times,

thus by avoiding Off-by-One errors

 If as well as else parts get executed in order to ensure both

the blocks are working properly
BLACK-BOX TESTING

The system was tested to check whether it meets the requirements determined in
the requirements analysis phase. The system met all the functional requirements.

INTEGRATION TESTING
Integration testing is systematic technique for conducting the program
structure. While at the same time conducting tests to uncover errors associated with the
interfacing.
The objectives are to take unit tested modules and to build a program that
has been dedicated by design.
There are two types of integration testing:
 Top down integration.
 Bottom up integration.

Top down Integration

Top down integration is an incremental approach to the construction of
program structure. Modules are integrated by moving downward through the control
hierarchy, beginning with the main control module.

Bottom up Integration
Bottom up integration testing, as it implies, begin construction and testing with
atomic modules. That is a module at the lowest levels in the program structure.

A bottom up integration strategy may be implemented with following steps.

 Low level modules are combined into clusters (some times builds) that perform a
specific software sub-function.
 A driver is to test case input and output.
 The cluster is tested (clusters means modules).
  Drivers are removed and clusters are combined moving upward in the program
structure.
VALIDATION TESTING
In the testing, software is completely assembled as package, interfacing
error have been uncovered and correction testing begins after each one of the two
possible conditions exists.
The function or performance characteristic’s is confirm specification and
are accepted. A deviation from the specification is uncovered and efficiency list is
created.
The testing, which can be carried out in this project is unit testing. The
reason for using this testing is described as below.
Unit Test Consideration
The module “interface” is testing to ensure that information properly flows
in and out of the programs unit under test. The local data structures are examined to
endure that the data stored temporarily maintains its integrity during all steps in an
algorithm execution.
Boundary conditions are tested to ensure that the modules operated properly at
boundaries established to limit or restrict processing. All independent paths through the
control structures are exercised to ensure that all statements in modules have been
executed at least once. Finally parts are tested.
Unit Test Performance
Unit test is considered an equivalent to the coding step. After
the source level code has been developed, reviewed and verified for correct syntax; unit
test case begins, since a module is not stand along program. Drivers or stub software
must be developed for each unit test.
User Acceptance
The application is created in such a way that the user need not know about the
implemented tool of the application. This application is a friendly GUI so that special hot spot
are given to make the user to maintain his path. Menus are provided to reduce navigational
effort for the users. The application is developed as user-friendly. The homepage of this
application is given with a link, which directs the user to the logging pages so that the user
need not even know about the navigation of the application.
5.2 SYSTEM IMPLEMENTATION
A crucial face in the system life cycle is the successful implementation of
the new system design. An important aspect of a system analysis job is to make sure that
the new design is implemented to established standards. The term implementation has
different meanings ranging from the conversion of basic application, to a complete
replacement of a computer system. Implementation used here is to mean the process of
converting a new or a revised system design into an operational one. Conversion is one
aspect of implementation. There are three types of implementation:
 Implementation of a computer system to replace a manual system. The
problem encountered are converting files, training users, creating accurate
files and verifying printouts for integrity.
 Implementation of a new computer system to replace conversion. If not
properly planed, there can be many problems. Some large computer systems
have taken as long as a year to convert.
 Implementation of a modified application to replace an existing one using the
same computer. This type of conversion is relatively easy to handle, provided
there are no major changes in the files.

Implementation is the process of converting a new or revised system design into

an operational one. It is the stage in achieving a successful new system because usually it
involves a lot of upheaval in the user department.
Therefore, it must be carefully planned and controlled. Apart from planning, the
three major tasks of preparing for implementation are education, training of users and
applying the process.
.

6. SYSTEM MAINTAINANCE
MAINTAINANCE PROCEDURE
Maintenance covers the activities such as correcting, coding and debugging errors.
Updating documentation and test data and upgrading user support. Many activities are
actually enhancements.
Four types of maintenance are performed on computer software

Corrective Maintenance

Corrective maintenance acts to correct errors that are uncovered after the

software is in use. This system maintenance due to some false assumption like details of

the user. So every thing is done manually and corrected.

Adaptive Maintenance

Adaptive Maintenance is applied when changes in the external environment

precipitate modifications to software. The system undergo this maintenance do add
additional encasement.

Perfect maintenance
Perfective Maintenance incorporates enhancements that are requested by
the user community. The system will updated according to fulfill user requirements, so
this maintenance is done.

Perfective Maintenance
 Preventive Maintenance improves future maintainability and reliability and
provides a basis for future enhancement. This helps the system to be reliable and easy to
when additional enhancement is done.

SECURITY MEASURE
The system is safeguarded from unauthorized use of the software by providing
proper authentication. The user is allowed to use the system provided he gives the
correct user name and password, otherwise the entry is restricted to the user. The user
name and password is unique and is stored in a database for reference. The password
field is set to display asterisks that help the password to be secure.

To increase the security of the system and protect it from other Virus software,
antivirus software is included in the system such as Norton Antivirus and Scan Disk, to
detect virus and to fix errors.
7.CONCLUSION & FUTURE ENHANCEMENT

CONCLUSION
Online Car Rental System developed in Asp.Net as front end and MS- SQL
Server as back end is an integrated system that is user-friendly and menu driven. The
screens are constructed in such a way that the user will find it easy to navigate the whole
system. Accurate headings and guidelines are provided wherever necessary. The system
is found to be effective and proves to be versatile as it’s a very flexible with user-friendly
screens enabling the user to use it without any inconvenience. This provides a better
system and it overcomes many problems that exist in the current system.
The system is designed in such a way that no formal programming knowledge is
expected from the user. Error correction and modification for future enhancement could
be made very easily. This system is highly portable and can be implemented in any
organization without much modification of the software.

FEATURE ENHANCEMENT

The system resulted in regular and timely preparation of the required outputs. In
comparison with manual system, the benefits under this system are there is a considerable
amount of the savings in manpower, working hours and effort. It can be observed that the
information required can be obtained with ease and accuracy in the computerized system.

The system can be further extended to include online subscription system by

updating the details on the internet. The system can also be extended to include customer
feedback and complaints module to improve the work efficiency of the organization.
8.BIBLIOGRAPHY
 Don Box, with Chris Sells, “Essential. Net”-Third Edition.
 Harold Davis, “Visual Basic.Net for Windows” - Second Edition.
 Steven Holzner,” Visual Basic.Net 2005”, Pearson Education.
 Matt J.Crouch, “VB.Net Web Programming”- corporate Edition.
 G.Andrew Duthie, “Microsoft Visual Basic.Net”- version 2005
 David solution, “Sam Teach Yourself VB 3.0 In 21 Days”, Crimson
Publications, Second Edition, March 2005.
 Elias M.Award, “ System analysis and design” ,Galgotia publishers,
Second Edition (2005).
 Roger S.Pressman, “Software Engineering, A Practioner’s
Approach ”, McGraw Hill international companies, Sixth Edition.
 Shooman, “Software Engineering”, Tata Mc-Graw Hill Publishing
Company Pvt ltd, 2005.
 lee & lee,” introduction system analysis and design”,ncc
publications edition – 2005.

WEBSITE REFERANCE
 http://www.ASPdotnetheaven.com/
 http://www.sysimp.com
 http://w3schools.com/dotnet
  http://www.testinggeek.com/testingtype.aspw
 http://www.sei.cmu.edu./domain-engineering/usecasediagram.html
 http://en.wikipedia.org/wiki/windows-XP
 http://www.sys-design.com

9. APPENDIX
DATA FLOW DIAGRAM

Level- 0

Car rental
User system Data Store Booking/Cancel
Level- 1
TABLE DESIGN

Table Name: UserMaster

Primary Key: User_Id

Sr. Field Name Data type(Size) Constraints Description

No

1 User_Id Int Primary Key It is store User id

2 Name Varchar(50) Not Null It is store User name
3 Password Varchar(20) Not Null It is store Password
4 Address Varchar(100) Not Null It is store address of User
It is store email address of
5 Email Varchar(50) Not Null User

It is store contact number

6 Contact Varchar(12) Not Null User
Table Name: Car

Primary Key: Car_Id

Data
Sr. No Field Name type(Size) Constraints Description
Primary
1 Car_Id Int Key It is store Car id
Model_Nam
2 e Varchar(20) Not Null It is store Model name
3 Brand Varchar(20) Not Null It is store Brand of the car
4 Color Varchar(10) Not Null It is store Color name of the ca
No_of_sheet It is store information of
5 s Varchar(10) Not Null passenger seats

6 Price Int Not Null It is store price of the car

7 Image Varchar(50) Not Null It is store images of car
8 Fuel type Varchar(10) Not Null It is store fuel type in car
Table Name: Booking

Foreign Key: Car_Id

Sr. No Field Name Data type(Size) Constraints Description

It is references to C_Id
1 Car_Id Int Foreign Key from car

2 Name Varchar(20) Not Null It is store name of the car

3 Date DateTime Not Null It is store booking date

4 S_address Varchar(50) Not Null It is store source address

It is store information
5 D_address Varchar(50) Not Null about destination addres

6 Email_Id Varchar(50) Not Null It is store email address

7 No. of Pieces Int Not Null It is store information

how many car available
 in time

It is store Contact no of
8 Contact_No Varchar(12) Not Null user

Table Name: Feedback

Foreign Key: User_id

Data Constrai
Sr. No Field Name type(Size) nts Description
1 User_id int Not Null It is store User Id
2 subject Varchar(20) Not Null It is store subject details
 3 Suggestion Varchar(50) Not Null It is store user suggestion

Table name: payment

Foreign key: user_id, Car_id

Sr.no FIELD DATATYPE(SIZE) CONSTRAINTS DESCRIPTION

NAME
1 user_id Int Foreign key Unique id of
executive
2 car_id Int Foreign key Unique id of
staff
3 km Varchar(7) Not null Total km 0f
drive
4 Rate Varchar(8) Not null Rate per km
5 total int Not null Total amount
of drive
6 Payment Datetime Not null Payment date
date

FORMS
Admin Login
User login
User main menu
Admin view booking report: