Vehicle management system

VEHICLE MANAGEMENT SYSTEM 10081A1215
10081A1218
10081A1210
SHADAN COLLEGE OF ENGINEERING & TECHNOLOGY Page 1
ABSTRACT

10081A1218
10081A1210
1:ABSTRACT
Will be able to create new users and change the passwords. He can add or update the
employee information in the company. He can add and view the information of Transport
categories and also available routes. Depending on the users‟ demands, new route and also new
pick up points can be added to the database. It is every company‟s need to see the welfare of its
employees by providing transportation for the employees to attend their duties successfully. This
is the reason many MNC companies maintain their own fleet and sometimes takes the
help of third party transport systems also. When several employees wish to utilize the bus
services provided by the company, naturally the company employees need a system to allot the
buses and oversee the transportation. Corporate Company‟s Vehicle Managementis a software
that quenches this need.
Corporate Company‟s Vehicle Management has four types of users. The administrator of this
software Beyond this, the administrator can also act as a normal user and book a bus or cab for
himself. He has authority to place a cab request or cancel a request for a bus. This system
calculates fare depending on three categories: short distance, medium and long distance and the
fare would be deducted from the employees‟ salaries.
When an employee of the company wants to avail the transportation facility, he will forward a
request which will be approved by the administrator depending on the availability of room in the
bus. When an employee wants a cab, it will be arranged by the approver and later depending on
the recommendation of the project manager the charge may or may not be deducted from the
employee salary.
Approver is another user of this system. He can view the details of transport categories, routes
and pick up points. He can approve a request for a cab from an employee and store the
information of assigned cab.
The transport people can view all the information related to who are the employees utilizing the
transportation. They can take a decision to approve or disapprove the requests placed for
transportation. They can arrange a cab physically for the employee and send the cab details to the
employee who placed the request.

10081A1218
10081A1210
Users and guest users are employees who want to use the transport facility. The users can place
their request for a bus to reach the company or for a cab when they want to go to a different
place. These requests are approved or declined by the transport people or project manager.
This application has rich user interface so that novice users can access easily. This application
provides the management reports like Occupancy report, Approval status report, to track the
usage of company‟s transport facility as well as cab facility.
Technologies used: J2SE, Servlets, JSP, JDBC and Java Script.

10081A1218
10081A1210
REQUIREMENT ANALYSIS

10081A1218
10081A1210
2:REQUIREMENT ANALYSIS
2.1:INTRODUCTION
Vehicle Management System is software which is helpful for bus operators,
who wants to operate many bus trips in a day. Vehicle Management System is a windows
application written for 32-bit Windows operating systems which focused in the area of adding,
editing and deleting the passengers, staff and the bus routes. In this software a person can be
register as a user and he can manage the bus routes and the staff, passengers‟ details. He can add
a bus and its details including bus route details. User can also add the details of the staff and their
duty time in the system.
There are mainly 5 modules in this software
Bus Management
Route Management
Employee Management
Passenger Management
In Bus module a user can add a new bus details to the database. He can set the details of the route
and the timing also. Bus details like the type, engine number, seating capacity and the route in
which the bus is going to be operated are added. Whenever the user wants to modify these details
he can update new values through this software. Route Management module deals with the route
management of the bus. A user can add the route and if he wants he can change it or delete that
route. The main advantage is that this module is helpful for the agents to get details of the route
and the details of the bus which have trip to that route. He can also get the information of the
number of seats available in a particular day.
Employee details of any bus can add to the database and this is helpful to
the bus operators in the case of the salary and bates for the employee. An operator can add the
personal details and if we want to edit or delete he can done modification using the Vehicle
Management System. This is very helpful for the passenger also; if they have any complaint
against staff he can approach the operator and easily identify the employee. Details of every
passenger are stored in the system. A user can add a passenger only one time and if he came
again operator can identify that person. Operator can add, edit and delete the details of the
passenger.It is every company‟s need to see the welfare of its employees by providing
transportation for the employees to attend their duties successfully. This is the reason many
MNC companies maintain their own fleet and sometimes takes the help of third party transport
systems also. When several employees wish to utilize the bus services provided by the company,
naturally the company employees need a system to allot the buses and oversee the transportation.
Corporate Company‟s Vehicle Managementis a software that quenches this need.

10081A1218
10081A1210
Corporate Company‟s Vehicle Management has four types of users. The administrator of this
software will be able to create new users and change the passwords. He can add or update the
employee information in the company. He can add and view the information of Transport
categories and also available routes. Depending on the users‟ demands, new route and also new
pick up points can be added to the database. Beyond this, the administrator can also act as a
normal user and book a bus or cab for himself. He has authority to place a cab request or cancel a
request for a bus. This system calculates fare depending on three categories: short distance,
medium and long distance and the fare would be deducted from the employees‟ salaries.
When an employee of the company wants to avail the transportation facility, he will forward a
request which will be approved by the administrator depending on the availability of room in the
bus. When an employee wants a cab, it will be arranged by the approver and later depending on
the recommendation of the project manager the charge may or may not be deducted from the
employee salary.
Approver is another user of this system. He can view the details of transport categories, routes
and pick up points. He can approve a request for a cab from an employee and store the
information of assigned cab.The transport people can view all the information related to who are
the employees utilizing the transportation. They can take a decision to approve or disapprove the
requests placed for transportation. They can arrange a cab physically for the employee and send
the cab details to the employee who placed the request.
Users and guest users are employees who want to use the transport facility. The users can place
their request for a bus to reach the company or for a cab when they want to go to a different
place. These requests are approved or declined by the transport people or project manager.
This application has rich user interface so that novice users can access easily. This application
provides the management reports like Occupancy report, Approval status report, to track the
usage of company‟s transport facility as well as cab facility
Vehicle Management System is developed and customized for commercial fleet owners and
organizations. Its modules support most type of vehicles (passenger, Truck, construction and
other commercial vehicles). It really reduces your vehicles cost while increasing performance
and dependability
Vehicle Management System uses JAVA as the front end and MS Access as the back end. It
involves four modules, Bus Management, Route Management, Employee Management
& Passenger Management.

10081A1218
10081A1210
In Bus module a user can add a new bus details to the database. This proposed system is very
useful for the operators and passengers. This avoids the overheads for the operators.
Front-end : Java (JDK 1.7 or use Java IDE like Net Beans 6.0)
Back-end : MS Access 2003 or later
FEATURES
ADMIN
View/Edit/Delete Vehicle Details
View/Edit/Delete Driver Details
Fuel Expences/ Oil Change Details
Vehicle Repair History
Booking Status Detail
USER MODULE
Login/Registration of User
Take a Car trip (Google Map Integration)
View Car Details
Car Booking

10081A1218
10081A1210
ORGANIZATION PROFILE:
ABOUT THE COMPANY
Honeypot IT Consulting Private Limited is an internationally established software development
company with offices USA and India. The Indian office and development centre is located in a
state-of-art facility in the heart of Hyderabad; India. Honeypot IT is into software product
development and enterprise consulting services. Honeypot IT service offerings cater to multiple
industry domains and verticals, following full or partial SDLC, optimally customized to cater to
specific client needs. Honey pot also provide human resources for the different areas of a
software development life cycle.
VISION
Honey pot IT Solutions is an interactive and technology solution Provider. We help clients to
plan their online strategy, budget their technology investments, integrate critical applications,
and implement projects that achieve business objectives and improve performance. Since our
inception we have focused on building dynamic, user-focused web sites, intranet's and extranets,
supported by interactive marketing and e-communication campaigns.

10081A1218
10081A1210
MISSION VALUES
Since its inception, Honey pot IT has been governed by its core values. They shape the culture
and define the character of our company. They guide how we behave and make decisions.
CLIENT VALUE CREATION
Improving our clients‟ business performance, creating long-term, win-win relationships and
focusing on execution excellence.
RESPECT FOR THE INDIVIDUAL
Valuing diversity, ensuring an interesting and inclusive environment and treating people as we
would like to be treated ourselves.
INTEGRITY
Inspiring trust by taking responsibility, acting ethically and encouraging honest and open debate.
Honey pot IT Consulting services range from customized software design and development
services to product based enterprise and web application development. Honey pot IT service
offerings cater to multiple industry domains and verticals, following full or partial SDLC,
optimallycustomized to cater to specific client needs.
Honey pot IT service offerings are based on its understanding of clients' business processes and
functional requirements. The business domain knowledge is then applied to develop software
solutions by utilizing the available pool of technical skill sets and proven methodologies.
Honey pot IT offer specialized services in outsourced software development, which allows our
clients to focus on their core competencies, while outsourcing IT requirements to Honey pot IT.

10081A1218
10081A1210
The clients benefit from Honey pot it‟s spectrum of technology tools, quality services and low
cost of development.
List of services
Application Services
Product Engineering
Web Designing & Development
Search Engine Optimization
QA & Testing Service
About the Project:
Problem statement is one of the basic and important phases of project phase. When the
basic problem is determined, it is documented and the symptomatic problem is analyzed, then the
current list of basic problem is completed. A system is simply a set of components that interact to
accomplish some purpose.
Transport Portal is an online software application which fulfills the requirement of a
typical management of details of vehicles, Transport Categories, Routes and the requests for bus
or cab from the employees in a company. It provides the interface to users in a graphical way to
manage the daily transactions. Also provides the management reports like Bus Request details,
Bus occupancy, Cab Request details, Cab Request Status etc.

10081A1218
10081A1210
The aim of this application is to reduce the manual effort needed to manage transactions
in a company. Also this application provides an interface to users to view the details like the
Transport Categories, Vehicle details, Routes, Bus and Cab Requests etc.
Current system is a manual one in which users are maintaining ledgers, books etc to store
the information like vehicles details, routes details, bus requests and approvals etc..
2.2:LITERATURE SURVEY
Purpose
The purpose of the literature survey relating to vehicle utilisation transport optimisation and the
implementation of „green‟ transport management measures within the freight industry with a
view to minimise the negative impact of road freight transport on the environment.
Design/Methodology/Approach
This report first reviews the key constraints on vehicle utilisation, before examining
opportunities to optimise transport operations. Within the remit of this report, three key areas for
improved efficiencies within the industry are identified: logistical efficiency, vehicle utilisation
and driver training and behaviour.
Findings
Environmental issues will increasingly influence the way transport managers do their jobs.
Currently, there is a growing field of governmental literature offering advice and guidance.
Research Limitations/implications
The scope of this review is limited by the availability of literature and time. As a broad study, it
does not present the full range of literature on the state of green transport management, but
attempts to give an overview of the main concerns and areas for improvement. The text and case
studies are illustrative of the previous work done in this field.

10081A1218
10081A1210
Practical implications
This report highlights limitations faced by transport managers in attempting to
operate vehicles efficiently and draws together environmentally-related literature
that offers guidance to transport managers.
Originality/value
As a literature review it aims to synthesise previous work rather than develop new
perspectives. It should provide a foundation for future research in this field.
This literature survey was prepared for the research team of Project
SceneSusTech which was funded by the European Commission‟s Targeted Socio-Economic
Reasearch programme.it is an empirical study of the „vehicle system‟ in four European
Countries(Athens,Bologna,Dublin and Helsinki); funding was for two years from January 1998
to December 1999.The empirical work for the project was delayed and is only now (March 2001)
nearing completion.A full list of published reports from the project is provided in Appendix 2 of
this document.
A draft version of this literature review, written by Dr .Maria Lohan, was submitted
to the European Commission in July 1998.This initial version was also distributed at the time to
the research team..The research team also received a review of some French and Iltalian
literature prepared by the Italian partners and the review of Finnish literature from the Finnish
partners.These separate reviews were the background for the team‟s emperical research.
Offering the greatest flexibility in terms of timings and destinations compared with
other modes, road transport dominants freight distribution in the UK (64.4% of all goods
transported (tonne-kms) in 2005 was carried by road) (Department for Transport, 2006a). In
moving this amount of freight by road, companies use 1 billion litres of fuel and produce 28
million tonnes of CO2 each year (Freight Transport Association, 2003), or approximately 5% of
total CO2 emissions in the UK (McKinnon, 2007). Aside from the direct negative effects of
greenhouse-gas emissions, freight traffic contributes to increased noise levels, congestion and
accidents. Current forecasts suggest that the number of truck-kms will increase by 10-11%
between 2000 and 2010 (Department for Transport, 2006a).
It is against this backdrop of projected growth and associated environmental impacts
that the government has set objectives for improving environmental performance of freight
transport by improving vehicle efficiency, minimising congestion, making better use of road

10081A1218
10081A1210
infrastructure and reducing greenhouse gas emissions (Department for the Environment,
Transport and the Regions, 1999a).
Within this context, the European Commission highlights five main approaches to
the adoption of environmental concerns in freight transport (European
Commission, 2001).
1. Reducing the impact of freight through cleaner, alternative fuels and improved truck design;
2. Driver training and behaviour;
3. Improving vehicle utilisation by increasing load factors, utilising new information
technology, improving routing and collaboration between companies;
4. Switching to more environmentally-friendly modes; &
5. City logistics.
This report considers the first three EC approaches, and will examine the optimisation of
transport, the utilisation of vehicles and associated transport management decisions. The rest of
this report is organised as follows: Section 2 outlines key performance measures associated with
vehicle utilisation; Section 3 highlights constraints on the optimisation of freight transport;
Sections 4-5 considers various efficiency measures aimed at either reducing fuel consumption
or maximising vehicle use and Section 6 draws conclusions and makes
suggestions for future research.
Transport managers have to make quite difficult decisions regarding the loading of
vehicles, owing to the almost exclusively one-directional movement of freight consignments
from point of production to point of consumption. The challenge in the freight industry is to find
backloads for returning vehicles, by making use of spare capacity on the return leg of a delivery
journey (McKinnon & Ge, 2006).
Yet it seems that empty running is inherent in the freight industry (Gorkie, 2006).
Not only does the returning empty vehicle represent a wasted resource in economic terms, but
such a journey is increasingly seen as having an environmental consequence (Department for the
Environment, Transport and the Regions, 1999a). For instance, Table 1 illustrates that empty
running for all goods vehicles in 2005 was 27.4% (Department for Transport, 2006a),
representing 6,103 million kilometres when vehicles were driven unladen, but were contributing
to noise and air pollution, congestion, and health and safety issues. Although fewer in number
than other types of truck, over a third of journeys undertaken by rigids over 25-tonnes are run
empty.

10081A1218
10081A1210
Over the last 30 years in the UK the proportion of empty running by trucks has steadily
declined, with resultant economic and environmental benefits (McKinnon & Ge, 2006); although
in the last couple of years this downward trend has faltered, leaving the question as to whether
stable levels have been reached. Ultimately though, some transport practitioners believe that
empty running will stabilise at around the mid- to low 20s% (McKinnon, 2006, per. comm.).
Within these overall figures there can be wide variations between sectors, even when
different fleets are engaged in similar delivery patterns. Léonardi & Baumgartner (2004) found
that in Germany the container transportation business recorded almost half their truck kilometers
as running empty (48%), whilst in Britain the retail sector tends to have slightly lower than
average empty running of vehicles (McKinnon, 2004). This may possibly be explained by the
sector using „dedicated‟ equipment, such as roll cages that are not necessarily classed as empty
running when returned from supermarkets (Department for Transport, 2003a). Despite being
essential to the retail logistics operation, dedicated equipment could be consolidated into returns
of fewer trips, thereby freeing-up vehicle capacity for other deliveries (Department for the
Environment, Transport and the Regions, 1999b).
Empty-running data collected at the micro-level during one-off studies, tend to be lower than
average annual values (McKinnon et al, 2003; Léonardi & Baumgartner, 2004). The 48-hour
snap-shot of the food supply chain in 2002 found only 19% of journeys were empty running,
although again with wide variations across the sample (Department for Transport, 2003a;
McKinnon et al, 2003).
Causes of empty running are numerous. ECR Europe (2000) list the following:
· Lack of co-operation between shippers and carriers within a region;
· Lack of co-ordination in planning and scheduling;
· Competitive and legal constraints;
· Imbalances in goods flows within and between regions;
· Insufficient visibility of opportunities for building efficient circuits;
· Replenishment practices which inhibit circuit operation (lack of synchronisation of collection
and delivery windows);
· Incompatibility between vehicle characteristics and product requirements
(e.g. need for temperature control).

10081A1218
10081A1210
2.2.1:EXISTING SYSTEM
Current system is a manual one in which employees has to submit their applications for
transport facility as well as for cab facility. Employees has to follow up regularly with transport
personnel to know the status of their requests which is time consuming and hectic.
Disadvantages:
The following are the disadvantages of current system
1. It is difficult to track the occupancy.
2. More manual hours need to generate required reports
3. It is tedious to track the details of cabs provided by third party.
4. There is no possibility to track the approvals of requests.
5. No co-ordination between various departments.
2.2.2:Proposed Systems
Proposed system is a software application which avoids more manual
hours that need to spend in record keeping and generating reports. This application keeps the
data in a centralized way which is available to all the users simultaneously. It is very easy to
manage historical data in database. No specific training is required for the employees to use this
application. They can easily use the tool that decreases manual hours spending for normal things
and hence increases the performance.
Advantages:
The following are the advantages of proposed system
1. Easy to process requests
2. Can generate required reports easily
3. Easy to manage historical data in a secure manner
4. Centralized database helps in avoiding conflicts

10081A1218
10081A1210
5. Easy to use GUI that does not requires specific training.
6. Implementation of approval process is very easy
7. Occupancy tracking helps in decision making.
2.3.SDLC(Software Development Life Cycle) METHODOLOGY
Vehicle management systems have been developed, which is based on conventional database.
However, previous systems cannot efficiently retrieve location data of vehicles, because
conventional databases did not take into consideration about property of moving object data such
as continuously changing location overtime. In this paper, we design the vehicle information
management system that is able to manage and retrieve vehicle locations efficiently in mobile
environment. Our proposed system consists of vehicle information collector, vehicle information
management server, and mobile clients. The system is able to not only process spatiotemporal
queries related to locations of moving vehicles but also provide moving vehicles‟ locations
which are not stored in the system. The system is also able to manage vehicle location data
effectively using a moving object index.
The stricter fuel consumption and emission regulations put the worldwide carmakers
and suppliers under pressure to develop more efficient thermal management systems. High
engine efficiency, increased comfort requirements, and stringent emission regulations are
examples of the political and public conflicting requirements. The coolant system of current
vehicles is already limited on performance due to package and styling constraints. Therefore, any
future incremental demands on the coolant system will need to be managed effectively so as to
remain within these constraints. Simulation-based design and virtual prototyping can insure
greater product performance and quality of both the time and cost required by traditional build-
and-test approach for the development of the vehicle thermal management process and the
development process in general.
The objective of this work is the integration of all partial thermal systems: gas circuit,
cooling circuit, engine oil circuit, engine structure, underhood flow, and passenger compartment.
A vehicle simulation program is used to determine the operating, load conditions of the vehicle,
and steer the data exchange between the different software modules used to simulate the
previously mentioned vehicle partial thermal systems.

10081A1218
10081A1210
The AUTOSAR-standard enables the use of a component based software design model
for the design of a vehicular system. The design model uses application software components
which are linked through an abstract component, named the virtual function bus.
The application software components are the smallest pieces of application software that
still have a certain functionality. The software of an application can then be composed by using
different application software-components. Standardized interfaces for all the application
software components necessary to build the different automotive applications are specified in
the AUTOSAR-standards. By only defining the interfaces, there is still freedom in the way of
obtaining the functionality.
The virtual function bus connects the different software components in the design model. This
abstract component interconnects the different application software components and handles the
information exchange between them. The virtual function bus is the conceptualization of all
hardware and system services offered by the vehicular system. This makes it possible for the
designers to focus on the application instead of the infrastructure software.
By using the virtual function bus, the application software components do not need to know with
which other application software components they communicate. The software components give
their output to the virtual function bus, which guides the information to the input ports of the
software components that need that information. This is possible due to the standardized
interfaces of the software components which specifies the input and output ports as well as the
format of data exchange.

10081A1218
10081A1210
2.4:FEASIBILITY STUDY
Whatever we think need not be feasible .It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the organization
by the development of a system. The impact can be either positive or negative. When the
positives nominate the negatives, then the system is considered feasible. Here the feasibility
study can be performed in two ways such as technical feasibility and Economical Feasibility.
TechnicalFeasibility.
We can strongly says that it is technically feasible, since there will not be much difficulty in
getting required resources for the development and maintaining the system as well. All the
resources needed for the development of the software as well as the maintenance of the
same is available in the organization here we are utilizing the resources which are available
already.
Economical Feasibility
Development of this application is highly economically feasible .The organization needed
not spend much m money for the development of t he system already available. The only
thing is to be done is making an environment for the development with an effective
supervision. I f we are doing so , we can attain the maximum usability of the corresponding
resources .Even after the development , the organization will not be in a condition to invest
more in t he organization.There fore , the system is economically feasible.

10081A1218
10081A1210
SYSTEM ANALYSIS

10081A1218
10081A1210
3:SYSTEM ANALYSIS
3.1:USER REQUIREMENT SPECIFICATIONS
The User Requirements Specification describes the business needs for what users
require from the system. User Requirements Specifications are written early in the validation
process, typically before the system is created. They are written by the system owner and end-
users, with input from Quality Assurance. Requirements outlined in the URS are usually tested in
the Performance Qualification or User Acceptance Testing. User Requirements Specifications
are not intended to be a technical document; readers with only a general knowledge of the system
should be able to understand the requirements outlined in the URS.
User Requirements Examples
Good requirements are objective and testable. For example:
Screen A accepts production information, including Lot, Product Number, and Date.
System B produces the Lab Summary Report.
Twenty users can use System C concurrently without noticeable system delays.
Screen D can print on-screen data to the printer.
System E will be compliant with 21 CFR 11.
The URS should include:
Introduction – including the scope of the system, key objectives for the project, and
the applicable regulatory concerns
Program Requirements – the functions and workflow that the system must be able
to perform
Data Requirements – the type of information that a system must be able to process
Life Cycle Requirements – including how the system will be maintain users
requirement.

10081A1218
10081A1210
3.1.1:FUNCTIONAL REUIREMENTS
APPLICATION DESIGN
USERS:
The major functionality of this product is divided into four categories.
1. Administrative User Functions.
2. Approvers Functions.
3. Transport Functions.
4. Guest Functions.
In this application each and every user must having their own User ID and Password,
using these User ID and Password only they can directly enter into their corresponding Login
forms.
1) Administrative User Functions:
In this functionality the administrator will do his own responsibilities. Whenever he
needs to change the Password, then he can directly change it. If any reason he needs to add a new
user he can directly add. The admin user can view the details of all the users and he can add or
remove any particular users. He can view the details of all the employees of the company and
any time he can add or remove any particular employee or employees. This application mainly
concentrated about the transport. The admin user can view the details of all the categories of the
transport. This categories viewing list has shows the ID Number of the category, category code,
how much amount per month, and how much distance allotted for the particular category, all
these information will be provided. The admin user can add and remove any particular category.
The admin user can view the details of all the vehicles details which are presently using in the
particular company. In this list also each and every vehicle has its own identification number,
registration number of the particular vehicle, and the type of the vehicle either it is own or hire.
The administrator can add the vehicle depends upon the situation of the company. The admin
user can view the details of all the routes. In this routes module the admin user can view the
route code, route ID, destination, bus no, and also he can view the pickup points of the particular

10081A1218
10081A1210
route. He can add or remove the pickup points of the route. He can add or remove the routes. He
can view the details of all the bus requests which are posted from the employees. If he needs the
transport facility, then he can also apply the bus request. He can add or remove the bus requests.
He can view the details of all the cab requests of the employees. He can also add or remove the
cab requests of the employees. The admin user can view the details of all the users and he can
add a new user. He can view or generate all the management reports.
2) Approvers Functions:
In this function, the Approver can enter into his functionality using his own User ID and
Password. After entering into his functionality, whenever he needs to change his password then
he can directly change it. The approver‟s user can view the details of all the users and employees
of the particular company. This application mainly concentrated about the transport. The
approver‟s user can view the details of all the categories of the transport. This categories viewing
list has shows the ID Number of the category, category code, how much amount per month, and
how much distance allotted for the particular category, all these information will be provided. He
can view the details of all the vehicles. In this list contains the Identification number of the
particular vehicle, registration number of the vehicle and the type of the vehicle means it is for
hire or own, this type of information will included in this list. The approver‟s user can view the
details of all the routes and their destination, location, route id, route code all these details will
displayed in this list. The approver‟s user can view the details of all the bus requests which are
posted from the employees of the company. He can add or remove the particular bus requests. He
can view the details of all the cab requests. He can add or remove the cab requests. Mainly the
approver‟s user can approve the cab requests which are posted from the employees of the
company. He can view the all types of the reports.

10081A1218
10081A1210
3) Transport Functions:
In this function, the Transport user can enter into his functionality using his own User ID
and Password. After entering into his functionality, whenever he needs to change his password
then he can directly change it. The Manager can view the details of all the users and the
employees of the company. He can view the details of all the categories of the transport. The
transport user can view the details of all the vehicles. He can view the details of all the routes.
The transport user can view the details of all the bus requests which are posted from the
employees of the company. After his careful verification only he can provide the transport
facility to the requested employee. He can add or remove the request of the employee.
4) Guest Functions:
In this function, the Accountants can enter into his functionality using his own User ID
and Password. After entering into his functionality, whenever he needs to change his password
then he can directly change it. Here the Guest user means any of the employee can login into the
user functionality. He can view the details of all the users and employees of the company. This
application mainly concentrated about the transport. The guest user can view the details of all the
categories of the transport. This categories viewing list has shows the ID Number of the
category, category code, how much amount per month, and how much distance allotted for the
particular category, all these information will be provided. He can view the details of all the
vehicles. In this list contains the Identification number of the particular vehicle, registration
number of the vehicle and the type of the vehicle means it is for hire or own, this type of
information will included in this list. The guest user can view the details of all the routes and
their destination, location, route id, route code all these details will displayed in this list. The
guest user can view the details of all the bus requests which are posted from the employees of the
company. Also he can add or remove the bus requests for his own. He can view the details of all
the cab requests. Also he can add or remove the cab requests for his own. He can view all types
of management reports.

10081A1218
10081A1210
3.1.2:NON FUNCTIONAL REQUIREMENTS
Nonfunctional requirements are the properties that your product must have. Think of
these properties as the characteristics or qualities that make the product attractive, or usable, or
fast, or reliable. These properties are not required because they are fundamental activities of the
product -- activities such as computations, manipulating data, and so on -- but are there because
the client wants the fundamental activities to perform in a certain manner. They are not part of
the fundamental reason for the product's existence, but are needed to make the product perform
in the desired manner.
Nonfunctional requirements do not alter the product functionality. That is, the
functional requirements remain the same no matter what properties you attach to them. The non-
functional requirements add functionality to the product -- it takes some amount of pressing to
make a product easy to use, or secure, or interactive. However the reason that this functionality is
part of the product is to give it the desired characteristics. So you might think of the functional
requirements as those that do the work, and the nonfunctional requirements as those that give
character to the work.
Nonfunctional requirements make up a significant part of the specification. They are important
as the client and user may well judge the product on its non-functional properties. Provided the
product meets its required amount of functionality, the nonfunctional properties -- how usable,
convenient, inviting and secure it is -- may be the difference between an accepted, well-liked
product, and an unused one.
Let's take a look at another real example. Anyone who has purchased a car, whether they were
aware of it or not, made their final decision based on which car met both their functional and
nonfunctional needs. Functionally, the car had to be able to transport passengers from some
starting location to a particular destination (that is, get me from point A to point B). A variety of
nonfunctional attributes or characteristics were likely considered: security and safety,
maintainability (ease of repair), reliability (probability of failure), scalability (ease of expansion),
efficiency and performance (gas mileage, engine size, capacity -- both in number of passengers
and cargo space), portability (ease of transport -- can it be towed easily or can it tow a trailer),
flexibility (ease of change -- can it adapt to changes in weather/road conditions), and usability
(ease of use -- comfort, handling, stereo sound quality)

10081A1218
10081A1210
3.1.3:DOMAIN REUIREMENTS
Requirements can cause substantial problems in large software projects if
not handled correctly and efficiently. The problems of missing requirements or incorrect de-
scoping of projects are virtually the most prominent ones.
Combining graphical representation of requirements and organizing these requirements in
several abstraction levels was identified as one of the potential solutions to such issues in our
research project conducted with one of major automotive companies in Sweden. The objective of
the research reported in this paper is to improve requirements engineering activities by using a
graphical modelling language for managing requirements based on Requirement.
Abstraction Model (RAM). We evaluated our results via a pilot controlled experiment and the
results show a statistically significant improvement in the time required to assess the impact of
changes by 37% with the same accuracy.
Domain requirements reflect the environment in which the system
operates so, when we talk about an application domain we mean environments such as train
operation, medical records, e-commerce etc.
Domain requirements may be expressed using specialised domain terminology or reference to
domain concepts. Because these requirements are specialised, software engineers often find it
difficult to understand how they are related to other system requirements.
Domain requirements are important because they often reflect fundamentals of the application
domain. If these requirements are not satisfied, it may be impossible to make the system work
satisfactorily. For example, the requirements for the insulin pump system that delivers insulin on
demand include the following domain requirement:
The system safety shall be assured according to standard IEC 60601-1:Medical Electrical
Equipment – Part 1:General Requirements for Basic Safety and Essential Performance.
This requirement means that the developers must be familiar with that standard to ensure that
they do not violate it. It constrains both the design of the device and the development process.
Other requirements have to be checked against this standard.
Sometimes, characteristics of the application domain mean that the requirements specification
has to include a description of how to carry out some computations. For example, the domain
requirement below is included in the requirements specification for an automated train protection
system. This system automatically stops a train if it goes through a red signal. This requirement

10081A1218
10081A1210
3.2:SYSTEM REUIREMENT SPECIFICATION
Should describe functional and non-functional requirements so that they are
understandable by system users who don‟t have detailed technical knowledge.
User requirements are defined using natural language,tables and diagrams.
3.2.1:Software Requirement Specification
Programming Languages : Java (jdk1.5).
Web Technologies : Html, JavaScript.
Database : Mysql
Server : Tomcat Apache 5.0
3.2.2:Hardware Requirements Specification
Processor : PIII
Hard Disk : 40 GB
Ram : 256 mb

10081A1218
10081A1210
3.3:Technical Design Documentation
Efficacy of Documentation
Documentation is used here to mean hard copy, online documents, online help, quick start
guides, and other written instructional information. The need for documentation is often an
afterthought when designing products. Product development engineers are so enmeshed in
creating the product that they feel its use is "intuitive" or self-evident. This assumption is usually
not the case. In many respects, documentation compensates for the lack of intuition. It permits
understanding the product and provides a quick source for looking up specific details that are not
immediately obvious to the user.
But all documentation is not created equally. It is important to offer the information that is
needed by the user rather than focusing on the product and covering each function without regard
to the user. So a user-centric approach is necessary to create effective documentation. This is not
much different from an Instructional Design process where the purpose is to train the user.
The importance of good documentation in all its forms should not be underestimated. Great
technological innovation can be a bust in the marketplace if end-users feel it is too hard to learn,
not easy to use, or too cumbersome. Good documentation can make a product easy to understand
and use which results in greater user acceptance.
Our Role
Usernomics' Instructional Psychologists apply Instructional System Design (ISD) techniques to
develop Documentation for hardware and software. We develop documentation for a wide range
of products from high tech to consumer products to aircraft.

10081A1218
10081A1210
SYSTEM DESIGN

10081A1218
10081A1210
4:SYSTEM DESIGN
4.1:ARCHITECTURE
Home
Add New Category
Add New Vehicle
View Route
Bus,Cab Requests
Bus,Cab Approvals
Reports
Log out
admin

10081A1218
10081A1210
4.2Module Description
The System after careful analysis has been identified to present with the following
modules.
EMPLOYEE INFORMATION & VEHICLES MODULE: This module maintains
all the information, which belongs to the employees who are working with the company. This
module maintains the details of all the four types of users. This module separately maintains the
information of different departments. This can be maintaining Admin, Approvers, Transport and
Guest users. All the employees‟ details are recorded to database and can be viewed as a report. :
This module deals with major and crucial part that includes the details of the vehicles in the
company. This module provides the interface to add the vehicles and can be viewed as a report
that displays all the details of the vehicles and it can also shows the different types of vehicles
available in the company. Basically some categories of the vehicles are available in the company.
For every user the vehicle details module has divided into two parts. i.e., one is the Add New
Vehicle and the other one is View the Vehicle details. Each and every vehicle has its own
Identification number and the registration numbers. Only Admin user can add the new vehicle to
transport. Any of the remaining users can‟t add the vehicles. All the four types of users can view
the details of all the vehicles. All the added vehicles details will be stored in the database.

10081A1218
10081A1210
TRANSPORT CATEGORIES & ROUTES MODULE: This module deals with
major and crucial part that includes the details of transport in the company. For every user the
Transport Categories Module has divided into three parts. i.e.,
a) Add New Category b) View Categories and
c) Cancel Category. But according their personal responsibilities only they can use
functionalities of the Transport Categories Module. Only Admin user can add the category of
the transport. Because he can deal the transport department. Also the Admin user only the
person to remove the category of the transport in the corresponding situation. But all the four
types of users‟ means admin, transport, approver and the guest users can view the details of
all the categories of the transport. This application mainly concentrated about the transport.
All the four types of users can view the details of all the categories of the transport. This
categories viewing list has shows the ID Number of the category, category code, how much
amount per month, and how much distance allotted for the particular category, all these
information will be provided. This module deals with major and crucial part that includes the
details of the routes in company. This module provides the interface to add the route and can
be viewed as a report that displays all the details of the routes and it can also shows the
different types of routes. For every user the routes modules has divided into three parts. i.e.,
Add New Route, the second one View the Routes and the final one is remove the Route. In
this module the identification of the route and the code of the routes are provided for the each
route. And also the destination and location of the route, Inbound and outbound times all
these information will be provided in this module. The main flexibility in this module is
Pickup Points. For every route so many pickup points are available. Depending upon the
capacity of the vehicle the user can add or remove the pickup points. The user can directly
view the details of the pickup points just clicking on the button “view” which is highlighted
in the screen. Only the admin user can add or remove the corresponding routes. All the four
types of users i.e., Admin, Approver, Transport and the Guest users can view the details of
all the routes. All the routes information will be stored in the database.

10081A1218
10081A1210
BUS REQUESTS & CAB REQUESTS MODULE: This module deals with major
and crucial part that includes Bus Requests of the employees and updates the status as
approved or not. This module provides the interface to Bus Request of the employee and can
be viewed as a report that displays all the Bus Requests of the employees in the company.
For every user the Bus Requests Module has divided into three parts. One Add New Bus
Request, View the details of Bus Requests and the final one Cancel the Bus Requests. In this
module, we will first enter the number of the employee who is posted the request for the bus.
Then it will show the details of employees who is applied for the transport facility. All the
four types of users i.e., Admin, Approver, Transport and the Guest users can add or remove
the Bus Requests for their own and also they can view the details of all the bus requests. This
requests will be finally approved by the transport user. This information will be stored in the
database. This module deals with major and crucial part that includes Cab Requests of the
employees and updates the status as approved or not. This module provides the interface to
Cab Requests of the employees and can be viewed as a report that displays all the Cab
Requests of the employees in the company. For every user the Cab Requests Module has
divided into four parts. i.e., Add New Cab Request, View Cab Requests, Assign Cab, and the
final one Cancel the Cab Requests. We will first enter the details of the employee who is
posted the request for the cab. Then it will show the details of the employees. Only the
transport user can assign the cab for the employee. Whether employees has really needs the
cab or not, this information will be checkout the by the approver user. He has really needs the
cab then the approver user will approve his request then the transport user will decide to
assign the cab for the employee or not. All the four types of users can add or remove the Cab
Requests for their own and also they can view the details of all the cab requests. This
information will be stored in the database.

10081A1218
10081A1210
APPROVALS MODULE: This module deals with major and crucial part that includes
Approvals of Bus Requests and the Cab Requests of the employees and update the status.
This module provides the interface to Approvals of the Bus Requests and the Cab Requests
of the employees and can be viewed as a report that displays all the approvals. For every user
the Approvals Module has divided into two parts. One is Bus Request and the another one is
Cab Request. Only the Approver can approve the Cab Requests. He can‟t approve the Bus
Requests. And only the Transport user can approve the Bus Requests. Remaining users
means Admin and the Guest users can‟t use Approvals Module. All this information will be
finally stored into the database.
ADMINISTRATOR & REPORTING MODULE: This module is used to maintain
the details of users of the project. Users are divided into four categories.
a. Admin
b. Approvers
c. Transport
d. Guest
All the four types of users details will be displayed in this module. Only the administrator
can have wrights to add or delete the users from the users list. If at all the administrator wants
to add one more user, then he can add. Remaining users can‟t do this type works. All the
admin user works, features will be provided in this module. The works and features of the
transport, approver and the guest users will be displayed in this module. All the four user‟s
can view the total reports of this application.

10081A1218
10081A1210
4.3:Data Flow Model
Corporate Company's
Vehicle Management
Administrator &
Reporting module
Employee
Information
& Vehicles
Module
Bus requests
and Cab
requests
module
Approvals
module
Transport
categories and
routes module
Database

10081A1218
10081A1210
4.4:UML DIAGRAM
USE CASE DIAGRAM
Home
ViewCategory
ViewVehicle
Add,View,Cancel Route
add,View,Cancel,AssignBus,Cab
Requests
Bus Approvals
Reports
Log out
Transport

10081A1218
10081A1210
Class Diagram

10081A1218
10081A1210
Sequence Diagram
User login categories Vehicle Details Route Bus,Cab
Requests
Approvals Reports Logout
1: Register( )
2: login
3: View Categories
4: View Vehicle Details
5: View Route
6: Add,View,Cancel Cab Requests
7: No Approval For User
8: View Reports
9: logout from project

10081A1218
10081A1210
SOURCE CODE

10081A1218
10081A1210
5:SOURCE CODE
Java Script
<html>
<head>
My first JavaScript
</head>
<body>
<br>
This is a normal HTML document
<br>
<script language=”JavaScript”>
Document.write (“this is a java script”)
</script>
<b r>
Backing HTML again
</body>
</html>

10081A1218
10081A1210
Functions
<html>
<head>
<script language=”JavaScript”>
function pushbutton ()
{
alert (“Hello!”);
}
</script>
</head>
<body>
<form>
<input type=”button” name=”Button1” value=”push me” onclick=”pushbutton ()”>
</form>
</body>
</html>

10081A1218
10081A1210
TESTING

10081A1218
10081A1210
6:TESTING
SOFTWARE TESTING
Software Testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding, Testing presents an interesting anomaly for the
software engineer.
Testing Objectives include:
1. Testing is a process of executing a program with the intent of finding an error
2. A good test case is one that has a probability of finding an as yet undiscovered error
3. A successful test is one that uncovers an undiscovered error
Testing Principles:
All tests should be traceable to end user requirements
Tests should be planned long before testing begins
Testing should begin on a small scale and progress towards testing in large
Exhaustive testing is not possible
To be most effective testing should be conducted by a independent third party

10081A1218
10081A1210
6.1:TYPES OF TESTING
SOFTWARE TESTING
Is the menu bar displayed in the appropriate contested some system related features
included either in menus or tools? Do pull –Down menu operation and Tool-bars work properly?
Are all menu function and pull down sub function properly listed ?; Is it possible to invoke each
menu function using a logical assumptions that if all parts of the system are correct, the goal will
be successfully achieved .? In adequate testing or non-testing will leads to errors that may appear
few months later.
This create two problem,
1. Time delay between the cause and appearance of the problem.
2. The effect of the system errors on files and records within the system
The purpose of the system testing is to consider all the likely variations to which it will be
suggested and push the systems to limits. The testing process focuses on the logical intervals of
the software ensuring that all statements have been tested and on functional interval is
conducting tests to uncover errors and ensure that defined input will produce actual results that
agree with the required results.
Program level testing, modules level testing integrated and carried out.
There are two major type of testing they are
1) White Box Testing.
2) Black Box Testing.

10081A1218
10081A1210
6.2:LEVELS OF TESTING
WHITE BOX TESTING
White box some times called “Glass box testing” is a test case design uses the control structure
of the procedural design to drive test case.
Using white box testing methods, the following tests where made on the system
a) All independent paths within a module have been exercised once. In our system, ensuring
that case was selected and executed checked all case structures. The bugs that were
prevailing in some part of the code where fixed
b) All logical decisions were checked for the truth and falsity of the values.
BLACK BOX TESTING
Black box testing focuses on the functional requirements of the software. This is black
box testing enables the software engineering to derive a set of input conditions that will fully
exercise all functional requirements for a program. Black box testing is not an alternative to
white box testing rather it is complementary approach that is likely to uncover a different
class of errors that white box methods like..
1) Interface errors
2) Performance in data structure
3) Performance errors
4) Initializing and termination errors

10081A1218
10081A1210
6.3:TESTING METHODOLOGIES
TESTING STRATEGIES
A Strategy for software testing integrates software test cases into a series of well planned
steps that result in the successful construction of software. Software testing is a broader topic for
what is referred to as Verification and Validation. Verification refers to the set of activities that
ensure that the software correctly implements a specific function. Validation refers he set of
activities that ensure that the software that has been built is traceable to customer‟s requirements
Unit Testing:
Unit testing focuses verification effort on the smallest unit of software design that is the
module. Using procedural design description as a guide, important control paths are tested to
uncover errors within the boundaries of the module. The unit test is normally white box testing
oriented and the step can be conducted in parallel for multiple modules.
Integration Testing:
Integration testing is a systematic technique for constructing the program structure,
while conducting test to uncover errors associated with the interface. The objective is to take unit
tested methods and build a program structure that has been dictated by design.
Top-down Integration:
Top down integrations is an incremental approach for construction of program structure.
Modules are integrated by moving downward through the control hierarchy, beginning with the
main control program

10081A1218
10081A1210
Bottom-up Integration:
This method as the name suggests, begins construction and testing with atomic
modules i.e., modules at the lowest level. Because the modules are integrated in the bottom up
manner the processing required for the modules subordinate to a given level is always available
and the need for stubs is eliminated.
Validation Testing:
At the end of integration testing software is completely assembled as a package.
Validation testing is the next stage, which can be defined as successful when the software
functions in the manner reasonably expected by the customer. Reasonable expectations are those
defined in the software requirements specifications. Information contained in those sections
form a basis for validation testing approach.
System Testing:
System testing is actually a series of different tests whose primary purpose is to fully
exercise the computer-based system. Although each test has a different purpose, all work to
verify that all system elements have been properly integrated to perform allocated functions.
Security Testing:
Attempts to verify the protection mechanisms built into the system.
Performance Testing:
This method is designed to test runtime performance of software within the context of an
integrated system.

10081A1218
10081A1210
SCREENS

10081A1218
10081A1210
8.SCREENS

10081A1218
10081A1210

10081A1218
10081A1210
CONCLUSION

10081A1218
10081A1210
9.CONCLUSION
The Corporate Company's Vehicle Management application has rich user interface so that
novice users can access easily. This application provides the management reports like
Occupancy report, Approval status report, to track the usage of company‟s transport facility.
Our project is only a humble venture to satisfy the needs in a library.
Several user friendly coding have also adopted. This package shall prove to be a powerful
package in satisfying all the requirements of the organization.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. Last but not least it is no the work that played the ways to success but
ALMIGHTY.

10081A1218
10081A1210
REFERENCES

10081A1218
10081A1210
10.REFERENCES
References for the Project Development were taken from the following Books and Web Sites.
Oracle:
PL/SQL Programming by Scott Urman
SQL complete reference by Livion
JAVA Technologies:
JAVA Complete Reference
Java Script Programming by Yehuda Shiran
Mastering JAVA Security
Head First EJB Sierra Bates
J2EE Professional by Shadab siddiqui
JAVA Server pages by Nick Todd
HTML:
HTML Black Book by Holzner
JDBC:
Java Database Programming with JDBC by Patel moss.
Software Engineering by Roger Pressman

Vehicle management system

More Related Content

What's hot

Viewers also liked

Similar to Vehicle management system

Recently uploaded

Vehicle management system