A Final Project Report On

Mobile Inventory Management System

Submitted to:

Department of Bachelor in Computer Application (BCA)

Patan Multiple Campus

Patan Dhoka, Lalitpur

For the partial fulfillment of BCA fourth semester.

 Submitted by:

Binod Khanal Anil Rajbhandari

2nd year / 4th semester 2nd year / 4th semester

220098 220101

2074 2074
 lqe'jg ljZjljBfno kmf]g g+=
Phone No.
TRIBHUVAN UNIVERSITY %–@^)%!) 5-260510
%–@^)@($ 5-260294
kf6g ;+o'Qm SofDk; %–%@@)&^ 5-

Patan Multiple Campus

td;f]df Hof]ltu{do

kf6g 9f]sf, nlntk'/, g]kfn

Patan Dhoka, Lalitpur, Nepal

kq ;+Vof÷Ref. No.:
ldlt÷Date:2076÷06÷02

Subject:Approval of Project

The project entitled “Mobile Inventory Management System.” developed by Anil

Rajbhandariand Binod Khanal for the partial fulfillment of the requirement for Bachelor
in Computer Application (BCA), fourth semester has been reviewed and approved for
final defence.

Proposal Evaluation Committee Signature

Dr. Laxman Singh Kunwar

Assistant Campus Chief
Patan Multiple Campus
Patan Dhoka, Lalitpur

Mr. Bhoj Raj Joshi

Program Coordinator
Patan Multiple Campus
Patan Dhoka, Lalitpur

Mr. Ramesh Singh Saud

Faculty Member
Patan Multiple Campus
Patan Dhoka, Lalitpur
 Declaration

We declare that this project entitled “Mobile Inventory Management System” done at
Patan Multiple Campus is a record of project work submitted by Binod Khanal and Anil
Rajbhandari for the partial fulfillment of the requirement for Bachelor in Computer
Application (BCA), fourth semester under the supervision and guidance of Mr Ramesh
Saud .

The Project is genuine and not a reproduction of any project previously done or
submitted.

________________ _______________
Ramesh Saud Binod Khanal
Signature of supervisor Signature of candidate

________________
Anil Rajbhandari
Signature of candidate
 Acknowledgement
We have taken efforts in this project. However, it would not have been possible without
the kind support and help of many individuals and organizations. I would like to extend
my sincere thanks to all of them.

We would like to express our gratitude to our project supervisor Mr.Ramesh Saud who
took keen interest on our project and guided us throughout the project by providing all
the necessary ideas, information and knowledge for the developing a functional web
application. Our special thanks to Mr. Basanta Chaulagain for his constant
encouragement guidance towards, making this report standard as per the norms and
values.

We are highly indebted to Patan Multiple campus for constant guidance and supervision,
as well as for providing all the necessary ICT infrastructure and friendly environment for
the successful completion of the project .We also appreciate the efforts of BCA
coordinator Mr.Bhojraj Joshi without him ,the project would have been nowhere near
completion.
 Abstract
This project is aimed to develop a desktop based application named Inventory
Management system for managing the inventory system of mobile shop. The inventory
management system (IMS) refers to the system an processes to manage the stock of
mobile with the involvement of Technology system . This system can used to store the
details of monthly based .This project is categorize individual aspects for the sales and
inventory management system .In this system we are solving different problem affecting
to direct sales and purchase management .Inventory management system is important to
ensure quality control business that handle transaction resolving around consumer goods.
Table of Contents
CHAPTER 1: INTRODUCTION1
1.1 INTRODUCTION INVENTORY1
4.1 PROBLEM STATEMENT1
4.1 OBJECTIVE1
4.1 SCOPE AND LIMITATIONS2
1.5 REPORT ORGANIZATION2
CHAPTER 2: LITREATURE REVIEW4
CHAPTER 3: REQUIREMENT ANALYSIS6

3.1 REQUIREMENT ANALYSIS6

3.1.1 FUNCTIONAL REQUIREMENTS7
3.1.2 7
3.2 FEASIBILITY STUDY8

3.2.1 TECHNICAL FEASIBILITY8

3.2.2 ECONOMICAL FEASIBILITY9

3.2.3 OPERATIONAL FEASIBILITY9

3.3 SYSTEM ANALYSIS10

3.3.1 DATA MODELINNG E-R10

3.3.2 PROCESS MODELING11

3.3.3 SYSTEM DEVELOPMENT MODEL13

CHAPTER 4: SYSTEM DESIGN14

4.1 SYSTEM ARCHITECTURE14

4.2 FLOW CHART15
4.3 SEQUENCE DIAGRAM17
4.4 SYSTEM ACTIVITY DIAGRAM18
CHAPTER 3: IMPLEMENTATION AND TESTING19

5.1 MODULE DISCRIPTION19

 5.2 TOOLS USED20
CHAPTER 6: CONCLUSION AND OUTCOME

6.1 CONCLUSION5
6.2 OUTCOME14
6.3 RECOMANDATION14
TABLE OF FIGURES
FIG 1. USECASE DIAGRAM………………………………………………………………………………………………………7

FIG 2.DATA MODELING E-R…………………………………………………………………………………………………….10

FIG 3.CONTEXTDIAGRAM………………………………………………………………………………............................11

FIG 4.DFD 1 LEVEL DIAGRAM……………………………………………………………………………………………………12

FIG 5. SYSTEM DEVELOPMENT MODEL……………………………………………………………………………………..14

FIG 6.SYSTEM ARCHITECTURE……………………………………………………………………………………………………15

FIG 7. SYSTEM FLOWCHART………………………………………………………………………………………………………16

FIG 8.SEQUENCE DIAGRAM……………………………………………………………………………………………………….18

FIG 9.ACTIVITY DIAGRAM………………………………………………………………………………………………………….19

 Abbreviations
BCA = Bachelor Of Computer Application

DBMS = Database Management system

DFD = Data flow Diagram

IMS = INVENTORY MANAGEMENT SYSTEM

PHP = Hypertext Pre-Processor

SQL = Structured Query Language

 Chapter 1

Introduction
1.1Introduction
Inventory or stocks are the lifeline and constitute brand image of any company or
business .Beginning from the manufacturing stage to the tracking of products and parts
during their transportation from vendor to warehouse between the warehouse and then to
retail location or directly to the customer . An inventory management is software is a
computer based system industry can utilize it to generate work order and bills of
materials.

We have designed inventory web application to meet the requirement of mobile pasal .
This software can be used as simple inventory control . It is easy to create report
management ,phone product management, phone category management, customer list
management, supplier details management.

1.2Problem of Statements
Inventory Management is huge issues in manufacturing company and industries in the
real world as it is the backbone of any business . It plays very significant role in the
proper running of any business .At present there is no significant number of online
inventory management system . Fast report generation is not possible . information about
issue/return of the goods are not properly maintained . Not accessible while away
physically and No central database can be created as information is not available in
database .Now a days manual system is also used in many organization which may our
system from various aspects.

We defined our problem statement

1. To make system easily manage and secure.

2. To make desktop based application of IMS for small organization
3. To cover all areas of IMS like purchase and sales details of stock
management.

1
 1.3Objectives
● To develop the application that deals with day to day requirement of any
production
● To develop the easy management of product.
● To handle the inventory details like purchase, sales ,return outward ,return inward
,balance stock details.
● To maintain the effective management of stock and simplify the use of inventory
in organization

1.4 Scope and Limitations

This System (IMS) is targeted to small or medium mobile company which doesn’t have
many godwon or warehouses i.e only to those company that has single power of
authority. Some of the scope and limitation are:

1.4.1 Scope

● Used widely especially in mobile industries.

● Warehouses can be added as per the requirement.
● Can be easily adopted

1.4.2 Limitation

● The admin will face technical difficulty while using the system
● Internet connection is required
● Doubts about its authenticity
● Failure of server fails whole system

2
 1.4Report Organization

Chapter 1
This chapter deals with the introduction of our system problem statement of
system objective ,scope ,limitation of the system

Chapter 2
This chapter deals with the literature review in this chapter we study the existing
system and find the problem

Chapter 3
This chapter is about the requirement analysis where functional and
nonfunctional and feasibility study is collected and described.

Chapter 4
This chapter is about the system design of the project where we draw the
different design like system architecture,system flowchart ,class diagram,activity
diagram etc

Chapter 5
This chapter is all aabout the implemention and testing of system where we
mentioned different tools used while developing this system.Here we have
shown the test cases ,test data and test results.

Chapter 6
This chapter we explain about the conclusion of the system and we explain the
outcome of system

3
 Chapter 2

Literature Review

Inventory management is considered as major concerns of every organization. In

inventory holding, many steps are taken by managers that result a cost involved in this
row. This cost may not be constant in nature during time horizon in which perishable
stock is held. To investigate on such a case, Taygi (2014) proposes an optimization of
inventory model where items deteriorate in stock conditions. In this paper, based on a
real-world case study for a municipal district in Tehran, a multi- objective mathematical
model is developed for the location-distribution problem. The proposed model considers
the role of demand in an urban area, which might be affected by neighbor wards.
Integrating decision making process for a disaster helps to improve a better relief
operation during response phase of disaster management cycle. In the proposed approach,
esmeli (2014) says, a proactive damage estimation method is used to estimate demands
for the district based on worst-case scenario of earthquake in Tehran This paper deals
with the application of six most potential preference ranking methods for selecting the
best FMS for a given manufacturing organization. Chatterjeea and Chakraborty (2014)
say, it is observed that although the performances of these six methods are almost similar,
ORESTE method slightly outperforms theothers. It is particularly applicable to those
situations where the decision maker is unable to provide crisp evaluation data and
attribute weight. Ulrich and Pearson (1998)introduce approaches for the integration of the
Quality Function Deployment method as well as feedback with system components for
computer aided product development. The integration is based on information models
representing product, process and factory information. Pastore and Martin (2012) study
was to examine students’ perceptions of designing and developing mobile based
instructions by interviewing and surveying of graduate students. Results of the survey
and qualitative data analysis indicated that usability was a key issue on the mobile device.
Users enjoyed quick access, good organization, user control, single column layouts, and
large links/buttons. These findings contribute to the literature base on the design and
development of mobile based instruction. Norman E (2012) discusses, while existing

4
factors identified in the literature were found to be present in the context of today’s
design program, the critical perspective of this study recontextualized these factors, along
with the identification of new or underrepresented factors. Taking on the perspective of a
student’s experience of pedagogy foregrounds issues of uncertainty and ambiguity,
highlighting the social interactions between fellow students, and the role of
communication and individual effort in learning to think in a more designerly way. In
today’s world every business tries to strike balance in inventory between what is needed
and what is demanded considering measure factor of cost cutting/reduction. This control
is called inventory management or inventory control. Inventory is basically assets (goods
and materials) which are stock of any business. Today inventory plays vital role in
business, it helps to generate reports, maintain the balance of the stock details and about
the purchase and sales in the organization before we start to developing inventory system,
we research existing inventory system in our market. Which gives knowledge for the
development of our project . These application software are only used by the large
organization. In our market we couldn’t find software used in small company so they
faces many problem to manage their product.

After analysis the other existing inventory system, So we decide to developed new
system which help in small mobile company to manage their inventory or product in
market and we are also adding some common key feature of pervious existing inventory
system in market which eventually helps to boom and flourish the small business by
maintaining proper record of purchase sales and product description.

5
 Chapter 3

Requirement Analysis
3.1 Requirement Analysis

We have analysied the the project from functional and non functional point of view
which is so significant for the system for better performance.

3.1.1 Functional Requirements (Use case diagrams)

Functional requirements specify what the system should do. In other words, a functional
requirement will describe a particular behaviour or function of the system when certain
conditions are fulfilled.

Login
Input: Enter the username and password provided.
Output : User will be able to use the features of software.
Manage product by admin
Add product
Input : Enter the details of the product details such as names ,quantity ,price,
brand etc.
Output : confirmation of addition.
Update product
Input : Enter the name of the product and quantity of products.
Output : Update the list of the products available.
Delete product
Input : search the product and delete.
Output : Show the deletion successful result.
Add customer
Input : Enter the details of the customer such as names ,address ,contact no etc.
Output : confirmation of addition.
Update customer
Input : Enter the name of the customer
Output : Update the list of the customer available.
Add supplier

6
Input : Enter the details of the supplier such as names ,address ,contact no etc.
Output : confirmation of addition.

Maintain list
List of product
List of customer
List of supplier
Prepare monthly account

7
8
3.1.2 Non-Functional Requirements

Non Functional Requirements specifies what constraints there are on the system
for its development. Some of the non functional requirements for our project are:
Availability Requirement
The system is available 100% for the user and is used 24 hrs a day and 365 days a
year. The system shall be operational 24 hours a day and 7 days a week.
Accuracy
The system should accurately provide real time information taking into
consideration various concurrency issues. The system shall provide 100% access
reliability.

Performance Requirement
The information is refreshed depending upon whether some updates have
occurred or not in the application. The system shall respond to the member in
optimum time of the request submitted. The system shall be allowed to take more
time when doing large processing jobs. Responses to view information will take
time as per the complexity.
Reliability Requirement
The system has to be 100% reliable due to the importance of data and the
damages that can be caused by incorrect or incomplete data. The system will run
7 days a week, 24 hours a day.

3.2 Feasibility Study

In Feasibility Study we basically study whether the development of proposed system is

possible from economic or operational standpoint or not. So, basically in our project we
focus on three types of feasibility study which are described below

3.2.1 Technical Feasibility

We can strongly say that it is technically feasible, since there will not be
much difficulty in getting required resources for the development and
maintaining the system as well. All the resources needed for the
development of the software as well as the maintenance of the same is
available in the organization here we are utilizing the resources which are
available already.

9
3.2.2 Economic Feasibility

Development of this application is highly economically feasible .The

organization needed not spend much money for the development of the
system already available. The only thing is to be done is making an
environment for the development with an effective supervision. If we are
doing so, we can attain the maximum usability of the corresponding
resources. Even after the development, the organization will not be in a
condition to invest more in the organization. Therefore, the system is
economically feasible.

3.2.3 Operational Feasibility

 We have made this to fulfill all the requirements of this project. This software could do
all operational activities easily. We tried our best to make it best user friendly for the
users.our system is enough to handle daily library activities between librarian and student
without any difficulties

3.3 System Analysis Diagrams

We have draw different diagram for system analysis

10
 3.3.1 Data Modeling E-R

3.3.2 Process Modeling

This process shows the process or steps to be performed by the systems properly

● Context Diagram

11
 Fig of :context diagram

● DFD
Level 1 DFD for admin

12
3.3.3System Development Model

13
The system development model suitable for Mobile Inventory Management System is the
'Prototype Model'.

Chapter 4

System Design
4.1 System Architecture

14
4.2 System Flowchart

15
4.3Class Diagram
16
It is a static diagram which represents the static view of the application. Class
diagram is not only used for visualizing, describing and documenting different
aspects of system but also for constructing executable code of software application.
Class diagram for library management system is show below:

4.4 Sequence Diagram

17
Sequence Diagrams are interaction diagrams that detail how operations are carried
out. They capture the interaction between objects in the context of collaboration.
Sequence diagram for our system is:

4.5 Activity Diagram

18
Activity diagram represents the dynamic aspects of the program. Activity diagram for
library management system is show below:

19
 Chapter 5

Implementation and Testing

5.1 Module Description

This web-based Mobile Inventory Management System is composed of single

modules which is the Admin Module.

Admin Module

Enable admin to view product

Enable admin to edit or delete product

Enables admin to add and search product

Enables admin to remove product

Enables admin to add supplier

Enables admin to update supplier

Enables admin to prepare supplier details

Enables admin to add customer

Enables admin to update customer

Enables admin to prepare customer details

Enable admin to prepare receipt

Enables admin to add prepare monthly statement.

20
 5.2 Tools used

We have used several tools to accomplish this table ,they are listed below

5.2.1 Front End Tools

• HTML
• CSS
• JAVA SCRIPT
• Bootstrap

5.2.2 Back End Tools

• PHP
Database
• MYSQL

5.2.3 Documentation Tools

• MS office

• Snipping tools

• Draw.io

21
5.3 System Testing (Test Cases, Test Data, Test Result)

Testing

We have tested the following cases:

SN Test case Expected Output Result

1 Enter valid name and Software should Successful
password & click on display main
login button dashboard
2 Enter invalid name Software should not Successful
and password & display main
click on login button dashboard
3 Fill up the product Software should Successful
details form display insert
completely in proper success
order
4 If the product Software should Successful
details form is display insert failure
incompletely fill up
5 Fill up the customer Software should Successful
details form display insert
completely in proper success
order
6 If the customer Software should Successful
details form is display insert failure
incompletely fill up
7 Fill up the supplier Software should Successful
details form display insert
completely in proper success
order
8 If the supplier Software should Successful
details form is display insert failure

22
 incompletely fil up
9 If we click on logut Software should Successful
only we should get display login page
back to login page
10 On clicking list Software should Successful
table system should display details
show the list and
details

Chapter 6

Conclusion and Outcome

6.1 Conclusion

To conclude Inventory Management System is Simple Desktop based application

suitable for small mobile shop. We are trying to add every basic items Which are used for
the small mobile shop.Where we can update ,insert and delete items as per the
requirement. In this web app we also add report on monthly basis to know monthly the
sales and purchase details.

6.2 Outcome

Doing something for long time periods always gives good lesson.some of thing that we
learnt are listed as below:

1. Basically we learnt to work in team

2. Learnt about the inventory Management process
3. Learnt about php validation and Bootstrap.
4. Learnt to work in pressure and to be patient.
5. Learn to manage database under the Mysql PhpMyadmin.

23
 6.3 Recommendations

Mobile Inventory Management system is a good working software but can be

expand further due to time constraint team and proper tools.In future we can add
online payment and many more ,we can add different further facilities to enhance
the use of customer lately we have managed single admin user in future we can
add customer and supplier to used the system which can be turned into online
platform

References

Slack N, Chambers S, Harland C, Harrison A and Johnston R, Operations

Management, Pitman, (1995)

Hilton, Ronald W., Anagerial Accounting. McGraw-Hill,Inc (2005)

Galloway R, Principles of Operations Management, Routledge(2005)

Hill T, Production/Operations Management, Prentice Hall, (2010)

Saunders, Strategic Purchasing and Supply Management, Pitman,(2006)

24
 Appendix

Its shows the actual output of project and shows how the project look in real

Login page

25
Dashboard

26
Selling Details form

27
Product details table

28
Selling details table

Bill print format

29
Receipt

30
31