标题：店铺库存管理系统

TITLE：Store Inevntory Management System (SIMS)

Student ID：179075010
Student Name：MD SABBIR AHMED
Major：SOFTWARE ENGINEERING
Graduation Year: 2021
Date: 2021.05.25
MA ‘Anshan, Anhui, China
 Store Inventory Management System
店铺库存管理系统 by
MD SABBIR AHMED
A THESIS

Submitted in partial fulfillment of the requirements for the degree

Bachelor OF SOFTWARE ENGINEERING

Supervisor’s name: Dr. Hou Shudong

Anhui University of Technology

(2021.05.25)
 CONTENTS
Abstract i

Declaration ii

Chapter 1 - Introduction 08-15

1.1. Introduction ………………………………………………….... 8
1.2. Existing System …………………………………………………… 9
1.3. Problems of Existing System ……………………………………… 10
1.3.1. Employee Errors ……………………………………………… 11
1.3.1. Stock Outs ……………………………………………………… 11
1.3.1. Misplaced Inventory …………………………………………… 11
1.3.1. Poor Communication ………………………………………… 12
1.3.1. Lack of Optimization …………………………………………… 12
1.4. How Inventory Management Works ……………………………… 13
1.5. Solution of Existing System ………………………………………… 14
1.6. Project Objectives …………………………………………………… 15
 Chapter 2 - Literature Review 17-41
2.1. Introduction …………………………………………………………. 17
2.2. Store Inventory Management (SIMS) ………………………… 18
2.2.1. Features of SIMS ………………………………………… 19
2.2.2. Prince Bazar Limited …………………………………………… 21
2.2.2.1. Features of Prince Bazar Limited ………………………… 22
2.3. Used Technology ……………………………………………………. 27
2.3.1. Python …………………………………………………… 27
2.3.2. JavaScript ……………………………………………………. 29
2.3.3. PostgreSQL …………………………………………………… 30
2.4. Entity Relationship Diagram (E-R Diagram) ……………………… 32
2.5. Data Flow Diagram (DFD) …………………………………………. 36
2.6. Use Case Diagram …………………………………………………… 39
41-68
Chapter 3 - Proposed System
3.1. Introduction …………………………………………………………. 41
3.2. Feasibility ……………………………………………………………... 42
3.3. Objective of Feasibility Study …………………………………... 44
3.3.1. Technical Feasibility …………………………………………… 44
3.3.2. Operational Feasibility ………………………………………. 44
3.3.3. Schedule Feasibility …………………………………………… 45
3.3.4. Financial Feasibility ……………………………………………. 45
3.4. Methodology ………………………………………………………… 46
3.4.1. Use of Agile ……………………………………………………. 47
3.5. System Requirement ………………………………………………… 48
3.5.1. Functional Requirement ………………………………………. 48
3.5.2. Non-Functional Requirement …………………………………. 51
3.6. Entity Relationship Diagram ………………………………………. 52
3.7. Data Flow Diagram …………………………………………………. 53
3.8. Use Case Diagram …………………………………………………… 56
3.9. Database Design ……………………………………………………… 57
3.10. Implementation ……………………………………………………. 63
3.11. Features ……………………………………………………………… 64
 Chapter 4 – User Manual 69-85
4.1. Introduction …………………………………………………………. 69
4.2. System Requirements ………………………………………………. 69
4.3. User Interfaces ………………………………………………………. 70
4.3.1. Authentication & Authorization – Admin …………………. 70
4.3.2. Authentication & Authorization – Manager ………………… 70
4.3.3. Authentication & Authorization – Staff ……………………… 70
4.3.4. Login ……………………………………………………………. 71
4.3.5. Dashboard ………………………………………………………. 72
4.3.6. Outlet ……………………………………………………………. 63
4.3.7. Manager …………………………………………………………. 73
4.3.8. Profile……………………………………………………………. 74
4.3.9. Staff………………………………………………………………. 74
4.3.10. Category………………………………………………………… 75
4.3.11. Brand…………………………………………………………… 75
4.3.12. Unit……………………………………………………………… 66
4.3.13. Product………………………………………………………... 76
4.3.14. Supplier ………………………………………………………… 77
4.3.15. Customer ………………………………………………………. 77
4.3.16. Purchase ………………………………………………………... 78
4.3.17. Purchase Items ………………………………………………… 78
4.3.18. Purchase Payment …………………………………………… 79
4.3.19. Sale ……………………………………………………………… 79
4.3.20. Sale Items ……………………………………………………… 80
4.3.21. Sale Payment …………………………………………………... 80
4.3.22. Adding multiple items ……………………………………… 81
4.3.23. Adding multiple payment…………………………………… 82
4.3.24. Product Stock ………………………………………………… 82
4.3.25. Report Generation……………………………………………… 83
4.3.26. Invoices………………………………………………………… 84
86-89
Chapter 5 – Conclusion
5.1. Conclusion ……………………………………………………………. 86
5.2. Bibiliography ……………………………………………………… 87

Appendices 88-89

Appendices A – Visual Studio Code Editor …………………………… 84

Appendices B – PostgreSQL Control Panel ……………………………. 85
 ABSTRACT

This is a web-based software for marinating super shop or any ware house.
There are so many super shop company and manufacture company in
Bangladesh. They had to manage many product or goods every day. Company
have to maintain various kind of operation as like maintain supplier details,
customer details, stock details, daily transaction, generate invoice and so many.
This kind of operation helps the management for future planning. This software
can be use in multiple shops, outlets or ware house so that the daily work will
be easier. The goal of this software is to easy all those processes and ensure a
quick delivery for their customer or client.

Another core feature of our system is monitoring all the outlets or branch from
anywhere in the world. So that the management can monitor their business. By
this website the management can see daily transaction, stock details of different
shop or outlets.
DECLARATION

I, MD SABBIR AHMED, do hereby declare that this research entitled

“Store Inventory Management System” is my own effort under the
supervision and guidance of Professor Dr. Hou Shudong .
I further declare that the work has not been submitted, in partial or in full,
to any other academic institution for any degree award.

Signature: Date: 2021.05.25

AUTHORIZATION

I, MD SABBIR AHMED,certify that Anhui University of Technology has

the right to preserve the submitted copies of the paper in photocopy, micro
printing and other forms. The confidential paper can be preserved by
Anhui University of Technology in the same way when it is declassified. It
is also certified that Anhui University of Technology has the right to open
the content of the paper, partial or full, to public to read or borrow.

Signature: Date: 2021.05.25

Supervisor’s Signature：
 Chapter 1 - Introduction

1.1. Introduction
Inventory management is an important aspect of a successful business. This is
the process of monitoring and controlling the stock flows a company uses to
produce goods for sale or distribution. Inventory typically contains a
combination of goods, raw materials and finished products, and efficient
processing of these products is essential to maximizing inventory levels and
maximizing the company's profit potential. In addition, companies can prevent
or mitigate inventory-related waste. Companies use inventory management
software for a number of reasons. it can track inventory costs during production
and sales, inform companies when to replenish inventory, and track profits. It
can also be used to predict inventory levels and prices, as well as expected
demand for a product.

When products pass through the manufacturing and sales processes, an

inventory management system keeps track of all aspects of a company's
inventory. Customer orders, delivery, prices, stock, and sales are all tracked as
part of the operation. Whether or not a company uses inventory software, there
are certain essential components that any system must have in order to function
properly. This includes things like well-organized place names, clear and
unambiguous location labels, specific item numbers, units of measure, a good
starting count, and, most importantly, people who know and will execute these
policies.

A software system that records all inventory operation should be used on top of
all of this, as keeping track of inventory data by hand or in a spreadsheet just isn't
enough. Inventory management software can make it easier to monitor stock and
give various people access to the information, as well as provide a comprehensive
view of a company's inventory operation. It also keeps a detailed record of
inventory movement and sales in the past.
Most of the above factors would assist companies in keeping costs down,
allowing them to keep a sufficient amount of stock on hand, set goals, and
monitor profits effectively. Since inventory is one of the most valuable assets a
company has, an effective inventory management system would assist it in
tracking and controlling those assets.

Inventory management is an important part of any retail or manufacturing

industry, but it seldom gets the attention it deserves.

1.1. Existing System

If a person wants to perform a similar operation under the manual method, he
must write down all of the details. Locate all suppliers and make a list of their
contact information. Another challenge is managing everyday transactions and
customer information. Then there's the stock information, which includes
calculating the stock and creating a potential plan. Since it is almost impossible
to perform this process manually while keeping the company running smoothly.

Inventory management can be a time-consuming task that slows down the

company's operations. A software tool with the appropriate features may be
beneficial. Apply a tag for anything and a way to keep track of it all. How about
some warnings when one product is in demand while another is in short supply?
This combination sums up what inventory management software can do for your
business.

An inventory management system is a tool for tracking goods throughout your

company's supply chain. It maps the entire journey of a product from order
placement with your vendor to order delivery to your customer, optimizing the
entire spectrum. This software's accountability has a major effect on a company's
bottom line. Businesses can reduce waste, evaluate patterns, and make better
investment decisions by accurately monitoring products.

Inventory management is a pure methodology of buying, storing, and selling

each raw materials (components) and finished product in an exceedingly
structured manner (products). Inventory management in business terms refers to
having the correct stock, at the correct levels, within the right place, at the correct
time, and at the correct price and value. Inventory management could be an
operate of the availability chain that involves things like watching and managing
orders from vendors and shoppers, stock storage, dominant the quantity of
merchandise purchasable, and order fulfilment.

Naturally, the exact inventory management definition for your business can
affect a variety of items you offer and the networks by which you sell them.
However, as long as those essential ingredients are present, you'll have a strong
base on which to create.

To keep track of inventory databases and make ordering decisions, small-to-

medium businesses (SMBs) often use Excel, Google Sheets, or other manual
resources.

1.1. Problems of Existing System

there are so many existing systems in Bangladesh. Different types of inventory
management have different issues. The majority of inventory management
systems are designed to meet the needs of their owners or businesses.

• I heard about the Hossain Group's system from our relatives, who told me that
they have several branches and use an offline database to keep track of their
factory details. They use a desktop-based software, which makes managing all
branches from any location extremely difficult. As a result, we'd like to alter it
using an online application.

• Another example is The Prince Bazar, which uses a desktop-based software and
only has one application per outlet, implying that two branches are not related
by a single application. So, I decided to make this application to change this
system under one application which is online based. Using this software, the
administrator can manage it from any location.

• Most of the manager uses pen & paper in a traditional manner for keeping
business details but it’s difficult to maintain. It is an old method to keep all
information about stock, employee details, and so on in this modern age. It's
impossible for a business owner to keep track of his company's details for a long
time. In today's digital world, a manual system for maintaining or storing all
information about a company is a relic.

• Every organization's data is at risk in a manual system. For all kinds of

situations, I inspired to create this web application because of this problem.
 1.3.1 Employee Errors

Employee errors can lead to inaccuracies in inventory records, causing

purchasing to miss out on purchasing materials or accumulate too much
inventory. Employees in charge of transacting supplies or job orders need to be
properly trained in order to correctly update the inventory system.

1.1.2. Stock Outs

Stock outs are inventory losses that may occur as a result of incorrect records or
poor inventory management. The purchasing department needs precise trigger
points to decide when material purchases should be made. Customers can
experience product delays as a result of stock outs.

1.1.2. Misplaced Inventory

Excessive stock incurs extra expenses in the form of storage fees and funds held
in unused inventory. When businesses do not use inventory immediately after
purchasing it, the goods tend to lose value. If some of the materials are flawed,
the company will require more work to discover the issue.

1.1.2. Poor communication

Miscommunication is present both within and across supply chain functions, and
it takes a toll on data analysis and collaboration in particular. Analysts, category
managers, sales managers, and supply chain staff all approach issues differently
and concentrate on various aspects. For CPG data analysts, extracting
information from data is always a difficult task, making collaboration difficult.
 1.1.2. Lack of Optimization

The inventory system must gather enough information to aid buying and
planning in forecasting potential supply requirements. A well-designed
inventory system will provide the organization with details on production
volumes as well as scrap and waste. This information can assist purchasing in
determining an accurate production material inventory level.

1.1.2. Poor communication

Poor communication is frequent at all stages of the supply chain, beginning with
the shop. Consider the following scenario:
• The product is sent to the store but not to the shelf.
• Promotional displays or products arrive at the store but do not make it to the
floor.
• At a warehouse, product is loaded into the wrong truck, sent to the wrong
store, or arrives late.
 1.4. How Inventory Management Works?
Inventory is a company's most valuable properties. The inputs and finished
goods are at the heart of a company's business in retail, manufacturing, food
service, and other inventory-heavy industries. When and where inventory is
needed, a shortage can be devastating.

Inventory, on the other hand, can be viewed as a threat (if not in an accounting
sense). Large inventories are vulnerable to spoilage, theft, loss, and demand
shifts. Inventory must always be insured, and if it is not sold in a timely basis, it
can be forced to be sold at a discount or lost entirely.
Inventory management is important for companies of all sizes for these reasons.
When to restock certain items, how much to buy or produce, what price to pay,
and when to sell and at what price can all be difficult decisions to make. Small
companies also maintain manual stock records and use Excel formulas to
calculate reorder points and quantities.

Depending on the market, different inventory management techniques are used.

An oil depot can store large quantities of inventory for long periods of time,
allowing it to wait for demand to increase. Although storing oil is costly and
dangerous, a fire in the United Kingdom in 2005 caused millions of pounds in
damage.
 1.4. Solutions of Existing System

• I specifically want to change the manual system to a digital system using digital
technologies, with only one person in charge of assigning details and information.

• Issues with Authentication and Authorization

• Keeps track of all suppliers, salespeople, and customers.

• Keep track of all product details

• Selling the goods to the consumer

• Invoice generator for purchases and sales

• Any date purchase/sale report

• Managing payments for purchases and sales

• Stock manages with notification

• Handling of stock returns

• Managing multiple outlets

• Mobile apps to keep track of all outlets by the administrator

• Calculate all profits and losses on a regular, weekly, and annual basis.

• I want to keep track of all information about every organization.

 1.5. Project Objectives
• Maintain the proper level of inventory to ensure smooth production and sales
operations.

• To ensure that raw materials and finished products are available at all times so that
manufacturing can continue uninterrupted and consumer demands are met.

• To reduce product carrying costs.

• To keep inventory expenditure at a maximum pace.

• To reduce fraud, obsolescence, and wastage losses, among other things.

• Make arrangements for slow-moving goods to be sold.

• To reduce the expense of ordering inventory.

• Unnecessary funds blockage in inventory.

• To reduce inventory carrying costs: Inventory carrying costs refer to a variety of

factors that affect inventory in storage, including:

o Depreciation

o Insurance

o Warehouse Space

o Replacement cost

o employer

o Imposition of taxes

o Delivery
• To save money: There are a variety of ways to save money. The four cost-
cutting approaches mentioned below define simple cost-cutting techniques that
are simple to implement.

• To keep inventory expenditure at a maximum level: Putting it bluntly: Optimal

inventory strikes the ideal balance between our customers' delivery needs and
our bottom line. This equilibrium must take into account monetary value,
intangible expectations, market share and penetration, pricing premiums, hard
and soft costs, and so on.
• To reduce the expense of ordering inventory: Use Inventory on Consignment
Consignment helps you to sell a part of your product to the vendor who is
already carrying it. The catch is that the manufacturer does not pay for the
inventory up front under this deal. Instead, they pay you after a sale is made.

• Shorten The Lead Time: Shortening the time it takes to accept a purchase order
is known as lead time reduction. The less time you spend on it, the better. Lead
time reduction lowers the inventory cost in two ways:
• It enables you to have less safety stock inventory on hand, resulting in less
obsolete stock in the future.
• It enables you to order less stock more often, reducing the size and expense of
your warehouse.
 Chapter 2 - Literature Review

1.6. Introduction

This chapter discusses on the project's literature review and context research. A
literature review is critical to achieving a stable system because it aids in
identifying problems that could have existed in the previous system. It also
assists in determining the best path to achieving the project objective based on
the research. Workflow management systems ensure that the right information
reaches the right person or computer software at the right time by identifying,
reviewing, and redesigning an organization's resources and operations.

The term "Inventory Management System" refers to a set of detail methods for
managing the system. User testing is will be manually, and i aim to make it as
accurate as possible.

These assist people or users in learning about the system. A chapter of case
studies, review exercises, and a glossary are included in the book. The authors
have created a special Web site that includes animation, interactive illustrations,
lecture materials, exercises and solutions, related links, and other useful
classroom tools. This chapter examines the usability of portals and compares
them to current systems.

Inventory management System Verification can be described as a computerized

system that is used by the general public to save time, minimize product loss,
prepare for the future, and many other things by using a computerized system.
1.7 Store Inventory Management System (SIMS)
It's a matter of survival of the fittest when it comes to evolution. If there is a need
to find a solution to a dilemma, evolution occurs. The manual system's problem
is that it takes a long time to process data, which is something that an online
system can help with.

The SIMS (Store Inventory Management System) is a pre-existing system for

keeping track of inventory. In Bangladesh, SIMS is used by a group of
companies. This software is a stand-alone application. It assists the operator in
stock estimation and product loss prevention.

It accepts all types of products and keeps track of them. The application keeps
track of both the input and output data. It also maintains track of the goods that
have been used in the past. So that the company can figure out why they're using
the product. One of the major advantages of this application is that it can
monitor project-based product use.

It's only used for factory stock management, so it's only designed for stock
details; the price list and supplier list aren't included. As previously stated, the
system can monitor individual project stock consumption. So that they can
calculate the project's true expense.
It is very useful and reliable for the industries. However, since this program is
offline, it has printed and checked all of the reports. If a company has two or
more warehouses, it may need to use separate units of this application and hire
more employees. This raises the bill and makes the application more difficult to
use.

I look at the SIMS framework that is currently in place. I 've noticed that
searching the stock takes longer, and that making a potential plan is extremely
difficult.
1.8 Features of SIMS
• Product Categorization: Product categorization, also known as product
classification, is a branch of natural language processing research (NLP). It's also
one of the most difficult obstacles for ecommerce businesses to overcome.
Researchers have been applying machine learning to product categorization
problems as AI technology has advanced. We'll go through what product
categorization is, why it's relevant, and how it applies to ecommerce sites in this
article. Finally, we'll talk about companies that offer product categorization
outsourcing and their market place.

• Product Measurement: Examines how inventory in the warehouse can be

better tracked and calculated. Finding out what needs to be tracked and
measured; a closer look at stock counting; explaining how information is
gathered; wondering what makes a good warehouse management system and
what the advantages are of combining inventory control and warehouse
management; and looking at operating with restricted systems are all things that
need to be considered.

• Product History: If the warehouse wants to find the product life cycle, this
software will locate the product details for the business. The application will
determine the project this product was used in as well as the quantity. So that the
organization can quickly determine how much of those products are consumed.

• Cycle Counting: They have a lot of recycled items in their inventory. These
types of products have a limited period or usage of validity. Assume they can
only use an item five times. As a result, they must measure how many cycles the
product has been used, and this application allows them to do so.

• Collaborative Inventory: In the second level, collaborative inventory planning

helps to place inventories across the supply chain network based on the results of
collaborative demand forecasting.
• Automatic Stock-out Reports: Weekly and monthly stock-out reports are
produced automatically by this program. There is no need to issue any
commands for this operation.

Figure 2.1: SIMS Software

1.9 Prince Bazar Limited
Prince Bazar Limited is a supershop which has two outlets in Mirpur and
Shyamoli.

They use same type of software that I’m developing. The sell all kind grosser &
home appliance product. They also sell the fresh vegetable & fish & meat.

Prince Bazar is the sister concern of Prince Group. The first supper shop
established in 2005 at Mirpur. After two years success in Mirpur they moved to
Mohammadpur in 2008 and serving their customer according to their demands.
At present they have 4 outlets which are Mirpur-1, Pallabi, Shyamoli and
Mohammadpur. Whatever a customer want they can get it easily at Prince
Bazar in a reasonable price and also quality products. Prince bazar is always set
to meet consumer demand. Customers can conveniently obtain whatever they
want at Prince Bazar for a fair price and high-quality goods. Prince bazar is
always ready to meet the needs of its customers.

As one of Dhaka's leading superstores, Prince Bazar relies on its Human

Resources team to understand the link between matching the right person to the
right job. HR associates work to motivate and empower Prince Bazar employees,
ensuring that each member of the team feels fulfilled, challenged, and capable of
successfully completing his or her role in the company's day-to-day operations.
The Benefits division of Prince Bazar is committed to the design and
administration of competitive health and financial benefits packages.
2.0 Features of Prince Bazar Limited

• Full Inventory Management

Inventory management is a function of the supply chain that involves things like
monitoring and managing orders from vendors and consumers, stock storage,
controlling the amount of merchandise for sale, and order fulfillment.
Naturally, the exact inventory management definition for your business can vary
depending on the types of items you offer and the networks by which you sell
them. However, as long as those essential ingredients are present, you'll have a
strong base on which to develop.
Inventory control practices for these systems go beyond simple reordering and
stock tracking and include anything from end-to-end output and market
management to lead time and demand forecasting, as well as measurements,
reports, and even accounting.

• Full Support for Units of Measurement

A unit of measurement is a definite magnitude of a quantity that is used as a

basis for measuring the same kind of quantity. It is described and accepted by
convention or by law. As I stated in our article, Prince Bazar Limited sells a wide
range of products, so the application must be able to measure them all. A length,
for example, is a physical quantity. The meter is a unit of measurement that
represents a specific length. When we say 10 meters (or 10 m), we're referring to
ten times the predetermined length of a "meter." The method of deciding how
large or small a physical quantity is in comparison to a simple reference quantity
of the same kind is known as measurement.
 • Make Purchase Orders, Turn Them to Bills

QuickBooks makes it easy to build purchase orders with custom PO numbers.

Customize the logo, colors, address, and other fields with your company's
information. Do you deal with a specific vendor on a regular basis? Put it in your
calendar and forget about it! Purchase orders for recurring transactions can be
easily scheduled in QuickBooks.

When an order is completed, QuickBooks converts it into a bill by copying the

products, amounts, and prices from the purchase order. Customers can pay with
a credit card, debit card, Square, or other payment service when they receive bills
from QuickBooks. QuickBooks handles payment management and keeps track of
it for you.

• Inclusive and Exclusive Taxation

The distinction between inclusive and exclusive tax is straightforward. It all

depends on whether or not the tax is applied to the total retail price.

Taxes are also included in the product's purchase price, so no additional taxes are
applied to the sales transaction's subtotal.

Exclusive tax - Since the tax rate is not included in the purchase price, it is
applied to the subtotal of the sales transaction before the checkout is completed.
 • Control Your Business with Smart Reports

Intelligent reporting and business knowledge Companies must adapt to the

uncertainty of data and take appropriate action as a result. Spreadsheets are no
longer sufficient solutions for a serious business that wants to properly interpret
and use all of the data collected.

That's where business intelligence reporting comes in – and it's proving to be

critical in enabling companies to efficiently gather data and turn information into
action.
So, how is business intelligence research progressing? It enables the creation of
smart reports using modern BI reporting tools, as well as the development of a
robust intelligent reporting practice. As a result, regardless of niche or market, BI
will help a company's overall evolution as well as profitability.

I'll look at the advantages of business intelligence reports, key BI characteristics,

and the fundamental functions businesses can use to stay ahead of the
competition in today's highly competitive digital environment to bring the
business-boosting benefits of BI into perspective.
The process of collecting data using various software and methods to gain
relevant insights is known as business intelligence reporting, or BI reporting.
Finally, it offers advice and insights on industry patterns, allowing decision-
makers to take action. No matter what business or sector you work in, if you
collect data, you must evaluate and report on it.

As a result, you'll be able to take a more analytical approach to your business

decisions and collect information that would otherwise go unnoticed. But first,
let's look at the advantages of these reporting methods and how companies,
whether small or large, can achieve profitable outcomes.
 • Increasing the workflow speed

Managers, staff, and key stakeholders are often stranded while waiting for a
detailed BI report from IT or SQL developers. Particularly if a business connects
data from various sources. The procedure will take several days, slowing down
the workflow. Decisions can't be taken, analyses can't be completed, and the
whole organization suffers as a result.

One of the key advantages an organization can have is centralizing all data
sources into a single location, with data connectors that can provide a single
point of access for all non-technical users in the company. The data-driven
environment doesn't have to be intimidating, and with the right BI resources, the
whole process can be handled in a matter of seconds.

Data visualization is an additional factor to consider. Since humans process

visual information 60.000 times faster than text, using smart intelligence in the
form of interactive, real-time visual data will dramatically improve workflow.
Each piece of data can be compiled into a single, real-time dashboard, resulting
in a workflow that is fast, transparent, easy, and effective. This type of report
would become more visual, accessible, and reliable in gathering data.

• Utilization of real-time and historical data

The enormous amount of gathered data is difficult to use and comprehend using
conventional reporting methods. Even the most seasoned executives can find it
difficult to create a clear presentation from a large amount of data. Another
important consideration is the ability to use real-time data.
The level of complexity that can be achieved in BI projects cannot be compared to
conventional news. A report written in Word will not have the same amount of
knowledge and value as real-time data analysis with applied alerts that can
forewarn about any business phenomenon, and this type of support software
can, as a result, improve business productivity and lower costs.

• Backup & Restore Your Data

Computers will eventually fail. These collisions can be highly costly. Important
data is lost, and a significant amount of time is wasted trying to recover it. Many
businesses depend on a network that almost always works. Data backup routines
that are reliable and well-planned are critical, if not the most important factor, in
making this possible. Computers are vulnerable, and we must compensate by
developing good and efficient data backup procedures.

• GST Ready
The GST is a value-added tax imposed on most products and services sold for
domestic consumption. Consumers pay the GST, but companies providing the
products and services must remit it to the government. GST is, in essence, a
source of revenue for the government.

The goods and services tax (GST) is a federal indirect sales tax that is levied on
the purchase price of such goods and services. The GST is added to the product's
price by the company, and the consumer pays the sales price plus the GST. The
GST part is received and forwarded to the government by the company or seller.
In certain countries, it is also known as Value-Added Tax (VAT).

2.1. Supporting Theory

My whole framework is web-based. I built framework using the following
components, which support various web technologies and resources for both the
frontend and backend. I have made our app is an online platform. The
technologies and methods used to create this online platform will be examined in
this paper.
 2.1. Used Technology

2.1.1. Python

Python is an interpreted and object-oriented high-level programming language

with its own semantics. Faster Development and as a scripting or glue language
for linking existing components are made possible by its high-level built-in data
structures, which are combined with dynamic typing and dynamic binding.
Python's simple, easy-to-learn syntax puts a focus on readability, which reduces
software maintenance costs. The Python interpreter and its extensive standard
library is available for free download and spread in source or equivalent
qualifications for all major platforms.

Python is popular amongst developers because it allows them to work more

efficiently. The modify cycle is extremely quick because there is no compiling
phase. Python programs are simple to debug: a bug or poor input would never
result in a segmentation fault.

The Python programming language, which dates back to 1991, was regarded as a
gap-filler, a way to write scripts that "automate the boring stuff" (as one famous
Python book put it) or to quickly prototype applications that would be applied in
other languages.

Python, on the other hand, has become a first-class citizen of modern software
creation, infrastructure management, and data analysis in recent years. It is no
long a side functionality language, but rather a significant force in web
application development and systems management, as well as a central driver of
the big data analysis and artificial intelligence explosions.
Stock Market Reporting and Analysis is a program that uses Google Financial
data for technical analysis, simulation, and prediction. Observing market data,
especially some general and other software columns. Pandas used to weigh the
risk of a stock based on its recent performance history by taking stock of the
details, looking at various aspects of it, and finally looking at it in some way. In
expectation of future costs, competing with the Monte Carlo process. Stock
exchange research is only for analyzing stock company data for different
organizations. Any company can easily extract relevant data using this method
of data analysis.
I looked at two simple research measurements and found no definitive proof for
their approximate significance. These forecasts are often very long-term and will
be valid for a year. Suggestions on this scale do not take up the majority of the
project's time. Instead, we'll concentrate on forecasting regular market patterns. I
avoided simple research because of these issues.

There are two different types of tools that could be useful. To begin, there are
numerous books and websites dedicated to Python programming. This is an
opportunity you can grab. If you have a programming query, a fast Google
search will usually yield an answer.

Second, the majority of the projects you'll be working on are focused on

mathematical problems and concepts that have been previously identified. You
should not, however, begin a project by searching the internet or a library. Each
framework is made to enable you to individually examine an issue. The main
part of your report should be a summary of your explorations and experiments.
It is appropriate to provide some background information on the project (with
proper citations to the books and websites from which it was derived), but it is
not needed, and you can receive a perfect score without it.
The Python programming language is really a great tool for data analysis, but it
can be made even better if you know a few basic tricks. This article will show
you how to use Python to make data analysis a breeze. Tips and Tricks can be
extremely useful, particularly in the programming world. A quick hack can save
both time and money.
• Retail: Billing software for use in stores and supermarkets.
• Django is a programming language that is designed to eliminate
implementation dependencies.
• Android: Android applications are written in java API.java or use.
It's used in server-side applications in the financial sector.
• Stock market: Create algorithms to determine which business to invest in.
• Hadoop is mostly used for big data.
• Scientific and Research Communities: Handling Massive Amounts of Data

2.1.2 JavaScript

React allows creating interactive UIs a breeze. Create simple views for each state
of your app, and React will update and make the appropriate components as
your data changes.
Create encapsulated modules that control their own state, then put them together
to create complex user interfaces. You can easily pass rich data via your
application and keep state out of the DOM as element functionality is composed
in JavaScript instead of templates. Since I do not even make assertions about the
rest of your technology stack, you can use React to create new features without
having to rewrite old code. React can also use Node to render on the server and
React Native to power mobile applications.
Changes to the DOM made outside of React are ignored by React. It determines
updates based on its internal representation, and if another library manipulates
the same DOM nodes, react becomes confused and unable to recover.
This isn't to say that combining React with other forms of influencing the DOM is
impossible or even difficult; you just have to be aware of what each is doing.
Preventing the React function from updating is the simplest way to avoid
conflicts. You can do this by making elements like an empty div /> that React
has no need to update.
 2.1.3PostgreSQL

Ingres, a project at the University of California, Berkeley, gave birth to

PostgreSQL. Michael Stonebreaker, the Ingres team's creator, left Berkeley in
1982 to work on a proprietary version of Ingres. In 1985, he returned to Berkeley
and started a post-Ingres project to solve the issues with modern database
systems that had become more apparent in the early 1980s. In 2014, he received
the Turing Award for these and other projects, as well as the methods he
pioneered in them.
The aim of the new project, POSTGRES, was to incorporate as few features as
possible to fully support data forms. The ability to identify types and completely
explain relationships was one of these features, which was commonly used but
retained entirely by the consumer. The database in POSTGRES recognized
relationships and could extract data from similar tables using rules in a natural
way. Many of Ingres' ideas were used in POSTGRES, but not its code.
The system's foundation was outlined in published papers beginning in 1986,
and a prototype version was shown at the 1988 ACM SIGMOD Conference. In
June 1989, the team published version 1 to a select group of users, followed by
version 2 in June 1990, which included a rewritten rules structure. In 1991,
Version 3 was released, which rewrote the rules system and added support for
multiple storage managers as well as a better query engine. By 1993, the project's
user base had grown to the point that it was being inundated with requests for
support and functionality. The project came to an end with the release of version
4.2 on June 30, 1994, which was basically a cleanup. POSTGRES was released
under an MIT License version, allowing other developers to use the code for any
purpose. POSTGRES used a POSTQUEL query language interpreter inspired by
Ingres at the time, which could be used interactively with a console program
called control.
Andrew Yu and Jolly Chen, both Berkeley graduate students, created Postgres95
in 1994 by replacing the POSTQUEL query language interpreter with a SQL
query language interpreter. psql has also taken the place of monitor. On May 5,
1995, Yu and Chen released the first version (0.01) to beta testers. On September
5, 1995, Postgres95 version 1.0 was released, with a more liberal license that
allowed the program to be freely modified.
On July 8, 1996, Marc Fournier of Hub.org Networking Services provided the
open-source development effort with the first non-university development
server. Work on stabilizing the code inherited from Berkeley started with the
help of Bruce Momjian and Vadim B. Mikheev.
The project was renamed PostgreSQL in 1996 to reflect its SQL support. On
October 22, 1996, PostgreSQL.org launched its online presence. On January 29,
1997, the first PostgreSQL update, version 6.0, was released. Since then, the
program has been managed by The PostgreSQL Global Development
Community, which is made up of developers and volunteers from all over the
world.
The project continues to release new versions under the PostgreSQL License,
which is free and open-source software. Contributions from proprietary
suppliers, support firms, and open-source programmers make up the code.

Figure 2.2: Server Connection

 2.5. Entity Relationship Diagram (E-R Diagram)
The relationships between entity sets stored in a database are depicted in an
entity relationship diagram (ERD). In this case, an object is a data component. ER
diagrams, in other words, depict the logical structure of databases.

There are several parts of an entity relationship diagram. are some of the
components that are commonly used to describe an e-r diagram.

• Entity
• Weak entity
• Attribute
• Multi value attribute
• Derived attribute
• Relationship

2.5.1 Entity
A individual, location, event, or object that is important to a system is referred to
as an entity. A school system, for example, can consist of pupils, teachers, major
courses, subjects, fees, and other things. In ER diagrams, entities are represented
by a rectangle and called with singular nouns. Rectangle is the symbol for it.

Figure 2.3: Entity

 2.5.1. Weak Entity
A individual, location, event, or object that is important to a system is referred to
as an entity. A school system, for example, can consist of pupils, teachers, major
courses, subjects, fees, and other things. In ER diagrams, entities are represented
by a rectangle and called with singular nouns. Rectangle is the symbol for it.

Figure 2.4: Week Entity

2.5.2. Attribute
A specification that specifies a property of an object, element, or file is referred to
as an attribute in computing. It may also apply to or set the value of a particular
instance of such. Attributes should be called metadata rather than attributes for
consistency. An attribute is a function of a property that is commonly and widely
used. However, depending on the technologies being discussed, the term
attribute can and is often used interchangeably with the term property. An
object's attribute usually consists of a name and a value; an element's attribute
usually consists of a type or class name; and a file's attribute usually consists of a
name and extension.

Figure 2.5: Attribute

 2.5.3. Multi valued attribute
The term "multi valued attribute" refers to an attribute that can have several
values. It's worth noting that this isn't the same as an attribute having its own set
of attributes. A teacher entity, for example, may have several subject values. A
double ellipse is used to represent it.

Figure 2.6: Multi valued attribute

2.5.4. Relationship

How entities interact with one another or are linked to one another.
Relationships may be thought of as verbs. For instance, the named student
might enroll in a class. The student and the course are the two individuals,
and the relationship depicted is the act of enrolling, which connects the two.
Diamonds or logos are usually drawn directly on the connecting lines to
indicate relationships.

Figure 2.7: Relationship

 2.5.5. Mapping Cardinality

The number of entity objects on either side of the relationship is referred to as

cardinality. There will be 4 main types of mapping cardinalities in an e-r
diagram. For instance, a customer may place multiple orders for the same
product.
• One-to-One
• One-to-Many
• Many-to-One
• Many-to-Many

2.5.6.1 One-to-One: The simplest relationship between two beans is a one-to-

one relationship. One entity bean only has one relationship with another
entity bean. A client, for example, can only be held in one word/cell at a
time.

Figure 2.8: One to One

2.5.6.2 One-to-Many: One object may refer to multiple instances of

another in a one-to-many relationship.

Figure 2.9: One to Many

 2.5.6.3 Many-to-One: Many objects may refer to one instance of another
in a many-to-one relationship.

Figure 2.10: Many to One

2.5.6.4 Many-to-Many: A many-to-many partnership is difficult to

understand. Many objects may relate to many other objects in a many-to-
many relationship. This is the most complicated cardinality to manage.
Figure 2.11: Many to Many

2.6. Data Flow Diagram (DFD)

The data flow diagram (DFD) shows the data flows between various business
processes. It's a graphical representation of data flow and the transformations
that occur when data moves from input to output.
DFDs are made up of just four symbols. They are as follows:
1. Process
2. Data Object
3. Data Store
4. External Entity
 2.6.1. Process

A process shows transformation or manipulation of data flow within the

system. The symbol used is an oval shape

Figure 2.12: Process

2.6.2. Data Flow

The data flow diagram represents the flow of data from a source to a destination.
A line represents data flow, with arrowheads indicating flow direction.

Figure 2.13: Data Flow

2.6.3. Data Store

A data store holding place for information within the systems. It is represented
by an open-ended narrow rectangle.

Figure 2.14: Data Store

 2.7. Use Case Diagram
At its most basic level, a use case diagram shows a user's interaction with the
system by illustrating the relationship between the user and the various use
cases in which the user is involved. A use case diagram is being used to
analyze the different types of users of a system as well as the various use
cases, and it is often followed by other types of diagrams.
People frequently use use case modelling for the following purposes as
they create use case diagrams in the early stages of development.

• Describe a system's meaning.

• Write down a system's specifications.

• Verify the architecture of a device.

• Assist with implementation and the development of test cases

• Created by analysts in collaboration with domain experts

2.7.1 Actor

• A user communicates with the use case (system function).

• Given a name by a noun.
• An actor has a job in the industry.

• A user is similar to a user, but a user can play multiple roles.

 For example:

• A professor may be both a teacher and a researcher.

• plays two roles to two systems

• The use case is triggered by the actor.

• The actor owes the system (inputs) a debt of gratitude, and the system
owes the actor a debt of gratitude.

Figure 2.15: Actor of Use Case Diagram

2.7.2. Use Case

• The system's operation (process - automated or manual)

• Named after a verb and a noun (or Noun Phrase).
• i.e. Do something
• Each Actor must be associated with a use case, though certain use cases may
not be.

Figure 2.16: UseCase of Use Case Diagram

 2.7.3. Communication Link
• The presence of an actor in a use case is seen by linking an actor to a use case
by a solid connection.
• Actors can be bound to use cases by associations, meaning that the actor and
the use case interact with one another using messages.

Figure 2.17: Communication Link of Use Case Diagram

2.7.4. Boundary of System

• The system boundary, as specified in the specifications document, could be the
entire system.
• Each module can serve as the system boundary in large and complex systems.
For example, each of the modules in an ERP system for an organisation, such as
staff, payroll, accounting, and so on.
• may be used to establish a device boundary for use cases unique to each of
these business functions.
• The entire system will cover all of these components, forming the system's
overall boundary.

Figure 2.18: System of Use Case Diagram

Chapter 3 - Proposed System
3.1. Introduction
In systems engineering and software engineering, requirements analysis refers to
the process of evaluating the needs or specifications that must be met for a new
or modified product, while taking into consideration the potentially conflicting
requirements of different stakeholders such as beneficiaries or users. Another
prerequisite for becoming a software manager is that you must be able to please
your supervisor. However, in finance, you must still please your boss.
An Inventory Management System reduces a lot of things to overcome the
limitations of the previous system. These are the following:

Keep records: It keeps track of all suppliers, salespeople, and customers for
potential inquiries. If an occurrence occurs, it is extremely beneficial.
Stock management with notifications: Allow stock alerts to keep track of
products that fall near or below a preset threshold. If you're at the counter or on
the go, you'll get updates in your dashboard or via email. At any time, you can
export stock levels and download your files to a printable spreadsheet.
Inventory management software helps you to view data from several sources. All
of the numbers and figures related to stock levels and anticipated demands in
terms of current financial positions can be found in one place and tweaked for
maximum performance.
This will assist you in identifying some crucial aspects of your business.
Consider the following scenario:
• Which places have a shortage of a particular item?
• With which goods, which outlets are more successful?
• Which stores are underperforming and need to be tweaked?
• What goods and outlets are not performing well?
• Which stores are more successful than others with certain products?
• Which products are frequently purchased together, and where is this most
common?
All of these observations will be available for company owners to examine in the
future in order to boost activities. Moreover, all of this knowledge is available in
one convenient place. Inventory storage in the cloud can be accessed from
anywhere on the globe at any time.

This implies you can manage your inventory from the comfort of your present
location. This enables a more efficient and versatile inventory management
system that can be tailored easily for optimal performance and industry
dynamics within hours.
The success of a project execution depends on the review of requirements.
Requirements must be recorded, implementable, observable, testable, and
relevant to established business needs or opportunities, with adequate detail for
system design. Architectural, technological, behavioural, functional, and non-
functional requirements can all be met.

3.2. Feasibility
Since the framework's creation a decade ago, the Django project's stability,
success, and community have all expanded. Mostly on web and in textbooks,
detailed tutorials and best practices are readily accessible. With each new
version, the architecture adds important new features including database
migrations. I strongly suggest that new Python web developers start with the
Django framework because the official documentation and tutorials are among
the best in the industry. Django-specific groups exist in many cities, such as
Django District, Django Boston, and San Francisco Django, where new
developers can seek assistance when they get stuck.
There's some discussion about whether learning Python through Django is a bad
idea. However, if you take the time to study Python syntax and semantics before
diving into web creation, the critique is invalid.
• A Gradle-based build framework that is adaptable.
• A feature-rich and quick simulator.
• A single development environment for all Android devices.
• Use Instant Run to update your running app without having to create a new
APK.
• Code templates and GitHub integration to make it easier to create and import
sample code for popular app features.
• A wide range of research methods and frameworks
• Lint software to detect performance issues, usability issues, version
compatibility issues, and other issues.
• Support for C++ and the NDK.

3.3. Objective of Feasibility Study

There are 4 main feasibility evaluations for technology projects that are customer
facing, rather than just internal to the organisation. It is critical to include market
feasibility in these assessments.
The three feasibility studies are:

• Technical feasibility
• Schedule Feasibility
• Operational feasibility
• Financial feasibility
 3.3.1. Technical Feasibility

Technology programmes are infamous for being late, overbudget, or totally

failing. The great news is that mobile ventures perform much better. In
comparison, only 29% of non-android ventures received funding.
This rate of success is likely aided by the fact that mobile projects for large
companies are typically smaller and require less (or, unfortunately, no)
integration with existing company IT infrastructure. The shocking news is that
26% of mobile ventures are completed late, over budget, or with an
unsatisfactory outcome, and another 5% fail (canceled or not used). To prevent
being the third project to fail, you must conduct a rigorous technology feasibility
review.

3.3.2 Operational Feasibility

Operational feasibility is a metric for how well a proposed system solves

problems and exploits opportunities identified during project scope, as well as
how well it meets the requirements defined during the requirement specification
process of system development.

Reach desired results must be communicated during design and de- elopement
to ensure progress. Reliability, maintainability, supportability, accessibility,
disposability, sustainability, affordability, and other design-dependent
parameters are among them. If desired organisational behaviours are to be
realised, these criteria must be considered early in the design process.
To fulfil the previously stated parameters, system design and implementation
necessitates the timely and effective application of engineering and management
efforts. When a system's technological and operating characteristics are designed
into the design, it can best fulfil its intended function. As a result, operational
feasibility is an important feature of systems engineering that must be considered
early in the design process.
 3.3.1. Schedule Feasibility
If a project takes too long to finish until it is useful, it will fail. Typically, this
entails calculating how long the system would take to develop and determining
whether it can be done in the same amount of time using techniques such as
payback period. The timeliness of a project is measured by its schedule viability.
Are the project deadlines fair, given our technical expertise? Some ventures are
started with a deadline in mind. It's important to figure out whether the
deadlines are required or desirable.

3.3.1. Financial Feasibility

The following criteria can be used to assess the financial feasibility of a new
project.
• The project's total expected cost
• Project financing in terms of capital structure, debt-to-equity ratio, and other
factors.
a percentage of the overall expense borne by the promoter
• The promoter's existing investment in some other sector, including estimated
cash flow and likelihood.
 3.4. Methodology

The methodology is a broad research strategy that describes how research will be
conducted and, among other things, specifies the techniques that will be used.
These methodologies specify the means or modes of data collection, or, in certain
cases, how a particular outcome is to be measured. Even though the essence and
types of procedures to be followed in a particular procedure or to achieve a goal
are given a lot of consideration, methodology does not describe specific methods.
Such processes, when appropriate to a study of methodology, form a
constructive generic structure that can be breaks divided into smaller, combined,
or their sequence modified.

In the same way that a methodology is a constructive framework, so is a

paradigm. The application of paradigms meets most or all of the standards for
methodology in theoretical work. An algorithm, like a paradigm, is a type of
constructive system, meaning that the structure is made up of logical rather than
physical components. Any description of a method for calculating a particular
result is always a method description, never a methodology description. As a
result, it's important not to use technique as a synonym for process or body of
methods. This restricts it to the process itself, or the collection of methods, or the
instruments that should have been its result, and removes it from its true
epidemiological sense.

A technique is the planning process for conducting research or developing a

procedure; it is not an instrument, system, or procedure in and of itself.
 3.4.1. Use of Agile

Agile is the software development approach used to create this system. The agile
methodology is a collection of values, principles, and core practices for software
development. Communication, flexibility, feedback, and bravery are the four
virtues. We suggest that systems analysts apply these principles to all projects
they work on, not just those that follow an agile methodology. Adjustments in
project management are often required to complete a project.

Figure 3.1: The Agile Development Methodologies

 3.5. System Requirement
The system requirement specifies the system's core functionalities as well as its
security. There are two sections of them.

3.5.1.Functional Requirement

• Authentication
o Admin

o Manager

o Stuff

• Outlet: A shop that sells goods and services in smaller amounts to the general
populace. A retail outlet will normally purchase products at a volume discount
directly from producers or wholesale vendors, then mark them up for sale to end
consumers.
• Product: This product's category indicates what kind of product it is. Assume a
beauty product, a vegetable, a grosser, and a bakery item.

• Brand: The products purchased by the company come in a variety of brands

and from a variety of suppliers. Those will be included in the list.
• Unit: A stock holding unit (SKU) is a distinct category of item for sale, such as
a product or service, and all characteristics associated with the item type that
differentiate it from other item types in the field of inventory management.
Manufacturer, definition, material, size, colour, packaging, and warranty
terminology are examples of attributes for a product. When a company takes
stock of its inventory, it counts how much of each SKU it has.
• Supplier: Creative Minds' Supplier Product Inventory Management Extension
enables licensed distributors to integrate and manage items on your site's front-
end dashboard. This allows you, the website owner, to delegate the task of
importing and upgrading the items for sale on your store to product vendors
without granting them access to the admin panel.

Based on your preferences, various degrees of control or moderation may be

applied to all or some suppliers.

• Purchase: Purchase is what a business buys for their sell in order to make a
profit. There are a few instructions that must be followed when making a
purchase. The following are the rules:
o Items: The super shop must buy itemises because they are less time consuming
and help the company run smoothly.
o Payments: The app has a sue option for payments, so if a company wishes to
make partial payments, it can.

o Invoice: For each transaction record, the programme generates an invoice.

a collection of business guidelines for issuing invoices

o Search by outlet: The sales bill can be searched by outlet name. So that
management can decide who is responsible for making the first payment.

• Customer: A company's main source of sales and business is its customer base.
A client base is made up of existing clients who have paid for goods or services.
Existing customers are among the first to hear about new products. Depending
on the market, a client base may be categorised or described in a variety of ways.
• Items on Sale: The itemised bill is included in the transaction. So that if a
customer makes a purchase, he will get an itemised bill.

o Payments: Payments determine the actual bill and account for it.

o Invoice: This is the bill that the vendor sends to the consumer for any potential
problems. The invoice bill contains every aspect of the transaction.

• Stock: The stock displays the written stock report in different formats.
o Total product stock quantity: This displays the outlet's entire product line.
Admin can view all of the outlets' products or a particular outlet's product from
this page.
o Total amount of stock: This is where we can see the total stock's monetary
value.

o Product search: Whether we are looking for a specific product or want to know
the quantity of a specific product, we can quickly find it here.

• Filter by any date and outlet: If we need to know the length of a given date,
we can do so from this section.

Purchase info
Number of Invoices: How many invoices for the same sum of money are there?
Total Amount: How many different purchase amounts will you find here?

Total Paid: This is where you'll find the total sum you've paid.

Total Due: This is where you'll find the total amount owed.
Sale Info:

Number of Invoices: We can find the number of sell invoices here.

Total Number: The total amount of sellable items we can locate.

Total Paid: The total sum paid by a customer that we can locate.
Total Due: This is where you can find the total amount owed by the consumer.
Net Benefit: Total profit can be found by subtracting total profit from total profit.

3.5.1. Non-Functional Requirement

• Operational Requirement

• The device should run on a Windows platform, and it should prompt the
user to make a backup at the end of the working day.
• Requirements for performance
• The system can provide users with quick access to information about
superbugs and antibiotics.
• The system should make it simple for users to check a provider in a short
amount of time.
• A complaint about a store should be completed in a reasonable amount of
time by the system.

Security Requirements

• In order to login and make changes to the system, the system should
verify the username and password.

• The device could ask the user for their current password before allowing
them to change it.

•
Usability Requirement

• The device should have a simple graphical user interface that interacts
with the user.
• The framework should make it simple for users to understand how each
module works.

3.6. Entity Relationship Diagram (E-R diagram)

The Inventory Management System Entity is described by this ER (Entity
Relationship) Diagram. The entity-relationship diagram of the Inventory
Management System represents all of the database tables' visual instruments as
well as the relationships between Customer, Stock, Inventory, and Supplier,
among other things. It was used to define the relationships between structured
data groups of Inventory Management System interfaces using structure data.
Inventory, Customer, Purchasing, Stock, Payment, and Supplier are the key
components of the Inventory Management System.

The E-R diagram of our system is shown below here.

Figure 3.2: E-R Diagram for Inventory Management System

 3.7. Data Flow Diagram (DFD)
Inventory Management System A data flow diagram is frequently used as a first
step to construct a summary of the Inventory without going into great detail,
which can then be focused upon later.

Zero Level Data Flow Diagram:

It’s a quick summary of a whole Sales and Inventory Management System or
process being evaluated or modelled. It's intended to be a quick glance at

Supplier, Customer, and Login, displaying the system as a single high-level

process with its connections to external entities such as Inventory,
Parchasing,and Sales. It should be understandable to a wide range of people,
including Inventory, Sales, and Suppliers. I represented the high-level flow of the
Sales and

Figure 3.3: Level-0 Diagram of Inventory Management System

First Level Data Flow Diagram:

The Sales And Inventory Management System's First Level DFD (1st Level)
diagram illustrates how the system is divided into sub-systems (processes), each
of which deals with one or more data flows to or from an external agent, and
which together provide all of the system's functionality.

Figure 3.4: Level-1 Diagram of Inventory Management System

Second Level Data Flow Diagram:

DFD Level 2 delves much further into areas of Sales and Inventory Level 1. It
might be appropriate to add more Sales and Inventory functionalities to meet the
required level of detail on how Sales and Inventory work. The Sales and
Inventory Management System's First Level DFD (1st Level) depicts how the
system is divided into sub-systems (processes). More information about Login,
Customer, Supplier, Payment, Sales, Purchasing, and Inventory can be found in
the 2nd Level DFD.

Figure 3.5: Level-2 Diagram of Inventory Management System

 3.8. Use Case Diagram
The interactions among the elements of the Inventory Management System are
graphically depicted in this Use Case Diagram. It signifies the system review
approach for identifying, clarifying, and organising Inventory Management
System system specifications.
In this Use Case Diagram, the key actors of the Inventory Management System
are Super Admin, System User, Supplier, and Anonymous Users, who conduct
various use cases such as Manage Inventory, Manage Customer, Manage
Purchasing, Manage Receiving Stock, Manage Payment, Manage Supplier,
Manage Users, and Full Inventory Management System Operations.

Figure 3.6: Use Case Diagram of IMS System

 3.9. Database Design
PostgreSQL, also recognized as Postgres, is a relational database management
system that focuses on extensibility and SQL enforcement. SQL statements are
used for interactive queries against a relational database as well as data collection
for reports.
This chapter will explain how the database for the system is designed. Database
architecture is an essential component of software development. The database
architecture is inextricably linked to the program's ability to achieve productivity
and ease of data access.
Databases are data repositories that are used in computing systems. The
information is held in tables inside the database. Several tables were used to
recreate the data manipulation for the system. The following are two crucial
database settings:
• Primary Key - the area that is special for each occurrence of the record.
• Foreign Key - a field that is used to establish a link between tables.

User Table

SL No. Name Type Description

1 Id Int Primary Key
2 Name Text
3 Email Text
4 Password Text
5 Role Text
6 Outlet Int Foreign Key

Table 3.1: User Table

Outlet Table

SL No. Name Type Description

1 Id Int Primary Key
2 Name Text
3 Address Text
4 Number Big Int
5 Email Text
6 Note Text

Table 3.2: Outlet Table

Category Table

SL No. Name Type Description

1 Id Int Primary Key
2 Name Text
3 Note Text

Table 3.3: Category Table

Brand Table

SL No. Name Type Description

1 Id Int Primary Key
2 Name Text
3 Note Text

Table 3.3: Brand Table

Unit Table

SL No. Name Type Description

1 Id Int Primary Key
2 Name Text
3 Note Text

Table 3.3: Unit Table

Cost Table

SL No. Name Type Description

1 Id Int Primary Key
2 Name Text
3 Note Text

Table 3.3: Cost Table

Supplier Table

SL No. Name Type Description

1 Id Int Primary Key
2 Company Text
3 Owner Text
4 Number Big Int
5 Email Text
6 Address Text
7 Note Text

Table 3.3: Supplier Table

Customer Table

SL No. Name Type Description

1 Id Int Primary Key
2 Name Text
3 Number Big Int
4 Email Text
5 Address Text
6 Note Text

Table 3.3: Customer Table

Product Table

SL No. Name Type Description

1 Id Int Primary Key
2 SKU Text
3 Category Int Foreign Key
4 Brand Int Foreign Key
5 Unit Int Foreign Key
6 Name Text
7 Mfg Date
8 Exp Date
9 Details Text

Table 3.3: Product Table

Purchase Table
SL No. Name Type Description
1 Id Int Primary Key
2 Invoice Text
3 Outlet Int Foreign Key
4 Supplier Int Foreign Key
5 Discount float
6 Date DateTime

Table 3.3: Purchase Table

Purchase Items Table

SL No. Name Type Description

1 Id Int Primary Key
2 Purchase Int Foreign Key
3 Product Int Foreign Key
4 PurchasePrice float
5 SalePrice float
6 Quantity Int

Table 3.3: Purchase Items Table

Purchase Payments Table

SL No. Name Type Description

1 Id Int Primary Key
2 Purchase Int Foreign Key
3 Amount float
4 Date DateTime

Table 3.3: Purchase Payments Table

Sale Table

SL No. Name Type Description

1 Id Int Primary Key
2 Invoice Text
3 Outlet Int Foreign Key
4 Customer Int Foreign Key
5 Discount float
6 Date DateTime

Table 3.3: Sale Table

Sale Items Table

SL No. Name Type Description

1 Id Int Primary Key
2 Sale Int Foreign Key
3 Product Int Foreign Key
4 Price float
5 Quantity Int

Table 3.3: Sale Items Table

Sale Payments Table

SL No. Name Type Description

1 Id Int Primary Key
2 Sale Int Foreign Key
3 Amount float
4 Date DateTime

Table 3.3: Sale Payments Table

3.10. Implementation
Following the observation and gathering of user requirements from the JAD
session. Will begin analysing, designing, and implementing each module based
on the user requirements gathered.
Until beginning construction, the team performs a final check of the ideas from
the prototypes in a setting that is as similar to production as possible. The proof
of concept is usually a continuation of some early research work (preliminary
proof of concept) that took place during the Planning Phase. On a non-
production simulation of the planned operating environment, the proof of
concept measures key elements of the solution.
To confirm their criteria, the team walks operations workers and users through
the solution. The proof of concept may include some solution code or
documentation that is carried over to the final solution implementation
deliverable, but it is not intended to be production-ready. The proof of concept is
called throwaway development because it gives the team one last opportunity to
double-check the content of the functional specification and fix any remaining
problems before moving on to development.

The team creates the solution by extending the core components to meet the
solution's unique requirements. Individual unit functional assessments are also
developed and conducted by the team to ensure that individual requirements are
met.
Specifications are met by the features. MSF suggests that project teams conduct
regular builds of their solution as a best practice. Simply adding various pieces of
code together to create a solution that can be executed on a regular basis offers a
variety of useful benefits. A regular build reveals unanticipated structural flaws
and simplifies defect diagnosis. During the available time, the regular build
should be subjected to as much of the complete suite of tests as possible. This
construct validation test pass aids in the early detection of integration flaws. It
also enables the team to verify their research methodology and facilities.
A team creates a testing infrastructure and fills it with test cases to ensure that
the entire solution works as anticipated. Individual feature tests used by
developers in designing solution components are usually included in this
solution test suite as a subset. MSF recommends planning regular builds of all
solution components for testing and analysis. This method is recommended for
both the creation of code and the assembly of hardware and software
components. The method of developing in-term builds helps a team to identify
problems early in the development process, reducing the project's development
cycle and expense. The practice of installing all of the components in order to
reach the final target of a solution is known as daily builds. This allows the team
to decide whether or not all elements can fit together sooner rather than later.
The team can also add features to a stable build using this tool. The aim is to
have a shippable product available at all times. As a result, the overall stability of
the solution is well known and adequate test data is available before it is released
into production.

3.6. Features
The device can be used for a variety of applications, and a few of its unique
features allow it to be used all over the world. Among the features are:
• The ability to store data in tables is the most important function. The fact that
data is stored in a standardized format will reduce iteration time significantly.
• It builds indexes for faster data retrieval by storing data in rows and columns
and allowing a facility primary key to establish specific row identification.
• Enables various types of data integrity, such as I Entity Integrity, where no
duplicate rows in a table exist, (ii) Domain Integrity, which enforces valid entries
for a given column by filtering the type, format, or wide use of values, (iii)
Referential Integrity, which prevents the deletion of rows that are used by other
records, and (iv) User Defined Integrity, which allows users to define their own
data integrity.
• Allows for the development of virtual tables, which provide a secure way to
store and secure sensitive data.
• RDBMS features include common column implementation as well as multi-
user usability.
 3.6. Applications
There are certain requirements the proposed application must fulfill to meet the
objectives of the project. The requirements to be achieved

3.6.1.Dynamic dashboard:

An organization's inventory is its life blood. I am offering ultimate inventory

management system to keep good track of inventory. A sensitive and interactive
dashboard is at the heart of the framework. the overall picture of the device Here
are some options for gaining immediate access to critical systems such as
invoicing, POS invoicing, goods, consumer, sales, and stock management
systems, among others.
Monthly progress report will be shown as a histogram on the dashboard. It also
has a graphical representation of the total amount of customers, suppliers, and
goods.

3.6.2.Easy invoicing system:

I made invoicing as simple as possible. With just a few taps, you can start
invoicing. You can generate a new invoice, a POS invoice, and get a simple
invoice management system in this section. Here you can build a new invoice
with product details, cartoon number, quantity, cost, discount, total amount, and
so on. Invoicing at the point of sale with barcode monitoring. Invoice
management saves all of your invoices in one place and allows you to manage
them on a timely basis.

3.6.3.Product Management:

You can use this module to bring your company to life in front of your eyes and
comfortably control your product while you sleep. The product section holds
details such as the product name, model, quantity, sales price, and supply price.
You can also monitor your product by scanning a barcode or QR code.
 3.6.4.CRM system:

Maintaining customer relationships is more important than can sales while

you're in company. CRM is necessary for the long business success. To assist you
in managing the customer relationship, I have included a customer section. The
parts that make up this function are as follows:

• Add a client: Fill in the blanks with information about the customer. Their
name, title, phone number, and email address, for example.

• Manage customer: Manage and update the customer's details.

• Credit customer: Separately manage your credit customer info.

• Paid customer: Separately manage your paid customer info.

3.6.5.Category based management system:

With the category choice, you can categorise any product detail based on
different variants. For this feature, you'll get the following system:
• Add category: You can make as many categories as you like.
• Manage categories: Select, update, manage, and obtain relevant information
about your items by clicking, dragging, and dropping.
 3.6.6.Supply chain management:

To ensure the best supply chain strategy, collect all supplier data. This function is
used to save supplier information such as name, address, contribution, and
actions. On behalf of your supply chain management, I have the best structural
data. This feature contains the following:

• Add a supplier: Enter and save supplier information such as name, contract,
and address.
• Manage supplier data: Edit, delete, and change supplier data.
• Supplier ledger: Get the ledger and keep track of your suppliers. You'll also get
a retailer ledger and a revenue basis.
• Payment history for suppliers: Input payment history for suppliers.
• Supplier information: Supplier details inform you the current status of your
supplier.

3.6.7.Purchase management:
You can earn good profits if you are more efficient in your purchasing. This is the
framework for keeping track of all of your records, estimating, and making
informed purchasing decisions. Our feature consolidates all of your data in one
location, allowing you to outperform your competition.
• Add a purchase: Enter the details of your purchase, such as the supplier's
name, date, invoice number, product details, quantity, stock size, and price.
• Manage purchases: connect, delete, and manage records to see the status of
your purchases in real time.
 3.12.1. Stock management system:

My software system helps in increasing and decrease stock levels for new items,
refunds, damages, shrinkage, and promotions, as well as multi-item stock
adjustments. You should keep track of your inventory on a FIFO-LIFO basis.
There are several parts below that will provide you with specific information:

• Stock report: This feature displays a stock report that includes information
such as the product name, model, quantity, selling price, supplier price, stock
out, stock in, and stock in hand.

• Supplier wise stock report: Get a stock report based on your supplier.

• Product wise stock report: Get a stock report based on your product.
 Chapter 4 - User Manual

4.1. Introduction
Several relevant diagrams were created at the end of the system requirements
collection in order to prepare the system model design. Designing the project
architecture and graphical user interfaces, as well as developing relational
databases, business logic, and file requirements, are all part of the design
process.

Microsoft's Visual Studio Code is a free source-code editor for Windows, Linux,
and macOS. Functionalities involve assistance for debugging, syntax
highlighting, intelligent code completion, snippets, code refactoring, and
embedded Git. Rather than using a project system, it enables users to open one or
more files, which can then be stored in workspaces for later use. This enables it to
act as a language-independent code editor for any language.

It supports a variety of programming languages, each with its own set of

features. The settings can be used to remove unwanted files and directories from
the project tree. Many Visual Studio Code features are only accessible via the
command palette, rather than through menus or the user interface.

4.2 Computer Software Requirements

• The uses of software for our computer side to development the

Inventory system.
• Operating System: Windows 7/8/10 (32 - or 64bit)
• IDE: Visual Studio Code
• PostgreSQL for database
• Postman (For API testing)
• Python Django Framework for backend
 • JavaScript React for frontend
• Windows 7/8/10 (32 - or 64bit)
• Google Chrome (Browser)

4.3 User Interfaces

This illustrates the graphical user interface of my project. by following this chapter, a
user can come to know how all the modules of this project works and how to use this
application in a user-friendly way

4.3.1. Authentication Authorization - Admin

• Admin login credential given by developer and admin can change this
credential after login.
• Create a unique outlet
• Create manager for individual outlet
• Admin can access all features and functionalities

4.3.2. Authentication Authorization - Manager

• Each outlet manager created by admin

• The manager can change login credential s
• Cannot create outlet
• Create stuff in this outlet
• Can access only this outlet information
4.3.3. Authentication Authorization - Stuff

• Each outlet stuff created by that outlet manager

• The stuff can change login credential s
• Cannot create outlet and manager
• Can access only this outlet information

Figure 4.1: Authentication and Authorization

This is the Login page of my website. Here you can login our app. If you login
then you will use all service of our app. After Sign up or login user directly go
to the dashboard. Figure 4.3 describe the Login page of Inventory System.

Figure 4.2: Login page

4.3.5. Dashboard

This is the home page of my website. Here we can see the item of our app. Which
you need just click on it and go inside for work. Without login a you cannot use
all item. From dashboard user can go any module and use any module to click
it. Figure 4.3 describe the dashboard of Inventory system.

Figure 4.3: Dashboard

4.3.6. Outlet

• Only admin can access

• Each outlet has unique name, address and contact number
• Search any outlet by any information

Figure 4.4: Outlet List

4.3.7. Manager

Figure 4.5: Manager

4.3.8. Profile

Figure 4.6: Admin profile

4.3.9. Staff

Figure 4.7: stuff List

4.3.10. Category

Figure 4.8: All category

4.3.11. Brand

Figure 4.9: All Brand

4.3.12 unit

Figure 4.10: unit list

4.3.13. Product

• Add all kinds4 of product

• Manage category, brand and unit of product
• Each product has unique product code called SKU
• Stock Keeping
• All outlet can access this feature

Figure 4.11: Product List

4.3.14. Supplier

• Create supplier for purchase product

• Create customer for sale product
• Each supplier and customer have unique id
• Track all history by that id

Figure 4.12: List of Suppler

4.3.15. Customer

Figure 4.13: List of Customer

4.3.16. Purchase
• Purchase product from supplier Sale product to customer
• Handle multiple items and payment in one invoice
• Filter any invoice by outlet, invoice, date, supplier and customer
• Print and make pdf of each invoice
• Easy to see total amount, paid, dues and sale profit

Figure 4.14: All Purchase

4.3.17. Purchase Items

Figure 4.15: purchase items

4.3.18. Purchase Payments

Figure 4.16: All Purchase payments

4.3.17. Sale

Figure 4.17: All Sale

4.3.19. Sale Items

Figure 4.18: All Sale items

4.3.20. Sale Payments

Figure 4.19: Outlet List

4.3.21. Adding multiple items at once

When a user is selling an item that is pre-sold (i.e.: the item has a customer
associated to it) the system will ask the user if other items that are available in
the inventory and belong to the same customer, this can be added to the invoice
as well. Multiple items will be added only if:

• They belong to the same customer

• They have the same aging.
• The aging cannot be negative.

Figure 4.20: All Sale Items

 Figure 4.21: All Sale Payment

4.3.24. Product Stock

• View each product purchase price, purchase quantity, sale quantity

• Each product stock quantity and total amount of stock
• Search any product by SKU and product name

Figure 4.22: Stock

4.3.25. Report Generation

View sales history in the form of a list of your most popular products. This
feature also enables you to manage items in your inventory that have not
reached the sales levels you expected, for example, by offering discounts on
them.

Figure 4.23: Report Generation

4.3.26. Invoices

An Invoice is a document sent to your client that indicates the

products/services sold by you with the payment information that the client has
to make.

• A new Invoice page opens up.

• The Customer Name field will help you choose the customer for who, you
wish to raise an invoice. You can also add a new customer from an
invoice.

• Invoice Number can be auto generated or you can manually enter it by

clicking on the gear icon on the Invoice Number tab and configuring it.

• If you have a physical sales order or say a purchase order from your
customer in hand, using the Order number field, you can record the order
number of the sales order associated with the invoice.

• By default, the Invoice Date will be the date on which you create the
invoice. But you can change it if you wish.

• You can set the due date for the invoice by choosing one of the standard
options in the Terms tab or by mentioning your own date.

• If you want to apply a price list to an invoice, you can select one from the
Price List dropdown at the transaction level or at the line item level.

• If you have enabled associating a Sales person in the settings, you can add
a sales person in the Sales person tab.
Figure 4.24: Invoice
 Chapter5-conclusions
5.1 Conclusions
Inventory management is a crucial feature that aids and maintains
manufacturing companies' performance. The successful introduction of
inventory would greatly boost the entire company. Modern inventory
management systems employ new and refined techniques that allow for
dynamic inventory optimization to improve customer experience while reducing
inventory and costs. The aim of good inventory management is to improve
rather than to achieve perfection. These enhancements should not be seen as a
one-time project, but rather as a long-term commitment. Increased sales and
earnings, a supportive work environment, and an overall improvement in
customer satisfaction are all examples of inventory management's return on
investment. A genuinely successful inventory management system can reduce
the complexity of organising, implementing, and managing a vital supply chain
network for business success.
Inventory managemnt is essential to the smooth operation of government
agencies. Inventory decisions must be rationally made on the basis of
quantitative assessment of the related factors involved for proper inventory
management. Fixing minimum and maximum quantities, assessing the amount
of inventory to be transported, deciding on issues, receipts, inspection
procedures, determining the economic order quantity, adequate storage facilities,
keeping track of obsolescence, and ensuring control over inventory movement
are all part of inventory management. As a result, inventory management is
important to a company's economic operations. It is critical to reduce the amount
of capital locked up in inventories in order to improve an organization's
operating performance and profitability. As a result, it's important to keep
inventory under control.
“Every Benchmark is complex, challenge them for continuous improvement” in
today's dynamic market. To stay competitive, every company must identify the
process, set the bar for success, and work to achieve it by strategizing and
designing an atmosphere, allocating necessary resources, and effectively
monitoring.In the management of materials handling, the inventory system is a
critical problem. It is highly controllable, and there are a plethora of scientific
models available in the literature to help us select the best inventory strategy.
5.3. Bibliography
1. Inventory Management Explained: A focus on Forecasting, Lot
Sizing, Safety Stock, and Ordering by David J. Piasecki
2. Essentials of Inventory Management by Max Muller
3. Inventory Accuracy: People, Processes, and Technology by
David J. Piasecki
4. Achieving Effective Inventory Management, 5th ed. Perfect
Paperback by Jon Schreibfeder
5. https://www.unleashedsoftware.com/blog/causing-inventory-
management-problems-avoid
6. https://creately.com/diagram/example/hjrneh3l/New%20E-
R%20Diagram%20for%20Inventory%20Management%20System
7. https://www.tutorialspoint.com/dbms/er_diagram_representation.
htm
8. https://iansommerville.com/software-engineering-
book/static/web/feasibility-study/
9. https://www.investopedia.com/terms/c/carrying-costs.asp
10. https://www.supplychain247.com/article/the_problem_with_
traditional_inventory_management
11. https://www.hashmicro.com/blog/tips-to-manage-item-
stocks-in-your-warehouse/
12. https://dashboardstream.com/successfully-managing-
multiple-retail-outlets-with-proper-inventory-management/
13. https://www.c-
sharpcorner.com/UploadFile/47fc0a/feasibility-study-in-project-
development/
14. https://www.datapine.com/blog/business-intelligence-
reporting/
15. https://www.tradegecko.com/inventory-management
16. https://quickbooks.intuit.com/accounting/purchase-orders/
17. https://lionbridge.ai/articles/what-is-product-categorization/
 Appendices

Appendix A---Visual Studio code editor

Figure A.1: Visual Studio Code Editor

Appendix B
PostSQL Control Panel

Figure B.1: PostgreSQL Control Panel