AUTOMOBILE SERVICE MANAGEMENT

SYSTEM
A UML Case study report submitted in partial fulfillment
of the requirements for the award of Degree in

Master of Computer Applications (MCA)

By

D. N. Yaswanth Chandra
(Regd No: 1223714107)

Under the guidance of

Smt K. Yasudha
Assistant Professor

Department of Computer Science

GITAM Institute of Science
GITAM University
Visakhapatnam-530 045, A.P.
(2015)
 CERTIFICATE

This is to certify that the UML Case study entitled “AUTOMOBILE SERVICE
MANAGEMENT SYSTEM” is a bonafide work done by Mr. D. Naga Yaswanth Chandra,
Reg.No:1223714107 from December 2015 to April 2016, in partial fulfillment of the
requirements for the award of degree of Master of Computer Applications (MCA) in the
Department of Computer Science, GITAM Institute of Science, GITAM University.

Guide Head of the Department

K. Yasudha Prof. V. Nagalakshmi
Assistant Professor
 DECLARATION

I, Duggirala Naga Yaswanth Chandra, 1223714107 hereby declare that the

UML Case study entitled “AUTOMOBILE SERVICE MANAGEMENT SYSTEM”, is an
original work done in the partial fulfillment of the requirements for the award of degree of
Mater Of Computer Applications (MCA) in GITAM Institute of Science, GITAM University.
I assure that this UML Case study has not been submitted towards any other
degree or diploma in any other colleges or universities.
.

D. N. Yaswanth Chandra

ACKNOWLEDGEMENT
 This UML Case study entitled "AUTOMOBILE SERVICE MANAGEMENT
SYSTEM" would not have been feasible one without the grace of my Parents and Family
members who gave me moral support to carry out this uphill task.

We are greatly indebted to k. YASUDHA (Assistant Professor), Dept of Computer

Science, GITAM Institute of Science, GITAM University who has taken special interest in our
work and has provided innovative ideas, wonderful guidance, constant encouragement, personal
advice and constructive criticism throughout this work.

We would like to express our sincere thanks and respectful regard to our beloved
Principal Prof. N. Lakshman Das , GITAM Institute of Science, GITAM University, for his
valuable support, facilities that were provided to us at the institution to carry out this work. With
great pleasure we wish to place our indebtedness to Head of Department Prof. V. Nagalakshmi
, for her constant encouragement, support she rendered during this work.

This Case study would not be a resplendent one without the timely help and
continuous support by our ever-loving parents, professors and friends. Finally, sincere thanks to
all who directly or indirectly helped me to complete this Case study successfully.

D .N . Yaswanth Chandra
 ABSTRACT

For the past one and a half decade the passenger car population has been steadily
increasing. This is mainly because the Indian economy is now considerably liberalized for all
types of industries. India is having around 30 odd passenger car models and different motorcycle
models on the roads developed indigenously. This gave rise to the importance of their service
and maintenance.

The aim of Automobile Service Management System is to provide efficient Service to the
Vehicle Companies and Vehicle Servicing Centers. This system will deal with all functionalities
a automobile service centre will encounter. This system is best suited for automobile deals of
Two Wheelers, Four Wheelers servicing, polishing, Wheel Alignment and Decors. This system
helps to track, required Vehicle maintenance and more. It Stores the details of Customers,
Vehicle details like past servicing records, Fitted Equipment, etc.

Initially employee of the organization logs on to the system and enters the details of the
Vehicle owner and vehicle and thereby creates Job card and sends the vehicle to servicing. After
completion of service, customer pay’s total amount and vehicle is returned.
 Table of Contents

S.No. Content Description Page No.

1. Introduction
1.1 About the Case study

2. Requirements Analysis Document

2.1 Introduction
2.2 Existing System

2.3 Proposed System

2.4 Feasibility Analysis
2.5 Functional Requirements
2.6 Non Functional Requirements

3. System Design
3.1 Introduction
3.2 Use-Case Diagram
3.3 Class Diagram
3.4 Interaction Diagram
3.4.1 Admin
3.4.2 Customer
3.4.3 Vehicle
3.4.4 Job Card
3.5 State Chart Diagram
3.6 Activity Diagram

4. About the Software

5. Testing

6. Screens Shots

7. Conclusion
INTRODUCTION
1.1 ABOUT THE CASE STUDY

The automotive industry in India is one of the larger markets in the world. India's
passenger car and motorcycle manufacturing industry is the sixth largest in the world, with an
annual production of more than 3.9 million units. According to recent reports, India overtook
Brazil and became the sixth largest passenger vehicle producer in the world, these reflect on the
growing need for quality repair and service facilities. Once the vehicle comes on the road it is
expected to run for an indefinite period requiring maintenance services throughout its operational
life. Moreover there is a considerable demand for wheel alignment , wash, Decor, polish/paint
services, which is required by almost every car, whether new or old.

Improper maintenance of vehicles, present conditions of roads, irresponsible driving,

using cheaper spare parts, etc are the main reasons to send the vehicles for service and
maintenance. Service station is the most essential unit to vehicle users. This unit can be
established in urban, semi-urban and village areas to meet the local requirement There is good
demand for automobile service system due to increase in the number of vehicles day to day.

The Automobile Service Management System is a progressive step in the field of service
centers. This system deals of Two Wheelers, Four Wheelers servicing, polishing, Wheel
Alignment and Decors. This system helps to track, required Vehicle maintenance and more. It
Stores the details of Customers, Vehicle details like past servicing records, Fitted Equipment,
etc.
REQUIREMENT ANALYSIS
2.1 INTRODUCTION
Increased productions of automobiles both in domestic market and worldwide have
boosted the confidence of auto ancillary units and automobile servicing sector. As the servicing
of existing vehicles population is an essential activity, there is large scope in this area given the
increasing number of vehicles on the road year after year.

An automobile services station, has to have facilities to service the vehicles, such as necessary
equipments facilitating, regular washing, wheel alignment, paint/polish etc. Automobile Service
Management System provides necessary services to the service station for efficient management.

2.2 PROPOSED SYSTEM

Vehicle service business is all about the time and quality. The Automobile Service
Management System provides authentication, service downtime by coordinating between
services and plan service recourses including mechanics and equipment. Automobile service
management system ensures collective vehicle service center business functions and allows to
manage the entire organization using this one system.

2.3 EXISTING SYSTEM

In Existing system, there is a lack of Authentication and it doesn't provide coordination

among different services. Due to lack of coordination among services, it leads to inefficient time
management.
2.4 FEASIBILTY ANALYSIS
Preliminary investigation examines Case study feasibility, the likelihood the system will
be useful to the organization. The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and debugging old running
system. All systems are feasible if they are given unlimited resources and infinite time. There are
aspects in the feasibility study portion of the preliminary investigation:
• Technical Feasibility
• Operation Feasibility
• Economical Feasibility

2.4.1 TECHNICAL FEASIBILITY

The system must be evaluated from the technical point of view first. The assessment of
this feasibility must be based on an outline design of the system requirement in the terms of
input, output, programs and procedures. Having identified an outline system, the investigation
must go on to suggest the type of equipment, required method developing the system, of running
the system once it has been designed.

Technical issues raised during the investigation are:

Does the existing technology sufficient for the suggested one? Can the system expand if
developed?

The Case study should be developed such that the necessary functions and performance can be
achieved within the constraints. The Case study is developed within latest technology. Though
the technology may become obsolete after some period of time, due to the fact that never version
of same software supports older versions, the system may still be used. So there are minimal
constraints involved with this Case study. The system has been developed using Java. The Case
study is technically feasible for development.
2.4.2 OPERATIONAL FEASIBILITY

User-friendly

Customer will use the forms for their various transactions i.e. for adding new routes, viewing the
routes details. Also the Customer wants the reports to view the various transactions based on the
constraints. These forms and reports are generated as user-friendly to the Client.

RELIABILITY

The package wills pick-up current transactions on line. Regarding the old transactions, User will
enter them in to the system

Security

The web server and database server should be protected from hacking, virus etc

Portability

The application will be developed using standard open source software (Except Oracle) like
Java, tomcat web server, Internet Explorer Browser etc these software will work both on
Windows and Linux o/s. Hence portability problems will not arise.

Availability
This software will be available always.

Maintainability

The system called the wheels uses the 2-tier architecture. The 1st tier is the GUI, which is said to
be front-end and the 2nd tier is the database, which uses My-Sql, which is the back-end.
The front-end can be run on different systems (clients). The database will be running at the
server. Users access these forms by using the user-ids and the passwords.
2.4.3 ECONOMIC FEASABILITY

The Computerized system takes care of the present existing systems' data flow and
procedures completely and should generate all the reports of the manual system besides a host of
other management reports.

It should be built as a web based application with separate web server and database server. This
is required as the activities are spread throughout the organization customer wants a centralized
database. Further some of the linked transactions take place in different locations.

2.5 FUNCTIONAL REQUIREMENTS

A Functional requirement defines a function of a software system or its components. A

function is described as asset of inputs, the behavior, and outputs. Functional requirements may
be calculations, technical details, data manipulation and processing and other specific
functionality that defines what a system is supposed to accomplish. Behavioral requirements
describing all the cases where the system uses the functional requirements are captured in use
cases. Functional requirements are supported by non-functional requirements (also known as
quality requirements), which impose constraints on the design or implementation (such as
performance requirements, security, or reliability).

The System must provide following functionalities:-

 Admin
 Customer
 Vehicle
 Job Card
Admin

Every authorized employee in the service centre will have a unique username and
password, by which they logs on to the system.

Customer

In this customer has to give information like name, address, phone number, Email-id,
driving license number for registration and a Customer Id is generated.

Vehicle

The Customer/owner gives the details of vehicle like make, year of manufacture, cbook
number, model, variant, class of vehicle. Then, each vehicle is linked to the respective customer
Id. Each Id can have two or more vehicles.

Job Card

Employee of the Organization records / creates the job card as per customer requirements
like body wash, wheel alignment, Paint / Polish, Decors and enter Time in, estimated Time out,
estimated Bill. This job card is linked to the Customer I'd, then the vehicle is sent to work. In
each and every requirement, price is calculated and updated to the total bill. Then Customer
pay’s the bill and vehicle is returned.

2.6 NON FUNCTIONAL REQUIREMENTS

 A non-functional requirement is a requirement that specifies criteria that can be used to
judge the operation of a system, rather than specific behaviors. This should be contrasted with
functional requirement that defines specific behavior or functions. The plan for implementing
functional requirements is detailed in the system design. The plan for implementing non-
functional requirements is detailed in the system architecture. Broadly, functional requirement
define what a system is supposed to do whereas non-functional requirements define how a
system is supposed to be. Non- functional requirements are often called qualities of a system.
Other terms for non-functional requirements are “constraints”, “quality attribute”, ”quality goals”
“quality of service requirements” and “non-behavioral requirements”. Informally these are
sometimes called the “utilities”, from attributes like stability and portability. Qualities, that are
non-functional requirements, can be divided into two main categories:
1. Execution qualities, such as security and usability, which are observable at run time.
2. Evolution qualities, such as testability maintainability, extensibility and scalability, which
are embodied in the static structure of the software system.

The Automobile Service Management System has the following non-functional requirements:
 24 X 7 availability.
 Better component design to get better performance.
 Flexible service based architecture will be highly desirable for future extension.
 Ease of Use-flexibility, performance.
 Security- Privacy, Confidentiality, Integrity, Authentication.
 Comprehensiveness- Transferability, Divisibility, Standardization.
 Maintenance.
 SYSTEM DESIGN

3.1 INTRODUCTION
 System design is the process of defining the elements of a system such as the
architecture, modules and components, the different interfaces of those components and the data
that goes through that system. It is meant to satisfy specific needs and requirements of a business
or organization through the engineering of a coherent and well-running system.

Systems design implies a systematic approach to the design of a system. It may take a bottom-up
or top-down approach, but either way the process is systematic wherein it takes into account all
related variables of the system that needs to be created—from the architecture, to the required
hardware and software, right down to the data and how it travels and transforms throughout its
travel through the system. Systems design then overlaps with systems analysis, systems
engineering and systems architecture.

The systems design approach first appeared right before World War II, when engineers were
trying to solve complex control and communications problems. They needed to be able to
standardize their work into a formal discipline with proper methods, especially for new fields
like information theory, operations research and computer science in general.

During system design, developers define the design goals of the Case study and decompose the
system into smaller subsystems that can be realized by individual teams. Developers also select
strategies for building the system, such as the hardware/software platform on which the system
will run, the persistent data management strategy, the global control flow, the access control
policy, and the handling of boundary conditions. The result of system design is a clear
description of each of these strategies, a subsystem decomposition, and a deployment diagram
representing the hardware/software mapping of the system. Whereas both analysis and system
design produce models of the system under construction, only analysis deals with entities that the
client can understand. System design deals with a much more refined model that includes many
entities that are beyond the comprehension (and interest) of the client

3.2 Use Case Diagram

 Use cases are used during requirements elicitation and analysis to represent the
functionality of the system. Use cases focus on the behavior of the system from an external point
of view. A use case describes a function provided by the system that yields a visible result for an
actor. An actor describes any entity that interacts with the system (e.g., a user, another system,
the system’s physical environment). The identification of actors and use cases results in the
definition of the boundary of the system, that is, in differentiating the tasks accomplished by the
system and the tasks accomplished by its environment. The actors are outside the boundary of
the system, whereas the use cases are inside the boundary of the system.

3.3 Class Diagram

 Class diagrams are used to describe the structure of the system. Classes are abstractions
that specify the common structure and behavior of a set of objects. Objects are instances of
classes that are created, modified, and destroyed during the execution of the system. An object
has state that includes the values of its attributes and its links with other objects. Class diagrams
describe the system in terms of objects, classes, attributes, operations, and their associations.

3.4 Interaction Diagram

 Interaction diagram is used to formalize the dynamic behavior of the system and to
visualize the communication among objects. They are useful for identifying additional objects
that participate in the use cases. We call objects involved in a use case participating objects. An
interaction diagram represents the interactions that take place among these objects

3.4.1 Admin Interaction Diagram

3.5.2 Customer Interaction Diagram

3.4.3 Vehicle Interaction Diagram
3.5 State Machine Diagram

State machine diagram describe the dynamic behavior of an individual object as a

number of states and transitions between these states. A state represents a particular set of values
for an object. Given a state, a transition represents a future state the object can move to and the
conditions associated with the change of state.
3.6 Activity Diagrams

An activity diagram describes the behavior of a system in terms of activities. Activities

are modeling elements that represent the execution of a set of operations. The execution of an
activity can be triggered by the completion of other activities, by the availability of objects, or by
external events. Activity diagrams are similar to flowchart diagrams in that they can be used to
represent control flow (i.e., the order in which operations occur) and data flow (i.e., the objects
that are exchanged among operations).
ABOUT THE SOFTWARE
4. JAVA

Java is a general purpose, high-level programming language developed by Sun

Microsystems. A small team of engineers, known as the Green Team, initiated the language in
1991. Java was originally called OAK, and was designed for handheld devices and set-top boxes.
Oak was unsuccessful, so in 1995 Sun changed the name to Java and modified the language to
take advantage of the burgeoning World

Java is an object-oriented language similar to C++, but simplified to eliminate language

features that cause common programming errors. Java source code files (files with
a .java extension) are compiled into a format called byte code (files with a .class extension),
which can then be executed by a Java interpreter. Compiled Java code can run on most
computers because Java interpreters and runtime environments, known as Java Virtual Machines
(VMs), exist for most operating systems, including UNIX, the Macintosh OS, and Windows.
Byte code can also be converted directly into machine language instructions by a just-in-time
compiler (JIT). In 2007, most Java technologies were released under the GNU General Public
License.

Features of JAVA

Simple
Java is easy to learn and its syntax is quite simple, clean and easy to understand. The
confusing and ambiguous concepts of C++ are either left out in Java or they have been re-
implemented in a cleaner way.

Object Oriented

In java everything is Object which has some data and behavior. Java can be easily
extended as it is based on Object Model.

Robust

The main areas which Java improved were Memory Management and mishandled
Exceptions by introducing automatic Garbage Collector and Exception Handling.
Platform Independent

Unlike other programming languages such as C, C++ etc which are compiled into
platform specific machines. Java is guaranteed to be write-once, run-anywhere language.
On compilation Java program is compiled into byte code. This byte code is platform independent
and can be run on any machine, plus this byte code format also provide security. Any machine
with Java Runtime Environment can run Java Programs.

Secure

When it comes to security, Java is always the first choice. With java secure features it enable us
to develop virus free, temper free system. Java program always runs in Java runtime environment
with almost null interaction with system OS, hence it is more secure.

Multi- Threading

Java multithreading feature makes it possible to write program that can do many tasks
simultaneously. Benefit of multithreading is that it utilizes same memory and other resources to
execute multiple threads at the same time, like While typing, grammatical errors are checked
along.

Architectural Neutral

Compiler generates byte codes, which have nothing to do with a particular computer
architecture, hence a Java program is easy to interpret on any machine.

Portable

Java Byte code can be carried to any platform. No implementation dependent features.
Everything related to storage is predefined, example: size of primitive data types

High Performance

Java is an interpreted language, so it will never be as fast as a compiled language like C

or C++. But, Java enables high performance with the use of just-in-time compiler.
TESTING
Testing

Software Testing is evaluation of the software against requirements gathered from users
and system specifications. Testing is conducted at the phase level in software development life
cycle or at module level in program code. Software testing comprises of Validation and
Verification.Testing is a fault detection technique that tries to create failures or erroneous states
in a planned way. This allows the developer to detect failures in the system before it is released
to the customer. Note that this definition of testing implies that a successful test is a test that
identifies faults. We will use this definition throughout the development phases. The
characteristic of a good test model is that it contains test cases that identify faults. Tests should
include a broad range of input values, including invalid inputs and boundary cases, otherwise,
faults may not be detected.

Testing Concepts

• A test component is a part of the system that can be isolated for testing. A component
can be an object, a group of objects, or one or more subsystems.

• A fault, also called bug or defect, is a design or coding mistake that may cause
abnormal component behavior.

• An erroneous state is a manifestation of a fault during the execution of the system. An

erroneous state is caused by one or more faults and can lead to a failure.

• A failure is a deviation between the specification and the actual behavior. A failure is
triggered by one or more erroneous states. Not all erroneous states trigger a failure.2

• A test case is a set of inputs and expected results that exercises a test component with
the purpose of causing failures and detecting faults.

• A test stub is a partial implementation of components on which the tested component

depends.

• A correction is a change to a component. The purpose of a correction is to repair a fault.

Note that a correction can introduce new faults.
SCREEN SHOTS
EMPLOYEE LOGIN SCREEN

SUCCESSFUL LOGIN SCREEN

CUSTOMER REGISTRATION SCREEN

VEHICLE REGISTRATION SCREEN

JOB CARD SCREEN

BILL PAY SCREEN

7. CONCLUSION

The goal of this Case study is to produce an interactive system for the Service Centers.
Automobile Service Center Management system is designed to provide features of all the
vehicles, services provided by the service centers, locations of all the service centers in the
vicinity etc. The above proposed model is easy to implement considering the available
technology infrastructure. The models is simple, secure and scalable. The proposed model is
based on connectionless system. But for future scope in enlarging the system we can use
connection system. We can even start online for registration and information based website. So
the proposed system can be used to reduce human efforts and luxuriate human lives with the
modern technology.