Table of Contents

1. Abstract.......................................................................................................................................... 2
2. Introduction ................................................................................................................................... 3
3. System Analysis ............................................................................................................................. 5
4. System Design ................................................................................................................................ 8
5. Implementation ........................................................................................................................... 15
6. Testing .......................................................................................................................................... 16
7. Conclusion ................................................................................................................................... 17
8. Reference ..................................................................................................................................... 18

1|Page
 1. Abstract

Inventory Management System is a desktop-based application for managing the inventory

system of any organization. The Inventory Management System (IMS) refers to the system
and processes to manage the stock of organization with the involvement of Technology
system. This system can be used to store the details of the inventory, stock maintenance,
update the inventory based on the sales details, generate sales and inventory report daily or
weekly based. This project is categorized individual aspects for the sales and inventory
management system. In this system we are solving different problem affecting to direct sales
management and purchase management. Inventory Management System is important to
ensure quality control in businesses that handle transactions resolving around consumer
goods. Without proper inventory control, a large retail store may run out of stock on an
important item. A good inventory management system will alert the wholesaler when it is
time to record. Inventory Management System is also on important means of automatically
tracking large shipment. An automated Inventory Management System helps to minimize the
errors while recording the stock.

2|Page
 2. Introduction
2.1 Introduction to Inventory Management System
The project Inventory Management System is a complete desktop-based application. The
main aim of the project is to develop Inventory Management System Model software in
which all the information regarding the stock of the organization will be presented. It is an
intranet-based desktop application which has admin component to manage the inventory and
maintenance of the inventory system. This desktop application is based on the management
of stock of an organization. The application contains general organization profile, sales
details, Purchase details and the remaining stock that are presented in the organization. There
is a provision of updating the inventory also. This application also provides the remaining
balance of the stock as well as the details of the balance of transaction. Each new stock is
created and entitled with the named and the entry date of that stock and it can also be update
any time when required as per the transaction or the sales is returned in case. Here the login
page is created in order to protect the management of the stock of organization in order to
prevent it from the threads and misuse of the inventory.

2.2 Literature Review

Products are considered as the business resources for the organization. This includes
managing the product with appropriate way to review any time as per the requirement.
Therefore, it is important to have a computer based IMS which has the ability to generate
reports, maintain the balance of the stock, details about the purchase and sales in the
organization. This application software is only used by the large organization but so we came
up with the application which can be used by the small company for the management of their
stock in the production houses. After analysing the other inventory management system, we
decided to include some of common and key features that should be included in every
inventory management system. So, we decided to include those things that help the small
organization in a way or other.

2.3 Problem Statement

After analysing many existing IMS we have now the obvious vision of the project to be
developed. We defined our problem statement as:
 To make desktop-based application of IMS for small organization.
 To make the system easily managed and can be secured.
 To cover all the areas of IMS like purchase details, sales details and stock
management.

3|Page
2.4 Scope of the Application
Inventory Management System (IMS) is targeted to the small or medium organization which
doesn’t have many warehouses i.e. only to those organization that has single power of
authority. Some of the scope are:

 Only one person is responsible in assigning the details or records

 It is security driven.
 Warehouses can be added as per the requirement.

4|Page
 3. System Analysis

3.1 Background Research

We started research by identifying the need of IMS in the organization. Initially we bounded
our research to find the general reasons that emerged the needs of Inventory Management
System. We used different techniques to collect the data that can clearly give us the overall
image of the application. The techniques we used were interview with the developers, visiting
online websites that are presented as the templates and visiting some organization to see their
IMS application. Basically, the following factors forced us to develop IMS application:
 Cost and affordability
 Lack of stock management.
 Effective flow of stock transfer and management.
 Difficulty in monitoring the stock management.

3.2 Requirement Analysis

We collected a number of requirements for project from our primitive research, website
visits, and interview to the concerned personnel and their experiences regarding the concepts
of its development. We have even visited some organization in Kathmandu valley and
analyse its importance and try to develop the project by fulfilling all the weakness that were
found in the application. We then decided to build same type of application with different
logic flow and new language which will be suitable for the small organization.

3.3 IMS Requirement

The goal for the application is to manage the inventory management function of the
organization. Once it is automated all the functions can be effectively managed and the
organization can achieve the competitive advantage. Business requirement are discussed in
the Scope section, with the following additional details:
 Helps to search the specific product and remaining stock.
 Details information about the product sales and purchase.
 Brief Information of the organization todays status in terms of news, number of
present inventories as per the date entered.
 It helps to identify the total presented inventory in the company.
 To know the balance and details of sales distributed in specific date.
 There is proper transaction management of inventory.
 All transaction has specific entry date along with quantity and rate.
 Only admin can login in the page.

5|Page
3.4 Feasibility Analysis
This software has been tested for various feasibility criterions from various point of
views.
3.4.1 Economic Feasibility
The system is estimated to be economically affordable. The system is medium scale
desktop application and has affordable price. The benefits include increased efficiency,
effectiveness, and the better performance. Comparing the cost and benefits the system is
found to be economically feasible.

3.4.2 Technical Feasibility

Development of the system requires tools like:
 Visual Studio 2015
 .NET Framework 4.5
 Microsoft SQL server 2008, etc which are easily available within the estimated
cost and schedule.

3.4.3 Operational Feasibility

The system provides better solution to the libraries by adding the typical requirement and
necessities. The solution provided by this system will be acceptable to ultimate solution
for the stock management.

3.4.4 Schedule Feasibility

The organized schedule for the development of the system is presented in the schedule
sub-section. The reasonable timeline reveals that the system development can be finished
on desired time framework.

3.5 User Requirement

3.5.1 Functional Requirements

A. Input/output

1. System shall have a form to accept the customer details.

2. System shall have a form to accept the Plant details.
3. System shall display transaction details.

6|Page
 4. System shall provide search facility on customer name, Order Placed, date of order,
date of order dispatch, date of transaction, transaction amount, credit card no etc.
5. System should provide facility for change in address/name.
6. System should maintain the details about placing order/dispatch or order i.e, order
status

B. Processing

1. System should automatically generate the bill.

2. System should inform the pending order and make changes if the order is dispatched.

C. Error handling

1. Should report any errors on duplicate primary keys.

2. Should report any ‘Out of Range’ values on numeric fields

3. Should report any data type mismatches any field on the forms.

4. Should report on any ‘Invalid dates’

5. Should report any violation of authorization of rights

6. Should report any Invalid Login errors

3.5.2 Non-functional Requirements

1. All user manuals should be provided in the necessary format

2. Application should support 5 simultaneous users.
3. Transaction should be completed within 1/5th of second
4. There will be backup procedure to maintain records.

7|Page
 4. System Design
4.1Process Flow Diagram
Process Flow Diagram or Flowchart is a diagram which uses geometric symbols and
arrows to define the relationships. It is a diagrammatic representation of the algorithm.
The Process flow Diagram of our application is shown below:

Figure 4.1: IMS Process flow diagram

8|Page
4.2 Use Case Diagram

Its purpose is to present a graphical overview of the functionality provided by a system in

terms of actors and their goals. The main purpose of a use case diagram is to show what
system functions are performed for which actors.
4.2.1 Diagram Building Block Use cases
A use case describes a sequence of actions that provide something of measurable value to an
actor and is drawn as a horizontal ellipse.
Actor
An actor is a person, organization or external system that plays a role in one or more
interactions with the system
System boundary boxes (optional)
A rectangle is drawn around the use case called the system boundary box to indicate scope of
the system.

Figure 4.2.1: IMS Use Case Diagram

9|Page
Use case Diagram for Supplier

Login Id and Password

Checks Inventories

<<include>>

Tracks Order

Dispatch order on time

Customer

Sends Invoice

Supplier

Updates Records

10 | P a g e
 Use Case Diagram for Customer

Studies
Requirements

Make list of requirements

Places the Order

Makes payment
Customer Clerk

Invoice

Send GRN

11 | P a g e
 4.3 Class Diagram for a customer order

Customer Order
Cust_Id Order_no
Name Ordercredate
Addr1 Order_status
Addr2 Shipment_dat
Cust_city e
Pincode Challan
Addcust()
Updatecust() calcBilltotal()
Getcustdet() Payment calctotalweig
Amount ht()
Payment
date
Makepayme
nt()
Getinvoice()

Ordetdetail Material
Orderno
Materialqty Materialcode
Materialvalue Plantcode
Stckqty
Caclsubtotal
calcweight Getpriceforqty()
Credit Cheque
Number Chqno
Type Bankname
Expirydate Bankid
validating validating

GRN
Recivedqty
Damaged
Rejected

Rejectgood()
Description()

12 | P a g e
4.4 Activity Diagram

Figure 4.3.1: IMS Activity Diagram

13 | P a g e
4.5 Sequence diagram for Supplier

Supplier Transaction Customer Invoice

Log In

Validate

Tracks order

Places order

Takes customr details

Fill Order details

Makes Payment

Dispatch Order

Send order details

Add new entry

Send Invoice
Log Out

Send GNR

14 | P a g e
 5. Implementation
Inventory Management System will be designed using Visual Studio as mentioned earlier
following the three-tier application architecture. It provided us with the code editor as a white
blank space and the solution explorer where every code file is kept. Code Editor is where the
logical were developed into code and kept safe in the solution explorer. In solution explorer
we kept every code file by creating the folder and adding those files in a folder that are
similar in nature. The main folder is the Inventory Management System.

15 | P a g e
 6. Testing
6.1 Purpose of Testing
The purpose of software testing is to access or evaluate the capabilities or attributes of
a software program’s ability to adequately meet the applicable standards and
application need. Testing does not ensure quality and the purpose of testing is not to find
bugs. Testing can be verification and validation or reliability estimation. The primary
objective if testing includes:
 To identifying defects in the application.
 The most important role of testing is simply to provide information.
 to check the proper working of the application while inserting updating and deleting
the entry of the products.

6.2 Type of Testing

We have used one type of testing to ensure the error free features of our software application:

6.2.1 Unit Test

This type of testing is the testing of individual software components. It is typically done by
the programmer and not by the testers. It requires details information and knowledge about
the internal program design and code to perform this. During unit testing, we carried out
various testing task such as the reflection of the unit data on database and its interface.
Various types of bugs associated with the component were identified and fixed. We use
various functional keys to test our software. In our software unit testing is concerned with the
stock units, opening stock units and product unit’s validation as well as the validation of
product units.

16 | P a g e
 7. Conclusion
7.1 Project Limitation
Since this is our first project it has some limitation. Due to less knowledge in particular fields
and limited time we were not able to fulfil all our expectations that we expected we could do
while the project got started. We hope this limitation are considerable. Some of the project
limitations are:
 This application is not suitable for those organization where there is large quantity of
product and different level of warehouses
 This software application is able to generate only simple reports.
 Single admin panel is only made.
 It is not suitable for large organization.

7.2 Conclusion
To conclude, Inventory Management System is a simple desktop based application basically
suitable for small organization. It has every basic item which are used for the small
organization. Our team is successful in making the application where we can update, insert
and delete the item as per the requirement. This application also provides a simple report on
daily basis to know the daily sales and purchase details. This application matches for small
organization where there small limited if warehouse. Through it has some limitations, our
team strongly believes that the implementation of this system will surely benefit the
organization.

17 | P a g e
 8.Reference
 https://en.wikipedia.org/wiki/Inventory_management_software
 https://blog.capterra.com/what-is-an-inventory-management-system/
 https://creately.com
 https://www.scribd.com
 https://www.academia.edu/Documents/in/Inventory_Management_System

18 | P a g e