VEHICLE SERVICE MANAGEMENT SYSTEM

SUBMITTED BY

ARUN MARSHLIN V(711521MMC001)

MANOJ L(711521MMC012)

Of

KIT-KALAIGNARKARUNANIDHI INSTITUTE OF TECHNOLOGY

(An Autonomous Institution)

OPEN LABORATORY PROJECT REPORT

Submitted to the

FACULTY OF INFORMATION AND COMMUNICATION

ENGINEERING

In partial fulfillment of the award of the degree

Of

MASTER OF COMPUTER APPLICATIONS

ANNAUNIVERSITY CHENNAI-600025

DEC-2022
 BONAFIDE CERTIFICATE

Certified that this Open Laboratory Project Report “VEHICLE SERVICE

MANAGEMENT SYSTEM” is the bonafide work of MR. ARUN
MARSHLIN V (711521MMC001) and MR. MANOJ L (711521MMC012)
who carried out the project work under my supervision.

Mr.R.Punithavel M.C.A., Mr.E.Vijayakumar M.C.A., (Ph.D.,)

Project Guide, Associate Professor & Head,

Department of Computer Applications, Department of Computer Applications,

KIT-KalaignarKarunanidhi Institute of KIT-KalaignarKarunanidhi Institute of

Technology(An Autonomous Technology (An Autonmous

Institution), Institution),

Kannampalayam, Coimbatore. Kannampalayam,Coimbatore.

Submitted to the Anna University Viva-Voce held on

Internal Examiner External Examiner

 DECLARATION

We affirm that the project work titled “VEHICLE SERVICE

MANAGEMENT SYSTEM” is the original work carried out by me and my
team. It has not formed part of any other project work submitted for the award of
any degree or diploma, either in this or any other university.

(Signature of the candidate)

ARUN MARSHLIN V, 711521MMC001

MANOJ L, 711521MMC012

I certify that the declaration made above by the candidate is true

(Signature of the Guide)

Mr. R.PUNITHAVEL AP/MCA

 ACKNOWLEDGEMENT

We have heartfelt gratitude and thanks to the Almighty God, my parents and other
family members and friends for providing the opportunity to undergo this project
successfully in this esteemed institution.

At the outset, I would like to thank our Founder and Chairman Thiru.
PONGALUR N. PALANISAMY, KIT- Kalaignarkarunanidhi Institute of
Technology, who has allowed me to undergo this Project Work, successfully in this
esteemed Institution.

We express my sincere thanks to Mrs P. INDU MURUGESAN, Vice

Chairperson, KIT- Kalaignarkarunanidhi Institute of Technology, who
encouraged me by giving her support and constant encouragement.

We extend my thanks and wishes to Dr N. MOHANDAS GANDHI, ME., MBA.,

PhD, Principal KIT- Kalaignarkarunanidhi Institute of Technology, for the valuable
suggestion in framing my carrier towards the fulfilment of this Project work.

We express my sincere thanks to Dr M. RAMESH, ME., PhD, Vice Principal,

KIT- Kalaignarkarunanidhi Institute of Technology, who encouraged me by
giving his valuable suggestion and constant encouragement.

We would like to acknowledge the respective Mr E. VIJAYAKUMAR MCA.,

(PhD.,) Associate Professor and Head Department of Computer Applications,
KIT- Kalaignarkarunanidhi Institute of Technology, for spending valuable time in
guiding and supporting me to make this project a successful one.

We take the privilege to extend my hearty thanks to our project Coordinator

and my internal guide Mr R. PUNITHAVEL M.C.A., Assistant professor,
Department of Computer Applications for spending his valuable time and energy
in guiding, supporting and helping me in the preparation of the project.

Finally, with great enthusiasm, I express my thanks to all the faculty members for
providing the necessary information and for their sustained interest in my successful
completion.
 TABLE OF CONTENTS

CHAPTER TITLE PAGE NO

ABSTRACT

1 Introduction

1.1.1 Objective 1

2 System Analysis

2.1 Existing System 2

2.1.1 Drawbacks 2

2.2 Proposed System 3

2.3 Feasibility Study 3

2.3.1 Economical Feasibility 3

2.3.2 Operational Feasibility 3

2.3.3 Technical Feasibility 3

3 System Specification

3.1 Hardware Requirements 4

3.2 Software Requirements 4

4 Software Description

4.1 Front End 5

4.2 Features 6

5 Project Description

5.1 Overview of the Project 7

5.2 Data Flow Diagram 7

5.3 Database Design 7

6 System Testing

6.1 Unit Testing 8

6.2 Acceptance Testing 8

6.3 Test Cases 8

7 System Implementation 9

8 Conclusion & Future Enhancements

8.1 Conclusion 10

8.2 Future Enhancements 10

9 Appendix

9.1 Source Code 11

9.2.Screen Shorts 15

10 References 17
 ABSTRACT

Vehicles now play a significant role in daily life. The growth in car sales over
time is seen in the vast majority of individuals commute daily using the
automobile. However, car maintenance is frequently disregarded. Regular
maintenance helps ensure that the car runs smoothly and that fuel is used
effectively. Another issue is that when automobiles are taken in for servicing or
maintenance, it is presumed that repairs would be made carefully, but it has been
noted that multiple vehicle accidents occur each year as a result of the neglect of
repair facilities and car dealers. When the car is handed over for repair, the
problem of confidence is crucial. Customers are frequently taken advantage of
under the name of service. A serious issue is the replacement of original parts
with outdated ones. Additionally, it might be challenging for clients to confirm
that the service providers are doing the tasks for which they are paying. Service
providers take advantage of this circumstance and overcharge customers. The
practice of "periodic vehicle maintenance, which mandates that the vehicle
have periodic servicing and maintenance, is widely used. A vehicle's service
life is typically determined by either a predetermined time frame or the mileage
travelled Generally speaking, it is advised to get the car serviced every six months
or 10,000 kilometres. However, the problem with "periodic vehicle maintenance"
is that it's difficult to determine which parts need to be repaired or replaced, which
might lead to repairs or replacements of parts that are still in good shape.
Predictive vehicle maintenance proves useful in this situation. This data is
obtained from numerous built-in or customized sensors in the car that are used to
keep track of the condition of various component.
 [1]

CHAPTER 1
1. INTRODUCTION

1. Objective

Owners of vehicles can avoid unforeseen car problems by maintaining

their vehicles regularly. Early detection of vehicle concerns is crucial to
preventing them from developing into serious difficulties. Owners of
vehicles frequently inquire about service at auto shops. Vehicle technicians
examine crucial parts of the vehicle and fix problems to make sure they are
in good condition and won't break down suddenly. The study was carried
out by the researchers to evaluate the everyday activities and transactions
carried out in auto repair facilities. The researchers gathered preliminary
data and discovered that the majority of auto repair companies or garages
still handle their daily transactions manually. Customer records are still
entered manually, as are transactions with clients, tracking of vehicle
repairs as they are made, updates on vehicle services, and billing. The
functioning of the garage and the response time to client inquiries will be
slowed by the ongoing usage of manual procedures. The researchers have
identified a need to modernize how auto repair shops work. Customers and
car garages will both profit from the system's installation. Utilizing the
technology to run the company will help car garages expand and improve
operational efficiency. Customers may do business for car service easily
and comfortably.
 [2]

CHAPTER 2
SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

The existing system is a manual one in which users maintain books to store
information like product details. Distributors details, purchases, sales details and
accounts for every month. It is very difficult to maintain historical data.

2.1.1 Drawbacks:
• The following are the disadvantages of the existing system. More manual
hours need to generate the required reports.
• It is tedious to manage historical data which needs much space to keep all
the previous years' ledgers, books etc.
• Daily sales and purchases details must be entered into books are very
difficult to maintain.
• it is difficult to maintain important information in books.
• More manual hours need to generate required reports.
2.2 PROPOSED SYSTEM
The DISTRIBUTORS MANAGEMENT TOOL is a software application which
avoids more manual hours that need to spend on 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 the
database. No specific training is required for the distributors to use this
application. They can easily use the tool that decreases manual hours spent on
normal things and hence increases performance. It is very easy to record
information on online sales and purchases in databases.
 [3]

2.3 Feasibility Study

A feasibility study is conducted once the problem is clearly understood. A
feasibility study is a high-level capsule version of the entire system analysis and
design process The objective is to determine quickly at a minimum expense how
to solve a problem. The purpose of feasibility is not to solve the problem but to
determine if the problem is worth solving.

The system has been tested for feasibility in the following points.
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.
1. Technical Feasibility
The project entitles "Courier Service System" is technically feasible because of
the below-mentioned feature. The project was developed in Java which Graphical
User Interface. It provides a high level of reliability, availability and compatibility
All these make Java an appropriate language for this project. Thus the existing
software Java is a powerful language.

2. Economical Feasibility
The computerized system will help automate the selection leading to the profits
and details of the organization. With this software, machine and manpower
utilization are expected to go up by 80-90% approximately. The costs incurred of
not creating the system are set to be great because precious time can be wanted
manually.

3. Operational Feasibility
In this project, the management will know the details of each project where he
may be presented and the data will be maintained as decentralized if any inquiries
for that particular contract can be known as per their requirements and necessaries
 [4]

CHAPTER 3
SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENTS

• Processor _ Intel i5 10 th gen

• Motherboard _ Intel Original
• RAM _ 4GB
• Hard Disk _ 500GB

3.2 SOFTWARE REQUIREMENTS

• Operating System – Windows 10

• Web-technology – ASP.NET
• Front End – C#.NET
• Back-End – SQL SERVER
 [5]

CHAPTER 4
SOFTWARE DESCRIPTION

4.1 FRONT END:

Microsoft .NET Framework
The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfil the following objectives:

To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-
distributed, or executed remotely.

To provide a code-execution environment that minimizes software deployment

and versioning conflicts.

To provide a code-execution environment that guarantees the safe execution of

code, including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on

the .NET Framework can integrate with any other code.
 [6]

4.2 BACK-END TECHNOLOGY:

About Microsoft SQL Server 2000
Microsoft SQL Server is a Structured Query Language (SQL) based, client/server
relational database. Each of these terms describes a fundamental part of the
architecture of SQL Server.

Database

A database is similar to a data file in that it is a storage place for data. Like a data
file, a database does not present information directly to a user, the user runs an
application that accesses data from the database and presents it to the user in an
understandable format.

A database typically has two components: the files holding the physical database
and the database management system (DBMS) software that applications use to
access data. The DBMS is responsible for enforcing the database structure,
including:

Maintaining the relationships between data in the database. Ensuring that data is
stored correctly and that the rules defining data relationships are not violated.
Recovering all data to a point of known consistency in case of system failures

Relational Database

There are different ways to organize data in a database but relational databases
are one of the most effective. Relational database systems are an application of
mathematical set theory to the problem of effectively organizing data. In a
relational database, data is collected into tables (called relations in relational
theory).
 [7]

CHAPTER 5
5.1 DATA FLOW DIAGRAM
 [8]

CHAPTER 6
SYSTEM TESTING

Testing is the process of executing a program with the intent of finding an error.
Testing is a crucial element of software quality assurance and presents an ultimate
review of specification, design and coding. System Testing is an important phase.
Testing represents an interesting anomaly for the software. Thus a series of testing
is performed for the proposed system before the system is ready for user
acceptance testing. Testing is a process of executing a program with the intent of
finding an error A good test case has a probability of finding an as yet
undiscovered

The primary objective for test case design is to derive a set of tests that has the
highest livelihood for uncovering defects in software. Two different test case
design techniques are used to accomplish this objective. They are

• White box testing

• Black box testing.
6.1 White-box testing
White box testing focuses on the program control structure. Test cases are derived
to ensure that all statements in the program have been executed at least once
during testing and that all logical conditions have been executed.

6.2 Block-box testing

Black box testing is designed to validate functional requirements without regard
to the internal workings of a program. Black box testing mainly focuses on the
information domain of the software, deriving test cases by partitioning input and
output in a manner that provides thorough test coverage. Incorrect and missing
functions, interface errors, errors in data structures, and errors in functional logic
are the errors falling in this category.
 [9]

CHAPTER 7
SYSTEM IMPLEMENTATION

7.1 System Implementation:

Implementation is the stage where the theoretical design is turned into a
working system. The most crucial stage in achieving a new successful system and
in giving confidence in the new system to the users that it will work efficiently
and effectively. The system can be implemented only after thorough testing is
done and if it is found to work according to the specification. The more complex
the system being implemented, the more involved will be the systems analysis
and design effort required just for implementation. It involves careful planning,
investigation of the current system and its constraints on implementation, design
of methods to achieve the changeover and an evaluation of change-over methods
apart from planning. Two major tasks of preparing the implementation are
education and training of the users and testing of the system.

The implementation phase comprises several activities. The required hardware

and software acquisition is carried out. The system may require some software to
be developed. For this, programs are written and tested. The user then changes
over to his new fully tested system and the old system is discontinued.
 [10]

CHAPTER 8
CONCLUSION & FUTURE ENHANCEMENTS

8.1 CONCLUSION
The package was designed in such a way that future modifications can be done
easily. The following conclusions can be deduced from the development of the
project. Automation of the entire system improves efficiency It provides a
friendly graphical user interface which proves to be better when compared to the
existing system. The System has adequate scope for future modification if
necessary System security, data security and reliability are the striking features.
It effectively overcomes the delay in communications. Updating information
becomes so much easier. It gives appropriate access to authorized users
depending on their permissions.

8.2 FUTURE ENHANCEMENTS

This application avoids manual work and the problems concerned with it. It is an
easy way to obtain information regarding the various vehicle information that is
present in the markets The next enhancement that we can add is the searching
option, We can directly search for the particular vehicle from this site These are
the two enhancements that we could think of at present we have planned to
implement the entire project in android because it has the leading user base and
it is more convenient one Well I and my team members have worked hard to
present an improved website better than the existing one's regarding the
information about the various activities. Still, we found out that the project can
be done in a better way. Primarily, when we request information about a particular
product it just shows the company, vehicle details, vehicle name and vehicle
service history. So, after getting the information we can get access to the vehicles
service website just by a click on the vehicle name.
 [11]

CHAPTER 9
APPENDIX
9.1 SOURCE CODE
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System. Data;
using System. Drawing;
using System. Linq;
using System. Text;
using System.Windows.Forms;

namespace vehicle service management system

{
public partial class Form1: Form
{
public Form1()
{
InitializeComponent();
}

private void button1_Click(object sender, EventArgs e)

{
if (textBox1.Text == "user" && textBox2.Text == "user")
{
label4.ForeColor = Color.Green;
label4.Text = "Login successfully";
 [12]

usersform uf = new usersform();

uf.Show();
}
else
{
label4.ForeColor = Color. Red;
label4.Text = "user name or password is incorrect";

}
}
private void linkLabel1_LinkClicked(object sender,
LinkLabelLinkClickedEventArgs e)
{
this.Hide();
Form2 al = new Form2();
al.Show();
}
}
}

namespace Mini_project_RTO
{
public partial class users form: Form
{
public usersform()
{
InitializeComponent();
 [13]

private void usersform_Load(object sender, EventArgs e)

{

private void button1_Click(object sender, EventArgs e)

{
appnewlicen al = new appnewlicen ();
this.Hide();
al.Show();
}

private void button7_Click(object sender, EventArgs e)

{
this.Hide();
fcveh fc = new fcveh();
fc.Show();
}
}
}
namespace Mini_project_RTO
{
public partial class Form2 : Form
{
public Form2()
 [14]

{
InitializeComponent();
}

private void button1_Click(object sender, EventArgs e)

{
if (textBox1.Text == "user" && textBox2.Text == "user")
{
label4.ForeColor = Color.Green;
label4.Text = "Login successfully";
usersform uf = new usersform();
uf.Show();
}
else
{
label4.ForeColor = Color. Red;
label4.Text = "user name or password is incorrect";
}
}
}
}
 [15]

9.2 SCREENSHOTS

9.2.1 Login Page

Figure9.2.2 ADMIN PAGE

 [16]

Figure 9.2.3 Updation Vehicle

Figure 9.2.3 View Vehicle Details

 [17]

CHAPTER 10
REFERENCES

BIBLIOGRAPHY
The following books were referred to during the analysis and execution phase of
the project
1. MICROSOFT.NET WITH C# Microsoft net series
2. ASP.NET 2.0 PROFESSIONAL Wrox Publishers
3. ASP.NET WITH C# 2000
4. C# COOKBOOK
5. Oreilly Publications
6. PROGRAMMING MICROSOFT ASP.NET 2.0 APPLICATION Wrox
Professional Guide
7. BEGINNING ASP .NET 2.0 E-COMMERCE IN C# 2005 Novice to
Professional
WEBSITES:
1. www.google.com
2. www.microsoft.com