GARAGE MANAGEMENT
Submitted By : Roll No.
1
Raj Chavan 09
Emmaual Karbhari 21
Clinton Mendonca 29
Malcolm Monserrate 30
Eric Simon 45
Jason Xavier 51
Index:
1. Organization of garage.
2. Introduction.
3. Front end, Back end.
4. Proposed System.
5. Brief Background.
6. Scope.
7. Modules.
8. Data Table Structure.
9. Data Flow Diagram.
10. E-R Diagram.
2
Organization of garage
Currently in garages, the employees are not distributed properly.
There isn’t any systematic approach of storing data which result in
loss of data.
There are many cases where employees feel that they are not given
proper bonuses nor promotions etc.
The standard at which work is done is not upto mark.
3
Introduction:
Our objective of the project is to modernize today’s generation of
garage working and to make the processing simple, reliable and more
systematic. The main aim is to provide the best to the employee from the
working point of view and to the customer from the service point of
view and thus increasing the level at which a car can be worked upon.
4
Front end: java.
Each page (visible to the user) will be designed using the above
programming languages.
Back end: Ms Access
Various kinds of data manipulation which is not visible to the user,
will be done using Microsoft Office Access.
5
Proposed System:
All decisions regarding employees will be systematically saved on
database.
All information regarding cars, parts, prices etc will be updated
periodically.
It will create more employment.
Employees will be well classified into their respective
departments.
Employees will be paid properly for the work they do.
6
Background Details:
Till now technology is not so advanced that computer applications
are used in a garage for its processing.
All the work in a garage is done manually.
Hence this project is to develop an application for a garage to ease
its processing and advancing its service.
The application provides a brief guidance to its user about the
vehicles, its parts and from the repairing point of view.
This application also provides information or gives a view to the
improvising that can be made to the vehicle.
The application will help to keep printed details of the transactions
between the customer and the garage.
The application takes care of the manual work as well as paper
work that are needed in garage processing.
7
Scope:
The application provides a better interface between employees and
customers.
Jobs performed will be more systematic.
It will increase the technical standards of the garage.
Paperless transaction.
Flexible and easy to use.
8
Modules:
Customization- It shows the details of the vehicles parts, its
modification, and contains other customization details.
Stock- It includes the stock details, its sales, purchase, etc.
Transaction- It includes all the transaction details of the garage, its
bill details, monthly and yearly profit and loss, etc.
Employee- It has all the details regarding the employees, their
salary, leave applications, their work shifts, etc.
Customer- It keeps all the customer records (regular customer), the
car details if the customer has left in the garage for repairing
purpose.
9
Data Table Structures:
1. Customization-
customer report.
repairing details.
modification details.
Accessories.
paint.
wash.
2. Stock-
stock details.
supply details.
stock updates.
3. Transactions-
customer report.
bill details.
4. Employee-
Employee details(name, address, etc).
5. Customer-
customer details.
car details.
10
Data Flow Diagram:
Stock inquiry
MANAGER
Stock availability
Acquires emp details Request permission
FETCHES DATA
to access database
Requests emp details
FROM DATABASE DATA-
-BASE
Requests car details Access granted
MECHANICS
Acquires car details
Submits daily Transaction
ACCOUNTANT
Acquires acknowledgement
Updates work related data
SUPERVISOR
Receives conformation
E-R DIAGRAM:
11
manages GARAGE provides Services
to
has
Stock Customers
provides
EMPLOYEE
provides
Supplier
ISA
deals Cars
MANAGER OTHERS
ACCOUNTANT MECHANICS
SUPERVISOR
prepares Provides details
manages repairs
Submitted to
Bills
12
