2021

ONLINE INVENTORY
MANAGEMENT SYSTEM

09- Twinkle Bothara

10- Rashi Chaturvedi
14-Shruti Chavan
USHA MITTAL INSTITUTE OF
TECHNOLOGY
8/12/2021
 ABSTRACT

Inventory Management System is extremely beneficial to business owners, as they

allow shops to properly store sales and purchase records. When inventory is mismanaged, it
leads to dissatisfied consumers, slower sales, too much cash on hand, and warehouses. This
inventory system reduces manual work, human mistake, and manual delays while
simultaneously speeding up the process. This inventory management system will be able to
track sales information as well as inventories.

It is an Internet based web application that is of benefit to any of the business

sectors, small scale and large scale industries, etc. In conventional business industries a lot
of paperwork is being done which is very time consuming and more manual resources needed
to complete the task. Due to this, customers, secondary and tertiary sellers are facing many
delay problems. In order to overcome these basic problems in managing records, we
developed an Online Inventory Management System. This Inventory project was developed
with .Net technologies and all details of the banking customers will be saved in the
PostgreSQL backend without any data loss.

This feature allows the user to manage and maintain his/her inventory with ease. It
has been developed to allow users to add an inventory, delete an inventory, enter inventory
quantity and other details, update inventory status and more. The inventory management
system has its own intelligently managed support system that allows users to view and
manage various inventories added in the system.

2
 INDEX

1. INTRODUCTION

I. Purpose of the System……………………………………………………………………………………………05

II. Scope of the System……………………………………………………………………………………………. 05

III. Objectives……………………………………………………….………………………………………………07

IV. Document Conventions………………………………………..……………………………………………....08

V. References…………………………………………………………………………………………………08

2. GENERAL DESCRIPTION

I. Product Perspective………………………………………………………………………………...…09

II. Product Features……………….……………………..………………………………………………09

III. User Characteristics………….……………………….……………………………………………..10

IV.Operating Environment……….…….………………..………………………………………………11

V. Design and Implementation Constraints……………….……………………………………………..11

VI. User Documentation…………………………………………………………………………………12

VII. Assumptions and Dependencies……………………….…………………………………………….12

3. SYSTEM ANALYSIS

I. System Features…………………………………..……………………………………………………14

II. Requirements of New System…………………………………..……………………………………..14

III. Functional Requirements………………………………...…………………………………………..14

4. EXTERNAL INTERFACE REQUIREMENTS

I. User Interface………………………………………………….………………………………………17

II. Hardware Interface…………………………………………………………………………………...17

III. Software Interface…………………………………………….……………………………………...17

IV. Communications Interface…………………………………………………………………………...17

3
5. OTHER NON-FUNCTIONAL REQUIREMENTS

I. Usability……………………………………………………………………………………………….18

II. Reliability……………………………………………………………………………………..………18

III. Performance…………………………………………………………………………………………18

IV. Supportability………………………………………………………………………………..………18

V. Maintainability…………………………………………………………………………...……..…….18

VI. Packaging………………………………………………………………………………………...….18

VII. Interfacing…………………………………………………………………………………….…….19

VIII. Legal………………………………………………………………………………………………..19

IX. Security…………………………………………………………………………………………...….19

X. Safety…………………………………………………………………………………………….……19

6. ADDITIONAL REQUIREMENTS

I. Other Requirements…………………………………………..…………………………………..……20

II. Appendices.………..……………………………….…………………………………………………20

i. Appendix A: Glossary.………………………………….…………………………………………20

ii. Appendix B: Analysis Models…………………………………….………………………………21

iii. Appendix C: Reference…………………………………….….…………………………………30

Diagram Index:
Sr. No. Diagram Pg. No.
1 FLOW DIAGRAM 21
2 ENTITY DIAGRAM 22
3 ACTIVITY DIAGRAM 23
4 USE-CASE DIAGRAM 24
5 CLASS DIAGRAM 25
6 DFD LEVEL-1 26
7 DFD LEVEL-1 27
8 DFD LEVEL-2 28
9 STATE TRANSITION DIAGRAM 29
10 SEQUENCE DIAGRAM 30

4
 INTRODUCTION

Purpose of the System:

Inventory management is key to maintaining a profitable, organized and productive business.

The purpose of inventory management is to help businesses easily and efficiently manage the ordering,
stocking, storing and using of inventory. By effectively managing your inventory, you’ll always know
what items are in stock, how many of them there are, and where they are located.
With increased online shopping and retail marketing, inventory management systems have
become the need of the hour. An online inventory management system is an organized and systematic
process for controlling the inflow and outflow of our product in the organization. The maintenance and
upkeep of our inventory are important to ensure that the right amount of inventory is available at the
right time and in the right quantity. The inventory management system has become more of a necessity
for businesses and it is being widely used in a variety of industries from manufacturing to utilities,
healthcare, education, government, and more.
This material management software has come a long way when it comes to the history of using
the inventory system. Inventory in the earlier days was managed by a system known as cardex system.
These cards were read and updated once an inventory was moved from a location. Apart from these
cards, books or registers were maintained to note these transactions and reports manually. This system
was quite basic and time consuming for the employees and had led to many human errors and product
losses.
Next came the credit and debit card for inventory methods which were equally time consuming
and prone to errors. A new revolution was created with new online inventory management system
software where intelligent applications manage the inventory, help in analysis, categorization and to a
large extent reduce human errors, product damage and theft. We will be creating similar online
inventory management system software here.

Scope:

This project aims at providing an efficient interface to the inventory management system. The
outcome of the project would be online inventory management service .The software will have all
common features and functionalities along with some other special facilities.

 To provide a user efficient working environment:

Supportive work environments provide conditions that enable workers to perform
effectively, making best use of their knowledge, skills and competences and the available
resources in order to provide high-quality services.

 User friendly interface for the target stakeholders:

A user-friendly interface is not overly complex, but instead is straightforward, providing
quick access to common features or commands. A good user interface is well-organized, making
it easy to locate different tools and options.

 Facility monitoring for inventory:

5
 Monitoring inventory leads to understanding of what your best-selling products are, how
often you turn over that particular inventory and what you need to have on hand to satisfy
orders. Maintaining inventory trends of the best-selling products helps you keep those products
in stock and allows you to keep filling orders.

 Easy maintenance and administration:

An online inventory doesn’t need log books to maintain its record, so they can’t be
damaged over time and can be seen anytime and anywhere. The data will be automatically saved
on the cloud and we can easily access it.

 Ensure a high level of security:

An online inventory management solution keeps your data secure offsite. There is
nothing to download or maintain. Data loss can also be prevented by regularly scheduled back-
up procedures. All of these can be automated, which means less risks of making errors.

 Access anywhere
It enables business leaders and other workers to access their inventory data from virtually
any location. Unlike desktop software, an online inventory management solution can be accessed
on any device with an Internet connection.

 Flexibility:
Flexibility in the online inventory management system also means adding a new shipper
or barcode system or introducing capabilities for quantity-based pricing and landed cost
calculations. It also allows defining business processes into the system while also offering the
flexibility to implement customization and business rules that support the business requirements.

 Formulation of policy:
The policies of investment procurement, storage, handling, accounting, storages and stock
outs, deterioration, obsolescence etc. are to be formulated under the scientific system of
inventory control

 Determination of economic order quantity

Economic order quantity (EOQ) is the ideal order quantity a company should purchase to
minimize inventory costs such as holding costs, shortage costs, and order costs. What, when and
how much of purchasing and fixation of minimum and maximum levels is also to be determined
for a given period of time.

 Reducing inaccuracies and less manual work

Inventory & Stock Management consist of an array of internal management processes.
When a person does all these tasks manually then there are chances for inaccuracies such as
doing data duplicity. One can save lots of man-hours by using inventory management software.
It will automate all the data recording and tracking processes leaving no room for errors.

 Happy customers
6
 A decent stock management methodology keeps the clients returning for more. Good
stock management can lead to exactly what one is aiming for – repeat clients. This assists in
making a good image, great service & a brand.

 Cost-saving
One can avoid dead stock & overstock situations with the assistance of an inventory
management system. Inefficient management of inventory can lead to revenue loss, over-
spending money, etc. Most importantly it can get the product history through which one can
refill their stock & manage inventory accordingly.

 Cut Costs and Increase Profits

The well-maintenance of inventory and stock management can enable you to cut
expenses and enhance the benefit ratio. It saves unnecessary expenses & through data analytics,
one can know in advance which item will be in more demand in which season.

This system will help in tracking records so that past records can be verified through them and
one can make decisions based on the past records. This system will complete the work in a very less
time resulting in less time consumption and high level of efficiency.

Objectives:

Operational and financial goals may be examined in regards to inventory management. The
operational goal is to have an adequate supply of inventory, so that we can fulfill customer demand and
the financial objective is to minimize unnecessary inventory and its associated expenses.

For these operational tasks, inventory management is done to help streamline operations. Some
of the most important purposes for which it is used are:

 To ensure a continuous supply of materials and stock so that production should not suffer at the
time of customers' demand.
 To avoid both overstocking and under-stocking of inventory.
 To maintain the availability of materials whenever and wherever required in enough quantity.
 To maintain minimum working capital as required for operational and sales activities.
 To reduce the manual labour and the labour cost.
 To optimize various costs indulged with inventories like purchase cost, carrying a cost, storage
cost, etc.
 To keep material cost under control as they contribute to reducing the cost of production.
 To eliminate duplication in ordering stocks.
 To minimize loss through deterioration, pilferage, wastages, and damages.
 To ensure everlasting inventory control so that materials shown in stock ledgers should be
physically lying in the warehouse.
 To ensure the quality of goods at reasonable prices.
 To facilitate furnishing of data for short and long-term planning with a controlled inventory.
 To supply the required material continuously.
7
  To maintain a systematic record of inventory.
 To make stability in price.
 To fulfill the orders with the right products available in times of need.
 To enhance the inventory production.
 Analyzing product sales patterns.
 Ensure the presence of Safety Stock Inventory in case of unexpected demand.

Document convention:

This document uses several conventions to highlight certain words and phrases and draw
attention to specific pieces of information. In PDF and paper editions, this manual uses typefaces drawn
from the Sylfaen text. Sylfaen is a multi-script serif font set. For projects involving lengthy text, such as
books, newspapers, and most magazines, serif typefaces are the most commonly used typestyle. They are
often used to convey simplicity and modernity or minimalism. Sylfaen typefaces tend to have less stroke
width variation than serif typefaces Sylfaen typefaces have become the most prevalent for display of text
on computer screens.

REFERENCES
 https://pdfcoffee.com/software-requirements-specification-inventory-management-system-
1-pdf-free.html
 https://pdfcoffee.com/stock-management-system-3-pdf-free.html
 https://www.cs.uic.edu/~spurohit/documents/Requirements%20Document.pdf
 https://www.selecthub.com/inventory-management/inventory-management-software-top-
features-requirements/

8
 GENERAL DESCRIPTION

Product perspective:

In this modern world of commercialization, business industries have been established as one of
the developing ones in our country. It has been one of the most flourishing import and export sectors
for our country. Our project here is concerned with this sector. This is a huge field to cover, as hundreds
of manageable aspects can be found to maintain the highest productivity of the above industry. We
choose inventory management as our preferred field to work.

To start with, this can be specified as a business to business system, from producers, distributors
to retailers and also the home dealers through some intermediate business nodes. And our goal would be
to facilitate this whole process, from collecting raw materials to the finished product shipment.

Unlike the old days, various industries have been implementing a variety of management
software, in order to enhance productivity, and to satisfy the customers' needs. As these deals are very
sensitive to handling, and there are a lot of variables that must be maintained, the need for online
interaction between the buyer and the seller, or even seller to seller, is a must, and can play a dramatic
influence on these deals. As the whole process has multiple steps to the way to finished goods, a single
delay in a single step can cause delay in the shipment schedule, suppose our delay in cutting can
demolish the required time structure, which can also cause financial damage and bad business
reputation.

The existing systems for inventory management have been in use for a while, and the maturity
level of the software industry in our country is yet at an average. So, the systems which are being used
in recent days do have a lot of bugs, functional dependencies and design constraints. Besides, there is
still a lack of a complete solution for the new inventory which is yet to be provided. Also we can find
that the majority of the industries still don't make use of any automated management system, where a
large amount of problems in manual management can be easily solved and rectified.

Even with the existing management software, there is a missing factor in it which we have been
planning and trying to introduce in this kind of usual management system; which is an online interface
to control the system. The Internet has been a pivotal determiner in every aspect of life. We are
proposing to introduce an internet controlling module of this system, so that the authority of our client
can monitor and manipulate the system, as well as the database through the internet.

At the same time, there are technologies being used to manage payroll, appointments, inventory,
and many other purposes. But as our major concerns will be inventory oriented, we will focus the most
on that.

Product features:

Inventory Management System must be designed to meet the dictates of the marketplace and
support the company's strategic plan. Along with the inventory system industries need some more
special attributes. The Software’s for different products are specially made for managing the various

9
steps in order of processing of product manufacturing process. This software is modular in design and is
web enabled for remote access as well as intranet usage without the need to install in every machine.

Inventory Management System has some features which are badly needed for a complete
Inventory system of business industries. So the features are:

 Inventory Tracking
 Product category and product stock information with value.
 Use of Digital labeling i.e. Bar-coding and tagging
 Reports include purchase, issues, stocks & categories.
 Customized package and shipping
 Notification System in case of any process delay.
 Check sheet automation.
 Web based interface
 Cloud infrastructure i.e. cloud-based software
 User based Login - password based authentication for data protection.
 Dynamic Modular structure – Each and every section related to a
 Production has separate menus.
 Manage master details of buyer, supplier and vendor.
 Transfer management
 Centrally store all your supplier details.
 Dynamically generate any quantity discounts given to make optimal purchasing easy.

User Characteristics:

The user must have basic knowledge of the Computer. Users must be familiar with all the
applications whose documents are used in the system. The user must be familiar with these computer
based systems and their operations done in the system.

There are two groups of users in our system. They are the production controller, distributor,
wholesaler, retailers and the system maintenance administrators (authorized staff for controlling the
system and maintaining the database). They have different authorities in our system.

The users of the software are classified into two categories – Registered user and unregistered
User. Both users will be able to visit the homepage of the website but only the registered user is
Allowed to give input in the system.

To work through the system one user should go through some fixed steps-

 First of all the user should be registered.

 The separate production module will be presented to the user as a catalog for viewing.
 The user can browse through the categories to choose the module they desire.
 The user can input a partially complete production quantity of the total production.
 They can view order sheets and sample sheets, create a new record along with date, edit the
entry as per entry and also add, modify and delete the stock entry

10
  Finally the product will be delivered within a fixed and trusted time period to the next
production module.
 And the process will continue until the shipment is completed

Operating Environment:

Software requirement:

Front End: HTML, CSS, JavaScript++

 HTML: HTML is used to create and save web documents. E.g. Notepad/Notepad++
 CSS: (Cascading Style Sheets) Create attractive Layout
 Bootstrap: responsive design mobile friendly site
 JavaScript: it is a programming language, commonly used with web browsers.

Back End: Visual studio, postgreSQL

 Visual studio: Visual Studio is a technology that allows software developers to create dynamically
generated web pages, in HTML, XML, or other document types, as per client request. Visual
Studio is open source software.

 PostgreSQL: PostgreSQL is a database, widely used for accessing, querying, updating, and
managing data in databases.

Operating System:
 Windows 10

For Documentation:
 Microsoft Office 2007

Hardware Requirements:
 Processor → Intel core i5
 RAM → 1GB onwards
 Free Hard Disk Space → 2 GB or more

Design and Implementation Constraints:

A key piece of the model is the constraints that define the evolution of the inventory. A good
inventory management system uses automated software approaches to reduce human error and
eliminate manual workloads which can cause some of the below issues:-

11
  The constraints imposed by the skills possessed by the member for the development. We had to
learn C++ ,JavaScript and HTML and then implement the system.
 Having mismanaged stock count and unorganized process to follow stock upkeep.
 Human resource wastage due to repetitive manual ways of inventory management and
warehouse look after for product tagging and rotation.
 The demand of the customers is shifting constantly. Keeping demand too much may result in
obsolete inventory that you are not able to sell, so keeping little demand will enable you to fulfill
customers’ needs.
 When your inventory is hard to identify or locate in the warehouse, it leads to incomplete,
inaccurate or delayed shipments. Receiving and finding the right stock is vital to efficient
warehouse operations and positive customer experiences.
 Global supply chains shift daily, placing a burden on your inventory planning and management
operations. The manufacturers and wholesale distributors that dictate when, where and how
your inventory ships require flexibility and offer unpredictable lead times.
 Keeping too much stock on hand can be as problematic as having too little. Overstock impacts
business cash flow and leads to inventory-related problems, such as storage and loss.
 It can be tough to find skilled inventory managers who are adept at the latest technology and can
improve inventory strategy. Simply upgrading your inventory management platform with a host
of features isn’t enough. You need capable management.
 The project should be developed and implemented within the time limit.

User Documentation:

Any user of the software system is the target audience for user documentation generated
about the software system. A range of short document types or user manual (e.g., guidelines,
tutorials, and frequently asked questions) in HyperText Markup Language (HTML) and Portable
Document Format (PDF) format must describe the use of the software system. This user manual will
be available to view on internet

Assumption and dependencies:

After completing our study about inventory and inventory management system, we thought
That, our Inventory management software will be ideal one in terms of business industries of
Our country. According to our view that inventory system will Contain module like:

 Information of different products category

 Available stock
 Price of different items
 Transaction details
 One can also extract any reports relating to purchase and Sale.

12
  The inventory management application will have all the categories, Subcategories, items, Stock
details and reports.

The administrator of this inventory system will have right to create product, add items delete
Items etc. The application will provide all information about the products. The category will be
Tagged with subcategory. Again the subcategories are tagged with different items in the
Respective category and rate of the item. Each item will have a specific bar code. The rates
Will be tagged to the bar code.

Using these functions the user can:

 Inventory tracking
 Batch tracking
 Add items to inventory
 Edit items in inventory
 Add an action for an item

The application will also help to generate reports to get latest update on
 Master Entry
 Purchase order entry
 Discount entry
 Receive entry
 Delivery entry
 Report

This inventory system also has some dependencies like

 If data are inserted it cannot be deleted except administrator
 User can insert a data but can’t delete
 If data is not inserted, the user cannot view the report.

13
 SYSTEM ANALYSIS

System features:

The key inventory management system specifications involve providing a way to store, organize,
manage and analyze inventory data. The some basic systems features included here are:
 An easy-to-use interface that doesn’t require advanced training, support or documentation.
 Automation for eliminating manual processes of business functions related to inventory
management.
 A reliable, secure database that provides accurate, real-time data.
 Performance that enables fast, actionable inventory monitoring and control.
 The ability for administrators to easily add software modules with minimal configuration so that
the system is scalable.
 Software integrations and automated features that minimize manual inventory updates or inputs.

Requirements of New System

 The system must be authorized.

 The system must be accessible to the account branch of the company.
 The system must be able to store inventory.
 Advanced Searching facilities must be included.
 The system should be convenient and work according to the Company Requirements.

Functional requirements:

The functional requirements specify the functional behavior of the system in response to an
external event. The external event may be a user action, another system or a timed event. In the current
project, the baseline of the functional requirements was developed from the business requirements.
Since the project was developed as a web application, the web site design requirements were added in
the subsequent section of the functional requirements. The requirements of the login page were
identified first. The system responses for invalid login attempts were documented in this section. The
main menu is displayed when the user logs on successfully. As a security measure, it was decided that
when the user doesn't have any activity for ten minutes, the user would be logged off automatically and
the login page will be displayed. When the user is already logged on and the user clicks the logout link,
the user is logged out and the login screen is redisplayed. When the user successfully logs on to the
system the system displays the Main Menu screen. It was decided that the Main Menu should provide
the links for the user so that the user could perform the business functions discussed previously.

It was decided that the links in the Main Menu would be divided into 2 functional areas. The
authorized staff and the product controller. These then link us to 1 and 3 sub functional areas
respectively. The authorized staff links us to the Centralized Data Section which contains ‘Inventory
level’, ‘Transaction records’, ‘Customer Data and Reviews’, ‘Reports and Notification’, ‘Sheet
Automation’, ‘Master Details’ and ‘Pricing and Discount Reports’. The product controller links us to
Inventory Tracking, Stock Management and Transfer Management. The Inventory Tracking section
would contain ‘Bar-coding’, ‘ product detailing’, ‘Product tracking’, ‘Packaging and shipping’, ‘Order
tracking’. The stock management link would contain ‘Product quantity’, ‘Product managing’ and ’Stock
entry details’ link, 'Create Purchase Order' link, ‘Create Selling item’ link, 'Receive Shipment' link,
14
'View Product purchase and selling History' link. The transfer management section would contain links
for 'Pricing of the item' Report, 'Selling price of the item' report, ‘keeping track of transaction history’,
'Transfer Stock' and 'View Transfer History' links.

It was identified that when the user would click the 'View inventory Level' link on the main
menu, the inventory Level screen would be displayed with the list of items in ascending order of the
items so that it would show the items that need to be ordered first. In accordance to the business
requirements, it was decided that the items displayed in view reorder level screen should have a link
where the user would be able to click when the user wants to create a purchase order. This means, the
system should navigate to create a purchase order screen when an item description is clicked. Next,
thorough analysis was done to decide what kind of information would be present in the purchase order
screen. It was found that, in order to create a purchase order, the system needs to know the originating
store information, so that the billing and shipping address could be determined. Hence the requesting
store details would form part of the screen. Since the receiving store information is available to the
system, the store information should be populated automatically by the system when the create
purchase order screen is displayed. In the purchase order screen, the user needs to provide the vendor
information so that the purchasing department knows from which vendor the item should be
purchased. The other piece of information needed for a purchase order is the item details, so that the
correct item could be purchased. The user can add multiple items in one purchase order. A new
purchase order would be in 'Open' status. Based on the above understanding, the purchase order
detailed information was documented in creating purchase order functional requirements.

Next, the functional requirements for 'Order tracking' were analyzed as follows: When a
shipment is received, the receiving clerk would open the purchase order to verify the items received
against the order. If the item received doesn't match the purchase order, the receiving clerk would
contact the store manager. If the store manager decides to receive the orders, the store manager would
click the 'Change Order' link to update the purchase order. The system would first prompt the manager
to login. If the store manager decides to return the order, the store manager can either change the order
or return the order. The store manager can change the status of the order and the system records the
date of change or return of the order and the status of the order in the purchase order table. Once the
items received match the items in the purchase order in the system, the receiving clerk would click the
'Receive Order' link and confirm that the items have been received. At this time, the system would
change the status of the order from Open to Closed and update the date delivered field to the received
date.

The functional requirements of the 'Transfer Stock' functionality were analyzed as follows: In
order to transfer inventory from one store to another, the Ordering clerk would click the Transfer Stock
link on the main menu. The current stock level would be displayed. The screen would be similar to the
reorder level screen. Users would click an item to transfer it to another store. At this time the Transfer
Information screen would be displayed. The item name and source store fields would be already filled.
The user would enter the destination store number and quantity to be transferred and click the
'Transfer' link. Item quantity transferred cannot be greater than the one hands item quantity. The
system would remove the item quantity from the sending store's Item table and put the item on the
receiving store's purchase order table. When the item is received by the receiving store, the receiving
store goes through the normal purchase order receiving process. A transfer order cannot be returned or
canceled.

15
 The functional requirements for the web site design include the design of the home page and the
main menu. The home page contains a greeting to the user and a page title. The home page would
contain fields where the user would input the login information. The home page would also have links
for the user to display 'About Us', 'Contact Us', and 'Help' information. The 'About Us' page would
display the information about the application. The 'Contact Us' page would display contact information
for the company. The functional requirements of the main menu include that the appropriate links
should be displayed in the main menu. The main menu and any other page would have links to go back
to the previous page, go to the home page and logout.

The links displayed on the main menu depend on the role of the user. In order to restrict the
user from performing actions that are not allowed for the user, four roles were defined in the
application. The Ordering Clerk role was created for the users who can create purchase orders or
transfer items only. The ordering clerks would be able to view the reorder level of items, create
purchase orders and view order history. The ordering clerks would not be able to receive orders.
Receiving Clerks would be able to view open purchase orders and receive the order. The receiving
clerks cannot create new orders. The Store Managers would be able to perform both the above actions
as well as they can run reports on the data in the store and view purchase order and transfer history.
The store managers would also be able to access a view only list of The Corporate users would be able to
perform maintenance actions as well as run reports. The corporate users cannot create purchase orders,
receive orders or transfer items to another store.

16
 EXTERNAL INTERFACE REQUIREMENTS

User Interfaces
User interface is one of the most important elements in any software. Most of the software’s are
used by non- technical persons. So they always seek of user friendly environment in their system. And
the user interface makes the system more familiar to its user. For our system we do not design a user
interface yet. But the process is going on.

Hardware Interfaces
In the current version of the software, it will have no special hardware interface with other
external systems. It will run in a general-purpose computer system with general-purpose hardware and
software.

Software Interfaces
The Current version of this system will be built on the following software:
Server:
 Internet Information system
 Cloud server
 PostgreSQL
 MVC 3.
Client:
 JavaScript.
 OpenSSL.
 JavaScript (synchronous/asynchronous) Enable Browser.

Communications Interfaces
All sorts of communications between server and client programs will be using ADO.NET
(ActiveX Data Objects for .NET) is a set of computer software components that programmers can be
used to access data and data services. It is a part of the base class library that is included with the
Microsoft .NET Framework. It is commonly used by programmers to access and modify data stored in
relational database systems, though it can also access data in non-relational sources and the messaging
will be done by XML format.

17
 OTHER NON-FUNCTIONAL REQUIREMENTS

Non-functional Requirements of a system specify the performance, reliability, availability,

security, maintainability, portability of a system. So below there are short descriptions of each of those
non-functional requirements.

Usability
 The system must be easy to use.
 The system must be easy to access.
 The system must be intuitive and simple in the way it displays all relevant data

Reliability
 The System must give accurate inventory status to the user continuously
 The system must provide a password enabled login to the user to avoid any foreign entity
changing the data in the system.
 The system should provide the user updates on completion of requested processes and if the
requested processes fail, it should provide the user the reason for the failure.
 The system should not update the data in any database for any failed processes

Performance
 The system must not lag, because the workers using it don’t have down-time to wait for it to
complete an action.
 All the functions of the system must be available to the user every time the system is turned on
 The calculations performed by the system must comply with the norms set by the user and
should not vary unless explicitly changed by the user.
 There are a lot of internal and external operations which are interrelated with each other for
fruit full production. So the communication among each end system should be tightly scheduled
and the notification should be sent in timely manner

Supportability
 The software is designed such that it works even on systems having the minimum configuration.
 The system is adaptable even if additional plugins or modules are added at a later point.
 The data can be exported to the manager so as to make the system more portable.

Maintainability
Software maintenance in software engineering is the modification of a software product after
delivery to correct faults, to improve performance or other attributes. Maintainability of software is
categorized in four classes:
 Adaptive – dealing with changes and adapting in the software environment.
 Perfective – accommodating with new or changed user requirements which concern
functional enhancements to the software.
 Corrective – dealing with errors found and fixing it.
 Preventive – concerns activities aiming on increasing software maintainability and
preventing problems in the future.

Packaging

18
  The system must be able to run on the Windows operating systems beginning with Windows
XP, and must be able to run on future releases such as the upcoming Windows 8
 The software must incorporate a license key authentication process.
 The packaging must come with a manual that details the use of the system, and also the
instructions on how to use the program. This manual may be included either in a booklet that
comes with the software, or on the disc that the software itself is on.

Interfacing
 The system must offer an easy and simple way of viewing the current inventory.

Legal
 The software must be licensed on an individual basis for smaller companies, as well as through a
multi-license deal for larger corporations.

Security
 This system will deal with huge amounts of data. So security is a prime issue of our system. So
the system should be secured from external interference by providing efficient security to the
entire system.

Safety
 The system should have a session that ends to prevent breach

19
 OTHER REQUIREMENTS

Other Requirements:

While our SRS document covers almost all important requirements used in the online
inventory management system, there are still some requirements which haven’t been covered above
as they are important but only useful for some specific sectors.

 If the user or handler is a factory administrator then they have control over the requirements
such as: Stock Inquiries, Vendor-Managed Inventory, and E-Commerce.
 The inventory tracking system will also perform requirements such as: Advanced Inventory
Tagging and Audit Trail.
 In transfer management requirements performed are: Multi-Location Tracking, Stock Transfer
Order Picking, Kitting and Product Bundling, Voice Picking, Pick-To-Light (PTL).
 While dealing with purchase also requirements such as Bulk POs, Partial Receiving, Supplier
Management, and Backordering are also performed.
 In customization and shipping; Labeling, Multi-Carrier Shipping, Multiple Shipment Orders,
Shipment by ID are requirements performed.
 While dealing with reports requirements such as Order Tracking, Quotations, Customer Pricing,
Multichannel Sales Returns were also performed.
 When managing master details; customize reports, report integration and drill down are some more
requirements we have used.
As a web base interface with cloud support it also supports mobile websites, native applications,
integration and synchronization.

Appendix A: Glossary

 Inventory: A complete list of items such as property, goods in stock, or the contents of a building.
 DMS: Document management system
 Cloud infrastructure: Cloud infrastructure is a term used to describe the components needed for
cloud computing, which includes hardware, abstracted resources, storage, and network resources.
 Economy quantity order:Economic order quantity is a technique used in inventory management. It
refers to the optimal amount of inventory a company should purchase in order to meet its demand while
minimizing its holding and storage costs.
 Authorized staff: System maintenance Administrators for Controlling the system and maintaining the
database
 Product control:A person for maintaining the inventory data specially for trading
 HTML: Hyper Text Markup Language
 Javascript: JavaScript is a text-based programming language used both on the client-side and server-
side that allows you to make web pages interactive.
 ASP.MVC3: ASP.NET MVC 3 is a framework for building scalable, standards-based web applications
using well-established design patterns and the power of ASP.NET and the . NET Framework.
 ADU.NET: ADO.NET is a set of computer software components that programmers can use to access
data and data services from a database.
 ER-Diagram: ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram
that displays the relationship of entity sets stored in a database
 DFD: DFD is the abbreviation for Data Flow Diagram. The flow of data of a system or a process is
represented by DFD. It also gives insight into the inputs and outputs of each entity and the process itself
20
  Bootstrap: A technique of loading a program into a computer by means of a few initial instructions
which enable the introduction of the rest of th
thee program from an input device.
 CSS: Cascading Style Sheet

APPENDIX B: Analysis Model

1. Flow Diagram:

Flow diagram is a collective term for a diagram representing a flow or set of dynamic
relationships in a system.

21
2. Entity Relationship Diagram:

ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram that
displays the relationship of entity sets stored in a database. In other words, ER diagrams help to
explain the logical structure of databases. ER diagrams are create
createdd based on three basic concepts:
entities, attributes and relationships.

22
3. Activity Diagram:

An activity diagram is a behavioral diagram i.e. it depicts the behavior of a system. An

activity diagram portrays the control flow from a start point to a finish point showing the various
decision paths that exist while the activity is being executed.

23
4. Use case Diagram:
In UML, use-case
case diagrams model the behavior of a system and help to capture the
requirements of the system. Use
Use-case diagrams describe the high-level
level functions and scope of a
system. These diagrams also identify the interactions between the system and its actors.

24
5. Class Diagram:
Class diagram describes the attributes and operations of a class and also the constraints
imposed on the system. The class diagrams are widely used in the modeling of object oriented
systems because they are the only UML diagrams, which can be mapped directly with object object-
oriented languages.

25
6. DFD Diagram:

A Data Flow Diagram (DFD) is a traditional visual representation of the information

inform flows within
a system. It shows how data enters and leaves the system, what changes the information, and
where data is stored. The objective of a DFD is to show the scope and boundaries of a system as a
whole.

a. Level 0:

DFD level 0 is also known as a context diagram. It's designed to be an abstraction view,
showing the system as a single process with its relationship to external entities. It
represents the entire system as a single bubble with input and output data indicated by
incoming/outgoing
g/outgoing arrows

26
b. Level 1:

In 1-level
level DFD, a context diagram is decomposed into multiple bubbles/processes.
In this level, we highlight the main objectives of the system and breakdown the high
high-level
process of 0-level
level DFD into sub
sub-processes.

27
c. Level 2:

This level two data flow diagram (DFD) template can map out information flow,
visualize an entire system, and be shared with your stakeholders.

28
2. State Transition diagram:

State Transition Testing is a type of software testing which is performed to check the
change in the state of the application under varying input. State
State-transition
transition diagrams are very
useful for describing the behavior of individual objects over the full set of use cases that affect
those objects.

29
 7. Sequence Diagram:

A sequence diagram or system sequence diagram (SSD) shows object interactions

arranged in time sequence in the field of software engineering. It depicts the objects involved in
the scenario and the sequence of messages exchanged between the objects needed to carry out the
functionality of the scenario.

APPENDIX C: References
 https://www.netsuite.com/portal/resource/articles/inventory
https://www.netsuite.com/portal/resource/articles/inventory-management/inventory
management/inventory-
management-system-features.shtml
features.shtml
 https://www.shareyouressays.c
https://www.shareyouressays.com/knowledge/7-main-scopes-of-inventory
inventory-control-and-
management/116410
 https://www.linnworks.com/blog/inventory
https://www.linnworks.com/blog/inventory-management-benefits
 https://www.selecthub.com/inventory
https://www.selecthub.com/inventory-management/5-benefits-inventory
inventory-tracking-software/
 http://www.smbceo.com/2019/08/08/4
//www.smbceo.com/2019/08/08/4-benefits-of-switching-to-an-online
online-inventory-
management-system/
 https://www.massgroup.com/benefits
https://www.massgroup.com/benefits-using-computerized-inventory
inventory-system/
 https://www.boxstorm.com/blog/advantages
https://www.boxstorm.com/blog/advantages-of-online-inventory-management/
management/
 https://www.assetinfinity.com/blog/advantages
https://www.assetinfinity.com/blog/advantages-of-inventory-management
management-system-software
 http://www.navata.com/cms/objectives
http://www.navata.com/cms/objectives-of-inventory-management-system/
system/
 https://www.assetinfinity.com/blog/inventory
https://www.assetinfinity.com/blog/inventory-management-system-objectives
objectives
 https://www.unleashedsoftware.com/bl
https://www.unleashedsoftware.com/blog/the-19-best-inventory-management
management-software-
features-to-look-for
 https://www.salesbabu.com/blog/online
https://www.salesbabu.com/blog/online-inventory-management-system/
system/
30
 https://www.netsuite.com/portal/resource/articles/inventory-management/inventory
management-system-features.shtml
 https://aglowiditsolutions.com/blog/features-of-inventory-management-system/
 https://epublications.regis.edu/cgi/viewcontent.cgi?article=1369&context=theses
 https://www.selecthub.com/inventory-management/inventory-management-software-top-
features-requirements/
 https://www.freeprojectz.com/dfd/inventory-management-system-dataflow-diagram

31