Product Stock Management

A MAJOR PROJECT REPORT
ON
“PRODUCT STOCK MANAGEMENT”
Submitted in Partial Fulfillment for the award of

Bachelor of Engineering in Computer Science & Engineering
(2016-2020)
Submitted to
RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA
BHOPAL (M.P.)
Submitted By:
Shivam Mishra (0302CS161046)
Approved By Under the Guidance of

Mr. Pradeep Tripathi Mr. C.P.Gautam
(Head of the Department) (Asst. Prof. CS Dept.)
Computer Science
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

VINDHYA INSTITUTE OF TECHNOLOGY AND SCIENCE
SATNA (M.P.)
i
Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal (M.P)
Vindhya Institute of Technology & Science
Satna (M.P)
CERTIFICATE
This is to certify that the MAJOR Project entitled as “PRODUCT
STOCK MANAGEMENT” which has been completed &
submitted by SHIVAM MISHRA in partial fulfillment of the
requirement for the award of the degree of Bachelor of Engineering in
Computer Science & Engineering for the session 2016-2020 is a
bonafied work by them and has been completed under my guidance and
supervision. It has not been submitted elsewhere for any other degree.
H.O.D Guided By
Mr. Pradeep Tripathi Mr.C.P.Gautam
(Head of the Department) (Asst. Prof. CS Dept.)
Computer Science
Principal
Dr. Jai Bahadur Balwanshi
ii
Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal (M.P)
Vindhya Institute of Technology & Science
Santa (M.P)
(Project Approval)
CERTIFICATE
This is to certify that the MAJOR Project entitled as “Product Stock
Management”which has been completed & submitted by Shivam
Mishra in partial fulfillment of the requirement for the award of the
degree of Bachelor of Engineering in Computer Science & Engineering
for the session 2016-2020.
(External Examiner) (Internal Examiner)
iii
ABSTRACT
• Product Stock Management is a complete system for the management of

the product from its arrival in the store till it is sold and it keeps all the
data related to the product in the proper way in database.
• This system is much more secure than any other software which are used
now a days because it uses 2 level of authentication i.e. manager
authentication and cashier authentication. Manager authentication is
necessary for the management of the product stock in the store and
cashier authentication is necessary for the selling of the product to the
customer.
• In this system there is only one manager account as there is only one
manager in the stores and there can be multiple numbers of cashier
accounts which can be created updated or deleted by the manager. Thus
this system follows the hierarchical model and is completely controlled
by the manager of the store.
iv
DECLARATION
We hereby declare that the work which is being presented in the project
report entitled “PRODUCT STOCK MANAGEMENT” partial fulfillment
of the requirement of the degree of “Bachelor of Engineering in Computer
Science & Engineering” branch is an authentic record of our work carried
out under the guidance of “Mr.C.P.Gautam”. The work has been carried
out at Vindhya Institute of Technology & Science, Satna.
Project Associate
Shivam Mishra(0302CS161046)
v
ACKNOWLEDGEMENT
I express my profound sense of gratitude to Dr. Jai Bahadur Balwanshi
Principal, Vindhya Institute of Technology & Science, Satna for providing
their valuable guidance, continuous motivation and moral support in
carrying out this project work.
I owe special thanks to my esteemed guide Mr. C.P.Gautam Vindhya
Institute of Technology & Science, Satna involved right from the inception
of ideas to the finalization of the work. He/She is always ready to extend a
helpful hand in times of need. I am deeply indebted to him/her whose help,
suggestions and encouragement helped me in all the time of implementation
for and writing of this project report. I learned many things from him/her.
I am thankful to Mr. Pradeep Tripathi Head, Computer
Science & Engineering Department for providing necessary facilities and
suggestions to carry out my project work. I am very grateful to him for
reading my thesis and giving me many good suggestions that greatly
improved the presentation and enhanced the clarity of my work. Their vision
was fundamental in shaping my work and I am very grateful for having the
opportunity to learn from him. I am also thankful to all the renowned
faculty members and friends for their valuable support.
Shivam Mishra (0302CS161046)
vi
List of Figures
FIGURE NO. NAME OF TOPIC PAGE NO.
01 USE CASE DIAGRAM 7
02 SEQUENCE DIAGRAM 8
03 CLASS DIAGRAM 9
04 ACTIVITY DIAGRAM 10
05 ER DIAGRAM 12
06 DATA FLOW DIAGRAM 13
vii
Table of Content
Title Page i
Declaration of student ii
Certificate of the guide iii
Abstract iv
Acknowledgment v
List of figures vi
1 INTRODUCTION 01
1.1 Problem Definition 02
1.2 Project Overview 02
1.3 Need and Scope 02
1.4 Glossary 02-03
2 REQUIREMENT ANALYSIS 04
2.1 Hardware Requirement 05
2.2 Software Requirement 05
2.3 Feasibility Study 05
3 SYSTEM ANALYSIS AND DESIGN 06

3.1 Use case diagram 07
3.2 Sequence Diagram 08
3.3 Class Diagram 09
3.4 Activity Diagram 10
4 SYSTEM DESIGN 11
4.1 ER Diagram 12
4.2 Data Flow Diagram 13
5 TECHNICAL DESCRIPTION 14 - 16
6 DATABASE DESIGN 17 – 19
7 SCREENSHOTS 20 – 23
8 TESTING 24 – 26
9 CONCLUSIOIN 27 – 28
10 LIMITATION AND FUTURE ENHANCEMENT 29 – 30
11 REFERENCES 31 - 32
viii
Product Stock Management
CHAPTER 1
INTRODUCTION
Department of Computer Science & Engineering, VITS, Satna 1

1.1 PROBLEM DEFINITION
The shopkeeper and different mall managers find difficulty in keeping the records of the
Products throughout their entire cycle from buying till selling of the product. The store
manager finds difficulty in managing different cashiers at the same time as the previous
system does not deal with the cashier database along with the product database. The
second major problem is that the manager is unable to find which cashier has sold the
particular product if there are more than one cashier in a store.
1.2 PROJECT OVERVIEW
As there is a common problem between shopkeepers to keep record of the products in a

secure way and also they need to know when they have a shortage of any product which
they have to order to fulfil the needs of the customers. This is the system which has a
solution for both the problems of the shopkeepers.
This system is capable of providing security through the means of 2 layers of
authentication and is able to safe keep the products data and along with that it indicates if
there is enough product for the sale or not. If the number of product is less then the
required number then it will generate insufficient quantity message.
1.3 NEED AND SCOPE
The need of this system is that this system is much more secure than any other software
which are used now a days because it uses 2 level of authentication i.e. manager
authentication and cashier authentication. This system also needs to keep the record of
the product along with the time when it is sold in the database thus one can get the
information about the product in an easier and organized way.
Providing an alarm system when some product in the inventory is going to be less than 10
or any minimal quantity according to that product. In the next update you can take buyer
details to add these in the purchasing receipt.
1.4 GLOSSARY
Category:- In this section we have to specify the category of the product which we are
going to add in the shop.

Brand:- In this section we have to specify the category of the product which we are
going to add in the shop.
POS:- This section is for the selling of the product and also shows the list of the selling
items.
Pay Invoice:- This section in the system shows how much customer has to pay for the
products to purchase.
Cashier:- In this system cashier is referred as a shopkeeper which sells product.
Product Code:- In this system this code shows that each product is assigned to a unique
number also known as product barcode.

CHAPTER 2
REQUIREMENT
ANALYSIS

2.1 HARDWARE REQUIREMENT
RAM - 1GB(minimum)
Hard Disk - 80GB
PROCESSOR – INTEL i3
2.2 SOFTWARE REQUIREMENT

BACK END - SQL database
FRONT END - JAVA
WORKSTATION – Windows
2.3 FEASIBILITY STUDY

Feasibility of project can project can be explained in two terms below
Technical Feasibility -:
Our project is technically feasible, as we have taken HTML as our front end.
Advantages of language are achieved as: -
• Good interface for user
• Allow changes as when required.
• It is Rapid Action development tool, which makes processing fast.
• Coding Make technical processing easy.
Economical Feasibility: -
• Before creation of this project all the database and function were managed
manually by persons but after creation there is a need of just a single operator for
complete management, which makes it economically feasible.
• Our project is quite affordable in terms of using of any level and provides
complete functionality as desired.
Project can also be called feasible economically in terms of convenience, as person can
also go phone anonymous.

CHAPTER 3
SYSTEM
ANALYSIS &
DESIGN

3.1 USE CASE DIAGRAM
Figure 1

3.2 SEQUENCE DIAGRAM
Figure 2

3.3 CLASS DIAGRAM
Figure 3

3.4 ACTIVITY DIAGRAM
Figure 4

CHAPTER 4
SYSTEM
DESIGN

4.1 ER DIAGRAM
Figure 5

4.2 DATAFLOW DIAGRAM
Figure 6

CHAPTER 5
TECHNICAL
DESCRIPTION

The technology used in making Product Stock Management System is java which is a
platform independent and is used to make desktop applications. SQL is used to manage
database of the system. It is easy to get results from the SQL system by just firing the
query in the system.
In Product Stock Management System the frontend is developed using java and database
of the system is handled in the SQL. This system is a complete system for the
management of the product from its arrival in the store till it is sold and it keeps all the
data related to the product in the proper way in database. It is much more secure than any
other software which are used now a days because it uses 2 level of authentication i.e.
manager authentication and cashier authentication. Manager authentication is necessary
for the management of the product stock in the store and cashier authentication is
necessary for the selling of the product to the customer.
The manager login in the system and manages the records of the cashiers and is
responsible for the category, brand and addition of the bought products in the stock then
comes the role of the cashier which starts from verification of the cashier by the means of
the cashier login page. After this the logged cashier is responsible for the selling of the
product to the customer and its receipt generation.
As the manager enter its credentials then the system checks it from the database from the
already saved manager details if both are same then the system allows the manager login
successfully if the case is not so then the system does not allows the manager to login by
giving popup error msg wrong credentials.
After the manager logged in the system then he is capable of adding, deleting or updating
the category and brand of the product. Product details are then stored in the system with
its special unique barcode which is also known as product code. Then as we proceed for
the next phase that is selling of the product then authentication of the cashier is required.
The cashier enters the name and password which is then matched with the record saved
by the manager of the store in the database. If the entered details matches the cashier
details entered by the manager then the system allows the cashier to proceed further
otherwise an error message indicating wrong credentials will popup in the screen.

As the cashier is able to logged into the system now he can choose the products selected
by the customer to calculate the final payable amount and generate the payment receipt
with the items list and their prices along with the total amount to be paid by the customer
and the details of the products will be stored in the database in the sales table.
The above description shows the functionality of the frontend system but in the backend
there are 6 tables namely cashier, category, brand, product, sales, sales_product which
stores the data and description of each table will be shown in the database section in this
document.

CHAPTER 6
DATABASE
DESIGN

In this Product Stock Management System we have a database named superpos which
contains 6 different tables namely cashier, brand, category, product, sales, sales_product.
The schemas and some content of the tables are shown below to have clear understanding
of what data is stored in the database and how.
The description of the table named cashier is shown with the help of the table schema and
its content.
id username password status
3 Deepak 123 Active
4 Shivam Shivam Active
6 Travit Travit@123 Active
This table contains the unique id, username, password and status of the cashier which is
to be controlled by the manager of the store.
The description of the table named category is shown with the help of the table schema
and its content.
id category status
1 fan Active
6 pen Active
7 TV Active
This table contains the unique id, category and status of the product which is to be
controlled by the manager of the store.
The description of the table named brand is shown with the help of the table schema and
its content.
id brand status
1 LG Active
3 Sony Active
4 Panasonic Active
This table contains the unique id, brand and status of the product which is to be

The description of the table named product is shown with the help of the table schema
and its content.
id product description cat_id brand_id cost_price retail_price qty barcode status
5 LG Full HD 1 1 30000 45000 89 111 Active
display45
6 TV 320 HD 7 3 40000 52000 45 222 Active
Display
7 Cooler Superfast 9 6 10000 15000 45 333 Active
A45
This table contains the unique id, product name, description of the product, category id,
brand id, cost price, retail price, quantity, barcode and status of the product which is to be
The description of the table named sales is shown with the help of the table schema and
its content.
id date cashier subtotal pay balance
19 2020/03/29 Deepak 75000 80000 5000
20 2020/04/30 Travit 45225 50000 4775
21 2020/04/30 Travit 104000 105000 1000
This table contains the unique id, date, cashier, subtotal, pay and balance of the product
sold which is to be controlled by the cashier of the store.
The description of the table named sales_product is shown with the help of the table
schema and its content.
id sales_id product_id sell_price qty total
1 5 111 45000 4 180000
2 5 222 52000 6 312000
3 6 111 45000 2 90000
This table contains the unique id, sales id, product id, selling price, quantity and total of
the product sold which is to be controlled by the cashier of the store.

CHAPTER 7
SCREENSHOTS
(RESULT &
OUTPUTS)

This shows manager credentials input and output will be successful login to the system.
This shows input details of the cashiers by the manager and output will be cashier record.

This shows input of the category of the product by the manager and output will be name
of the category added in the list of the product.
This shows input of the category of the product by the manager and output will be name
of the category added in the list of the product.

This shows the input as the details of the product is filled and output will be addition of
the product in the stock.
This shows the input as a addition of the products in the buying list and the output will be
the receipt generation of the bought products.

CHAPTER 8
TESTING

TESTING AND DEBUGGING
After the code has been generated testing step starts. The testing process focuses on the
logical internal of the software that ensures all statements have been tested A good test
has a high probability of finding and error. To achieve this goal, the tester must
understand the software and attempt to develop a mental picture of how the software
might fail. Ideally, the classes of failure are probed. A good test is not redundant. Testing
time and resources are limited there is no point in conducting a test that has the same
purpose as another test. Every test should have a different purpose, a good test should be
“best of breed”. In a group of testhat have a similar intent, time and resources limitation
may mitigate towards the execution of only a subset of these tests. The test should be
neither too simple not too complex.
TEST CASES
ID Brand Category Product Cost_price Retail_price Qty Desired Total
Total
1 LG TV LG 30000 45000 4 180000 180000
display45
2 Acer Laptop AcerT1 35000 40000 2 80000 80000
3 Nataraj Pencil Pencil h1 3 5 10 50 50
4 Shivlal Book Data 130 150 4 600 600
Structure
The above test cases shows that the system works fine with almost complete accuracy
and the output is equal to the desired output thus this system is able to satisfy the working
needs of the system users.
SECURITY TESTING
Security testing attempts to verify that protection mechanisms built into a will in facility
protect it from improper penetration. “That system’s Security must, of course, be tested
for invulnerability from frontal attack-but must also be tested for in vulnerability from
flank or rear attack”.

In this system there is 2 level of security provided so that the data should be safe and
nobody other than the authenticated users will be allowed to make changes in the system.
Each level is tested and passed its functionality and thus is now available for the users.
VALIDATION TESTING
A final series of software tests- validation testing may begin validation can be defined in
many ways, but a simple definition is that validation. Succeeds when software functions
in a manner that can be reasonably expect by the customer. This system is passed through
validation testing and is able to pass it with nearly complete accuracy as all the
functionality of the system works as it is required by the users of the system. This is the
final stage of testing and is passed by this system thus this system is now available for the
users.

CHAPTER 9
CONCLUSION

The conclusion states the final points which we get from the project thus from this
Product Stock Management system we have found mainly three important conclusions.
These are stated below in the points.
• The Project clearly depicts that the Product Management is done efficiently and it is
also capable to keep records which is necessary for the future use. Thus this system is
suitable for the current scenario.
• The previous system which is used till now lacks the records of the cashier which
sold the products but this system overcome the previous bugs and have additional
functionalities.
• It may be perfect for the current scenario but it has some points which can be
upgraded to the best in the future.
The above conclusions shows that even though the system does its work for which it is
developed but from time to time there can be possibilities of upgradation of the system as
the time progresses. This means that no system is perfect for all the time thus we have to
upgrade it to make it viable in future also but if we talk for the current scenario the
system works fine and does almost all the tasks required by the shopkeepers and it also
provides certain special features such as autofill of details in the fields to make it easier
for the shopkeepers to handle the system, this functionality is achieved via accessing the
database. Thus this system is perfect for the shopkeepers at the present time.

CHAPTER 10
LIMITATION
AND FUTUTRE
ENHANCEMENT

LIMITATION
The limitations of the system shows how we can improve the system in the future or in
the next update of the system. There are some features that we can add in the next
version. Some of the points on which we can work are shown below.
• The control of the password change of the manager can be given to the owner of the
mall or supermarket.
• The details of the customer can be stored in the database for the future reference or
for the advertising purpose of the supermarket.
• The receipt can be generated in the name of the customer and payment mode can be
included in the receipt.
The above mentioned points shows the areas in which improvement can be made in the
future but for the current scenario the system is best suited of all the available ones in the
market.
FUTURE ENHANCEMENT
The future work which can be done in this system to make it more attractive and viable
can be illustrated in mainly 3 points. These points are listed below.
• Providing an alarm system when some product in the inventory is going to be less
than 10 or any minimal quantity according to that product.
• For providing more facilities we can add both discount and GST in the same system
to make it all in one system.
• In the next update you can take buyer details to add these in the purchasing receipt.
The above points are the improvements for the limitation section of this project. This
enhancement can be done in the near future when these features are to be needed by the
users of the system.

CHAPTER 11
REFERENCES

• https://www.productschool.com
• https://www.prodpad.com
• https://www.apphawks.com
• https://www.youtube.com
• www.freeprojectz.com
These are all the references which I have taken in the development of the project from its
requirement to its implementation as a system.

Product Stock Management

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Product Stock Management

Uploaded by

Copyright:

Available Formats

A MAJOR PROJECT REPORT

Submitted in Partial Fulfillment for the award of

Approved By Under the Guidance of

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

(External Examiner) (Internal Examiner)

• Product Stock Management is a complete system for the management of

Shivam Mishra (0302CS161046)

FIGURE NO. NAME OF TOPIC PAGE NO.

01 USE CASE DIAGRAM 7

06 DATA FLOW DIAGRAM 13

3 SYSTEM ANALYSIS AND DESIGN 06

Department of Computer Science & Engineering, VITS, Satna 1

1.2 PROJECT OVERVIEW

As there is a common problem between shopkeepers to keep record of the products in a

1.3 NEED AND SCOPE

Department of Computer Science & Engineering, VITS, Satna 2

Department of Computer Science & Engineering, VITS, Satna 3

Department of Computer Science & Engineering, VITS, Satna 4

2.2 SOFTWARE REQUIREMENT

2.3 FEASIBILITY STUDY

• Good interface for user

• Allow changes as when required.

• It is Rapid Action development tool, which makes processing fast.

• Coding Make technical processing easy.

Department of Computer Science & Engineering, VITS, Satna 5

Department of Computer Science & Engineering, VITS, Satna 6

Department of Computer Science & Engineering, VITS, Satna 7

Department of Computer Science & Engineering, VITS, Satna 8

Department of Computer Science & Engineering, VITS, Satna 9

Department of Computer Science & Engineering, VITS, Satna 10

Department of Computer Science & Engineering, VITS, Satna 11

Department of Computer Science & Engineering, VITS, Satna 12

Department of Computer Science & Engineering, VITS, Satna 13

Department of Computer Science & Engineering, VITS, Satna 14

Department of Computer Science & Engineering, VITS, Satna 15

Department of Computer Science & Engineering, VITS, Satna 16

Department of Computer Science & Engineering, VITS, Satna 17

Department of Computer Science & Engineering, VITS, Satna 18

Department of Computer Science & Engineering, VITS, Satna 19

Department of Computer Science & Engineering, VITS, Satna 20

Department of Computer Science & Engineering, VITS, Satna 21

Department of Computer Science & Engineering, VITS, Satna 22

Department of Computer Science & Engineering, VITS, Satna 23

Department of Computer Science & Engineering, VITS, Satna 24

Department of Computer Science & Engineering, VITS, Satna 25

Department of Computer Science & Engineering, VITS, Satna 26

Department of Computer Science & Engineering, VITS, Satna 27

Department of Computer Science & Engineering, VITS, Satna 28

Department of Computer Science & Engineering, VITS, Satna 29

Department of Computer Science & Engineering, VITS, Satna 30

Department of Computer Science & Engineering, VITS, Satna 31

Department of Computer Science & Engineering, VITS, Satna 32

You might also like