VISVESVARAYA TECHNOLOGICAL UNIVERSITY

BELAGAVI

Synopsis of

Mini Project Work entitled

“INVENTORY MANAGEMENT SYSTEM”

Submitted by

ABHINAV.A. BALOL 4BB20CS011

ANAND.H. BETAGERI 4BB20CS025

Under theGuidance of
Mr. Venkatesh K,B.E.,M. Tech
Associate Professor

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

DEPARTMENT OF INFORMATION SCIENCE & ENGINEERING

Bahubali College of Engineering
Shravanabelagola-573 135
2022-23

I
 BAHUBALI COLLEGE OF ENGINEERING
Shravanabelagola - 573135

DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

_________________________________________________________

CERTIFICATE
This is to certify that the Mini Project Work entitled “Inventory

ManagementSystem” is work carried out by bonafide students of Bahubali College of

Engineering,Abhinav. A. Balol (USN:4BB20IS011),Anand. H. Betageri
(USN:4BB20IS002) in partial fulfilment of V Semester to award the Bachelor Degree in
Information Science and Engineering of the Visvesvaraya Technological University,
Belagavi during the year 2022-23. It is certified that all corrections/suggestions indicated for
Internal Assessment have been incorporated in the Report and deposited in the department
library. The Mini Project Report has been approved as it satisfies all the academic requirements
in respect of Mini Project Work prescribed for the Bachelor of Engineering Degree.

Mr. Venkatesh K Mr. Venkatesh K Dr. Yashodha M

Asso. Prof & Guide Asso. Prof & Coordinator Prof & HOD

Name of the Examiners Signature with Date

1.

2.

II
 ACKNOWLEDGEMENT

Inspiration and guidance are valuable in all aspects of life, especially what is
academic. “Experience is the best teacher”, is an old saying. The satisfaction and
pleasure that accompany the gain of experience would be incomplete without
mentioning the people who made it possible.

We are extremely thankful and grateful to our guide Mr. Venkatesh K,

Associate Professor, Department of Computer Science and Engineering. He being
our guide has taken keen interest in the progress of the Mini Project by providing
facilities and guidance. We want to indebted to our guide for his inspiration, support
and kindness showered throughout the course.

We express our heartfelt gratitude to our mini project Coordinator Mr.

Venkatesh K, Associate Professor, Department of Computer Science and
Engineering for providing the support for making our Mini Project work possible.

We express our profound sense of gratitude to Dr. Yashodha, Professor & HOD,
Department of Information Science and Engineering for giving us the opportunity to
pursue our interest in our Mini Project work.

We express our special gratitude to our Principal Dr. Sunil Kumar D for
providing the resources and support for making our Mini Project work.

Nevertheless, we express heartfelt thanks towards our parents, friends and

teaching and non-teaching staff of our college for their kind co-operation and
encouragement which helps us to completion of our Mini Project.

Abhinav. A. Balol

Anand. H.Betageri
III
 CONTENTS

CHAPTER 1: INTRODUCTION OF PROJECT 01-10

1.1. Introduction to database management system (DBMS) 01
1.2. DBMS architecture 02-05
1.2.1. 3-tier Architecture 02
1.2.2. Table(database) 04
1.2.3. Field Content 04
1.2.4. Record & Row 04
1.2.5. Column 05
1.2.6. NULL value 05
1.3. SQL Define 05-07
1.3.1. SQL 06
1.3.2. A Brief History of SQL 06
1.3.3. SQL Process 06
1.3.4. SQL Commands 07
1.4. Advantages of DBMS 08
1.5. Application and Uses of Database 09-10
1.5.1. Online Shopping 09
1.5.2. Library Management System 09
1.5.3. Banking 09
1.5.4. Universities and Colleges 09
1.5.5. Credit and Transaction 10
1.5.6. Social Media Sites 10
1.5.7. Telecommunications 10
1.5.8. Finance 10
1.5.9. Military 10
1.5.10. Railway Reservation System 10
CHAPTER 2: REQUIREMENT ANALYSIS 11-11
2.1. Input Requirement 11
2.2. Output Requirement 11
2.3. Hardware Requirement 11

IV
2.4. Software Requirement 11
CHAPTER 3: DESIGN 12-16
3.1. Entity-Relationship Diagram (Model) 12
3.2. Relational Model 15
3.3. Database Schema 15
CHAPTER4: IMPLIMENTATION 17-18
4.1. Front End 17
4.2. Back End 18
CHAPTER5: RESULTS 19-22
5.1. Front Page 19
5.2. Admin Login Page 19
5.3. Student login page 20
5.4. First Page 20
5.5. Student registration page 21
5.6. Issue Book Page 21
5.7. Status Page 22
5.8. Return Book Page 22
CONCLUSION 23-23
REFERENCES 24-24

V
 ABSTRACT
The "Inventory Management System"is aimed at developing a desktop
application named inventory management system for managing the inventory system. It
allows to maintain the records of user and to change the profile also.This system has
been developed to allow users to add item,delete an item,enter item quality and others
details,update item status.

Inventory Management System, as described above, can lead to error free,

secure, reliable and fast management system. It can assist the user to concentrate on
their other activities rather to concentrate on the record keeping. Thus, it will help
organization in better utilization of resources. The organization can maintain
computerized records without redundant entries. That means that one need not be
distracted by information that is not relevant, while being able to reach the information.

VI
 Inventory Management System

CHAPTER 1

INTRODUCTION
1.1. Introduction to database management system (DBMS)

A database management system (DBMS) is system software for

creating and managing databases. The DBMS provides users and programmers
with a systematic way to create, retrieve, update and manage data.A DBMS
makes it possible for end users to create, read, update and delete datain a
database. The DBMS essentially serves as an interface between the database
and end users or application programs, ensuring that data is consistently
organized and remains easily accessible.
The DBMS manages three important things: the data, the data base
engine that allows data to be accessed, locked and modified -- and the database
schema, which defines the database’s logical structure. These three foundational
elements help provide concurrency, security, data integrity and uniform
administration procedures. Typical database administration tasks supported by
the DBMS include change management, performance monitoring/tuning and
backupand recovery. Many database management systems are also responsible
for automated rollbacks, restarts and recovery as well as the loggingand
auditing of activity.
The DBMS is perhaps most useful for providing a centralized view of
data that can be accessed by multiple users, from multiple locations, in a
controlled manner. A DBMS can limit what data the end user sees, as well as
how that end user can view the data, providing many views of a single database
schema. End users and software programs are free from having to understand
where the data is physically located or on what type of storage media it resides
because the DBMS handles all requests.

1
 Inventory Management System

The DBMS can offer both logical and physical data independence. That
means it can protect users and applications from needing to know where data is
stored or having to be concerned about changes to the physical structure of data
(storage and hardware).

SQL as API
1.2. DBMS -Architecture

The design of a DBMS depends on its architecture. It can be centralized or

decentralized or hierarchical. The architecture of a DBMS can be seen as either
single tier or multi-tier. An n-tier architecture divides the whole system into
related but independent n modules, which can be independently modified,
altered, changed, or replaced.
In 1-tier architecture, the DBMS is the only entity where the user directly
sits on the DBMS and uses it. Any changes done here will directly be done on
the DBMS itself. It does not provide handy tools for end-users. Database
designers and programmers normally prefer to use single-tier architecture.
If the architecture of DBMS is 2-tier, then it must have an application
through which the DBMS can be accessed. Programmers use 2-tier architecture
where they access the DBMS by means of an application. Here the application
tier is entirely independent of the database in terms of operation, design, and
programming.

2
 Inventory Management System

1.2.1. 3-tierArchitecture
3-tier architecture separates its tiers from each other based on the
complexity of the users and how they use the data present in the database. It
is the most widely used architecture to design a DBMS.

Fig. 1.2: DBMS 3-tier architecture

 Database (Data) Tier − At this tier, the database resides along

with its query processing languages. We also have the relations
that define the data and their constraints at this level.
 Application (Middle) Tier − At this tier reside the application
server and the programs that access the database. For a user, this
application tier presents an abstracted view of the database. End-
users are unaware of any existence of the database beyond the
application. At the other end, the database tier is not aware of any
other user beyond the application tier. Hence, the application layer
sits in the middle and acts as a mediator between the end-user and
the database.
 User (Presentation) Tier − End-users operate on this tier and they
know nothing about any existence of the database beyond this layer. At
this layer, multiple views of the database can be provided by the
application. All views are generated by applications that reside in the
application-tier.

3
 Inventory Management System

Multiple-tier database architecture is highly modifiable, as almost all its

components are independent and can be changed independently.
Data models define how the logical structure of a database is modelled.
Data Models are fundamental entities to introduce abstraction in a DBMS.
Data models define how data is connected to each other and how they are
processed and stored inside the system.
The very first data model could be flat data-models, where all the data
used are to be kept in the same plane. Earlier data models were not so
scientific; hence they were prone to introduce lots of duplication and update
anomalies.

1.2.2. Table(database)

A table is a collection of related data held in a structured format within a

database. It consists of columns, and rows.
In relational databases, and flat file databases, a table is a set of data
elements (values) using a model of vertical columns (identifiable by name) and
horizontal rows,the cell being the unit where a row and column intersect. A table
has a specified number of columns, but can have any number of rows. Each row is
identified by one or more values appearing in a particular column subset. The
columns subset which uniquely identifies a row is called the primary key.
"Table" is another term for "relation"; although there is the difference in that a table is
usually a multiset(bag) of rows where a relation is a set and does not allow duplicates.
Besides the actual data rows, tables generally have associated with them some
metadata, such as constraints on the table or on the values within particular
columns.The data in a table does not have to be physically stored in the database.
Viewsalso function as relational tables, but their data are calculated at query time.

4
 Inventory Management System

1.2.3. Field content

Every table is broken up into smaller entities called fields. The fields in the
BILLING table consist of ID, UNAME, BILL & DATE.A field is a column in a
table that is designed to maintain specific information about every record in the
table.

1.2.4. Record &Row

A record is also called as a row of data is each individual entry that exists
in a table. For example, there are 4 records in the above BILLING table.
Following is a single row of data or record in the BILLING table.

1.2.5. Column
A column is a vertical entity in a table that contains all information
associated with a specific field in a table.For example, a column in the BILLING
table is PRODUCT_ID, which represents product description.

1.2.6. NULL value

A NULL value in a table is a value in a field that appears to be blank,

which means a field with a NULL value is a field with no value.It is very
important to understand that a NULL value is different than a zero value or a field
that contains spaces. A field with a NULL value is the one that has been left blank
during a record creation.
SQL supports a special value known as NULL which is used to represent
the values of attributes that may be unknown or not apply to a tuple. For example,
the Apartment number attribute of an address applies only to address that are in
apartment buildings and not to other types of residences.

5
 Inventory Management System

1.3. SQL Define

SQL is Structured Query Language, which is a computer language for
storing, manipulating and retrieving data stored in a relational database.
SQL is the standard language for Relational Database System. All the
Relational Database Management Systems (RDMS) like MySQL, MS Access,
Oracle, Sybase, Informix, Postgres and SQL Server use SQL as their standard
database language.Also, they are using different dialects, such as −

• MS SQL Server using T-SQL,

• Oracle using PL/SQL,
• MS Access version of SQL is called JET SQL (native format) etc.
1.3.1. SQL
SQL is widely popular because it offers the following advantages −
 Allows users to access data in the relational database management
systems.
 Allows users to describe the data.
 Allows users to define the data in a database and manipulate that data.
 Allows to embed within other languages using SQL modules,
libraries &pre- compilers.
 Allows users to create and drop databases and tables.
 Allows users to create view, stored procedure, functions in a database.
 Allows users to set permissions on tables, procedures and views.
1.3.2. A Brief History of SQL
 1970 − Dr. Edgar F. "Ted" Codd of IBM is known as the father of
relational databases. He described a relational model for databases.
 1974 − Structured Query Language appeared.
 1978 − IBM worked to develop Codd's ideas and released a
product named System/R.
 1986 − IBM developed the first prototype of relational database
and standardized by ANSI. The first relational database was
released by Relational Software which later came to be known as
Oracle.

6
 Inventory Management System

1.3.3. SQL Process

When you are executing an SQL command for any RDBMS, the system
determines the best way to carry out your request and SQL engine figures out how
to interpret the task.
There are various components included in this process.These components are –
• Query Dispatcher
• Optimization Engines
• Classic Query Engine
• SQL Query Engine, etc.
A classic query engine handles all the non-SQL queries, but a SQL query
engine won’t handle logical files.

Fig. 1.3: Simple diagram of SQL Architecture

1.3.4. SQL Commands
The standard SQL commands to interact with relational databases are
CREATE, SELECT, INSERT, UPDATE, DELETE and DROP. These commands
can be classified into the following groups based on their nature−
Sr. Command &
No. Description
CREATE
1
Creates a new table, a view of a table, or other object in the database.
ALTER
2
Modifies an existing database object, such as a table.
DROP
3
Deletes an entire table, a view of a table or other objects in the database.
• DDL – Data Definition Language

7
 Inventory Management System

• DML – Data Manipulation Language

Sr. Command &

No. Description
SELECT
1
Retrieves certain records from one or more tables.
INSERT
2
Creates a record.
UPDATE
3
Modifies records.
DELETE
4
Deletes records.

 DCL - Data Control Language

Sr. Command &
No. Description
GRANT
1
Gives a privilege to user.
REVOKE
2
Takes back privileges granted from user.

1.4. Advantages of DBMS

Using a DBMS to store and manage data comes with advantages, but also overhead.
One of the biggest advantages of using a DBMS is that it lets end users and
application programmers’ access and use the same data while managing data integrity.
Data is better protected and maintained when it can be shared using a DBMS instead
of creating new iterations of the same data stored in new files for every new
application. The DBMS provides a central store of data that can be accessed by
multiple users in a controlled manner.
Central storage and management of data within the DBMS provides:

• Data abstraction and independence

• Data security

8
• A locking mechanism for concurrent access

9
 Inventory Management System

• An efficient handler to balance the needs of multiple applications

using the same data
• The ability to swiftly recover from crashes and errors, including
restart ability and recoverability
• Robust data integrity capabilities
• Logging and auditing of activity
• Simple access using a standard application programming interface (API)
• Uniform administration procedures for data
Another advantage of a DBMS is that it can be used to impose a logical,
structured organization on the data. A DBMS delivers economy of scale for
processing large amounts of data because it is optimized for such operations.
A DBMS can also provide many views of a single database schema. A view
defines what data the user sees and how that user sees the data. The DBMS
provides a level of abstraction between the conceptual schema that defines the
logical structure of the database and the physical schema that describes the files,
indexes and other physical mechanisms used by the database. When a DBMS is
used, systems can be modified much more easily when business requirements
change. New categories of data can be added to the database without disrupting the
existing system and applications can be insulated from how data is structured and
stored.

1.5. Applications and Uses of Database Management System

Due the evolution of Database management system, companies are getting more from
their work because they can keep records of everything. Also, it makes them faster to
search information and records about any people or product that make them more
effective in work. So here we are sharing some of the applications and uses of
database management system (DBMS).

10
 Inventory Management System

1.5.1. Online Shopping

Online shopping has become a big trend of these days. No one wants to
go to shops and waste his time. Everyone wants to shop from home. So, all
these products are added and sold only with the help of DBMS. Purchase
information, invoice bills and payment, all of these are done with the help of
DBMS.

1.5.2. Library Management System

There are thousands of books in the library so it is very difficult to keep
record of all the books in a copy or register. So, DBMS used to maintain all
the information relate to book issue dates, name of the book, author and
availability of the book.

1.5.3. Banking
We make thousands of transactions through banks daily and we can do
this without going to the bank. So how banking has become so easy that by
sitting at home we can send or get money through banks. That is all possible
just because of DBMS that manages all the bank transactions.

1.5.4. Universities and Colleges

Examinations are done online today and universities and colleges
maintain all these records through DBMS. Student’s registrations details,
results, courses and grades all the information is stored in database.

1.5.5. Credit Card Transactions

For purchase of credit cards and all the other transactions are made
possible only by DBMS. A credit card holder knows the importance of their
information that all are secured through DBMS.

11
 Inventory Management System

1.5.6. Social Media Sites

We all are on social media websites to share our views and connect
with our friends. Daily millions of users signed up for these social media
accounts like Facebook, twitter, Pinterest and Google plus. But how all the
information of users is stored and how we become able to connect to other
people, yes, this all because DBMS.

1.5.7. Telecommunications
Any telecommunication company cannot even think about their
business without DBMS. DBMS is must for these companies to store the call
details and monthly post-paid bills.

1.5.8. Finance
Those days have gone far when information related to money was
stored in registers and files. Today the time has totally changed because
there are lots of thing to do with finance like storing sales, holding
information and finance statement management etc.

1.5.9. Military
Military keeps records of millions of soldiers and it has millions of
files that should be keep secured and safe. As DBMS provides a big security
assurance to the military information so it is widely used in militaries. One can
easily search for all the information about anyone within seconds with the help
of DBMS.

1.5.10. Railway Reservation System

Database is required to keep record of ticket booking, train’s departure and
arrival status. Also, if trains get late then people get to know it through database
update.

12
 Inventory Management System

CHAPTER 2

REQUIREMENT ANALYSIS
2.1. Input requirements:

The admin must be able to enter the details of every item, purchase details.
Admin must be able to create their account and must be able to reset the password.
Admin should be able to add new items also and upload the image of the item.

2.2. Output requirements:

Admin must be able to login to main page and must be able to enter the sale
details, purchase details. Admin should be convenient and able to enter the details about
every item. Adminshould be able to fetch the data of the itemsas well as update the
details of the item also. Admin should be able to see the total number ofsalesdone so far
and edit the customer details. Admin must also be able to search any item by providing
the product Id.

2.3. Hardware requirements:

 Processor: Intel Core i5
 Processor Speed: 2.3 GHz
 Solid State Drive (SSD): 512GB
 Random Access Memory (RAM): 1 GB
 System Type: 64 Bit

2.4. Software requirements:

 Operating System (OS): Windows 10
 Front End Tool: Phyton
 Back End Tool: SQL
 Database: MySQL

13
 Inventory Management System

CHAPTER 3

DESIGN
Database design is the process of producing a detailed data model of
database. This data model contains all the needed logical and physical design
choices and physical storage parameters needed to generate a design in a data
definition language, which can then be used to create a database. A fully
attributed data model contains detailed attributes for each entity.
Inturn database design can be used to describe many different parts of
the design of an overall database system. Principally, and most correctly, it can
be thought of as the logical design of the base data structures used to store the
data. In the relational model these are the tables and views. In an object
database the entities and relationships map directly to object classes and named
relationships. However, the term database design could also be used to apply to
the overall process of designing, not just the base data structures, but also the
forms and queries used as part of the overall database application within the
database management system.

3.1. Entity-Relationship Diagram (Model)

Entity-Relationship (ER) Model is based on the notion of real-world

entities and relationships among them. While formulating real-world scenario
into the database model, the ER Model creates entity set, relationship set,
general attributes and constraints.ER Model is best used for the conceptual
design of a database. ER Model is based on,
 Entities and their attributes.

Relationships among entities

14
 Inventory Management System

 Entity −An entity in an ER Model is a real-world entity having properties

called attributes. Every attribute is defined by its set of values called
domain. For example, in a school database, a student is considered as an
entity. Student has various attributes like name, age, class, etc.
 Relationship −The logical association among entities is called
relationship. Relationships are mapped with entities in various ways.
Mapping cardinalities define the number of associations between two
entities.
 Mapping Cardinalities

 One to One

One instance of an entity (A) is associated with one other

instance of another entity (B). For example, in a database of
customer, each customer name (A) is associated with only one user
number (B).

 One to Many

One instance of an entity (A) is associated with zero, one or many

instances of another entity (B), but for one instance of entity B there is
only one instance of entity.
A The administrator has all the information about all the users and about
all products. Only admin have access into this admin page. Admin may
be the owner of the shop.

15
 Inventory Management System

 Many to Many

One instance of an entity (A) is associated with one, zero or many

instances of another entity (B), and one instance of entity B is associated
with one, zero or many instances of entity A. The application was
designed into two modules first is for the customers who wish to buy the
articles.
Once the authorized personnel feed the relevant data into the system,
several reports could be generated as per the security.

E-R for Inventory Management

16
 Inventory Management System

3.2. Relational Model

The most popular data model in DBMS is the Relational Model. It is

more scientific a model than others. This model is based on first-order predicate
logic and defines a table as an n-array relation. For an ex:

Fig. 3.3: Relational Model Diagram

The main highlights of this model are

 Data is stored in tables called relations.

 Relations can be normalized.

 In normalized relations, values saved are atomic values.

 Each row in a relation contains a unique value.

 Each column in a relation contains values from a same domain.

3.3. Database Schema

A database schema is the skeleton structure that represents the
logical view of the entire database. It defines how the data is organized and
how the relations among them are associated. It formulates all the
constraints that are to be applied on the data.

17
 Inventory Management System

A database schema defines its entities and the relationship among them. It
contains a descriptive detail of the database, which can be depicted by means of
schema diagrams. It’s the database designers who design the schema to help
programmers understand the database and make it useful.

A database schema can be divided broadly into two categories −

 Physical Database Schema – This schema pertains to the actual

storage of data and its form of storage like files, indices, etc. It defines
how the data will be stored in a secondary storage.
 Logical Database Schema − This schema defines all the logical
constraints that need to be applied on the data stored. It defines tables,
views, and integrity constraints.

18
 Inventory Management System

CHAPTER 4
IMPLEMENTATION

4.1. FRONT END:Phyton

Python is an interpreted, object-oriented, high-level programming language with
dynamic semantics. Its high-level built-in data structures, combined with dynamic
typing and dynamic binding, make it very attractive for Rapid Application
Development, as well as for use as a scripting or glue language to connect existing
components together. Python's simple, easy to learn syntax emphasizes readability and
therefore reduces the cost of program maintenance. Python supports modules and
packages, which encourages program modularity and code reuse. The Python
interpreter and the extensive standard library are available in source or binary form
without charge for all major platforms, and can be freely distributed.
Often, programmers fall in love with Python because of the increased productivity it
provides. Since there is no compilation step, the edit-test-debug cycle is incredibly fast.
Debugging Python programs is easy: a bug or bad input will never cause a
segmentation fault. Instead, when the interpreter discovers an error, it raises an
exception. When the program doesn't catch the exception, the interpreter prints a stack
trace. A source level debugger allows inspection of local and global variables,
evaluation of arbitrary expressions, setting breakpoints, stepping through the code a line
at a time, and so on. The debugger is written in Python itself, testifying to Python's
introspective power. On the other hand, often the quickest way to debug a program is to
add a few print statements to the source: the fast edit-test-debug cycle makes this
simple approach very effective.Python is often compared to other interpreted languages
such as Java, JavaScript, Perl, Tcl, or Smalltalk. Comparisons to C++, Common Lisp
and Scheme can also be enlightening. In this section I will briefly compare Python to
each of these languages. These comparisons concentrate on language issues only.
Java:
Python programs are generally expected to run slower than Java programs, but they
also take much less time to develop. Python programs are typically 3-5 times shorter
than equivalent Java programs. This difference can be attributed to Python's built-in
high-level data types and its dynamic typing. For example, a Python programmer
wastes no time declaring the types of arguments or variables, and Python's powerful
polymorphic list and dictionary types, for which rich syntactic support is
builtstraightinto the language, find a use in almost every Python program. Because of
the run-time typing, Python's run time must work harder than Java's.

19
 Inventory Management System

JavaScript:
Python's "object-based" subset is roughly equivalent to JavaScript. Like JavaScript
(and unlike Java), Python supports a programming style that uses simple functions and
variables without engaging in class definitions. However, for JavaScript, that's all there
is. Python, on the other hand, supports writing much larger programs and better code
reuse through a true object-oriented programming style, where classes and inheritance
play an important role.
C++:
Almost everything said for Java also applies for C++, just more so: where Python code
is typically 3-5 times shorter than equivalent Java code, it is often 5-10 times shorter
than equivalent C++ code! Anecdotal evidence suggests that one Python programmer
can finish in two months what two C++ programmers can't complete in a year. Python
shines as a glue language, used to combine components written in C++.

4.2. BACKEND TOOL: MYSQL

Dr. E. F. Codd published the paper, "A Relational Model of Data for Large Shared Data
Banks", in June 1970 in the Association of Computer Machinery (ACM)
journal, Communications of the ACM. Codd's model is now accepted as the definitive
model for relational database management systems (RDBMS). The language,
Structured English Query Language (SEQUEL) was developed by IBM Corporation,
Inc., to use Codd's model. SEQUEL later became SQL (still pronounced "sequel"). In
1979, Relational Software, Inc. (now Oracle)introduced the first commercially
available implementation of SQL. Today, SQL is accepted as the standard RDBMS
language.

 MySQL is database system used on the web, server, large application.

 MySQL uses standard SQL. It compiles number of platforms.

 The data is a MySQL database are stored in tables.

 MySQL is the de-facto standard database system for websites with huge
volumes of both data and end-user.

 SQL is portable. It processes query quickly.

 SQL enables you to run containers easily and quickly without managing any

Infrastructure.

20
 Inventory Management System

 SQL uses its own storage system, but it does maintain multiple safeguards
against loss of data. Both systems are able to run in clusters for high
availability.

 SQL Server offers a wide variety of data analysis and reporting tools. SQL
Server Reporting Services is the most popular one and is available as a free
download. There are similar analysis tools for MySQL available from third-
party software companies, such as Crystal Reports XI and Actuate BIRT.

21
 Inventory Management System

CHAPTER 5
RESULTS
SNAPSHOTS:

Fig. 5.1: Front Page/Item Details Page

Fig. 5.2: Admin Login Page

22
 Inventory Management System

Fig. 5.3: Purchase Details Page

Fig. 5.4 Vendor Details Page

23
 Inventory Management System

Fig. 5.5: Sale Details Page

24
 Inventory Management System

Fig. 5.6: Customer Details Page

Fig. 5.7: Search Inventory Page

Fig. 5.7: Reports Page

25
 Inventory Management System

CONCLUSION

In this report, the Mini Project “Inventory Management System”has been

designed and tested. Integrating features of all the software components used
have developedit. With the help of growing technology, the project willbe
successfully implemented. Project will definitely reduce the human effort and
make the task of the User easier. It is efficient to use and easy to work on it.
Thus, keeping in mind, the advantages and applications, we are developing
aInventory management software which has total management control of
record of the Inventory items.

26
 Inventory Management System

REFERENCES

1. Inventory management system complete project developed from

scratch in Phyton Part1
https://youtu.be/CgwElbZTD2U
2. Library management system complete project developed from scratch
in Phyton,creating database:

27
 Inventory Management System

-1-

28