PROJECT REPORT ON
Automobile shop MANAGEMENT SYSTEM
SUBMITTED BY:
Viraj koliUNDER THE GUIDENCE OF
PROFESSOR.
Mrs.2010-2011
Acknowledgement
*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)
04System Coding Menu Tree List of tables with attributes and
constraintsProgram Description Validations Test Cases, Test Data
and Test Results Screen Layouts & Report Layouts Program
Listing
05
System Implementation
06
Future Enhancements
07References and Bibliography
01. Preliminary Investigation
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.
1.1 Existing SystemOur 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.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 .
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 .NETprovides 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 ApplicationsPowerful Windows-based
ApplicationsSimplified DeploymentPowerful, Flexible, Simplified
Data AccessImproved CodingDirect Access to the PlatformFull
Object-Oriented ConstructsXML Web ServicesMobile ApplicationsCOM
InteroperabilityReuse Existing InvestmentsUpgrade 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
FeatureDescription
Database MirroringExtend 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 RestoreWith 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 OperationsThe 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 RecoveryA 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 AccessAny object, data source, or
business intelligence component can be exposed using
standards-based protocols such as SOAP and HTTPeliminating 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 StudioSQL 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 ConnectionSQL Server 2005 provides a
dedicated 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 IsolationSnapshot 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 PartitioningData partitioning is enhanced with native table
and index partitioning that enables efficient manageability of
large tables and indexes.
Hosted Common Language RuntimeWith SQL Server 2005 developers
can create database objects using familiar languages such as
Microsoft Visual C# .NET and Microsoft Visual Basic .NET.
Developers can also create two new objectsuser-defined types and
aggregates.
Native XML SupportNative XML data can be stored, queried, and
indexed in a SQL Server databaseallowing developers to build new
classes of connected applications around Web services and across
any platform or device.
ADO.NET version 2.0From 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 EnhancementsThe 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 EnhancementsSQL Server 2005 provides new language
capabilities for developing scalable database applications. These
enhancements include error handling, recursive query capabilities,
relational operator PIVOT, APPLY, ROW_NUMBER and other row ranking
functions, and more.
Reliable Messaging for Asynchronous ApplicationsService Broker
is a robust messaging infrastructure that provides reliable
transactional delivery of critical messages between serverswith the
scalable high-performance that is expected with asynchronous
queuing.
Visual Studio IntegrationTight integration with Microsoft Visual
Studio and the .NET Framework streamlines development and debugging
of data-driven applications.
Web ServicesWith 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 EnhancementsFor 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
Embedded ReportsUse 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.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.
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 PersistenceThe main
property which we have used is that of Persistence: the ability of
an objects 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
applications implementation and testing. Thus 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 STUDYThe 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: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 FEASABILITYThe 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 HOLDERSA corporate stake holder is a party that can affect
or be affected by the actions of the business as a wholeTYPES OF
STAKE HOLDERS:
Internal stake holderInternal 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 Add new Book then all fields are properly
field the quantity of book correctly mention GANTT CHART
Task NameJunJulAugSepOctNovDecJan
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
02.System Analysis EVENT TABLEEVENTTRIGGER SOURCE ACTIVITY
RESPONSEDESTINATION
Add EmployeeEmployee detailsEmployeeAdd Employee
detailsInformation savedEmployee
UpdateEmployeeUpdate Employee detailsEmployee update Employee
detailsInformation updatedEmployee
Add ModelAdd Model detailModelAdd Model detailsInformation
savedModel
Add CustomerAdd Customer detailsCustomerAdd Customer
detailsInformation updatedCustomer
Add SupplierAdd Supplier detailsSupplierAdd SupplierSupplier
addedSupplier
Payment DetailsPayment DetailsPaymentPayment DetailsPayment
updatedPayment
Sales ReportGenerate salessalessales detailsInformation
savedsales
Purchase ReportGenerate PurchasingPurchasePurchase
detailsInformation savedPurchase
Automobile shop management
14
UML DiagramsThe 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 diagramNow 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 ClassificationStatic,
Dynamic, and ImplementationA 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: Static Use case diagram
Class diagram Dynamic Object diagram State diagram Activity diagram
Sequence diagram Collaboration diagram Implementation Component
diagram Deployment diagramFinally, let us take a look at the 4+1
view of UML diagrams.4+1 View of UML DiagramsConsidering 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
USE CASE DIAGRAMThe 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 EmployeeAdd SupplierAdd
CustomersAdd PaymentSales ProductAdd Product
AdminEmployee
ER Diagram for library Management system
CustomerProductSalestakeOnPayPaymentSales Purchase
takeRegistraion hasOn
Activity Diagram BasicsThe 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.
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.
OBJECT DIAGRAMAlthough 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
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.
03.System Design
Converting ERD TO Tables:
CustomerCustomer IDCustomer Name AddressGender
ProductProduct IDMakers NameBike ModelPrice
PurchasePurchase IDBike IDSales IDProduct IDPrice
RegistrationRegistrationNoRegistration DateProduct ID
Address
SalesSales IDPayment IDCustomer NameTotal Amount
PaymentPayment IDCustomer NameSales IDProduct IDPrice
Component Diagram BasicsThe 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 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
PACKAGE DIAGRAMA 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.
DEPLOYMENT DIAGRAMThe 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 builtDeployment Diagram
Figure 2 Deployment diagram for the Automobileshop Management
SystemFigure 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.
SYSTEM FLOW CHART:
***************
STRUCTURED CHART:
Automobile Shop Management System
4. System Coding
List Of Tables And AttributesEmployee MasterEmployee IdPersonal
DetailsNameAgeSexAddressC/o Person Details
Customer MasterName AddressContact details
Supplying Company MasterNameAddressContact DetailsCountry
Item MasterModel No.ColourEngine No.Engine Capacity (CC)
Sales MasterDescriptionColoursEngine Capacity (CC)Rate /
CostDiscounts Offered
StockStock registerDay to Day stock details
Program DescriptionI.] 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[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
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.
Test Cases
FormValid DataIn Valid Data
Add EmployeeAll Field are CompulsoryEmpty Fields, alphabets in
quantity
purchaseAll Field are CompulsoryEmpty Fields
Add SupplierAll Field are CompulsoryEmpty Fields, alphabets in
Contact No.
Add customerAll Field are CompulsoryEmpty Fields, alphabets in
Contact No.
productAll Field are CompulsoryEmpty Fields
paymentAll Field are CompulsoryEmpty Fields
ControlValid DataIn Valid Data
Contact no. Text Box096895874851A,*,.,; ,1a
,0969858745842,mnji444448
ModelQuantity Text
box6,5,8,10,3,5548884admin,admin51465,admin.,admin****,admin&&&&&,
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.
ADD EMPLOYEE FORM:This form use to add Employee.
UPDATE EMPLOYEE FORM:This form use to update Employee.
NEW CUSTOMER FORM:This form use to add Customer.
NEW MODEL FORM:This form use to add model.
ADD SUPPLIER FORM:This form use to add the supplier details.
SEARCH SUPPLIER FORM:This form use to search the supplier
details.
ADD PURCHASE FORM:This form use to add the purchase details.
SEARCH MODEL FORM:This form use to search model.
ABOUT US FORM:This is the about us form of Automobile shop
Management System
Report OF Customer Form:This form displays the customer
report.
Report OF Payment Form:This form displays the payment
report.
Report OF Purchase Form:This form displays the purchase
report.
Stock Form:This form displays the stock details.
SALES FORM:Add sales Details information
REGISTRATION FORM:Add registration information
ADD NEW USER:
This is use to add new user.
PAYMENT FORMThis is use to give payment
SEARCH PAYMENT DETAIL FORM:This is use to search payment.
SEARCH REGISTRATION FORM
This is use to search registration details
SEARCH EMPLOYEE FORMTo search employee detail.
PROGRAM LISTForm NameForm Caption
Description
FRM_CREATE_EMPLOYEEEMPLOYEE RECORDThis form used to create the
member employee.
FRM_ EMPLOYEE UpdateUpdate Employee FORMThis form updates the
details.
FRM_CustomerCustomer DetailThis form stores the Customer
details.
FRM_ModelAdd Model DetailsThis form Add Model Details.
FRM_SupplierAdd Supplier DetailsThis form used to Supplier
details.
FRM_STOCKAdd STOCK FormThis form used to add stock details.
FRM_ABOUTABOUT USThis is About us form, displaying about us
information.
FRMLOGINLOGINThis login is for entering into the system.
MDI_AUTO MOBILE SHOP MANAGEMENT SYSTEMWELCOME TO MOBILE SHOP
MANAGEMENT SYSTEMThis is the MDI form of which all the above forms
are child forms of this.
FRM_UserSet User FormThis is use store user in user master
REPORT LISTReport name
Report Caption
Description
PURCHASE INFORMATIONPURCHASE DETAIL REPORTpurchase wise maintain
the purchase information.
PAYMENT REPORT PAYMENT DETAIL REPORTPayment wise maintains
report.
CUSTOMER INFORMATIONCUSTOMER DETAIL REPORTmaintain customer
report
05.System Implementation
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.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
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
07. References and Bibliography
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
Employee RecordEmployee DetailssalespurchaseproductAdd
customerRegistrationAdd paymentCreate Employee
New product Process
Product Record
Payment Report
Purchase RecordSales Record Purchase And sales Process
BookPurchase report
S sales report
Sales recordEmployee Record Customer Record
Supplier Record Maintain payment
Maintains Paymentcuctomer DetailsSales DetailsEmploye
DetailsSupplier Detail
Add EmployeeDetailsAdd CustomerDetailAdd Sales Details
PaymentTypeAdd SupplierDetails
UpdateEmployee DetailsUpdate Supplier DetailsView CustomerUpdate
SalesDetails
Delete Employe DetailsDelete supplierDetailsUpdate
customerDelete Sales Details
MENU TREEHelpAutomobile Shop Management SystemPayment
DetailAbout
usSalesPurchaseProductPaymentSupplierCustomerEmployeeCustomerSalesSupplierSearchHelpSales
DetailData ReportEmployeeMaster
Purchase DatailUser Set Up
