A PROJECT REPORT

ON
Inventory Management System

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE AWARD

OF

DIPLOMA IN
Computer Technology

SUBMITTED TO

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION, MUMBAI

SUBMITTED BY

Name of Student Enrollment No.

1. Janhvi Vinod Tathed 2000790184

GUIDED BY
Prof. G.M.Lodha
 SHHJB Polytechnic Chandwad

CERTIFICATE
This is to Certify that the project report entitled “Inventory Management
System” Was successfully completed by Student of fourth semester Diploma in
Computer Technology.

1.Janhvi Vinod Tathed 2000790184

in partial fulfillment of the requirements for the award of the Diploma in

Computer Technology and submitted to the Department of Computer
Technology of SHHJB Polytechnic Chandwad work carried out during a
period for the academic year 2021-22 as per curriculum.

Subject Teacher HOD Principal

G.M. Lodha A.S. Chordiya V.A. Wankhede
 Teacher Evaluation Sheet
Name of Student: Janhvi Vinod Tathed
Enrollment No. 2000790184
Name of Program - Computer Technology Semester – 4th
Course Title: -Software Engineering Code: - 22413
Title of the Micro–Project: - Inventory Management System

Course Outcome:
• Select Suitable Software Process Model For Software
Development
• Prepare Software Requirement Specification
• Use Software modeling to create data design
• Estimate Size & Cost of Software Product
• Apply Project Management And Quality assurance principle in
Software Development

Evaluation as per Suggested Rubric for Assessment of Micro-Project:

Sr. Characteristic to be Poor Average Good Excellent

No. assessed (Marks (Marks (Marks (Marks
1-3) 4-5) 6 - 8) 9 – 10)
1 Relevance to the
Course
2 Literature Survey /
Information Collection
3 Project Proposal
4 Completion of the
Target as per project
proposal
5 Analysis of data and
representation
6 Quality of Prototype /
Model
7 Report Preparation
8 Presentation
9 Defense
Micro – Project Evaluation Sheet

Process Assessment Product Assessment

Part B –
Individual
Part A – Project Total Marks
Project Presentation
Name of project Report
Methodology / 10
Student Proposal / Working
(2 marks) Viva (4
(2 marks) Model
marks)
(2 marks)

Comments / Suggestions about teamwork / leadership / inter – personal

communication (if any) :---------------------------------------------------------------
-------------------------------------------------
Any Other Comment: :------------------------------------------------------------------
---------------------------------------------

Name and designation of the faculty Member – Prof. G.M.Lodha

Signature __________
 ACKNOWLEDGEMENT

I would like to express my special thanks of gratitude to my project guide Mr

G.M. Lodha Sir as well as our principal Prof. Dr. V.A. Wankhede who gave me the
golden opportunity to do this wonderful project on the topic Medical Store
Management, which also helped me in doing a lot of research and I came to know
about so many new things I am really thankful to them.
Secondly, I would also like to thank my parents and friends who helped me a
lot in finalizing this project within the limited time frame.

Date -

Place - Chandwad

2
 ABSTRACT
For organizations that handle transactions involving consumer goods, an inventory
management system is critical for quality control. A huge retail store could run out
of supply of a critical item if inventory is not properly managed. When it's time to
reorder, an effective inventory management system will notify the retailer. This
inventory management system is also useful for tracking huge shipments
automatically. Counting each pair of stocks by hand will almost certainly result in
a mistake. The risk of human error can be reduced by using an automated inventory
management system.
An Inventory Management System also aids in the tracking of retail product theft,
providing useful information regarding store revenues and the need for
theftprevention devices. Scanning a barcode on the item or a barcode scanner is
how Automated Inventory Management Systems function. The central computer
system then keeps track of this data. The purchase order can also include a list of
items that need to be pulled for packaging and shipping. In this situation, the
Inventory Management System can perform a range of tasks. It can assist a
warehouse worker in locating things on an order list, encoding shipment
information such as tracking numbers and delivery addresses and removing
purchased items from the inventory tally to maintain a correct count of in-stock
items. All of this information works together to give firms real-time inventory
tracking data. The simple search in a database makes it easy to find and look at
inventory information in real-time.

3
 TABLE OF CONTENTS

Sr. No. Contents

1 Introduction
2 Problem Statement & Analysis
3 Scope Of Project
4 Model Implementation
5 Sequence Diagram
6 Use Case Diagram
7 Activity Diagram
8 Class Diagram
9 DFD Diagram
10 Design view
11 Estimation
12 Test Cases
13 Test Case Result
14 Defect Report
15 Conclusion & Scope of Project
16 References

1. INTRODUCTION
Managing inventory is the ongoing process of moving parts and products into and
out of a company’s location(s). Companies manage their inventory on a daily basis
as they place new orders for products and ship orders out to customers. It’s
important that business leaders gain a firm grasp of everything involved in the
inventory control process. That way, they can figure out creative ways to solve
inventory challenges by finding the right solutions. When most people think of
inventory management, they think of retail applications. While retail operations
rely heavily on inventory management, inventory management systems are widely
used in a variety of industries, from manufacturing to utilities, healthcare,
education, government, and more. Inventory management systems streamline and
centralize the process for controlling the flow and maintenance of inventory to
ensure that the right amount of inventory is available at the right time and of the
right quality.
4
Inventory Management System

We propose to keep track of each and every ingredient by dynamically linking it to

the product and as a result create a dependent relationship to that product. At a
specific time period (typically the end of the week); if the inventory is below the
threshold level, order forms to the specific vendors are generated in order to restock
the required items for the next week. The project also makes smart predictions on
required inventory for the following week based upon the predicted climate and
possible occasions or events that may influence near future sales. At the end of the
week, the software takes into account all threshold levels, predictions, and other
factors to generate an order form, which after being verified by the manager is sent
out to the vendors.

2. PROBLEM STATEMENT & ANALYSIS

Problem Statement

Demand is frequently unpredictable in inventory systems, and lead times can often
vary. Managers frequently keep a safety supply to minimize shortages. In such
cases, it's difficult to say what order amounts and reorder points will result in the
lowest total inventory cost. The inventory issue refers to the general issue of
deciding how much inventory to keep on hand in expectation of possible demand.
Loss occurs when a business is unable to meet demand (for example, when a store
loses sales or when soldiers in a war run out of ammunition) or when commodities
are stocked for which there is no demand.

3. SCOPE OF PROJECT

An inventory system's scope can include valuing inventory, measuring inventory

change, and forecasting future inventory levels, among other things. At the end of
each period, the value of the company's inventory is used to figure out how much
money the company makes and loses.

5
 4. MODEL IMPLIMENTATION

Fig. 4.1 Waterfall model

4.2 Reason for choosing waterfall model

• This is small project and requirements are well understood.

• This model is simple and easy to understand and use
• Waterfall model is simple to implement and also the number of resources
required for it areminimal
• It is easy to manage due to rigidity of the model each phase has specific
deliverables and review process.
• In this model output is generated after each stage, therefore it has high
visibility. The client and project manager gets a feel that there is
considerable progress. Here it is important to note that in any project
psychological factors also play important role.
• In this model phases are processed and completed one at a time. Phase do
not overlap.
• This project is conversion from manual to automatic.
6
5. SEQUENCE DIAGRAM

6. USECASE DIAGRAM

7
7. ACTIVITY DIAGRAM

8. CLASS DIAGRAM

8
 9. DFD DIAGRAM

LvL 0:

LvL 1:

9
 10. DESIGN VIEW

Main Interface:

10
 11. ESTIMATION

11.1 COCOMO MODEL

It is the one type of static model to estimates software development effort quickly
and roughly. It mainly deals with the number of lines of code and the level of
estimation accuracy is less as we don’t consider the all parameters belongs to the
project. The estimated effort and scheduled time for the project are given by the
relation:

Effort (E) = a*(KLOC)b MM

Scheduled Time (D) = c*(E)d Months(M)

Where,

• E = Total effort required for the project in Man-Months (MM).

• D =Total time required for project development in Months (M).
• KLOC = the size of the code for the project in Kilo lines of code.
• a, b, c, d= The constant parameters for a software project.
Project type a b c d
Organic 5.4 1.05 2.5 0.83
Semidetached 3 1.12 2.5 0.35
Embedded 3.6 1.2 2.5 0.32

11
For a given project was estimated with a size of 300 KLOC. Calculate the Effort,
Scheduled time for development. Also, calculate the Average resource size and
Productivity of the software for Organic project type.

Effort (E) = a*(KLOC)b = 2.4*(300)1.05 = 957.61 MM

Scheduled Time (D) = c*(E)d= 2.5*(957.61)0.38 = 33.95 Months(M)
Avg. Resource Size = E/D = 957.61/33.95 = 28.21 Mans
Productivity of Software = KLOC/E = 300/957.61 = 0.3132 KLOC/MM = 313
LOC/MM

12. TEST CASES

Test case is an object for execution for other modules in the architecture does not
represent any interaction by itself. A test case is a set of sequential steps to execute
a test operating on a set of predefined inputs to produce certain expected outputs.
There are two types of test cases:-manual and automated. A manual test case is
executed manually while an automated test case is executed using automation. In
system testing, test data should cover the possible values of each parameter based
on the requirements. Since testing every value is impractical, a few values should
be chosen from each equivalence class. An equivalence class is a set of values that
should all be treated the same. Ideally, test cases that check error conditions are
written separately from the functional test cases and should have steps to verify the
error messages and logs. Realistically, if functional test cases are not yet written, it
is ok for testers to check for error conditions when performing normal functional
test cases. It should be clear which test data, if any is expected to trigger errors.

12
 13. TEST CASE RESULT

Login form:
Sr.no Test Case Expected Result Actual Result Test Result
1 Enter valid name and the Software should As expected, the Successful
password & click on login display login done
button
2 Enter Invalid Software should As expected, the Successful
not display main error message is
window display

Main Form:
Sr.no Test Case Expected Result Actual Result Test Result
1 On click on the On the click on the search The search result is Successful
search button button, it must display the came as expected
Inventory elements with the proper way.
2 On the click of the This deletes the details in The details are Successful
delete button database. deleted as expected
3 On the click of the The existing record will be The record is updated Successful
update button update. as it instructed
On the click of the It must need to add the new The result of this test Successful
4 add button stock details to inventory case is also a great as
database. expected
5 On the click of the Exit the form The account is logout Successful
exit button and exit from the
application.

Sale Invoice:
Sr.no Test Case Excepted Result Actual Result Test Result
1 On the click of At first user have to enter to The amount is Successful
calculate button fill all details with proper data. calculated as user
After it clicking input, for wrong
calculate button calculates the input it also displays
total amount. the error message.
2 On the click of the This saves the details of sale It saves the data Successful
save button in database.
3 On the click on the It loads the sale table from the It loads the table as Successful
Load of the table database and displays it to the user wanted.
form.
4 Click on the exit Exit form Exited Successful
button

13
 14. DEFECT REPORT
ID #4987
Project name Add Inventory Project

Product name Inventory Management System

Release 1.12.89
Version
Module Add
Detected 1.115.1
build version

Summary This defect is found when a tester tries to add the add data to database of
inventory. The data is added but on the real time basis it cannot get access on the
time after adding it. It takes a usually a little more time to get new added data.

Description This defect is found when a tester tries to add the add data to database of
inventory. The data is added but on the real time basis it cannot get access on the
time after adding it. It takes a usually a little more time to get new added data.

Steps to 1. Enter the data

replicate 2. Then the click on add
3. Try to access data it takes a little more time to display.
Actual result The error message is not given

Expected --
result
Attachments --
Remarks --
Severity Medium
Priority Low
Reported by Janhvi Tathed
Assigned to Mr. Gautam Lodha
Status Almost solve
Fixed build 1.13.454
version
14
 15. CONCLUSION & SCOPE OF PROJECT

Conclusion
The project “Inventory Control System for Calculation and Ordering of Available
and Processed Resources” mainly as the name suggests deals with the calculation
of the available and processed resources for an accurate inventory control and
process management for a domain specific client who are related to the subject of
food chains/outlets. This enables the inventory to be applied at every level in the
hierarchy of the products and its complex combinations of recipes. A system that
accurately calculates the atomic ingredients used for making a recipe then
automatically performs the back end operation pertaining to a database of many
relational tables onto which the changes are being made with each and every
operation performed on the front end and which also shows up if at the time of
retrieval. The most important part of Inventory controlling is its ability to check for
threshold levels and alert the manager to replenish the stock before it reaches a
danger zone. So as when an ingredient level goes below the threshold level then it
routes an alert to the manager. Then if needed accordingly an automated order
form is produced so as to each specific vendor along with the quantities needed for
replenishment. As a part of the standard maintaining a drill of risk management is
done in order to sustain during the days of special occasion or holidays when the
demand reaches to rather more different scale as compared to other days. These
occasions call on for special inclusions into the menu which reflects on the recipes
and in turn reflects the ingredients being used up eventually. Thus was provided
the liberty of adding special recipe to the menu for some special occasion and is
regarded as a key feature. To be able to simplify the user friendliness even more
the concept of ‘prediction’ is added which enables the manager to see the past
years prediction of the ingredients usage and then based on the informational
analysis done on the data a prediction is then generated which would suit the
requirements of the current year and then accordingly an appropriate order form is
generated and then passed on to the vendor as the requirements for replenishing the
stock.

15
Scope for future development

We also propose to include a special feature “Prediction”. This feature keeps track
of any upcoming occasions, climatic changes and special events that may influence
inventory needs for the upcoming week. The system will then predict the required
resources for these events based on previously accumulated
information/knowledge. It will now generate an updated purchase order in
accordance with the predictions. The product also aims to keep track of the shelf
life of resources. If any resource nears the end of its shelf life, it would intimate to
the manager (admin) the details of the quantity that is near its expiration date. The
restaurant must function efficiently, the groceries must be tracked correctly, timely
orders must be sent out to the vendors, and the inventory must be maintained and
updated at all times.

16. REFERENCES

Website –

• www.w3schools.com
• https://www.geeksforgeeks.org/
• www.tutorialspoint.com
• https://www.freeprojectz.com/

Books –

Author
Robert C. Martin Clean Code
Andrew Hunt & Dave Thomas The Pragmatic Programmer
Steve McConnel Code Complete ( Edition 2 )
John Sonmez Soft Skills

16