STOCK MANAGEMENT SYSTEM

MUHAMMAD FARID AFIF BIN MOHAMAT JOHARI

BACHELOR OF COMPUTER SCIENCE

(INTERNET COMPUTING) WITH HONORS
UNIVERSITI SULTAN ZAINAL ABIDIN

1
 DECLARATION

I hereby declare that this report is based on my original work except for quotations and

citations, which have been duly acknowledged. I also declare that it has not been previously or

concurrently submitted for any other degree at Universiti Sultan Zainal Abidin or other

institutions.

________________________________
Name : Muhd Farid Afif b Moht Johari

i
 CONFIRMATION

This is to confirm that this final year project entitled Stock Management System has

been prepared and submitted by Muhammad Farid Afif bin Mohamat Johari, with matric

number BTCL17047628 and has found satisfactory in terms of scope, quality, and presentation

as a part of the requirement for the Bachelor of Computer Science in Software Development in

University Of Sultan Zainal Abidin (UniSZA). The research conducted and the writing of this

report was under my supervison.

________________________________
Name : DR MUHAMMAD DANIAL BIN ZAKARIA

ii
 DEDICATION

I am using this opportunity to express my gratitude to everyone who has supported me

to completed my final year project entitled Stock Management System based on mobile

application. I am thankful for their aspiring guidance, invaluably constructive criticism and

friendly advice during this project work. I express my greatest gratitude to my supervisor, Dr

Muhammad Danial Bin Zakaria, who helps in guiding me throughout my journey in finishing

this project. Under his supervision with a lot of advices, I was able to complete this final year

project successfully. Then, a honorable respect I present to my family especially my parents for

their understanding with my study. I would also love to thanks all my friends and my course

mates for supporting me and gave me an inspiration to improve this project. I would like to

thank all the people for their help whether it was directly or indirectly to completing this project

iii
 ABSTRACT

Nowadays, most of organization are still manually record all the stock. This may

sometime lead to the situation where the worker forgot to update their stocks and will cause a

lot of problem and will cause inefficient restocking process. Another problem faced by current

system is, device is required for scanning purrpose to record the stocks. If the worker did not

bring the device, the stock could not be updated to the database. The proposed system of using

mobile device will solve the problem of the current system.

In this advance era, mobile devices are quite common and people are using all the time.

By developing an applicatio on mobile devices platform, maximize the utilization of mobile

devices and ease the workers’ job in stock updating process. The proposed system could also

remind by using notification function in this appication the person-in-charge of the remaining

stock if it need to be ordered or not. Lastly, the system will use barcode scanner from mobile

phone to automatically update the data in inventory database. The person-in-charge also can

monitor the movement of the stock as the stock will be updated online to the database. The

success of this product could eventually change the future usage of inventory system.

iv
 ABSTRAK

Pada masa ini, kebanyakan organisasi masih merekodkan semua stok secara manual. Ini

kadang-kadang boleh membawa kepada keadaan di mana pekerja lupa untuk mengemas kini

stok mereka dan akan menyebabkan banyak masalah dan akan menyebabkan proses pengisian

semula yang tidak cekap. Masalah lain yang dihadapi oleh sistem semasa adalah, peranti

diperlukan untuk mengimbas tujuan untuk merekod stok. Sekiranya pekerja tidak membawa

peranti, stok tidak dapat dikemas kini ke pangkalan data. Sistem penggunaan peranti mudah

alih yang dicadangkan akan menyelesaikan masalah sistem semasa.

Pada era maju ini, peranti mudah alih cukup biasa dan orang selalu menggunakannya.

Dengan mengembangkan aplikasi pada platform peranti mudah alih, memaksimumkan

penggunaan peranti mudah alih dan memudahkan pekerjaan pekerja dalam proses

pengemaskinian stok. Sistem yang dicadangkan juga dapat mengingatkan dengan

menggunakan fungsi pemberitahuan dalam aplikasi ini yang bertanggung jawab atas baki stok

jika perlu dipesan atau tidak. Terakhir, sistem akan menggunakan pengimbas kod bar dari

telefon bimbit untuk mengemas kini data secara automatik dalam pangkalan data inventori.

Orang yang bertanggungjawab juga dapat memantau pergerakan stok kerana stok akan dikemas

kini secara dalam talian ke pangkalan data. Kejayaan produk ini akhirnya dapat mengubah

penggunaan sistem inventori di masa hadapan.

v
 TABLE OF CONTENTS
DECLARATION .......................................................................................................................................... i
CONFIRMATION .......................................................................................................................................ii
ABSTRACT ........................................................................................................................................... iv
CHAPTER 1............................................................................................................................................... 1
INTRODUCTION ................................................................................................................................... 1
1.1) BACKGROUND PROJECT ..................................................................................................... 1
1.2) PROBLEM STATEMENT ....................................................................................................... 2
1.3) OBJECTIVE ........................................................................................................................... 3
1.4) SCOPE .................................................................................................................................. 3
1.5) EXPECTED OUTCOME ................................................................................................. 4
1.6) SUMMARY ........................................................................................................................ 4
CHAPTER 2 .......................................................................................................................................... 5
LITERATURE REVIEW ................................................................................................................. 5
2.1 INTRODUCTION ................................................................................................................... 5
2.2 STOCK MANAGEMENT SYSTEM DEFINITION ........................................................... 6
2.3 COMPARISON BETWEEN EXISTING SYSTEMS .......................................................... 7
2.3.1 STOCK CONTROLLER – INVENTORIES (2018) ..................................................... 7
2.3.2 STOCK COUNT(2018) .................................................................................................... 8
2.3.3 SMART INVENTORY SYSTEM ................................................................................... 9
2.3.4 COMPARISON TABLE OF THE EXISTING APPLICATION .............................. 10
2.4 SUMMARY............................................................................................................................ 11
CHAPTER 3 ........................................................................................................................................ 12
METHODOLOGY .......................................................................................................................... 12
3.1 INTRODUCTION ................................................................................................................. 12
3.2 DEFINITION OF AGILE SOFTWARE DEVELOPMENT METHODOLOGY .......... 14
3.3) METHOD IN AGILE METHODOLOGY ........................................................................ 15
3.3.1) PLANNING ................................................................................................................... 16
3.3.2) DESIGNING .................................................................................................................. 16
3.3.3) CODING ........................................................................................................................ 17
3.3.4) TESTING ....................................................................................................................... 17
3.3.5) LISTENING .................................................................................................................. 18
3.4) FRAMEWORK DESIGN.................................................................................................... 19
3.5) Context Diagram .................................................................................................................. 20
3.6) Data Flow Diagram Level 0 ................................................................................................. 21
3.6.1) Data Flow Diagram Level 1 (Process 1.0) ................................................................... 23

vi
 3.6.2) Data Flow Diagram Level 1 (Process 2.0) ................................................................... 24
3.6.3) Data Flow Diagram Level 1 (Process 3.0) ................................................................... 25
3.6.4) Data Flow Diagram Level 1 (Process 4.0) ................................................................... 26
3.6.5) Data Flow Diagram Level 1 (Process 5.0) ................................................................... 27
3.7) ENTITY RELATIONSHIP DIAGRAM ............................................................................ 28
3.7 SUMMARY............................................................................................................................ 29
CHAPTER 4............................................................................................................................................. 30
IMPLEMENTATION AND RESULT .......................................................................................... 30
4.0) INTRODUCTION ................................................................................................................ 30
4.1) IMPLEMENTATION OF STOCK MANAGEMENT SYSTEM.................................... 30
4.2) PROGRAMMING LANGUAGE ....................................................................................... 31
4.3) INTERFACE DESIGN ........................................................................................................ 32
4.3.1) Startup Slider Interface ................................................................................................ 32
4.3.2) Login and Register Interface........................................................................................ 33
4.3.3) Admin Homepage Interface ......................................................................................... 34
4.3.4) Staff Homepage Interface ............................................................................................. 35
4.3.5) Admin and Staff Add Stock Interface ......................................................................... 36
4.3.6) Admin and Staff View Stock List Interface ................................................................ 37
4.3.7) Admin and Staff Scan Barcode Interface ................................................................... 38
4.3.8) Admin and Staff Make and View Report Interface ................................................... 39
4.3.9) Admin Notification Function Interface ....................................................................... 40
4.3.10) Admin and Staff Logout Button Interface ................................................................ 41
4.4 TEST CASE ........................................................................................................................... 42
4.4.1) Register .......................................................................................................................... 42
4.4.2) Login............................................................................................................................... 43
4.4.3) Admin Add Stock List .................................................................................................. 43
4.4.4) Staff Add Stock List ...................................................................................................... 44
4.4.5) Admin View Stock ......................................................................................................... 44
4.4.6) Staff View Stock ............................................................................................................ 44
4.4.7) Admin Update Item....................................................................................................... 45
4.4.8) Staff Update Item .......................................................................................................... 45
4.4.9) Admin Delete Item ........................................................................................................ 46
4.4.10) Staff Delete Item .......................................................................................................... 46
4.4.11) Admin Make Report ................................................................................................... 47
4.4.12) Staff Make Report ....................................................................................................... 47
4.4.13) Admin View Report .................................................................................................... 48

vii
 4.4.14) Admin Send Notification ............................................................................................ 48
4.4.15) Admin and Staff Logout ............................................................................................. 49
4.5) SUMMARY .......................................................................................................................... 49
CHAPTER 5 ........................................................................................................................................ 50
CONCLUSION ................................................................................................................................ 50
5.0) INTRODUCTION ................................................................................................................ 50
5.1) DISCUSSION ....................................................................................................................... 50
5.2) LIMITATIONS / CONSTRAINT OF WORK .................................................................. 51
5.3 PROJECT CONSTRAINT AND LIMITATIONS ............................................................. 51
5.4 FUTURE WORK .................................................................................................................. 52
APPENDIX .......................................................................................................................................... 53
GANTT CHART ............................................................................................................................. 53
I. GANTT CHART FYP 1...................................................................................................... 53
II. GANTT CHART FYP 2 .................................................................................................. 53
REFERENCES .................................................................................................................................... 54

viii
 CHAPTER 1
INTRODUCTION

1.1) BACKGROUND PROJECT

Stock management system is a mobile application system that handles the

product management for company equipment or any items to stored. The main aim of

the project is to develop Stock Management System Model software in which all the

information regarding the stock of the organization will be presented . Nowadays, many

companies use the system to avoid overstock, miscount and outages. It is a system for

organizing a better inventory data than that was used before which is generally stored

in manual form which is in books or spreadsheets. This application has admin

component to manage the inventory and maintenance of the inventory system. The

application has general organization profile, stock details, purchase details and the

remaining stock that are presented in the organization. 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 updated any time when required as per the transaction or the sales is

returned in case. Here the login page is created to protect the management of the stock

of organization in order to prevent it from the threats and misuse of the inventory. This

management system can be used by staffs that can enables the user to view the product

and item information that have been key-in. Staff or user can update any other

information directly by using online system just like any other online systems. The

added valued contain in this system is Product Calculation Method (PCM) which it can

be used by staffs to key-in any item that company bought or item in store to make sure

the actual amount of that item or product. This method will make the calculation before

1
 the item stored and give a recommendation about the place that item should be stored.

This method can help staffs to move the item easily when they know the actual places

to keep the item.

1.2) PROBLEM STATEMENT

The main problem that occured in several company or retailer is a system to

calculate the amount of stocks stored or needed. Based on my survey, I have found that

there are company that still using paper based or filing system to save their information

or details about their stocks. Heavily manual work will involved in managing and

maintaining data which is time-consuming if the administrators or manager want to trace

the product status, product information and etc. This also may lead to a situation where

the workers forgot to update the inventory to the database or worst may lead to miscount

when using manual system. RFID scanner and external barcode scanner require a device

which is costly and limited to do a single task which is scan an image where this features

can be done by using an mobile device. This application will lower the extra expenses

of buying this scanner because we can replace it with mobile device and we can carry it

anywhere and anytime.

2
1.3) OBJECTIVE

The objective of the proposal system are :

• To design and develop a user friendly system which handles the information of

items or products and calculated it to manage the information system

• To help staffs in order to find location and the quantity of stocks that have been

stored

• To develop an application that deals with the day-to-day needs of any production

organization

1.4) SCOPE

Stock Management System (SMS) is targeted to the small or medium organization

which have provided many store or warehouses for managing various stock data. This

system focused on calculate the amount of stock in and out for a company. The scope

for user for this system are administrator and staffs.

• Contractors/Staffs

- Login, manage update and view stock in store, manage reordering process

and write reports.

• Admin/Manager

- Have full privileges for adding, editing, viewing and deleting users and stock

from the system.

• System

- Developed on Android Platform

- Targeted for small and medium company for fully utilized the functionality

3
1.5) EXPECTED OUTCOME

This application is used to show the stock remaining and details about the used item and

purchased item. It gives the details about the stock on daily based and weekly based

• Login page: As application starts the login page appears. Admin login is

determined by the username and password that has all the authority to add,

update and delete the stock of the organization as per the requirement

• Stock details: It show the details about remaining stock in inventory. It also show

the details about the used stock

• Purchase details: It shows the details about the purchase made by the

organization along with the price and dates

• Automated calculation the quantity of items that will and have been stored

1.6) SUMMARY

In chapter 1, the purpose of the project of the system is identified to overcome

the problems that occur in the current system. Also, the function and limit of the project

are stated. Besides, the brief about every chapter was stated in this chapter

4
 CHAPTER 2

LITERATURE REVIEW

2.1 INTRODUCTION

Literature review is the formal methods that can be used to review the critical points of

current knowledge including findings as well as theoretical and methodological particular topic

for supporting issues. 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 andsales in the

organization. Before developing this application we came across with several Inventory

Management System existing in the market, which helps to give the knowledge for the

development of this project. These application software are 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 analyzing 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 features that

help the small organization to adapt with this apllication.

5
2.2 STOCK MANAGEMENT SYSTEM DEFINITION

An inventory management system is the combination of technology (hardware and

software) and processes and procedures that oversee the monitoring and maintenance of stocked

products, whether those products are company assets, raw materials and supplies, or finished

products ready to be sent to vendors or end consumers. Additionally, the system will help

managers on making right decision for recording process where only the recently used products

and popular products will be ordered. The contractors also could make a request on any

additional products that they needed. The objective of an stock management system is to make

inventory flows smoothly and helps in making decision that will minimize the total cost of

inventory which is distinctly different from minimizing inventory.

6
2.3 COMPARISON BETWEEN EXISTING SYSTEMS

2.3.1 STOCK CONTROLLER – INVENTORIES (2018)

This is a mobile based application that can be consider fulfill the requirement of

the stock management system. However, this application is not quite intelligence

application because it does not provide QR or Bacrcode scanner functional in the system

but it got some attractive features in the application such as notification if the quantity

of stock is low and user can insert image in the database to organise the group of stock.

Figure 2.1 : Figure show the interface of stock controller application

7
2.3.2 STOCK COUNT(2018)

This is also an example of the stock management system based mobile

application. This application is quite interesting because it come in two language which

are English and Bahasa Indonesia. It contain Bahasa Indonesia language because the

developer of this application was from Indonesia. The application is intelligent because

it provide Barcode scanner function but the interface of the application is very simple

and bored. It also provide database for local if the emergency case happen such as loss

internet connection or no internet connection, the user still can access it offline.

Figure 2.2 : Figure show the interface of stock count

8
2.3.3 SMART INVENTORY SYSTEM

The application is not smart as the name given because it not provide the

notification function in the application even though it contain QR and Barcode scanner

to add the stock quantity. This application have an attractive interface, so the user can

use the application easier than the other application.

Figure 2.3 : Figure show the interface of smart inventory system

9
2.3.4 COMPARISON TABLE OF THE EXISTING APPLICATION

From the research, there are three applications that related to my application

Stock Management System. There are also several function and features from these

applications that will be referred and uses in my application.

Figure 2.4 : Figure show comparison table of three existing applications

10
2.4 SUMMARY

In summary, there are many previous research carried upon this system that I can

referred and make my system more advance than existing system. There is also system that

identical in this system where it can notify user of any low-stock products in store. A system

that can be running on any platform but did not have dedicated Android application where it is

hard to be use on Android environment.

Lastly, there are many researchers made about this stock management system that has

been conducted around the globe which offers more than from our country technology. So, I

will build the system that has more benefit to company where it could help to improve the

overall organization system.

11
 CHAPTER 3

METHODOLOGY

3.1 INTRODUCTION

This chapter would mainly discuss about the methodology that was going to be used

during the system development. A system development methodology in software engineering

is the main guidance for constructing, planning and also controlling the process of developing

an information system. Common methodologies used were waterfall model, prototyping, spiral

development, extreme programming and also some other various types of methodologies. In

this system development, agile software development model methodology was used as the

guidance. Rather than traditional software development like the Waterfall method, where we

might spend several months or years on a project without showing it to the user, Agile is all

about moving fast, releasing often, and reacting to the real needs of your users.

12
13
3.2 DEFINITION OF AGILE SOFTWARE DEVELOPMENT METHODOLOGY

Agile Methodology is a people-focused, results-focused approach to software

development that respects our rapidly changing world. It’s centered around adaptive planning,

self-organization, and short delivery times. It’s flexible, fast, and aims for continuous

improvements in quality. It is used to minimize risk by developing software in short time boxes

which are called iterations that generally last for one week to one month. Agile methodology is

also a practice that promotes continuous iteration of development and testing throughout the

software development lifecycle of the project. There are various methods present in agile testing

which are scrum, extreme programming(XP), FDD and others example in figure 3.1.

Figure 3.1

14
3.3) METHOD IN AGILE METHODOLOGY

In this project i have decided to use extreme programming(XP) as a method for this

agile methodology as my reference. I choose this method because extreme programming is a

very helpful technique when there is constantly changing demands or requirements from the

customers or when they are not sure about the functionality of the system. It advocates frequent

"releases" of the product in short development cycles, which inherently improves the

productivity of the system and also introduces a checkpoint where any customer requirements

can be easily implemented. The XP develops software keeping customer in the target. XP is

centered on frequent releases and short development cycles. It uses code review, pair

programming, unit testing, and frequent communication with the customer.

This is the example of the flows of extreme programming (XP) method in agile

methodology.

15
3.3.1) PLANNING

The Extreme Programming software development process starts with planning.

Before I start to develop this project, I have found and meet my target customer and user

and have examine their stories and problem. This application is develop for Common

Hardware Sdn. Bhd which is a company that store their stock and item in a warehouse.

This application target is to help the manager and workers to allocate the stock or the

item needed. I have converts user stories into iterations that cover a small part of the

functionality or features required and all iterations consist of four basic phases in its life

cycle: designing, coding, testing, and listening.

3.3.2) DESIGNING

An iteration of XP programming starts with designing. By using systems

metaphor or standards on names, class names and methods, and agreeing on uniform

styles and formats to ensure compatibility on designing the system. Class

Responsibilities and Collaboration (CRC) Cards software was used in this phase. This

software allow for a departure from the traditional procedural mindset and make

possible object oriented technology. Such cards allow all user and developer of the

project to contribute ideas, and collate the best ideas into the design.

16
3.3.3) CODING

Coding constitutes the most important phase in the Extreme Programming life

cycle. XP programming gives priority to the actual coding over all other tasks such as

documentation to ensure that the customer receives something substantial in value at the

end of the day. I have developing the code based on the agreed metaphors and standards,

and adopting a policy of collective code ownership. Strict adherence to 40-hour

workweeks with no overtime. This ensures the developers work in the peak of mental

and physical faculties. Frequent integration of the code to the dedicated repository, with

only one pair integrating at a time to prevent conflicts, and optimization at the end.

3.3.4) TESTING

Extreme program integrates testing with the development phase rather than at

the end of the development phase. All codes have unit tests to eliminate bugs, and the

code passes all such unit tests before release.

Another key test is customer acceptance tests, based on the customer specifications.

Acceptance test run at the completion of the coding, and the developers provide the

customer with the results of the acceptance tests along with demonstrations.

17
3.3.5) LISTENING

The basis of extreme programming is a continuous mechanism of customer

involvement through feedback during the development phase. Apart from the customer,

the developer also receives feedback from the project manager.

The basis of feedback is the customer acceptance tests. Each feedback of the

customer that specifies revised requirement becomes the basis of a new design, and the

process of design-coding-tests-listening repeats itself. If the customer remains satisfied

with the test results the iteration ends there, and the design for the new iteration starts,

which again follows the design-coding-testing-listening cycle.

18
 3.4) FRAMEWORK DESIGN

Image Processing
Raw Data
Visualisation

Processing

Data And Information Preprocessing

Add new product

GRAPHICAL USER INTERFACE

Receive notification Data

Raw Data Processing

Data
Request new product

Data Filtering
hypertext

Raw Data Processing

Receive Feedback

Data

Database
Android Based Expert System

Figure 3.4: Framework Design

Figure 3.4 shows the overall framework design system which will work based on the

following and explains each function works and what data will be retrieve or gain. Every flow

is connected to each other where none of the data will be lost.

19
3.5) Context Diagram

Login

Add New User

Admin/Manager
Update Stock List

Add New Stock

View Stock Report

View Stock Report
Notification for Low Stock Stock Management System
View User

Update Stock Count

Request New Stock

Contractor
Scan for Stock Out

Figure 3.5 : Context Diagram

20
3.6) Data Flow Diagram Level 0

1.0 User Detail

STOCK

User Detail
MANAGE USER
Stock Detail
Stock Detail

Stock Detail ADMIN / MANAGER USER

3.0

User Detail
STOCK 2.0

MANAGE
User Detail
PROFILE
Order Detail

Stock Detail Reports

TRANSACTION
Stock Detail

4.0 5.0
Order Detail
STOCK REPORT
REORDERING
Order Detail

Reports
Order Detail

Reports
Order Detail

CONTRACTOR

STOCK REORDER REPORTS

Reports

User Detail

FIGURE 3.6 : DFD LEVEL 0

21
 Figure 3.6 shows Data Flow Diagram of this stock management system. Only

Admin/Manager have the privileges to manage other users of this system. The process of adding

and deleting users will be controlled by Admin/Manager. Admin also can gain access to the

system by login into the system and manage new stocks, reports and stock reordering process.

Contractors should also login to this system to manage their profile, manage reports and request

new stock orders from Manager/Admin. All the transaction of stock in and out will be saved in

Transaction database.

22
3.6.1) Data Flow Diagram Level 1 (Process 1.0)

1.1 User Detail

ADD USER
User Detail

1.2
Admin/Manager User Detail User Detail
DELETE USER USER
User Detail

1.3
User Detail
VIEW USER

Figure 3.7 : DFD Level 1 (Process 1.0)

Figure 3.7 shows a process of managing users by Admin. Admin can add, delete and

view detail of users in the system.

23
3.6.2) Data Flow Diagram Level 1 (Process 2.0)

User Detail
User Detail 2.1
Admin/Manager
UPDATE
USERNAME User Detail
User Detail

2.2 User Detail

CONTRACTOR UPDATE USER USER

User Detail PROFILE User Detail

Figure 3.8 : DFD Level 1 (Process 2.0)

Figure 3.8 shows a process of managing user profile by Admin and Contractor. Admin

can update the username and user profile but Contractor only can update their profile.

24
3.6.3) Data Flow Diagram Level 1 (Process 3.0)

Stock Detail Stock Detail

3.1
ADMIN/MANAGER Stock Detail
STOCK IN

Stock Detail

3.2 Stock Detail

EDIT STOCK Stock Detail

Stock Detail

STOCK TRANSACTION

3.3
Stock Detail
DELETE STOCK

Stock Detail
Stock Detail
3.4

CONTRACTOR STOCK OUT

Stock Detail Stock Detail

Figure 3.9 : DFD Level 1 (Process 3.0)

25
 Figure 3.9 shows a process of managing stock by Admin and Contractor. Admin can

add (Stock in), edit, delete and Stock out the stock from system but the Contractor only can

make Stock out from the system. All the transaction of Stock in and Stock out will be saved in

Transaction Database.

3.6.4) Data Flow Diagram Level 1 (Process 4.0)

4.1 Order Detail

ADD NEW STOCK

ORDER
Order Detail

4.2
Contractor Order Detail Order Detail STOCK
DELETE ORDER REORDER
Order Detail

Order Detail
Admin/Manager

4.3
Order Detail
VIEW ORDER

Order Detail

Figure 3.10 : DFD Level 1 (Process 4.0)

26
 Figure 3.10 shows a process of managing reordering process by Manager and

Contractor. Contractor have the priviledge to add, delete or view orders from the system and

Manager can do the same work except for add new stock order.

3.6.5) Data Flow Diagram Level 1 (Process 5.0)

Report Detail Report Detail

5.1

CONTRACTOR
ADD REPORT
Report Detail

5.2

DELETE REPORT Report Detail

Report Detail

REPORTS
Report Detail

5.3

Report Detail
EDIT REPORT

Report Detail
5.4

ADMIN/MANAGER VIEW REPORT

Report Detail Report Detail

Figure 3.11 : DFD Level 1 (Process 5.0)

27
 Figure 3.11 shows a process of managing reports by Manager and Contractor.
Contractor can add, delete, edit and view detail reports in the system while Manager can do the
same except for add and edit function.
3.7) ENTITY RELATIONSHIP DIAGRAM

manager Stock_list
Manage order_id VARCHAR(10)
A_id VARCHAR(10)
order_quantity INT(10)
A_name VARCHAR(10)
stock_id VARCHAR(30)
A_email VARCHAR(30)
user_id VARCHAR(10)

Manage View

contractor Update

c_id VARCHAR(10) User_detail

c_name VARCHAR(10)

c_email VARCHAR(30) user_id VARCHAR(10)

View user_password TEXT

A_level INT(1)

Make
stock

stock_id VARCHAR(10)
reports
stock_name VARCHAR(10)
View Report_id VARCHAR(10)
stock_qty VARCHAR(30)
Report_desc VARCHAR(90)

c_id VARCHAR(10)

Figure 3.12 : ENTITY RELATIONSHIP DIAGRAM

28
3.7 SUMMARY

The most important thing is to make sure the system development process run smooth is

methodology. There are many different software development methodologies that is good to

use to develop a system. However, choosing the right methodology is important because it will

affect the work flow of the system development process. The project can be done in time if the

right methodology is used to develop a system. Finally, all phase is the methodology used are

explained straightly so that it can be understood easily.

In a system modelling and design, the details about the system data flow and entities

involved in the system is explained and all the module also being described completely from

one module to another. The Data Flow Diagram (DFD) design give an insight about the flow

of the system and the explanation about each flow easy to understand while the Entity

Relationship Diagram (ERD) and database design give a clear understanding on database of the

system and relation between each table.

29
 CHAPTER 4

IMPLEMENTATION AND RESULT

4.0) INTRODUCTION

Implementation and result are executed to ensure the system fulfil the user requirements

and achieved the main objectives of the system. Implementation is conducted to ensure that the

developed system is able to achieve the desired result. This Stock Management System is the

right path and fulfil its specifications. The result shown that when the admin and the staff can

add, retrieve, update and delete stock list in the database and admin can send notification to

staff.

4.1) IMPLEMENTATION OF STOCK MANAGEMENT SYSTEM

There are several programming language been used to develop the Stock Management

System. PHP was used for the server side programming language. While, MySQL was used as

database management and the version of XAMPP Control Panel v3.2.1 with 3306 port(s) and

14216 PID(s). Notepad++ is used to write the code. Programming language that have been used

in this system are JAVA, HTML, CSS and PHP. Validation is important to make sure that user

do not give wrong input. For example, email and password is compulsory when register new

user. User also will get an error message when the email that want to register was taken before.

If admin forget to input any required section in the form, the system will remind admin to fill

in the blank.

30
4.2) PROGRAMMING LANGUAGE

• JAVA AND HTML

➢ Used to create form and column and other process

• PHP

➢ Used to make a connection between database and application

• CSS

➢ Used to design interface colour, size and other

31
4.3) INTERFACE DESIGN

4.3.1) Startup Slider Interface

Figure 4.1

Figure 4.1 show the startup slider interface. When user first time install this

application, this interface will appear and there is skip and got it button which are can

be click to go to next interface. After user click the button, this slider interface will not

appear again until the user delete the application and install it back.

32
4.3.2) Login and Register Interface

Figure 4.2

Figure 4.2 show the login and register interface. There are form for user to insert

the detail when login and register into the application.

33
4.3.3) Admin Homepage Interface

Figure 4.3

Figure 4.3 show the admin homepage interface. In this interface there are

navigation bar at the side of page to allow admin to perform add, delete or view and

update stock of the item. There are also notification and add report function.

34
4.3.4) Staff Homepage Interface

Figure 4.3

Figure 4.3 show the admin homepage interface. In this interface there are

navigation bar at the side of page to allow admin to perform add, delete or view and

update stock of the item. There are add report function but no notification function in

the user activity.

35
4.3.5) Admin and Staff Add Stock Interface

Figure 4.4

Figure 4.4 show the interface of admin and user interface which allow user and

admin to make operation to add stock manually by insert name or barcode id, stock

category and others.

36
4.3.6) Admin and Staff View Stock List Interface

Figure 4.5

Figure 4.5 show the view stock list for admin and user review the list of stock

that have been added.

37
4.3.7) Admin and Staff Scan Barcode Interface

Figure 4.6

Figure 4.6 shows the scan barcode or Qr Code interface which is allow user and

admin make a operation of add stock by using barcode and qr code scanner.

38
4.3.8) Admin and Staff Make and View Report Interface

Figure 4.7

Figure 4.7 is an interface of make and view report for user and admin. This activity

allows user and admin create report and view the report that made by others.

39
4.3.9) Admin Notification Function Interface

Figure 4.8

Figure 4.8 shows the notification function interface for admin to send a

notification to another admin or send notification for all staff.

40
4.3.10) Admin and Staff Logout Button Interface

Figure 4.9
Figure 4.9 shows the interface of logout button function for admin and user

interface that allows user and admin to logout from the application.

41
4.4 TEST CASE

A test case is a set pf condition or variable which a tester used to determine whether

a system satisfy its requirement or not. The process of developing test cases can also

help to detect any problems related to the requirement of the system itself. Table below

show the list of cases for several processes in the Stock Management System.

4.4.1) Register

Step Procedure Expected Result Pass/Fail

1. Insert name, email and Pass

password

Name: Farid

Email:Farid@gmail.com

Password:1234

2. Click “Register” Button Register Successful Pass

Display Admin/Staff

Dashboard and

Homepage

42
4.4.2) Login

Step Procedure Expected Result Pass/Fail

1. Insert into email and Pass

password

Email:Farid@gmail.com

Password:1234

2. Click “Login” Button Login Successful Pass

Display Admin/Staff

Dashboard and

Homepage

4.4.3) Admin Add Stock List

Step Procedure Expected Result Pass/Fail

1. Go to Add Item page Pass

2. Fill the required Pass

information

3 Click “Add Item” Add Successfull : Go to Pass

button View Item page

43
4.4.4) Staff Add Stock List

Step Procedure Expected Result Pass/Fail

1. Go to Add Item page Pass

2. Fill the required Pass

information

3 Click “Add Item” Add Successfull : Go to Pass

button View Item page

4.4.5) Admin View Stock

Step Procedure Expected Result Pass/Fail

1. Go to View Item page Pass

2. Retrieve all the data list View all the stock list Pass

from stock database

4.4.6) Staff View Stock

Step Procedure Expected Result Pass/Fail

1. Go to View Item page Pass

2. Retrieve all the data list View all the stock list Pass

from stock database

44
4.4.7) Admin Update Item

Step Procedure Expected Result Pass/Fail

1. Go to View Item page Pass

2. Retrieve all the data list Pass

from stock database and

perform update

operation

3 Click “update” button Item update successfull: Pass

Refresh item list in

View Item page

4.4.8) Staff Update Item

Step Procedure Expected Result Pass/Fail

1. Go to View Item page Pass

2. Retrieve all the data list Pass

from stock database and

perform update

operation

3 Click “update” button Item update successfull: Pass

Refresh item list in

View Item page

45
4.4.9) Admin Delete Item

Step Procedure Expected Result Pass/Fail

1. Go to View Item page Pass

2. Retrieve all the data list Pass

from stock database and

perform delete

operation

3 Click “delete” button Item deleted: Refresh Pass

item list in View Item

page

4.4.10) Staff Delete Item

Step Procedure Expected Result Pass/Fail

1. Go to View Item page Pass

2. Retrieve all the data list Pass

from stock database and

perform delete

operation

3 Click “delete” button Item deleted: Refresh Pass

item list in View Item

page

46
4.4.11) Admin Make Report

Step Procedure Expected Result Pass/Fail

1. Go to Report page Pass

2. Insert report contain Pass

into form

3 Click “Add Report” Report added Pass

button successfull: Go to page

View Report

4.4.12) Staff Make Report

Step Procedure Expected Result Pass/Fail

1. Go to Report page Pass

2. Insert report contain Pass

into form

3 Click “Add Report” Report added Pass

button successfull: Go to page

View Report

47
4.4.13) Admin View Report

Step Procedure Expected Result Pass/Fail

1. Go to View Report Pass

page

2. View all the report that Admin can view all Pass

has been submitted report that has been

submitted by staff

4.4.14) Admin Send Notification

Step Procedure Expected Result Pass/Fail

1. Go to Notification page Pass

2. Insert message contain Pass

into notification form

3 Click “Send Notification message Pass

Notification” button sent to staff and staff

receive the notification

48
 4.4.15) Admin and Staff Logout

Step Procedure Expected Result Pass/Fail

1. Go to Homepage Pass

2. Pass

3 Click “Logout” button Logout Success: Go to Pass

Login page

4.5) SUMMARY

In this chapter, we have to make sure the system is ready and complete to be used

by user. All of the activity that was created in the application must be tested and make

sure each of the activity can be used completely without any error. The design of

interface shown in this chapter is for the user to have an overview about the application

before installing and using it.

When all of the operation succeed in this Stock Management System, this

application will be distributed to all staff and admin so they can start using this

application

49
 CHAPTER 5

CONCLUSION

5.0) INTRODUCTION

This chapter concludes all the work done in this project proposal which are expectations,

achievements and recommendations are in order to improve the project in future especially for

the development phase. The strength, weaknesses and suggestions for the improvement are also

being stated in this chapter.

5.1) DISCUSSION

Stock Management System is an online system in which the staff can easily add the item

into the system and admin can view the item. This system is focused on providing utilities in

order to ease the admin to send the item to any user instead of prepare the document, print and

need to prepare storage like file in manual ways.

This system is focused on providing a database for easy retrieval of stock list. For example,

when staff is adding the item then admin in charge can easily view the item. The system also

provide a reliable system where items are always backed-up and never allow unauthorized

accessed. Email and password are needed in order for login to access the user account. KPP

also can approve the file anytime and anywhere without hardcopy.

In this system, the system will be able to view in mobile view without any problem with

the interface design.

50
5.2) LIMITATIONS / CONSTRAINT OF WORK

There are some limitations when proposing this project. First is the difficulty on how to

understand the adding process for item page since some of the form is specific to user. For

example, item location, not all in each of warehouse there will be department for item location.

The other difficulty is to understand the concept localhost because this database is local so, the

connection for all devices must be same and connected to the local connection.

5.3 PROJECT CONSTRAINT AND LIMITATIONS

There are several problems and limitations that occurred throughout the development of

the project. The problems and limitations in conducting this system are as follow:

The relationship between admin and staff in managing the system is not obviously can be

shown such as when admin want to send notification to staff, the notification message

sometimes not popup on staff mobile phone.

It is quite complicate to assign selected admin to the selected staff.

51
5.4 FUTURE WORK

There are some suggestions that can be made to upgrade the system in order to make it

more efficient and user friendly. Some suggestion that need to be considered are:

Implement more algorithm such as rule-based algorithm and heuristic algorithm to ensure

the system is well developed.

Generate the system just like file-based system such as Google Drive. So, admin can keep

any private data for their own view and set allow sharing to be viewed by staff.

Enhance the interface of the system so that it can suit to the environment of a data sharing

system for admin and staff

52
 APPENDIX

GANTT CHART

I. GANTT CHART FYP 1

II. GANTT CHART FYP 2

53
 REFERENCES

1) Lee, J. K., Lee, I. S., & Kwon, Y. J. (2011). Scan & learn! Use of quick response
codes & smartphones in a biology field study. The American Biology Teacher, 73(8),
485-492.

2) Chapin, Christopher, Henry Eisenson, and Eric Eisenson. "Peer-to-peer inventory

management system." U.S. Patent Application 11/345,842, filed August 31, 2006

3) Blanchard, Jean-Louis, et al. "System and method for stock options market
management." U.S. Patent No. 7,181,423. 20 Feb. 2007

4) Xie, Y., & WANG, H. W. (2007). Research on Automated Stock Management System
Based on Internet of Goods and its Application [J]. Logistics Technology, 4, 90-93.

5) Yasarcan, H., & Barlas, Y. (2005). A generalized stock control formulation for stock
management problems involving composite delays and secondary stocks. System
Dynamics Review: The Journal of the System Dynamics Society, 21(1), 33-68.

6) Bontis, N., Crossan, M. M., & Hulland, J. (2002). Managing an organizational

learning system by aligning stocks and flows. Journal of management studies, 39(4),
437-469.

7) Blanchard, Jean-Louis, et al. "System and method for stock options market
management." U.S. Patent No. 7,181,423. 20 Feb. 2007.

8) Kaur, Mandeep, et al. "RFID technology principles, advantages, limitations & its
applications." International Journal of Computer and Electrical Engineering 3.1
(2011): 151.

9) Kimball, James F., and Stephen B. Leonard. "Inventory management system using
RFID." U.S. Patent No. 7,680,691. 16 Mar. 2010.

54