Automobile

PROJECT REPORT ON

Automobile shop MANAGEMENT SYSTEM

SUBMITTED BY:

Viraj koli
UNDER THE GUIDENCE OF

PROFESSOR.

Mrs.
2010-2011

1
 Automobile

Acknowledgement

2
 Automobile

*INDEX*

Chapters No. Contents

01 Preliminary Investigation

 Organizational Overview
 Description of System
 Limitation of present system
 Proposed system and is adv.
 Feasibility Study
 Stakeholders
 Gantt chart
02 System Analysis

 Fact Finding Techniques(InterView,

Questionnaire,RecordView,Observation)

 Event Table
 Use case Diagram & use case Description
 ERD
 Activity Diagram
 Class Diagram
 Object Diagram
 Sequence Diagram/Collaboration Diagram

03 System Design

 Converting ERD to Tables

 Component Diagram
 Package Diagram
 Deployment Diagram
 System flow chart
 Structure chart(Program level & System level)

3
 Automobile

04 System Coding

 Menu Tree
 List of tables with attributes and constraints
Program Description

 Validations
 Test Cases, Test Data and Test Results
 Screen Layouts & Report Layouts
 Program Listing

05 System Implementation

06 Future Enhancements

07 References and Bibliography

4
 Automobile

01. Preliminary Investigation

5
 Automobile

1.Introduction

In today’s world Computer System is one of the integral part of out life.
Computers have made the life and lifestyle of corporate world to common
man ease to a great extend.

The use of software in corporate world has made the functioning of the
organization smooth and efficient. Due to this the industry is able to keep the
track of its progress and maintain the records. These records can be easily
accessed and thus help the organization to know it’s functioning & track the
success & failures of the processes. This helps the organization to grow.

1.1 Existing System

Our client who owns a automobile showroom , currently has an computerised
system which is used to create , maintain, retrieve,update and delete data
from the system.

This system used by the client is in form of Excel sheet and Word documents.

The Excel sheet is mostly being used to keep track of the inventory, to check
howmany products are available , to place a new order is the number of
products in stock is less.

Also the word documents are used to generate bills and reports. Bills are used
as a proof of sales and the delivery to the product.

6
 Automobile

When the showroom started, the Word and Excel documents worked fine, but
as the time passed by, the data of the showroom went on increasing and it
started taking more time to insert,update,retrieve,delete and maintain data.

At this point of time, our client has many customers and to maintain the data
of such a high number of customers through Word doucuments and Excel
sheets becomes very time consuming and can also lead to errors in some
cases.These errors can be fatal in todays competiotional world.

Also there used to be confusion in some cases , where the customers of the
showroom had same last name, also not everyone in the showroom were
good at Excel to maintain the Excel sheets.

Hence there is a need of an easy to use software which has a very simple and
user friendly Graphical User Interface(GUI), and also at the same time can
insert , update, retrieve data from the software easily.

1.2 Literature Survey

Technology Overview

A major element in building a system is the selection of compatible software

since the software in the market is experiencing a geometric progression.
Selected software should be acceptable to the firm and the user as well as it

should be feasible for the system. The system is developed in VB.NET 2005 and
SQL Server 2005 for use on Windows environment.

The software we have used for our project is Visual Studio 2005 for Designing
and Coding and Reports. SQL Server 2005 for Database .

7
 Automobile

VB.Net:

Visual Basic .NET (VB.NET) is an object-oriented computer programming

language that can be viewed as an evolution of Microsoft's Visual Basic (VB)
which is generally implemented on the Microsoft .NET Framework. Microsoft
currently supplies Visual Basic Express Edition free of charge. Visual Basic
.NET provides the easiest, most productive language and tool for rapidly
building Windows and Web applications

Visual Basic .NET comes with enhanced visual designers, increased application
performance, and a powerful integrated development environment (IDE). It
also supports creation of applications for wireless, Internet-enabled hand-held
devices.

Features of VB.NET

Powerful Windows-based Applications

Powerful Windows-based Applications

Simplified Deployment

Powerful, Flexible, Simplified Data Access

Improved Coding

Direct Access to the Platform

Full Object-Oriented Constructs

XML Web Services

Mobile Applications

8
 Automobile

COM Interoperability

Reuse Existing Investments

Upgrade Wizard

SQL SERVER 2005:

Microsoft SQL Server 2005 provides the database developer the opportunity to
locate programming code in native formats or create server-driven complex
systems. The .NET framework, in combination with the SQL Server 2005,
delivers the functionality of the powerful class library in combination with
modern programming languages. Common Language Runtime (CLR) is used to
code procedures, triggers and functions within the chosen language in the
.NET framework. Using object-oriented constructs such as structured
exception handling, namespaces, classes and arrays assist the programmer in
effectively handling procedural issues when programming with SQL Server
2005.

Feature of SQL SERVER 2005

Feature Description

9
 Automobile

Database Mirroring Extend log shipping capabilities with the

database mirroring solution. You will be
able to use database mirroring to enhance
availability of your SQL Server systems by
setting up automatic failover to a standby
server.

Online Restore With SQL Server 2005, database

administrators are able to perform a
restore operation while an instance of SQL
Server is running. Online restore improves
the availability of SQL Server because only
the data being restored is unavailable; the
rest of the database remains online and
available.

Online Indexing Operations The online index option allows concurrent

modifications (updates, deletes, and
inserts) to the underlying table or
clustered index data and any associated
indexes during index data definition
language (DDL) execution. For example,
while a clustered index is being rebuilt, you
can continue to make updates to the
underlying data and perform queries
against the data.

Fast Recovery A new faster recovery option improves

availability of SQL Server databases.
Administrators can reconnect to a
recovering database after the transaction
log has been rolled forward.

Standards-based Information Any object, data source, or business

10
 Automobile

Access intelligence component can be exposed

using standards-based protocols such as
SOAP and HTTP—eliminating the need for
a middle-tier listener, such as IIS, to access
a Web services interface that is exposed by
SQL Server 2005.

SQL Server Management Studio SQL Server 2005 includes SQL Server
Management Studio, a new integrated
suite of management tools with the
functionality to develop, deploy, and
troubleshoot SQL Server databases, as well
as enhancements to previous functionality.

Dedicated Administrator SQL Server 2005 provides a dedicated

Connection administrator connection that
administrators can use to access a running
server even if the server is locked or
otherwise unavailable. This capability
enables administrators to troubleshoot
problems on a server by executing
diagnostic functions or Transact-SQL
statements.

Snapshot Isolation Snapshot Isolation (SI) level is provided at

the database level. With SI, users can
access the last committed row using a
transitionally consistent view of the
database. This capability provides greater
scalability.

Data Partitioning Data partitioning is enhanced with native

table and index partitioning that enables
efficient manageability of large tables and

11
 Automobile

indexes.

Hosted Common Language With SQL Server 2005 developers can

Runtime create database objects using familiar
languages such as Microsoft Visual C# .NET
and Microsoft Visual Basic .NET.
Developers can also create two new
objects—user-defined types and
aggregates.

Native XML Support Native XML data can be stored, queried,

and indexed in a SQL Server database—
allowing developers to build new classes of
connected applications around Web
services and across any platform or device.

ADO.NET version 2.0 From new support for SQL Types to

Multiple Active Result Sets (MARS),
ADO.NET in SQL Server 2005 evolves
dataset access and manipulation to
achieve greater scalability and flexibility.

Security Enhancements The security model in SQL Server 2005

separate users from objects, provides fine-
grain access, and enables greater control
of data access. Additionally, all system
tables are implemented as views, providing
more control over database system
objects.

Transact-SQL Enhancements SQL Server 2005 provides new language

capabilities for developing scalable
database applications. These
enhancements include error handling,
recursive query capabilities, relational

12
 Automobile

operator PIVOT, APPLY, ROW_NUMBER

and other row ranking functions, and
more.

Reliable Messaging for Service Broker is a robust messaging

Asynchronous Applications infrastructure that provides reliable
transactional delivery of critical messages
between servers—with the scalable high-
performance that is expected with
asynchronous queuing.

Visual Studio Integration Tight integration with Microsoft Visual

Studio and the .NET Framework
streamlines development and debugging of
data-driven applications.

Web Services With SQL Server 2005 developers can

develop Web services in the database tier,
making SQL Server a hypertext transfer
protocol (HTTP) listener and providing a
new type of data access capability for Web
services-centric applications.

Replication Enhancements For distributed databases, SQL Server 2005

provides comprehensive schema change
(DDL) replication, next-generation
monitoring capabilities, built in replication
from Oracle to SQL Server, merge
replication over https, and significant
merge replication scalability and
performance improvements. Additionally,
the peer-to-peer transactional replication
feature improves support for data scale
out using replication

13
 Automobile

Embedded Reports Use client-side reporting controls to

embed real-time reports into an
application at design time

Time: In normal as well as peak condition the data can be retrieved by just a
click of second.

Volume: Any number of records cab be stored.

Availability: Data is available to user as soon as the user entre the required
information.

1.3 Scope of the Project

The proposed system for the Automobile showroom will be developed in

Visual Studio 2005 and SQL Server 2005 will be used in backend.

This new system will allow the users to quickly insert, delete, update and
retrieve data from the system.

This new system will allow security to the data, by mean of authorizing users.

14
 Automobile

Only those users who have a valid user-id and password can access the system.

Thus those people who do not have the access rights cannot use the system
and thus the data can be secured by means of unauthorized access.

Also the proposed system will have an MDI form, which will provide a single
page control. By mean of the MDI form the user of the system can go to
different options of the system from the single page itself.

This will provide an easy to use software in term of GUI and also the time of
the user will be saved.

1.4 Objective of Project

 Information storage of customer, vehicle supplying company, employees

details, workshop etc.

 Date storage of customer payments, discounts offered and rates

applicable with effective from the predefined date / period.

 Department or user wise relevant screens for type of job / profile

handled.

 User access control and rights management.

 Configurable tracking system for internal tracking as well as during the

audits.

 Uploading facility for the information received in soft copy to the

system.

15
 Automobile

 Payment details of the employees as per the work done.

1.5 Project Methodology

Some programs are written around “what is happening” and others are
written around “who is being affected”. The first way is called Structure or
Procedure oriented model. This approach characteristics a program as a series
of linear steps (that is code).Here code acts on data.

To manage the increasing complexity, the second way i.e. the Object-Oriented
approach was conceived.

Object-oriented programming organizes a program around the data and a set

of well-defined interfaces to that data. Here there is data controlling access to
code.

Object Orientation is an approach to software development that organizes

both the problem and its solution as a collection of discrete objects; both data
structure and behavior are included in the representation.

Object oriented representation is recognized by its seven characteristics:

Identity, Abstraction, Classification, Encapsulation, Inheritance, Polymorphism

And Persistence

The main property which we have used is that of Persistence: the ability of an
object’s name, state and behaviors are saved as the object is transformed.

An Object Oriented process uses the encapsulation of data and behavior to

form independent units (objects).The same constructs represent the system
from the requirements to the application’s implementation and testing. Thus

16
 Automobile

Object Oriented is a philosophy of problem and solution representation, not a

software Life cycle by itself.

Indeed OO can be used in many different software life cycles from waterfall to
spiral model.

In general, OO deals with requirements, high-level design, coding and testing

but not necessarily in a sequential fashion; the sequence is determined by the
life-cycle, not by the OO representation.

FEASABILITY STUDY
The feasibility study is divided into three different parts:
 Operational Feasibility
 Technical Feasibility
 Economic Feasibility

 OPERATIONALFEASABILITY:
The employees were not comfortable with the manual system. The software
developed will lead to heavy reduction in the amount of paperwork. The new
system will decrease work load, strain, work time, manual calculation and will
lead to error free and accurate work. The software will be easy to use.

There will reduction in the space required to store all the paper work, and
will lead to less confusion.

Information about different products, database about the customers,

employees service details can be easily retrieved from the system.

Any person with a basic knowledge of computers can also use this
software.

 TECHNICAL FEASABILITY:

17
 Automobile

Technical feasibility centers around the existing computer system (HW/SW)

and to what extends it can support the proposed additions.
Support for the software is readily available. There is no need for a technical
person to supervise the working of the software. The proposed system is user
friendly. There is just one operator needed to use the system, rather than so
many people needed to keep track of the documents.

 ECONOMIC FEASABILITY
The proposed system is economically feasible. As the hardware and the
software used are already available, there is no need to buy a new copy of
the software thus maintaining the budget.

STAKE HOLDERS
A corporate stake holder is a party that can affect or be affected by the
actions of the business as a whole

TYPES OF STAKE HOLDERS:

 Internal stake holder

Internal stake holders-Market (or primary)Stake holders are those that are
engaged in economic transactions with the business.

 External stake holder:

External stake holders-Non market(or secondary) stake holders are those
who although they do not engaged in direct economic exchange with the
business are affected by or can affect its actions.
 Owner

18
 Automobile

The owner of the admission system needs to keep a check on

everything which is visiting admission system about each and every
registration and viewing and making changes i.e.upadate, delete etc. this is one
of the important issue to be handled

 Member

The add new member then enter the l fields in correct in all the
textboxes.

 Book
Add new Book then all fields are properly field the quantity of book
correctly mention

19
 Automobile

GANTT CHART

Task Name Jun Jul Aug Sep Oct Nov Dec Jan

Planning for the system for

Library

Defining Problem
Defining Current System
Developing Current System

System Analysis
Fact Finding
Use Case Diagram
Object Diagram
Activity Diagram
Sequence/Collaboration Diagram

System Design
Convert ERD into Tables
Component Diagram
Package Diagram
Deployment Diagram
System Flow Chart

System Coding
Menu Tree
Program/Report List
List of Tables with Attribute
Validation
Test Cases, Test Data & Test
Layout

System Implementation
Future Enhancement
Project Report Submission

20
 Automobile

02.System Analysis

21
 Automobile

 EVENT TABLE
EVENT TRIGGER SOURCE ACTIVITY RESPONSE DESTINATION

Add Employee Employee Employee Add Employee Information Employee

details details saved

Update Update Employee update Information Employee

Employee Employee updated
Employee
details details

Add Model Add Model Model Add Model Information Model

detail details saved

Add Customer Add Customer Customer Add Customer Information Customer

details details updated

Add Supplier Add Supplier Supplier Add Supplier Supplier added Supplier
details

Payment Payment Payment Payment Payment Payment

Details Details Details updated

Sales Report Generate sales sales sales details Information sales

saved

Purchase Generate Purchase Purchase Information Purchase

Report Purchasing details saved

22
 Automobile shop management

UML Diagrams
The underlying premise of UML is that no one diagram can capture the different
elements of a system in its entirety. Hence, UML is made up of nine diagrams that can be
used to model a system at different points of time in the software life cycle of a system.
The nine UML diagrams are:

 Use case diagram

 Class diagram
 Object diagram
 State diagram
 Activity diagram
 Sequence diagram
 Collaboration diagram
 Component diagram
 Deployment diagram
Now that we have an idea of the different UML diagrams, let us see if we can somehow
group together these diagrams to enable us to further understand how to use them.

 UML Diagram Classification—Static, Dynamic, and

Implementation
A software system can be said to have two distinct characteristics: a structural, "static"
part and a behavioral, "dynamic" part. In addition to these two characteristics, an
additional characteristic that a software system possesses is related to implementation.
Before we categorize UML diagrams into each of these three characteristics, let us take a
quick look at exactly what these characteristics are.

 Static: The static characteristic of a system is essentially the structural aspect of

the system. The static characteristics define what parts the system is made up of.
 Dynamic: The behavioral features of a system; for example, the ways a system
behaves in response to certain events or actions are the dynamic characteristics
of a system.
 Implementation: The implementation characteristic of a system is an entirely
new feature that describes the different elements required for deploying a
system.

The UML diagrams that fall under each of these categories are:

23
 Automobile shop management

 Static

Use case diagram

o
o Class diagram
 Dynamic
o Object diagram
o State diagram
o Activity diagram
o Sequence diagram
o Collaboration diagram
 Implementation
o Component diagram
o Deployment diagram

Finally, let us take a look at the 4+1 view of UML diagrams.

4+1 View of UML Diagrams

Considering that the UML diagrams can be used in different stages in the life cycle of a
system, let us take a look at the "4+1 view" of UML diagrams. The 4+1 view offers a
different perspective to classify and apply UML diagrams. The 4+1 view is essentially
how a system can be viewed from a software life cycle perspective. Each of these views
represents how a system can be modeled. This will enable us to understand where exactly
the UML diagrams fit in and their applicability.

These different views are:

 Design View
 Process View
 Component View
 Deployment View
 Use case View

24
 Automobile shop management

USE CASE DIAGRAM

The Use case diagram is used to identify the primary elements and processes that
form the system. The primary elements are termed as "actors" and the processes
are called "use cases." The Use case diagram shows which actors interact with
each use case.
.

 Use case diagram: The use case diagram is used to identify the primary elements
and processes that form the system. The primary elements are termed as
"actors" and the processes are called "use cases." The use case diagram shows
which actors interact with each use case.


Add
Employee

Add Supplier

Add
Employee
Customers

Add Product

Admin
Sales
Product

Add 25
Payment
 Automobile shop management

ER Diagram for library Management system

Payment

Customer Sal
Pa tak
y e

tak
e

Product
On
Purch

On

ha
s Registra
Sales

26
 Automobile shop management

 Activity Diagram
 Basics
The easiest way to visualize an Activity diagram is to think of a flowchart of a code. The
flowchart is used to depict the business logic flow and the events that cause decisions and
actions in the code to take place.

27
 Automobile shop management

CLASS DIAGRAM

 Class diagram: The class diagram is used to refine the use case
diagram and define a detailed design of the system. The class diagram
classifies the actors defined in the use case diagram into a set of
interrelated classes. The relationship or association between the classes
can be either an "is-a" or "has-a" relationship. Each class in the class
diagram may be capable of providing certain functionalities. These
functionalities provided by the class are termed "methods" of the class.
Apart from this, each class may have certain "attributes" that uniquely
identify the class.

28
 Automobile shop management

OBJECT DIAGRAM
Although we design and define classes, in a live application classes are not directly used,
but instances or objects of these classes are used for executing the business logic. A
pictorial representation of the relationships between these instantiated classes at any point
of time (called objects) is called an "Object diagram." It looks very similar to a class
diagram, and uses the similar notations to denote relationships.

Object diagram: The object diagram is a special kind of class diagram. An object is an
instance of a class. This essentially means that an object represents the state of a class
at a given point of time while the system is running. The object diagram captures the
state of different classes in the system and their relationships or associations at a given
point of time.

This class diagram shows that one customer can study in a single Book. Now, if we were
to add attributes to the classes "product" and " customer," we would have a diagram as
shown in Figure 5.2: Figure 5.2—the class diagram with attributes

29
 Automobile shop management

SEQUENCE DIAGRAM

Sequence diagram: A sequence diagram represents the interaction between different

objects in the system. The important aspect of a sequence diagram is that it is time-
ordered. This means that the exact sequence of the interactions between the objects
is represented step by step. Different objects in the sequence diagram interact with
each other by passing "messages".

A Sequence diagram is two-dimensional in nature. On the horizontal axis, it shows the

life of the object that it represents, while on the vertical axis, it shows the sequence of
the creation or invocation of these objects. Because it uses class name and object name
references, the Sequence diagram is very useful in elaborating and detailing the
dynamic design and the sequence and origin of invocation of objects.

30
 Automobile shop management

03.System Design

31
 Automobile shop management

Converting ERD TO Tables:

32
 Automobile shop management

Purchase
Customer Payment
Customer ID Purchase ID
Customer Name Bike ID Payment ID
Address Sales ID Customer Name
Gender Product ID Sales ID
Price Product ID
Price

Registration
Product
Product ID RegistrationNo
Makers Name Registration Date
Bike Model Product ID
Price Address

Sales

Sales ID
Payment ID
Customer Name
Total Amount

Component Diagram

 Basics
The different high-level reusable parts of a system are represented in a Component
diagram. A component is one such constituent part of a system. In addition to

33
 Automobile shop management

representing the high-level parts, the Component diagram also captures the inter-
relationships between these parts.

 The component diagram represents the high-level parts that make up the system.
This diagram depicts, at a high level, what components form part of the system
and how they are interrelated. A component diagram depicts the components
culled after the system has undergone the development or construction phase.

Secondly, a component must provide an interface to enable other components to interact

and use the services provided by the component. Elements of a Component Diagram

34
 Automobile shop management

PACKAGE DIAGRAM
A package provides the ability to group together classes and/or interfaces that are either
similar in nature or related. Grouping these design elements in a package element
provides for better readability of class diagrams, especially complex class diagrams.

35
 Automobile shop management

DEPLOYMENT DIAGRAM

The deployment diagram captures the configuration of the runtime elements of the
application. This diagram is by far most useful when a system is built and ready to be
deployed.

This diagram is by far more useful when a system is built and ready to be deployed. But,
this does not mean that you should start on your deployment diagram after your system is
built. On the contrary, your deployment diagram should start from the time your static
design is being formalized using, say, class diagrams. This deployment diagram then
evolves and is revised until the system is built

Deployment Diagram

Figure 2 Deployment diagram for the Automobileshop Management System

Figure 2 shows the Deployment diagram for the Automobile shop Management System.
The deployment diagram shows the three nodes PRD_WEB_SERVER,
PRD_APP_SERVER, and PRD_DB_SERVER that represent the nodes for the Web
server, application server, and database server, respectively. The View, Controller, and
Model components are depicted in the application server node and the three nodes are
interconnected to denote association between them in the Automobile shop Management
System.

36
 Automobile shop management

SYSTEM FLOW CHART:

***************

Create
Employee Employee Details Employee
Record

Add payment
Product
Record
New
Registration product
Process
Payment

Report
Add customer

product

purchase Purchase Book Purchase Purchase

And Record report
sales
Process
sales
Sales Record
S sales report

37
 Automobile shop management

STRUCTURED CHART:

Automobile Shop
Management System

Employee Record Sales record Customer

Record Supplier Record Maintain payment

Employe Details Sales Details cuctomer Details Supplier Detail Maintain

s
Payment

Add Employee Add Sales Add Customer Add Supplier Payment

Details Details Detail Details Type

UpdateEmploye Update Sales View Customer Update Supplier

e Details Details Details

Delete Employe Delete Sales Update Delete supplier

Details Details customer Details

38
Automobile shop management

39
 Automobile shop management

4. System Coding

40
 Automobile shop management

MENU TREE
Automobile Shop Management
System

Master

Sales

Employee

Supplier

Customer
Data Report
Purchase

Sales Detail
Product
Payment Detail

Purchase Datail Payment

User Set Up

Search
Help
Employee
About us
Supplier
Help
Sales

Customer
41
 Automobile shop management

List Of Tables And Attributes

Employee Master

Employee Id

Personal Details

Name

Age

Sex

Address

C/o Person Details

Customer Master

Name

Address

Contact details

Supplying Company Master

Name

Address

Contact Details

Country

42
 Automobile shop management

Item Master

Model No.

Colour

Engine No.

Engine Capacity (CC)

Sales Master

Description

Colours

Engine Capacity (CC)

Rate / Cost

Discounts Offered

Stock

Stock register

Day – to – Day stock details

43
 Automobile shop management

Program Description

I.] Administrator.

Administrator is must be an authorized user. He can further change the password. There is the
facility for password recovery, logout etc.

The main aim of the entire activity is to automate the process of Library Management System
that includes Add Employee, Add Product, Add Supplier, Add payment, etc.

The limited time and resources have restricted us to incorporate, in this project, only main
activities that are performed in a Auto Mobile Shop Management System, but utmost care has
been taken to make the system efficient and user friendly. " Auto Mobile Shop Management
System" has been designed to computerize the following functions that are performed by the
system:

[1]Maintain Employee Information

[a]Add Employee Information

[b]Update Employee Information

[c]Delete Information

[2]Purchase

[a]Purchase Date.

[3] Payment Record

44
 Automobile shop management

[4] Customer Record

[a] Customer ID

[b] Customer r Name.

[c] Customer Address

[d] Customer Contact Number

[5] Supplier Record

[a] Supplier ID

[b] Supplier Name.

[c] Supplier r Address

[d] Supplier Contact Number

45
 Automobile shop management

VALIDATIONS

1. Check whether the Administrator of Library has entered valid values for
username and password.

2. Check the Employee details are perfect.

3. Check the Employee is correct for Updated.

4. Check whether the textboxes are properly filled

5. Check whether any unauthorized person is trying to access.

6. Check whether customer has correctly purchase.

7. Check details are payment.

8. Check availability of model.

9. Check the Supplier information is correctly stored.

10. Check the customer information is correctly stored.

11. Check whether the correct contact number is filled.

46
 Automobile shop management

Test Cases

Form Valid Data In Valid Data

Add All Field are Compulsory Empty Fields, alphabets in quantity

Employee

purchase All Field are Compulsory Empty Fields

Add All Field are Compulsory Empty Fields, alphabets in Contact No.
Supplier

Add All Field are Compulsory Empty Fields, alphabets in Contact No.
customer

product All Field are Compulsory Empty Fields

payment All Field are Compulsory Empty Fields

Control Valid Data In Valid Data

Contact no. 096895874851 A,*,.,; ,1a ,0969858745842,mnji444448

Text Box

ModelQuan 6,5,8,10,3,55 48884admin,admin51465,admin….,ad

tity Text box min****,admin&&&&&,

47
 Automobile shop management

Splash Screen Form:

Login Form:
The login screen allows the security interface for the user interacting
with the system. Every time a user logs into the system he has the
appropriate rights to work with the system with some modules.

48
 Automobile shop management

ADD EMPLOYEE FORM:

This form use to add Employee.

49
 Automobile shop management

UPDATE EMPLOYEE FORM:

This form use to update Employee.

50
 Automobile shop management

NEW CUSTOMER FORM:

This form use to add Customer.

51
 Automobile shop management

NEW MODEL FORM:

This form use to add model.

52
 Automobile shop management

ADD SUPPLIER FORM:

This form use to add the supplier details.

53
 Automobile shop management

SEARCH SUPPLIER FORM:

This form use to search the supplier details.

54
 Automobile shop management

ADD PURCHASE FORM:

This form use to add the purchase details.

55
 Automobile shop management

SEARCH MODEL FORM:

This form use to search model.

ABOUT US FORM:
This is the about us form of Automobile shop Management
System

56
 Automobile shop management

Report OF Customer Form:

This form displays the customer report.

Report OF Payment Form:

This form displays the payment report.

57
 Automobile shop management

Report OF Purchase Form:

This form displays the purchase report.

Stock Form:
58
 Automobile shop management

This form displays the stock details.

SALES FORM:
Add sales Details information

59
Automobile shop management

60
 Automobile shop management

REGISTRATION FORM:
Add registration information

61
 Automobile shop management

ADD NEW USER:

This is use to add new user.

62
 Automobile shop management

PAYMENT FORM
This is use to give payment

63
 Automobile shop management

SEARCH PAYMENT DETAIL FORM:

This is use to search payment.

64
 Automobile shop management

SEARCH REGISTRATION FORM

This is use to search registration details

65
 Automobile shop management

SEARCH EMPLOYEE FORM

To search employee detail.

66
 Automobile shop management

PROGRAM LIST

Form Name Form Caption Description

FRM_CREATE_EMPLOYEE EMPLOYEE RECORD This form used to create the member

employee.

FRM_ EMPLOYEE Update Update Employee FORM This form updates the details.

FRM_Customer Customer Detail This form stores the Customer details.

FRM_Model Add Model Details This form Add Model Details.

FRM_Supplier Add Supplier Details This form used to Supplier details.

FRM_STOCK Add STOCK Form This form used to add stock details.

FRM_ABOUT ABOUT US This is About us form, displaying about us

information.

FRMLOGIN LOGIN This login is for entering into the system.

MDI_AUTO MOBILE SHOP WELCOME TO MOBILE SHOP This is the MDI form of which all the above
MANAGEMENT SYSTEM MANAGEMENT SYSTEM forms are child forms of this.

FRM_User Set User Form This is use store user in user master

67
 Automobile shop management

REPORT LIST

Report name Report Caption Description

PURCHASE PURCHASE DETAIL REPORT purchase wise maintain the purchase

INFORMATION information.

PAYMENT REPORT PAYMENT DETAIL REPORT Payment wise maintains report.

CUSTOMER INFORMATION CUSTOMER DETAIL REPORT maintain customer report

68
 Automobile shop management

05.System Implementation

69
 Automobile shop management

System Implementation
After the completion of each module, a small working model with the required
database was created and Installed on the Work Area for the respective Module.
The Users were trained to use the system and their responses and suggestions for
updating were noted. The same were implemented wherever possible and the
updated copy of the Model was once again installed and the same above
procedure was repeated till the end user was satisfied sufficiently with the
system.

The same procedure was repeated with the full system fill the end users were
fully satisfied with the System.

For making an exe file select make project name.exe under the File menu.

Once the user has completed with the coding the application, and tested on
multiple machines, it is ready to be deployed. In order to deploy any application,
the user can use the Package and Deployment Wizard Provided by Microsoft. The
prerequisite of deploying an application is packaging.

To Package your application perform the following steps:

Start the Package and Deployment Wizard.

 After selecting the administration module project, click on the Package
button.
 As per the requirements, select the type of packaging as Standard Setup
Package.

70
 Automobile shop management

The Wizard will then takes over and perform the rest of the packaging steps for
you. You will see all the required files, including the runtime files, automatically
being included.To deploy your application, perform the following steps: -

 Select the package you want to deploy, and click on the Deploy button.
a) Select the Deployment method. In this case, it will be Folder. The wizards
will then take over and perform the rest of the deployment steps for you.

06.FUTURE
ENHANCEMENT
71
 Automobile shop management

FUTURE ENHANCEMENT

Future enhancement about the project would be as following:

1. The first up gradation would be the support for the examination

system along with.

2. The support for the networking system environment

3. Adding employee, product, supplier, customer Details

4. Other employee requirements

5. Maintain the sales & purchase Procedure

6. Other possibilities

72
 Automobile shop management

07. References and

Bibliography

73
 Automobile shop management

BIBLIOGRAPHY

References Books:
 System Analysis, Design Written by: S. Parthasarthy

 Introduction to Software Engineering Written by: S. Parthasarthy

 System Analysis and Design Written by: Sain James

 Software Engineering Written by: Roger Pressman

 Software Engineering Written by: Pankaj Jalote

 Project Management Written by: K.R.Sharma

74
Automobile shop management

75