STOCK MAINTENANCE

SYSTEM
MADURAI INSTITUTE OF ENGINEERING AND
TECHNOLOGY

PRESENTED BY
S.MUTHUMEENA
K.NARMATHASUNAMI
S.SAROJINI
INTRODUCTION

• Stock maintenance is an interface between the

customer and the sales person
• It aims at improving the efficiency in
maintaining the stocks
ABSTRACT
• This project is aimed at developing a desktop based application named
stock maintenance system for maintaining the stock system of any
organization.
• This system can be used to store the details of the stock, stock maintenance,
update the stock based on the sales details and generate sales and stock
report daily or weekly based.
• Stock maintenance system is important to ensure quality control in
businesses that handle transactions resolving around consumer goods.
• Without proper stock control a large retail store may run out of stock of an
important item.
• An automated stock maintenance system helps to minimize the errors while
recording the stock
OBJECTIVE
•To provide a complete version of a
stock maintenance system and to
manage the entire stock management
process of a company.
PURPOSE
• The entire process of stock maintenance is
done in manual manner considering the fact
that number of customers for purchasing is
increasing every year, a maintenance system is
essential to meet the demand.
• So this system uses several programming and
database techniques to elucidate the work
involved in this process
SCOPE OF THIS PROJECT
• The system provides an interface to the
customer where they can fill in orders for
the item needed.
• The sales person is concerned with the
issue of items and can be use this system
provide a communication platform between
the customer and the sales person.
FRONT END

•Visual basic 6.0

BACK END
•Oracle 9i
SOFTWARE USED

•Rational Rose
OPERATING SYSTEM

•Windows family
HARDWARE REQUIREMENTS
• Processor : Intel Pentium III or later.
• CPU speed : 1.0 GHZ
• Storage capacity : 20 GB
• RAM Capacity : 512 MB
SYSTEM FUNCTIONS
• Secure order of information by the customer.
• Schedule the customer an appointment for manual
delivery of the product.
• Separate modules have been created for
purchasing, viewing stock details, selling details,
and delivery details.
 ITEM DETAILS
• The item module deals with information about
the details of the product that the concern
handling.

• It consist of details such as the name of the

product, id generated, quantity, cost etc.

• This information is retrieved during the sales

and purchase of a product.
 SUPPLIER DETAILS
• The supplier module deals with the information
about the details of the suppliers giving product
to the organization.

• It consist of the details such as supplier name,

address, email id, phone number, sales tax number
etc.

• This information is retrieved when a purchase is

done .
 PURCHASE DETAILS
• The purchase module deals with various
item name ,supplier name, quantity of the
product, amount per unit.
 SALES DETAILS
• The sales module maintains daily sale of the
product of the organization

• It consist of details such as the item name,

sales id, quantity, amount etc.

• The information is retrieved from the

database when a sales details report or view
activity is made by the concern .
USE CASE DIAGRAM
• The functionality of a system can be described in a number of different use-
cases, each of which represents a specific flow of events in a system.
• It is a graph of actors ,set of
use-cases enclosed in a
boundary, communication,
associations, between the
actors and use-cases and
generalization among the
Use-cases.
ACTIVITY DIAGRAM
• It shows organization and their
dependence among the set of
components.

• These diagrams are particularly

useful in connection with workflow
and in describing behaviour that
has a lot of parallel processing.

• An activity is a state of doing

something :either a real world
process, or the execution of a
software routine.
 CLASS DIAGRAM

A class diagram describes

the type of objects in
system and various kinds of
relationships that exists
among them.
UML INTERACTIONS DIAGRAM
• It is the combination of sequence and
collaboration diagram.

• It is used to depict the flow of events in

the system over a timeline.

• The interaction diagram is a dynamic

model which shows how the system
behaves during execution.
SEQUENCE DIAGRAM

• A sequence diagram represents the

sequence and interaction of a
given use-cases or scenario.
• Sequence diagram can capture
most of the information about the
system.
• It is also represented by the order
in which things occur and how the
objects in the system send message
to one another.
COLLABORATION DIAGRAM

• A collaboration diagram
is an interaction
diagram that shows the
order of messages that
implement an operation
or a transaction.

• Collaboration diagram
shows objects, their
links, and their
messages.
 DEPLOYMENT DIAGRAM
• Deployment diagram are used to visualize the topology of the
physical components of a system where software components are
deployed.
IMPLEMENTATION OF USER INTERFACE
LAYER
EXISTING SYSTEM
• The system which is followed at present is a manual system.

• The system consist of book of accounts that has to be maintained in all aspects.

• In the existing system each and every time a reference should be made manually.

• There are high possibilities to commit errors and mistakes, which leads to produce
the wrong statements to the management.

• The above said reason are overcome by using the visual basic 6.0.

• Since the security system in the package is more secure than other software projects.
DRAWBACKS OF THE EXISTING SYSTEM

• Manual work

• Security of information flow

• Time consumption

• High manpower
 CONCLUSION
• Thus the project gives the detailed explanation about
how stock is maintained in an organization.
• It also gives idea about how stocks are to be
purchased and how to be maintained in a company.
 FUTURE
ENHANCEMENT
• T h e re i s a l w a y s a ro o m f o r i m p ro v e m e n t i n a n y
s o f t w a re p a c k a g e , h o w e v e r g o o d a n d e f f i c i e n t i t m a y
be.

• T h e i m p o r t a n t t h i n g i s t h a t t h e s o f t w a re s h o u l d b e
flexible enough for further modifications.

• I n f u t u re w e w i l l e n h a n c e t h i s p ro j e c t b y m a k i n g o u r
s y s t e m t o s t o re d e t a i l s o f t h e c u s t o m e r s u c h a s t h e
h o u s e a d d re s s t o m a k e t h e d o o r d e l i v e r y w h i c h i s a n
e a s y a n d q u i c k w a y.
REFERENCE BOOKS
• “programming in Microsoft Visual Basic 6.0” by
• Francesco Balena.

• “Oracle The complete Reference” by George Koch and Kevin

Loney.

• “Visual Studio .NET: The .NET Framework Black Book” by Temple

man and Vitter.
REFERENCE WEBSITES

• www.epay.com
• www.v3schools.com