Automobile Shop MANAGEMENT SYSTEM
Automobile Shop MANAGEMENT SYSTEM
Automobile Shop MANAGEMENT SYSTEM
PROJECT REPORT ON
Viraj koli
UNDER THE GUIDENCE OF
PROFESSOR.
Mrs.
2010-2011
Acknowledgement
01
Contents
Preliminary Investigation
02
Organizational Overview
Description of System
Limitation of present system
Proposed system and is adv.
Feasibility Study
Stakeholders
Gantt chart
System Analysis
03
Event Table
Use case Diagram & use case Description
ERD
Activity Diagram
Class Diagram
Object Diagram
Sequence Diagram/Collaboration Diagram
System Design
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
1.Introduction
In todays 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 its functioning & track the
success & failures of the processes. This helps the organization
to grow.
VB.Net:
Features of VB.NET
Powerful Windows-based Applications
Feature
Description
Database Mirroring
Online Restore
Online Indexing
Operations
Standards-based
Information Access
SQL Server
Management Studio
11
Snapshot Isolation
Data Partitioning
Hosted Common
Language Runtime
Security
Enhancements
Transact-SQL
Enhancements
Visual Studio
Integration
Web Services
Replication
Enhancements
14
16
FEASABILITY STUDY
The feasibility study is divided into three different parts:
Operational Feasibility
Technical Feasibility
Economic Feasibility
OPERATIONALFEASABILITY:
18
19
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
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
20
Task Name
Jun
Jul
Au
g
Sep
Oct
Nov
Dec
Jan
21
22
02.System Analysis
23
EVENT TABLE
EVENT
TRIGGER
SOURCE
ACTIVITY
RESPONSE
DESTINATI
ON
Add
Employee
Employee
details
Employee
Add
Employee
details
Information
saved
Employee
Update
Update
Employee
details
Employee
update
Employee
details
Information
updated
Employee
Add Model
Add Model
detail
Model
Add Model
details
Information
saved
Model
Add
Customer
Add
Customer
details
Customer
Add
Customer
details
Information
updated
Customer
Supplier
Add Supplier
Supplier
added
Supplier
Employee
Payment
Details
Payment
Payment
Details
Payment
updated
Payment
Sales Report
Generate
sales
sales
sales details
Information
saved
sales
Purchase
Report
Generate
Purchasing
Purchase
Purchase
details
Information
saved
Purchase
24
1 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:
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.
25
The UML diagrams that fall under each of these categories are:
Static
Class diagram
Dynamic
o
Object diagram
State diagram
Activity diagram
Sequence diagram
Collaboration diagram
Implementation
o
Component diagram
Deployment diagram
Design View
Process View
Component View
Deployment View
Use case View
Add Employee
27
Add Supplier
Add
Add
Product
Add
Payment
Sales Product
Customers
Employe
Admin
28
O
n
29
30
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.
31
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.
32
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.2the class diagram with attributes
33
34
SEQUENCE DIAGRAM
35
03.System Design
36
37
38
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 Customer
to
representing the high-level parts, the Component diagram also captures the interCustomer ID
relationships between these parts.
Customer Name
Address
The component diagram represents the high-level parts that
Gender
Product
ID
Secondly, a component must provide an interface to enable other components
to interact
Makers Name
and use the services provided by the component. Elements of a Component Diagram
Bike Model
Price
39
40
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.
41
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 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.
42
***************
43
44
STRUCTURED CHART:
Automobile
Shop
Management
45
4. System Coding
46
47
Customer Master
Name
Address
Contact details
48
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
49
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
50
51
VALIDATIONS
52
Test Cases
Form
Valid Data
In Valid Data
Add
Employee
Empty Fields
Add
Supplier
Add
All Field are
customer Compulsory
product
Empty Fields
payment
Empty Fields
Control
Valid Data
In Valid Data
Contact
no. Text
Box
096895874851
A,*,.,; ,1a ,
0969858745842,mnji444448
ModelQua 6,5,8,10,3,55
ntity Text
48884admin,admin51465,admi
n.,admin****,admin&&&&&,
53
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.
54
55
57
58
59
60
61
62
ABOUT US FORM:
This is the about us form of Automobile shop
Management System
63
64
Stock Form:
65
SALES FORM:
Add sales Details information
66
67
REGISTRATION FORM:
Add registration information
68
69
PAYMENT FORM
This is use to give payment
70
71
72
73
PROGRAM LIST
Form Name
Form Caption
Description
FRM_CREATE_EMPLO
YEE
EMPLOYEE RECORD
FRM_ EMPLOYEE
Update
FRM_Customer
Customer Detail
FRM_Model
FRM_Supplier
FRM_STOCK
FRM_ABOUT
ABOUT US
FRMLOGIN
LOGIN
MDI_AUTO MOBILE
SHOP MANAGEMENT
SYSTEM
FRM_User
74
REPORT LIST
Report name
Report Caption
Description
PURCHASE
INFORMATION
PAYMENT REPORT
CUSTOMER
INFORMATION
75
05.System Implementation
76
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:
78
06.FUTURE
ENHANCEMENT
FUTURE ENHANCEMENT
6. Other possibilities
79
80
BIBLIOGRAPHY
References Books:
Software Engineering
Software Engineering
Project Management
81
82