A

Project Synopsis
On
Vehical Information System
At
DUCAT Institute of Training Noida

Submitted in partial fulfillment of requirement of Bachelor of

Technology in Computer Science Engineering

Submitted By:
ASHISH KUMAR
B.Tech 4th year
Computer science Engg.
ROLL NO-1664910006
ID windashish1566@gmail.com

Department of Computer Science

M.G INSTITUTE OF
MANAGEMENT & TECNOLOGY COLLEGE
APPROVED BY AICTE ,NEW DELHI MINISTRYOF HRD AFFILIATED TO AKTU
Objective of Project
The project is desired to meet the following objectives:
 The objective of this web application is to completely automate
the process of Vehicle information.
 Provide the same level of services to user, as we would expect for
ourselves.
 This web application is basically use to provide the various
informations related to the vehicle.
 This web application is a combination of various services which
are user usually needed.
 This digitalized system is better than the manual system.
 Provide excellent and easy to access means of communication
medium between Customer and various service provider.
 Only the related service provider has the authority to view their
related data.
 User can send information through mail and query to each other.
 To store and maintain the information about the process of
organization.
 Provides the facility to maintain profile and inbox of each
employee separately.
 Scope of Project
1. Easy in accessing.
2. Fast services.
3. Provide many more links which are very helpful to user.
4. Provide updated information.

Resource(Software & Hardware) to be

used

Software Requirement:

Server

Browser : IE 8.0, Firefox 4, Chrome 18 or above

Database : Oracle
Web server : Apache Tomcat (7.059)
Operating System : Windows

Client

Browser : IE 8.0, Firefox 4, Chrome 18 or above

Operating System : Any O.S. Windows/Linux/Solaris

Developer

Browser : IE 8.0, Firefox 4, Chrome 18 or above

IDE : Eclipse JUNO
Database : MS SQL Server 2012
Operating System : Windows 8.1
Web server : Apache Tomcat (7.059)
Documentation tool : MS-Word, MS-PowerPoint
Designing tool : Dreamweaver
Scripting language : JavaScript, jQuery

Hardware Specification:
Server:

Processor : 1 .6 (GHz) Pentium processor

RAM : 1 GB
HDD : 80GB
Display : 1024 x 768 High color-32-bit

Client:

Processor : P3 866 MHz or later

RAM : 512 MB
HDD : 40GB
Display : 1024 x 768 High color-32-bit SOFTWARE

Developer:

Processor : 1 .6 (GHz) Pentium processor

RAM : 1 GB
HDD : 40GB
Display : 1024 x 768 High color-32-bit SOFTWARE
 Gantt chart
The Gantt chart showing the software development plan is
shown below:

Requirement
Gathering

SRS Completion

Design

Coding

Test Cases

Testing

Implementation

February
January March April May June

Time Duration of Milestones

the Activity
 Project Team Member
Admin
In admin module the whole project team is contributed. Because admin
module is the main and first module of the project. In admin module
there is lot of sub modules which relates to every main module of the
project.

Customer
In vehicle information system, the “Customer” is the second module.
This module is handling by one of the team member name “Ashish
kumar”.

Police and RTO

In vehicle information system, the “Police and RTO” is the third and
fourth module. This module is handling by one of the team member
name “Ashish kumar”.

Finance and insurance

In vehicle information system, the “Finance and Insurance” is the fifth
and sixth module. This module is handling by one of the team member
name “Ashish kumar”.
Workshop

In vehicle information system, the ”Workshop” is the last module. This

module is handling by one of the team member name “Ashish kumar”.
 Process Description:

In the above diagram the modules of the Vehicle Information System

has been shown. In which the arrows are showing the flow of
submit/getting information with the different different modules. The
purpose of the proposed system is that to gathering all the vehicle related
services available for the customer. This system is going to be managed
by the admin means that all the updated information related module are
accessed by the admin. Here the customer will submit the related
information to this system.
At here when the customer is registered his/her self can submit
information related to services to service provider and get quick
response.

Detailed Description of the modules

Admin
Admin will add the customer and provide all the information and he/she
will add service related information like add vehicle, add parts, add
insurance, add finance and managing all the modules. The admin can
also view all information and make updation related to modules. Like
view parts which is workshop related information and also view all the
employee and customer details by the work ID and customer ID. These
are the responsibilities which are going to play by the admin.

Customer
In the customer module, first the customer will register his/her self in the
system by entering the personal information. In customer home page all
the links are available for the related services. Like Insurance, Police,
RTO, Vehicle, etc. The mailing facility is also available in customer
page for send and receiving the mails from the related services provider.
Police and RTO
These modules are totally related with customer module. In police
module there are various sub modules like theft complaints, theft status,
report generation.
Like when the customer mails to police for registering a complaint for
vehicle theft. And then the police will send a reference ID of the
complaint to the customer through mail.
And, In the RTO module the customer can send request related to
vehicle. Like transferring of vehicle, renewal request of vehicle and after
this a valid report will be generated by the RTO authority sends it to the
customer through mail.
Finance and Insurance
These are the precious service used by the customer so, admin will add
particular service provider in the system. If a customer want to use
finance service for purchasing a new vehicle and for purchasing part of
vehicle he/she can contact with authorized finance providers then the
related reference ID will be send to the customer.
In insurance service the customer can make the request to insurance
provider for making their vehicle insurance. Like new insurance,
renewal and also for claims and further communication will be makes by
various sub modules.
Workshop
In the workshop module the customer can take the instance
facilities.Like vehicle servicing, can view the availability of needed
parts, can also search for parts. Here the mail facility is also available for
further communication. The related workshop also provides the online
payment service which is totally secure.
 Acknowledgement
This is to certify that SRS entitled “Vehicle Information System” which is
submitted by me in partial fulfillment of the requirement for the award
of degree B.Tech to MGIMT College Lucknow (APJAKTU, Lucknow-U.P.)
comprises only my own work and due acknowledgement has been
made in the text to all other material used.
Date: Name of Student:
Ashish Kumar

Approved By:
HOD
Department of Computer Science
MGIMT College Lucknow
 Certificate

This is to certify that SRS entitled “Vehicle Information System” which is

submitted by Ashish Kumar in partial fulfillment of the requirement for
the award of degree B. Tech to MGIMT College Lucknow (APJAKTU,
Lucknow-U.P.) is a record of the candidate’s own work carried out by
him under my supervision. The matter embodied in this SRS is original
and has not been submitted for the award of any other degree.

Date: Supervisor Name & Signature:

 Table of Contents
Acknowledgement
Certificate of Originality

1. Introduction
5
1.1. Purpose
1.2. Scope
1.3. Definitions, Acronyms, and Abbreviations 6
1.4. References
6
2. The Overall Description 7
2.1 Product Perspective 7
2.2 Product Functions 8
2.3 User Characteristics 8
3. Specific Requirements 9
3.1 System Requirements 9
3.1.1 Software Requirements
3.1.2 Hardware Requirements
3.2 Software System Attributes 10
3.2.1 Power and Flexibility
3.2.2 Manageability
3.2.3 Scalability and Availability
3.2.4 Security
3.3 List of Diagrams 13
3.3.1 DFD
3.3.2 Use Case Diagram
3.3.3 Sequence Diagram
1. Introduction
This system “Vehicle Information System” allows providing information
and service for vehicles. If customer got any problem with his vehicle
based on guarantee card, they are providing services.
The real power of this project lies not in direct selling of
products, but in the creation of tighter relationships with customers
and delivering of a high level of service and support, which in turn
improves organization sales and its goodwill. A service organization is a
business entity that takes care of servicing a customer vehicle in the
after sales domain. As the number of customers and size of operations
increases, the organization divides the geographical area into service
areas and branch locations, to allow Engineers to be more responsive
to the customer-needs.
1.1 Purpose
The “Vehicle Information System” will benefit us in many particulars to
ease the process flow through paperless and well-organized system.
This VIS system will be developed as a web-based system is used to
make easy for keeping the records and user can also get information
about their vehicle related to RTO, insurance, workshop, finance etc.
upon request or on subscription.
Consequently, this system will help and make easy the user specifically
the staff who in charge in managing the vehicles record. This system
will facilitate the staff in keeping all the vehicles information. Besides
that, this system also is proposed to build up the complete vehicle
database providing every solution relating vehicle and road.
1.2 Scope
 To developing a web-based system where the user can search for
additional information of the vehicles on services and other related
information.
 To register and keep the information about all vehicles.
 To build up a system that provides and generate the summary or
report from the database records in order to get the whole view
about the vehicles.
 To keep the record of many of the activities of vehicles.
1.3 Definitions, Acronyms, and Abbreviations
 VIS (Vehicle Information system) The proposed system which gives
information related to the vehicles.  JDK (Java Development Kit) The
JDK is a software development environment used for developing Java
applications and applets.  JSP (Java Server Pages) JSP is a technology
that helps software developers create dynamically generated web
pages based on HTML, XML, or other document types.  HTML
(Hypertext Markup Language) HTML, a standardized system for tagging
text files to achieve font, color, graphic, and hyperlink effects on World
Wide Web pages.  CSS (Cascading Style Sheets) CSS is a style sheet
language used for describing the presentation of a document written in
a markup language.  RTO (Regional Transport Office) RTO is an Indian
government bureau which is responsible for the registration of vehicles
and the issue of Driver's Licenses in India.
1.4 References
www.google.com Google Search Engine
www.javatpoint.com Java tutorials
www.wikipedia.com Information’s
 2. The Overall Description
More than two –third of automotive customers indicate that Service
Convenience is a determining in selecting a brand or purchasing from a
Specific dealership. Consequently, Customer Service and service
information is of vital relevance to ensure ongoing Customer loyalty
and retention and ultimately, dealer Profitability.
This system allows providing information and service for vehicles. If
customer got any problem with his vehicle based on guarantee card,
they are providing services.
The real power of this project lies not in direct selling of products, but
in the creation of tighter relationships with customers and delivering of
a high level of service and support, which in turn improves organization
sales and its goodwill. A service organization is a business entity that
takes care of servicing a customer vehicle in the after sales domain. As
the number of customers and size of operations increases, the
organization divides the geographical area into service areas and
branch locations, to allow Engineers to be more responsive to the
customer-needs.
Dealer Business Management enables efficient Service and information
Processing and for any given number of orders per day .it includes
Service requests and Scheduling ,Optimization of technicians, tools and
parts as well as their deployment and scheduling .User friendly
interfaces provides ease of use and the integration technology ensure a
seamless and smooth business process into channel System, including
RTO, Finance, Insurance etc. Service monitoring and analysis increases
the Visibility in Overall fixed Operations and helps increases service
Capacity utilization, efficiency and decreased operating cost.
Recreation Vehicle service technician inspect, test, service, and replace
every system installed in a recreation Vehicle with the exception of the
dry.
Both intervals are equally important for properly marinating your
Vehicle Remember all Toyota dealerships offer a broad range of Parts
and Service.
2.1 Product Perspective
The Vehicle Information System is a software application which avoids
more manual hours that need to spend in getting any information
related to your vehicle. This application keeps the information in a
centralized way which is available to all the users simultaneously. It is
very easy to manage all the information in database. No specific
training is required for the distributors to use this application. They can
easily use the tool that decreases manual hours spending for normal
things and hence increases the performance. It is very easy to record
the information of online requests and responses in the databases.
The objective of the Vehicle information System is to provide better
information for the users of this system for better results for servicing
regarding to the particular vehicle.
2.2 Product Functions
There will be several types of information like: - Vehicle’s RTO
information and request, approval and response. - If the customer
wants to finance his/her vehicle then information regarding to finance
will also be available here and takes forward to a financer. - Workshop
information’s. - In case of accident or theft, you can request for FIR to
the police and in revert the police can send you a confirmation
message. - A customer can also apply for new and renewal of the
insurance of the vehicle.
2.3 User Characteristics User Profiles:
 Administrators – These individuals oversee the information’s related
to vehicles and all of its aspect. They are responsible for maintaining
information accuracy, user issues such as request problems, login
issues, and request and response problems.
Users – These individuals are the ones who use the Vehicle Information
System. The user of the VIS is expected to have some basic knowledge
of computer and internet usage and the opera
 3. Specific Requirements
The Vehicle Information System must be capable of providing fast,
accurate, and courteous ("user friendly") services for all requests
supported. The system must be able to :  answer inquiries about
vehicles,  generate, modify, and cancel vehicle owners profiles and
accounts,  make, changes, complete, and cancel requests,  obtain
request and verify request and give response etc.
3.1 System Requirements
3.1.1 Software Requirements:
Front end: Java/J2EE technologies (Servlet, JSP), HTML, CSS
Back end: MS Access
Middleware/Server: Apache Tomcat v7.0
IDE: Eclipse IDE for Java EE Developers
Browser: Best results on Mozilla Firefox
Operating System: Window XP (Minimum)
Software Development Environment: JDK v1.7

3.1.2 Hardware Requirements:

CPU: Pentium-IV (Processor) RAM: 256 MB
Hard Disk: 10GB
Display: CRT, LCD
Microsoft compatible keyboard
3.2 Software System Attributes
Tools and Platforms Used:
 Front End - Java Server Pages
User friendly GUI
Separation of work (designing & coding)
Written once run anywhere Middle-Tier
 Back End - MS Access
Security
Performance
Scalability
Reliability
Support DBMS concepts

3.2.1 Power and Flexibility Because JSP is based on the common

language runtime, the power and flexibility of that entire platform is
available to Web application developers. The class library, Messaging,
and Data Access solutions are all seamlessly accessible from the Web.
3.2.2 Manageability JSP employs a text-based, hierarchical
configuration system, which simplifies applying settings to your server
environment and Web applications. Because configuration information
is stored as plain text. A JSP application is deployed to a server simply
by copying the necessary files to the server. No server restart is
required, even to deploy or replace running compiled code.
3.2.3 Scalability and Availability JSP has been designed with scalability
in mind, with features specifically tailored to improve performance in
clustered and multiprocessor environments. Further, processes are
closely monitored and managed.
3.2.4 Security
In the software security there are two levels of security. The 1st level of
security, which is provided by the FRONT END and 2nd level of security
provided by the database which is being used.
3.2.4.1 SOFTWARE INTERFACE
FRONT END We have implemented JSP for all the Client-side
validations. Client-side coding is designed to reside inside HTML
document & ensure they run properly. It is object based, event driven,
platform independent. These are important parts of any Web
application to implement Client-side Validations and the invalid data is
not submitted. The form is not submitted until user fills in correct data.
It is extremely useful to restrict mistakes by user.
We have implemented Java Server Pages in between which is fetching
the data values given by the user and storing the input into database
(into appropriate tables). It use appropriate drivers to make connection
with database and store data. It provides support to execute queries via
creating objects of Statement and Connection Interfaces. These are
object byte codes that can be dynamically loaded off the Internet.
These are platform independent, dynamically loadable.
o FRONT END SECURITY: This security level is developed or designed by
the s/w developer or designer. S/he provides her/his s/w the security
for the system, by considering many factors regarding to the particular
s/w. In this software following are used to provide security:
LOGIN CHECKING:
There are six type of login’s are provided in this software for
Administrator, Customer, RTO, Police, Workshop and Finance. In order
to avail the services of software users have to provide a valid id and
password and only after entering correct id and password employee
will get entry otherwise, they will not be allowed to access any services
of this site. Similarly, a login check is provided for a vehicle owner
applying for information. In order to enter Vehicle related Information
zone user, have to enter id and password which they got after
registration, in this way security have been provided for all sections.
There is also provision to change the password in case password is
known by other.
BACK END
We have used MS Access as the Back end. MS Access provides
efficient/effective solution for major database tech. - Large database
and space management. - Many concurrent database users. - High
transaction processing requirement - High Availability - Industry
accepted standards - Manageable security - Portability o BACK END
SECURITY: In this particular software our back end used is MS Access.
So, all the inbuilt security aspects provided by the MS Access database
is used as it is. It will provide the strong feature of security so that it will
be difficult to change, modify any personal or vehicle related data.
Information is vital to success, but when damaged or in the wrong
hands, it can threaten success. MS Access provides extensive security
features to safe guard your information from both unauthorized
viewing and intentional or inadvertent damage. This security is
provided by granting or revoking privileges on a person- by- person and
privilege-by-privilege basis.
The user is also expected to be capable of learning how to operate VIS
systems. o
BACK END SECURITY:
In this particular software our back end used is MS Access. So all the
inbuilt security aspects provided by the MS Access database is used as
it is. It will provide the strong feature of security so that it will be
difficult to change, modify any personal or vehicle related data.
Information is vital to success, but when damaged or in the wrong
hands, it can threaten success. MS Access provides extensive security
features to safe guard your information from both unauthorized
viewing and intentional or inadvertent damage. This security is
provided by granting or revoking privileges on a person- by- person and
privilege-by-privilege basis.
Software Requirements Specifications Document
3.3 Diagrams
3.3.1 DFD (Data Flow Diagrams) :
The DFD takes an input-process-output view of a system i.e. data
objects flow into the software, are transformed by processing
elements, and resultant data objects flow out of the software.
Data objects represented by labeled arrows and transformation are
represented by circles also called as bubbles. DFD is presented in a
hierarchical fashion i.e. the first data flow model represents the system
as a whole. Subsequent DFD refine the context diagram (level 0 DFD),
providing increasing details with each subsequent level.
The DFD enables the software engineer to develop models of the
information domain & functional domain at the same time. As the DFD
is refined into greater levels of details, the analyst performs an implicit
functional decomposition of the system. At the same time, the DFD
refinement results in a corresponding refinement of the data as it
moves through the process that embody the applications.
A context-level DFD for the system the primary external entities
produce information for use by the system and consume information
generated by the system. The labeled arrow represents data objects or
object hierarchy.
RULES FOR DFD:
 Fix the scope of the system by means of context diagrams.
 Organize the DFD so that the main sequence of the actions
 Reads left to right and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with Rounded
circles.
Software Requirements Specifications Document
 A process is required for all the data transformation and Transfers.
Therefore, never connect a data store to a data Source or the
destinations or another data store with just a Data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything
the process is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with Squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple Record
retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.
3.3.2 USE CASE DIAGRAM :
Use case diagrams model behavior within a system and helps the developers
understand of what the user require. The stick man represents what’s called an
actor. Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can’t do. Use case diagram
consists of use cases and actors and shows the interaction between the use case and
actors.
 The purpose is to show the interactions between the use case and actor.  To
represent the system requirements from user’s perspective.  An actor could be
the end-user of the system or an external system.

USECASE DIAGRAM :
A Use case is a description of set of sequence of actions. Graphically it is rendered
as an ellipse with solid line including only its name. Use case diagram is
a behavioral diagram that shows a set of use cases and actors and their relationship.
It is an association between the use cases and actors. An actor represents a real-
world object. Primary Actor – Sender, Secondary Actor Receiver.
Page
3.3.3 Sequence Diagrams :
Sequence diagram and are also called INTERACTION DIAGRAMS.
An interaction diagram shows an interaction, consisting of set of objects
and their relationship including the messages that may be dispatched
among them
A sequence diagram is an introduction that empathizes the time ordering
of messages. Graphically a sequence diagram is a table that shows
objects arranged along the X-axis and messages ordered in increasing
time along the Y-axis.