This thesis portrays the Inventory Management System adequately to decide the possibility and convenience of a completed system. The main idea is to trace the trading from the sales registers with extra highlights for deciphering the information. It utilizes a server model with an associated database to permit numerous stores and other locations to be associated. This takes into account later extension while as yet supporting the focus on independent small ventures.

This thesis depicts the IMS adequately to decide the practicality and convenience of a completed framework. The center idea is to follow the offer of things from the sales registers with extra highlights for deciphering the information. It utilizes a customer worker model with an associated information base to permit various stores and distribution centers to be associated. This takes into account later development while as yet supporting the focus on private companies. Inventory Management (IMS) are generally utilized in industry these days to build the effectiveness of thin streams. The conventional technique for IMS included a great deal of administrative work, for example, a bookkeeping page and request list which will be harder to oversee as the capacity becomes greater. In this manner, IMS can be modernized to further expand the effectiveness. This undertaking intended to create IMS programming can store a huge sum of information. Additionally, it has check in/out capacity and search work that runs utilizing examine QR Code. Other than that, the product additionally has the element of low stock notice capacity to caution the client if the thing has low amounts. To build up the product, first the measures of the product are resolved by picking the product advancement devices to build up the product that can accomplish the models of the product. Next the product will be created and fixed. This paper centers on creating IMS programming for SMEs and biomedical field organization use.


ABSTRACT                                                                                                                                     VII

CHAPTER 1: INTRODUCTION                                                                                                     1

CHAPTER 2: LITERATURE REVIEW                                                                                         5

  1. INTRODUCTION                                                                                                                                                         5
    1. HISTORICAL OVERVIEW                                                                                                                                                           5
    2. REVIEW OF THE EXISTING SYSTEM                                                                               7
    3. JUSTIFICATION OF THE NEW SYSTEM                                                                           7
    4. BENEFITS OF THE NEW SYSTEM                                                                                    7
    5. RELATED WORK                                                                                                                                                             8

SUMMARY                                                                                                                                                                                 11

CHAPTER 3: REQUIREMENTS ANALYSIS AND DESIGN                                                      13

3.2.2. Agile Development Methodology                                                                                   14

  1. APPROACH TO CHOSEN METHODOLOGY/METHODS                                                                                                   15
    1. WATERFALL METHODOLOGY APPROACH                                                                   16
    2. AGILE METHODOLOGY APPROACH                                                                             17
    3. TOOLS AND TECHNIQUES                                                                                                                                            18
    4. ETHICAL CONSIDERATION                                                                                                                                            19
    5. REQUIREMENT ANALYSIS                                                                                                                                             20
      1. Responsibility Matrix                                                                                                       21
      2. Fact-Finding Techniques                                                                                               21
    6. REQUIREMENTS SPECIFICATIONS                                                                                                                                22
      1. Functional Requirement Specifications                                                                        22
      2. Non-Functional Requirement Specifications                                                                23
    7. SYSTEM DESIGN                                                                                                                                                          23
      1. Application Architecture                                                                                              24
      2. Use Case                                                                                                                      24
      3. Sequence Diagram                                                                                                       25
      4. Data Flow Diagram                                                                                                     26

3.8.6    Entity-Relationship Diagram (ERD)                                                                             27

CHAPTER 4:  IMPLEMENTATION AND TESTING                                                                  28

Table 4. 4 Test Summary Report                                                                                              39


REFERENCES                                                                                                                               46

APPENDICES                                                                                                                                 47


Table 1.1: Risk and Assessment of Project Table 3.1: Developers Specification Hardware Table 3.2: Developers Specification Software Table 3.3: Developers Specification Hardware Table 3:4: Responsibility Matrix

Table 3.5 Functional Requirement Specifications Table 3.6 Non-Functional Requirement Specifications Table 4.1: Test Plan

Table 4.2Test Suite Performed Table 4.3: Test Traceability Matrix Table 4. 4 Test Summary Reports


FIGURE 2 1 SILVER INVENTORY SYSTEM                                                                                                                                                8

FIGURE 2 2 ZOHO INVENTORY MANAGEMENT SYSTEM                                                                                                                           9

FIGURE 2 3 SORTLY IMS                                                                                                                                                                       10

FIGURE 3 1 WATERFALL MODEL (TECHTARGET                                                                                                                                   14

FIGURE 3 2 AGILE MODEL (TECHTARGET, 2011)                                                                                                                                  15

FIGURE 3 3 APPLICATION ARCHITECTURE DIAGRAM                                                                                                                            24

FIGURE 3 4 USE CASE DIAGRAM                                                                                                                                                           25

FIGURE 3 5 SEQUENCE DIAGRAM                                                                                                                                                        26

FIGURE 3 6 DATAFLOW DIAGRAM LEVEL ZERO                                                                                                                                    26

FIGURE 3 7 DATAFLOW DIAGRAM LEVEL ONE                                                                                                                                      27

FIGURE 3 8 ENTITY RELATIONSHIP DIAGRAM                                                                                                                                       28

FIGURE 4 1 LOGIN PAGE                                                                                                                                                                       29

FIGURE 4 2 DASHBOARD                                                                                                                                                                      30

FIGURE 4 3 PRODUCT PROFILE                                                                                                                                                            30

FIGURE 4 4 STOCK INVENTORY                                                                                                                                                            31

FIGURE 4 5 CUSTOMER PROFILE                                                                                                                                                          31

FIGURE 4 6 DAILY SALES                                                                                                                                                                      32

FIGURE 4 7 EXPIRED ITEM                                                                                                                                                                    32

FIGURE 4 8 ADD ITEM                                                                                                                                                                     33

FIGURE 4 9 ADMIN LOGIN                                                                                                                                                             36

FIGURE 4 10 NEW ITEM ADDED                                                                                                                                                            37

FIGURE 4 11 ITEM ADDED TO CART                                                                                                                                                      37

FIGURE 4 12 ITEMS IN STOCK                                                                                                                                                               38

FIGURE 4 13 NEW STOCK ADDED                                                                                                                                                         39

FIGURE 4 14 NEW CUSTOMER ADDED                                                                                                                                                  39

FIGURE 4 15 NETBEANS IDE                                                                                                                                                                41

FIGURE 4 16 OPEN IAS USING APP                                                                                                                                                       42

FIGURE 4 17: RUN THE CODE USING BROWSER                                                                                                                                   42

FIGURE 4 18 SERVER DIRECTORY (DATABASE                                                                                                                                     43

FIGURE 4 19 NAVIGATE PAGES                                                                                                                                                             44


CPU                    Central Processing Unit

ERD                    Entity Relationship Diagram

IT                         Information Technology

IMS                     Inventory Management System

ERD                    Entity Relationship Diagram



Walid Halal Spices is a medium scale business whose Chief Executive Officer is Mr Walid. The research is served to develop an Inventory Management System that covers the product information storage needs for Walid Halal Spice Inventory Management System. With the implementation of this prototype, the company information will be far safer and much better accessible. Companies usually keep their record manually which in this generation can be of inconvenience. In respect to this system, it will help the business run their operation smoothly with accurate and accessible data. This chapter is dedicated to fully understanding the nature of the problem and developing a solution to it. It also explains the significance of the system to the Company.

    Background and Motivation

Walid Halal is one of the largest retail shops for spices in Gombe State and has gained such a wealth of reputation in the Spice industry. It has a quite reasonably sized store. Its vast interest in Spice Business spans across a wide Market Area with one Shop and a Store in Gombe. The shop offers wholesale, retail and distribution services of their products to its customers across the country. For the matter of wholesale services, it is only carried out from the shop and store while the retail services are offered at the shop where distribution services are offered in both places.

The current system for the medium scaled business was described by manual field enrollment and record based system which was vulnerable to an inordinate couple of mistakes, information repetition and the trouble of data about the items in stock are nevertheless only a couple of the difficulties the organization faces.

    Statement of the Problem

Walid Halal uses a manual ledger system which brings about a lot of inconveniences and undesired drawbacks. There is a lot of time wasting since the information is first documented on hard copies then entered into a spreadsheet application. It takes a very long time to search for a particular record with the current system and lots of paper and ink are wasted which makes the system very inefficient. With flat files, data duplication is a common problem that results in all

sorts of problems such as update and delete errors just to mention but a few. Since the manual ledger system can easily be manipulated, ledger books can get lost and it also undergoes wear and tear thus leading to loss of data which is vital to the company ergo making the system insecure.

This therefore brought about a need for an Automated Inventory Management System to be put in place which would help in improving the system. The advent of an Automated Inventory Management System would thus rid of the problems nurtured by the manual ledger system used by Walid Halal Spices.

    Aim and Objectives

The general objective is to implement and develop an Automated Inventory Management System (IMS) that will effectively and efficiently manage the inventory of Walid Halal Spices in their Store. To design an Automated Inventory Management System that acts as the blueprint for the new system.

To collect and analyze user requirements that was to provide the researchers with enough information of what the system users want the system to accomplish.

To test and validate the designed system that ensures all systems requirements are met.

To implement a prototype of the designed system that realizes the system designs and provides the real first taste of the actual system.

    Significance of the Project

The execution of this has a great advantage to the business people dealing with goods in a way that due to the problems the companies are facing, the designed system can be more important to the company in the following ways.

The company is able to save a bit more money on expenses as it wouldn’t need to buy much paper and ink. Whereas the customers are better served as information access with the new system would be far much faster by managing your inventory. Also, the suppliers for the company also benefit as the new system makes it easier to know which items need to be restocked.

With the old system, it is quite easy to maneuver around the books and change numbers but rather, the system also goes a long way in reducing fraud as it would neatly keep track of all the assets in the company. Such that all stock, items and sales are always up to date.