ONLINE VEHICLE SERVICE CENTRE

MANAGEMENT SYSYTEM

ABSTRACT

OBJECTIVE-:

This system “Vehicle services” allows providing vehicle for service. 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 instrument 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.

This project contains 3 modules namely: -

 User Registration
 Service Charges
 Submission module
USER CREATION-:

In this module we are Registration the username, password, phone

and vehicle no, warranty and branch no. are user creations.

SERVICE CHARGES-:

In this module we are Registered the Customer Name, Vehicle no, Parts
and Servicing Charges as well as Paying the money.

SUBMISSION MODULE-:

In this module the dealer is handover to the Customer and before

registering the Customer name, Vehicle no and phone. Maintenance
Order Registration and Warranties.

INTRODUCTION-:

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
management is of vital relevance to ensure ongoing Customer loyalty
and retention and ultimately, dealer Profitability.
Dealer Business Management enables efficient Service order
Processing and billing designed 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 OEM channel System, including ,job and Package Catalogues,
Vehicle history files ,Warranty Systems, 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. The Driver and Vehicle Licensing
Agency ,the Driving Standards Agency and the Vehicle and Operator
Service Agency Provide Services for 42 million drivers.
The Vehicle and Operator Services Agency(VOSA) Provides a range of
licensing, testing and enforcement services with the aim of improving
the roadworthiness standards of Vehicles ensuring the Compliance of
operators and drivers , and Supporting the independent Traffic
Commissioner.

OBJECTIVE OF THE SYSYTEM-:

The objective of the Vehicle Services is to provide better information

for the users of this system for better results for their maintenance in
the product details that is sales, purchases and stock.

SYSTEM SPECIFICATIONS-:

 HARDWARE REQUIREMENTS-
 Pentium-IV(Processor).
 256 MB Ram
 512 KB Cache Memory
  Hard disk 10 GB
 Microsoft Compatible 101 or more Key Board

 SOFTWARE REQUIREMNETS-:
 Operating System : Windows
 Programming language: MS.NET
 Web-Technology: ASP.NET
 Front-End: C#.NET
 Back-End: SQLSERVER 2000

USECASE DIAGRAMS:

Use case diagrams model behaviour 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.

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 labelled 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 perform 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 labelled arrow represents data objects or
object hierarchy.

USER REGISTRATION-:
BOOKING CAR-:

E-R DIAGRAMS-:
The Entity-Relationship (ER) model was originally proposed by Peter in
1976 [Chen76] as a way to unify the network and relational database
views. Simply stated the ER model is a conceptual data model that
views the real world as entities and relationships. A basic component of
the model is the Entity-Relationship diagram which is used to visually
represents data objects. Since Chen wrote his paper the model has
been extended and today it is commonly used for database design For
the database designer, the utility of the ER model is:

 it maps well to the relational model. The constructs used in

the ER model can easily be transformed into relational tables.
 it is simple and easy to understand with a minimum of
training. Therefore, the model can be used by the database
designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the
database developer to implement a data model in a specific
database management software.
DATABASES-:
A database in Microsoft SQL Server consists of a collection of tables
that contain data, and other objects, such as views, indexes, stored
procedures, and triggers, defined to support activities performed with
the data. The data stored in a database is usually related to a particular
subject or process, such as inventory information for a manufacturing
warehouse.

SQL Server can support many databases, and each database can store
either interrelated data or data unrelated to that in the other
databases. For example, a server can have one database that stores
 personnel data and another that stores product-related data.
Alternatively, one database can store current customer order data, and
another; related database can store historical customer orders that are
used for yearly reporting. Before you create a database, it is

important to understand the parts of a database and how to design

these parts to ensure that the database performs well after it is
implemented.

NORMALIZATION THEORY-:

Relations are to be normalized to avoid anomalies. In insert, update

and delete operations. Normalization theory is built around the
concept of normal forms. A relation is said to be in a particular form if it
satisfies a certain specified set if constraints. To decide a suitable
logical structure for given database design the concept of
normalization, which are briefly described below.
1. 1 st Normal Form (1 N.F): A relation is said to be in 1 NF is and only if
all unaligned domains contain values only. That is the fields of an n-set
should have no group items and no repeating groups.
2. 2 nd Normal Form (2 N.F) : A relation is said to be in 2 NF is and only
if it is in 1 NF and every non key attribute is fully dependent on primary
key. This normal takes care of functional dependencies on non-key
attributes.
3. 3 rd Normal Form (3 N.F) : A relation is said to be in 3 NF is and only
if it is in 2 NF and every non key attribute is non transitively dependent
on the primary key. This normal form avoids the transitive
dependencies on the primary key.
 4. Boyce code Normal Form (BCNF) : This is a stronger definition than
that of NF. A relation is said to be in BCNF if and only if every
determinant is a Candidate key.
5. 4 th Normal Form (4 NF) : A relation is said to be in 4 NF if and only if
whenever there exists a multi valued dependency in a relation say A>-
>B then all of the relation are also functionally dependent on A(i.e. A>X
for all attributes x of the relation.).
6. 5 th Normal Form (5 NF) OR Projection Join Normal Form (PJNF): A
relation R is in 5 NF. if and only if every join dependency in R is implied
by the candidate key on R . A relation can‘t be non-loss split into two
tables but can be split into three tables. This is called Join Dependency.

FUNCTIONALITY OF PROJECT-:

 Complete Inventory from Sales of spare parts

 Reports for all invoices, taxes collected and more
 Reports for all Items in Stock as well as Items to be Ordered
 Maintains Details of vehicle repairs, spares used and other
information via repair history
 Invoice reports for particular period – Summary as well as detailed
 Reports of outstanding amounts by customer for sales as well as
service
 Maintains the Employee, Supplier as well as Customer details