Project Report of Vehicle Management System

Report of Vehicle Management System

Page - 1
 Project Report of Vehicle Management System

Chapter 1:

Abstract of the Project Vehicle Management System:

The purpose of Vehicle Management System is to automate the existing manual
system by the help of computerized equipments and full-fledged computer software,
fulfilling their requirements, so that their valuable data/information can be stored for a
longer period with easy accessing and manipulation of the same. The required software
and hardware are easily available and easy to work with.

Vehicle Management System, as described above, can lead to error free, secure,
reliable and fast management system. It can assist the user to concentrate on their
other activities rather to concentrate on the record keeping. Thus it will help organization
in better utilization of resources. The organization can maintain computerized records
without redundant entries. That means that one need not be distracted by information
that is not relevant, while being able to reach the information.

The aim is to automate its existing manual system by the help of computerized
equipments and full-fledged computer software, fulfilling their requirements, so that their
valuable data/information can be stored for a longer period with easy accessing and
manipulation of the same. Basically the project describes how to manage for good
performance and better services for the clients.

Page - 2
 Project Report of Vehicle Management System

Chapter 2:

Introduction of the Project Vehicle Management System:

The "Vehicle Management System" has been developed to override the problems
prevailing in the practicing manual system. This software is supported to eliminate and
in some cases reduce the hardships faced by this existing system. Moreover this
system is designed for the particular need of the company to carry out operations in a
smooth and effective manner.

The application is reduced as much as possible to avoid errors while entering the data.
It also provides error message while entering invalid data. No formal knowledge is
needed for the user to use this system. Thus by this all it proves it is user-friendly.
Vehicle Management System , as described above, can lead to error free, secure,
reliable and fast management system. It can assist the user to concentrate on their
other activities rather to concentrate on the record keeping. Thus it will help organization
in better utilization of resources.

Every organization, whether big or small, has challenges to overcome and managing
the informations of Driver, Vehicle, Maintanance, Vehicle Type, Fuel. Every Vehicle
Management System has different Vehicle needs, therefore we design exclusive
employee management systems that are adapted to your managerial requirements.
This is designed to assist in strategic planning, and will help you ensure that your
organization is equipped with the right level of information and details for your future
goals. Also, for those busy executive who are always on the go, our systems come with
remote access features, which will allow you to manage your workforce anytime, at all
times. These systems will ultimately allow you to better manage resources.

Page - 3
 Project Report of Vehicle Management System

Chapter 3:

Literature Review of Vehicle Management System

It may help collecting perfect management in details. In a very short time, the
collection will be obvious, simple and sensible. It will help a person to know the
management of passed year perfectly and vividly. It also helps in current all works
relative to Vehicle Management System. It will be also reduced the cost of collecting the
management & collection procedure will go on smoothly.

Our project aims at Business process automation, i.e. we have tried to

computerize various processes of Vehicle Management System.

 In computer system the person has to fill the various forms & number of copies of
the forms can be easily generated at a time.
 In computer system, it is not necessary to create the manifest but we can directly
print it, which saves our time.
 To assist the staff in capturing the effort spent on their respective working areas.
 To utilize resources in an efficient manner by increasing their productivity through
automation.
 The system generates types of information that can be used for various
purposes.
 It satisfy the user requirement
 Be easy to understand by the user and operator
 Be easy to operate
 Have a good user interface
 Be expandable
 Delivered on schedule within the budget.

Page - 4
 Project Report of Vehicle Management System

Existing System of Vehicle Management System:

In the existing system the exams are done only manually but in proposed system we
have to computerize the exams using this application.
 Lack of security of data.
 More man power.
 Time consuming.
 Consumes large volume of pare work.
 Needs manual calculations.
 No direct role for the higher officials

Proposed System of Vehicle Management System:

The aim of proposed system is to develop a system of improved facilities. The
proposed system can overcome all the limitations of the existing system. The system
provides proper security and reduces the manual work.
 Security of data.
 Ensure data accuracy’s.
 Proper control of the higher officials.
 Minimize manual data entry.
 Minimum time needed for the various processing.
 Greater efficiency.
 Better service.
 User friendliness and interactive.
 Minimum time required.

Page - 5
 Project Report of Vehicle Management System

Chapter 4: Project Details

4.1 Overview Of Vehicle Management System:

The main objective of the Project on Vehicle Management System is to manage

the details of Vehicle, Driver, Insurance, Maintanance, Fuel. It manages all the
information about Vehicle, Vehicle Type, Fuel, Vehicle. The project is totally built at
administrative end and thus only the administrator is guaranteed the access. The
purpose of the project is to build an application program to reduce the manual work for
managing the Vehicle, Driver, Vehicle Type, Insurance. It tracks all the details about the
Insurance, Maintanance, Fuel.

Functionalities provided by Vehicle Management System are as follows:

 Provides the searching facilities based on various factors. Such as Vehicle,

Insurance, Maintanance, Fuel
 Vehicle Management System also manage the Vehicle Type details online for
Maintanance details, Fuel details, Vehicle.
 It tracks all the information of Driver, Vehicle Type, Maintanance ect
 Manage the information of Driver
 Shows the information and description of the Vehicle, Insurance
 To increase efficiency of managing the Vehicle, Driver
 It deals with monitoring the information and transactions of Maintanance.
 Manage the information of Vehicle
 Editing, adding and updating of Records is improved which results in proper
resource management of Vehicle data.
 Manage the information of Maintanance
 Integration of all records of Fuel.

Page - 6
 Project Report of Vehicle Management System

Chapter 4.2:

Functional Requirements:

The old manual system was suffering from a series of drawbacks. Since whole of
the system was to be maintained with hands the process of keeping, maintaining and
retrieving the information was very tedious and lengthy. The records were never used to
be in a systematic order. there used to be lots of difficulties in associating any particular
transaction with a particular context. If any information was to be found it was required
to go through the different registers, documents there would never exist anything like
report generation. There would always be unnecessary consumption of time while
entering records and retrieving records. One more problem was that it was very difficult
to find errors while entering the records. Once the records were entered it was very
difficult to update these records.

The reason behind it is that there is lot of information to be maintained and have
to be kept in mind while running the business .For this reason we have provided
features Present system is partially automated (computerized), actually existing system
is quite laborious as one has to enter same information at three different places.

Following points should be well considered:

 Documents and reports that must be provided by the new system: there can also
be few reports, which can help management in decision-making and cost
controlling, but since these reports do not get required attention, such kind of
reports and information were also identified and given required attention.
 Details of the information needed for each document and report.
 The required frequency and distribution for each document.
 Probable sources of information for each document and report.

With the implementation of computerized system, the task of keeping records in an

organized manner will be solved. The greatest of all is the retrieval of information, which
will be at the click of the mouse. So the proposed system helps in saving the time in
different operations and making information flow easy giving valuable reports.

Page - 7
 Project Report of Vehicle Management System

Chapter 4.3:

Non Functional Requirements:

Performance :The system must be interactive and the delays involved must be less .So
in every action-response of the system, there are no immediate delays. In case of
opening windows forms, of popping error messages and saving the settings or sessions
there is delay much below 2 seconds, In case of opening databases, sorting questions
and evaluation there are no delays and the operation is performed in less than 2
seconds for opening ,sorting, computing, posting > 95% of the files. Also when
connecting to the server the delay is based editing on the distance of the 2 systems and
the configuration between them so there is high probability that there will be or not a
successful connection in less than 20 seconds for sake of good communication.

Safety : Information transmission should be securely transmitted to server without any

changes in information

Reliability : As the system provide the right tools for discussion, problem solving it must
be made sure that the system is reliable in its operations and for securing the sensitive
details.

Availability : If the internet service gets disrupted while sending information to the
server, the information can be send again for verification.

Security : The main security concern is for users account hence proper login
mechanism should be used to avoid hacking. The tablet id registration is way to spam
check for increasing the security. Hence, security is provided from unwanted use of
recognition software.

Usability : As the system is easy to handle and navigates in the most expected way
with no delays. In that case the system program reacts accordingly and transverses
quickly between its states.

Page - 8
 Project Report of Vehicle Management System

Chapter 4.4: High Level Design:

Chapter 4.4.1:

Context Level Diagram

Page - 9
 Project Report of Vehicle Management System

Chapter 4.4.2:

DFD Dataflow Diagram:

Page - 10
 Project Report of Vehicle Management System

Chapter 4.4.3:

ER Entity Relationship Diagram:

Page - 11
 Project Report of Vehicle Management System

Chapter 4.4.4:

Test Cases:

Feature Description Release

Unit test case Core test case class and assertions 1.0
Html display Simplest possible display 1.0
Autoloading of test cases Reading a file with test cases and loading them into 1.0
a group test automatically
Mock objects Objects capable of simulating other objects 1.0
removing test dependencies
Web test case Allows link following and title tag matching 1.0
Partial mocks Mocking parts of a class for testing less than a 1.0
class or for complex simulations
Web cookie handling Correct handling of cookies when fetching pages 1.0
Following redirects Page fetching automatically follows 300 redirects 1.0
Form parsing Ability to submit simple forms and read default form 1.0
values
Command line interface Test display without the need of a web browser 1.0
Exposure of expectation Can create precise tests with mocks as well as test 1.0
classes cases
XML output and parsing Allows multi host testing and the integration of 1.0
acceptance testing extensions
Browser component Exposure of lower level web browser interface for 1.0
more detailed test cases
HTTP authentication Fetching protected web pages with basic 1.0
authentication only
SSL support Can connect to https: pages 1.0
Proxy support Can connect via. common proxies 1.0
Frames support Handling of frames in web test cases 1.0

Page - 12
 Project Report of Vehicle Management System

Feature Description Release

File upload testing Can simulate the input type file tag 1.0.1
Mocking interfaces Can generate mock objects to interfaces as well as 1.0.1
classes and class interfaces are carried for type
hints
Testing exceptions Similar to testing PHP errors 1.0.1
HTML label support Can access all controls using the visual label 1.0.1
Base tag support Respects page base tag when clicking 1.0.1
PHP 5 E_STRICT PHP 5 only version that works with the E_STRICT 1.1
compliant error level
Alternate HTML parsers Can detect compiled parsers for performance 1.1
improvements
REST support Support for REST verbs as put(), delete(), etc. 1.1
BDD style fixtures Can import fixtures using a mixin like given() 1.5
method
Plug-in architecture Automatic import of extensions including command 1.5
line options
Reporting machinery Improved message passing for better cooperation 1.5
enhancements with IDEs
Fluent mock interface More flexible and concise mock objects 1.6
Localisation Messages abstracted and code generated as well 1.6
as UTF support
CSS selectors HTML content can be examined using CSS 1.7
selectors
HTML table assertions Can match HTML or other table elements to 1.7
expectations
Unified acceptance Content searchable through selectors combined 1.7
testing model with expectations

Page - 13
 Project Report of Vehicle Management System

Feature Description Release

DatabaseTestCase SQL selectors and DB drivers 1.7
IFrame support Reads IFrame content that can be refreshed 1.8
Integrated Selenium Easy to use built in Selenium driver and tutorial or 1.9
support similar browser automation
Code coverage Reports using the bundled tool when using XDebug 1.9
Deprecation of old Simpler interface for SimpleTest2 2.0
methods
PHPscript suport Use of PECL module to add PHPscript to the native 3.0
browser

Page - 14
 Project Report of Vehicle Management System

Chapter 4.5:

Logical Data Structure

-- Database: `vehicle_management_system`
--
-- Table structure for table `city`
--
CREATE TABLE `city` (
`city_id` int(10) UNSIGNED NOT NULL,
`city_name` varchar(45) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `country`
--
CREATE TABLE `country` (
`country_id` int(11) NOT NULL,
`country_name` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `driver`
--
CREATE TABLE `driver` (
`driver_id` int(11) NOT NULL,
`driver_name` varchar(255) NOT NULL,
`driver_mobile` varchar(255) NOT NULL,
`driver_licence_no` varchar(255) NOT NULL,
`driver_licence_start` varchar(255) NOT NULL,
`driver_licence_end` varchar(255) NOT NULL,
`driver_city` varchar(255) NOT NULL,
`driver_state` varchar(255) NOT NULL,

Page - 15
 Project Report of Vehicle Management System

`driver_address1` varchar(255) NOT NULL,

`driver_address2` varchar(255) NOT NULL,
`driver_image` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `fuel`
--
CREATE TABLE `fuel` (
`fuel_id` int(11) NOT NULL,
`fuel_vehicle_id` varchar(255) NOT NULL,
`fuel_qunatity` varchar(255) NOT NULL,
`fuel_cost` varchar(255) NOT NULL,
`fuel_date` varchar(255) NOT NULL,
`fuel_description` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 ROW_FORMAT=COMPACT;

--
-- Table structure for table `insurance`
--
CREATE TABLE `insurance` (
`insurance_id` int(11) NOT NULL,
`insurance_vehicle_id` varchar(255) NOT NULL,
`insurance_start_date` varchar(255) NOT NULL,
`insurance_end_date` varchar(255) NOT NULL,
`insurance_company` varchar(255) NOT NULL,
`insurance_cost` varchar(255) NOT NULL,
`insurance_policy_no` varchar(255) NOT NULL,
`insurance_description` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

Page - 16
 Project Report of Vehicle Management System

-- Table structure for table `maintanance`

--
CREATE TABLE `maintanance` (
`maintanance_id` int(11) NOT NULL,
`maintanance_vehicle_id` varchar(255) NOT NULL,
`maintanance_date` varchar(255) NOT NULL,
`maintanance_cost` varchar(255) NOT NULL,
`maintanance_description` text NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `role`
--
CREATE TABLE `role` (
`role_id` int(11) NOT NULL,
`role_name` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `state`
--

CREATE TABLE `state` (

`state_id` int(11) NOT NULL,
`state_name` varchar(255) NOT NULL,
`state_description` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `type`
--
CREATE TABLE `type` (

Page - 17
 Project Report of Vehicle Management System

`type_id` int(11) NOT NULL,

`type_name` varchar(255) NOT NULL,
`type_description` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `user`
--
CREATE TABLE `user` (
`user_id` int(11) NOT NULL,
`user_level_id` varchar(255) NOT NULL DEFAULT '2',
`user_username` varchar(255) NOT NULL,
`user_password` varchar(255) NOT NULL,
`user_name` varchar(255) NOT NULL,
`user_add1` varchar(255) NOT NULL,
`user_add2` varchar(255) NOT NULL,
`user_city` varchar(255) NOT NULL,
`user_state` varchar(255) NOT NULL,
`user_country` varchar(255) NOT NULL,
`user_email` varchar(255) NOT NULL,
`user_mobile` varchar(255) NOT NULL,
`user_gender` varchar(255) NOT NULL,
`user_dob` varchar(255) NOT NULL,
`user_image` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Table structure for table `vehicle`
--
CREATE TABLE `vehicle` (
`vehicle_id` int(11) NOT NULL,
`vehicle_number` varchar(255) NOT NULL,

Page - 18
 Project Report of Vehicle Management System

`vehicle_type_id` varchar(255) NOT NULL,

`vehicle_driver_id` varchar(255) NOT NULL,
`vehicle_chechis_no` varchar(255) NOT NULL,
`vehicle_company` varchar(255) NOT NULL,
`vehicle_color` varchar(255) NOT NULL,
`vehicle_registration_date` varchar(255) NOT NULL,
`vehicle_image` varchar(255) NOT NULL,
`vehicle_descritpion` text NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

ALTER TABLE `city` ADD PRIMARY KEY (`city_id`);

ALTER TABLE `country` ADD PRIMARY KEY (`country_id`);
ALTER TABLE `driver` ADD PRIMARY KEY (`driver_id`);
ALTER TABLE `fuel` ADD PRIMARY KEY (`fuel_id`);
ALTER TABLE `insurance` ADD PRIMARY KEY (`insurance_id`);
ALTER TABLE `maintanance`ADD PRIMARY KEY (`maintanance_id`);
ALTER TABLE `role` ADD PRIMARY KEY (`role_id`);
ALTER TABLE `state` ADD PRIMARY KEY (`state_id`);
ALTER TABLE `type` ADD PRIMARY KEY (`type_id`);
ALTER TABLE `user` ADD PRIMARY KEY (`user_id`);
ALTER TABLE `vehicle` ADD PRIMARY KEY (`vehicle_id`);

Page - 19
 Project Report of Vehicle Management System

Chapter 4.7:

Application Development Environment and Technology

The Software Requirements Specification is produced at the culmination of the

analysis task. The function and performance allocated to software as part of system
engineering are refined by establishing a complete information description, a detailed
functional and behavioral description, an indication of performance requirements and
design constraints, appropriate validation criteria, and other data pertinent to
requirements.

The proposed system has the following requirements:

 System needs store information about n
 ew entry of Vehicle.
 System needs to help the internal staff to keep information of Driver and find
them as per various queries.
 System need to maintain quantity record.
 System need to keep the record of Insurance.
 System need to update and delete the record.
 System also needs a search area.
It also needs a security system to prevent data.

Name of component Specification

Operating System Windows 98, Windows XP, Windows7,
Linux
Language PHP 2 Runtime Environment
Database MySQL Server
Browser Any of Mozilla, Opera, Chrome etc
Web Server Tomcat 7
Software Development Kit PHP JDK 1.7 or Above
Scripting Language Enable PHP (PHP Server Pages)
Database JDBC Driver MySQL Jconnector

Page - 20
 Project Report of Vehicle Management System

Chapter 4.8:

Implementation Environment and Technology

Hardware Requirements:

Name of component Specification

Processor Pentium III 630MHz
RAM 128 MB
Hard disk 20 GB
Monitor 15” color monitor
Keyboard 122 keys

Page - 21
 Project Report of Vehicle Management System

Chapter 4.9:

Screenshots:

Page - 22
Project Report of Vehicle Management System

Page - 23
Project Report of Vehicle Management System

Page - 24
Project Report of Vehicle Management System

Page - 25
Project Report of Vehicle Management System

Page - 26
Project Report of Vehicle Management System

Page - 27
Project Report of Vehicle Management System

Page - 28
Project Report of Vehicle Management System

Page - 29
Project Report of Vehicle Management System

Page - 30
Project Report of Vehicle Management System

Page - 31
Project Report of Vehicle Management System

Page - 32
Project Report of Vehicle Management System

Page - 33
Project Report of Vehicle Management System

Page - 34
Project Report of Vehicle Management System

Page - 35
Project Report of Vehicle Management System

Page - 36
Project Report of Vehicle Management System

Page - 37
Project Report of Vehicle Management System

Page - 38
Project Report of Vehicle Management System

Page - 39
Project Report of Vehicle Management System

Page - 40
 Project Report of Vehicle Management System

Chapter 6:

Conclusion of the Project Vehicle Management System:

Our project is only a humble venture to satisfy the needs to manage their project
work. Several user friendly coding have also adopted. This package shall prove to be a
powerful package in satisfying all the requirements of the school. The objective of
software planning is to provide a frame work that enables the manger to make
reasonable estimates made within a limited time frame at the beginning of the software
project and should be updated regularly as the project progresses.

At the end it is concluded that we have made effort on following points…

 A description of the background and context of the project and its relation to work
already done in the area.
 Made statement of the aims and objectives of the project.
 The description of Purpose, Scope, and applicability.
 We define the problem on which we are working in the project.
 We describe the requirement Specifications of the system and the actions that
can be done on these things.
 We understand the problem domain and produce a model of the system, which
describes operations that can be performed on the system.
 We included features and operations in detail, including screen layouts.
 We designed user interface and security issues related to system.
Finally the system is implemented and tested according to test cases.

Page - 41
 Project Report of Vehicle Management System

Chapter 7:

Future Scope of the Project:

In a nutshell, it can be summarized that the future scope of the project circles
around maintaining information regarding:

 We can add printer in future.

 We can give more advance software for Vehicle Management System including
more facilities
 We will host the platform on online servers to make it accessible worldwide
 Integrate multiple load balancers to distribute the loads of the system
 Create the master and slave database structure to reduce the overload of the
database queries
 Implement the backup mechanism for taking backup of codebase and database
on regular basis on different servers

The above mentioned points are the enhancements which can be done to increase
the applicability and usage of this project. Here we can maintain the records of Vehicle
and Driver. Also, as it can be seen that now-a-days the players are versatile, i.e. so
there is a scope for introducing a method to maintain the Vehicle Management System.
Enhancements can be done to maintain all the Vehicle, Driver, Insurance, Maintanance,
Fuel.

We have left all the options open so that if there is any other future requirement
in the system by the user for the enhancement of the system then it is possible to
implement them.In the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We hope that the project will serve its
purpose for which it is develop there by underlining success of process.

Page - 42
 Project Report of Vehicle Management System

Chapter 8:
References and Bibliography:
 Google for problem solving
 http://www.PHPworld.com/PHPworld/jw-01-1998/jw-01-Credentialreview.html
 Database Programming with JDBC and PHP by O'Reilly
 Head First PHP 2nd Edition
 http://www.jdbc-tutorial.com/
 PHP and Software Design Concepts by Apress
 https://www.tutorialspoint.com/PHP/
 http://www.PHPtpoint.com/PHP-tutorial
 https://docs.oracle.com/PHPse/tutorial/
 http://www.wampserver.com/en/
 http://www.PHP.net/
 http://www.tutorialspoint.com/mysql/
 httpd.apache.org/docs/2.0/misc/tutorials.html

Page - 43