TITLE: STOCK MANAGEMENT SYSTEM

CANDIDATE NAME: LOMEJU EKAALE ABEDNEGO

INDEX NUMBER: 5342140026

CENTRE NAME: AFRICAN INSTITUTE OF RESEARCH AND

DEVELOPMENT STUDIES

CENTRE CODE: 534214

COURSE NAME: DIPLOMA IN INFORMATION COMMUNICATION

TECHNOLOGY

COURSE CODE: 2920/308

PRESENTED TO: THE KENYA NATIONAL EXAMINATION COUNCIL FOR

PARTIAL FULFILLMENT FOR A WARD OF DIPLOMA IN
INFORMATION COMMUNICATION TECHNOLOGY

EXAM SERIES: JULY 2023

SUPERVISOR: MADAM KIMAIWA

 DECLARATION

I hereby declare that this project 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 diploma in any institution.

Name: ……………………………….

Signature…………………………….. Date…………………………………….

I certify that the student worked under my supervision to complete the project.

Signature …………………………… Date …………………………………….

ii
 DEDICATION

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

complete my final project entitled Stock Management System. 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 who helps in guiding me throughout my journey

to finishing this project. Under his supervision with a lot of advice, I was able to complete this

project successfully. I also thank my family especially my parents for their giving me a privilege

to study. I would also love to thank all my friends and my course mates for supporting me and

giving me an aspiration to improve this project. I would like to thank all the people for their help

whether it was directly or indirect to complete this project.

iii
 ACKNOWLEDGEMENT

I want to thank God in the strongest possible terms for everything. I wish to express my

gratitude to my parents and guardians for their up to this point assistant. I would want to use

this opportunity to express my gratitude to my project supervisor and serve as the light in the

darkness the entire time.

iv
 ABSTRACT

Currently, most of the organizations are still using the manual system which is natively recorded.

This may sometimes lead to the situation where the worker forgot to update the stock and will

cause time wastage as they have to wait for stock order when it is in need. If the user does not

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

management system will help in the recording of stock so that the clients cannot miss the stock.

The system could also remind the person in charge of the remaining stock whether it needed to

be ordered or not. However, the system will use a barcode scanner to automatically update the

data in the stock database. The person in charge also can monitor the movement of the stock as

the stock will be updated online in the database. This system can be used to store the details of

the stock, stock maintenance, update the stock based on the sales details, and generate sales and

stock report daily or weekly based. In this system, we are solving different problems affecting

direct sales management and purchase management. Stock Management System is important to

ensure quality control in businesses that handle transactions revolving around consumer goods.

One more problem faced by the current system is, the device used to take the stock have to be

brought anywhere and anytime by the worker. Without proper stock control, a large retail store

may run out of stock on an important item. A good stock management system will alert the

wholesaler when it is time to record. Stock Management System is also an important means of

automatically tracking a large shipment. An automated Stock Management System helps to

minimize errors while recording the stock.

v
 Table of Contents

DECLARATION..................................................................................................................................ii

DEDICATION.....................................................................................................................................iii

ACKNOWLEDGEMENT..................................................................................................................iv

ABSTRACT...........................................................................................................................................v

CHAPTER ONE: INTRODUCTION.................................................................................................1

1.1 Background of the Study.............................................................................................................1

1.2 Current System...............................................................................................................................2

1.3 Problem statement.......................................................................................................................2

1.4 Objective..........................................................................................................................................3

1.5 Scope of the study........................................................................................................................3

1.6 Future of the project....................................................................................................................3

CHAPTER TWO: REVIEW OF THE LITERATURE....................................................................5

2.1 Introduction.....................................................................................................................................5

2.2 Stock management system definition............................................................................................5

2.3 Comparison between existing system and stock controller inventories (2023)......................6

2.4 Stock count (2023)...........................................................................................................................6

vi
2.5 Smart stock system.........................................................................................................................6

2.6 Summary.........................................................................................................................................7

CHAPTER THREE: RESEARCH METHODOLOGY...................................................................8

3.1 Introduction.....................................................................................................................................8

3.2 Development methodologies..........................................................................................................8

3.2.1 Waterfall methodology................................................................................................................8

3.3 Planning...........................................................................................................................................9

3.4 Analyzing.........................................................................................................................................9

3.5 Design.............................................................................................................................................10

3.6 Implementation.............................................................................................................................10

3.7 Testing............................................................................................................................................10

3.8 Maintenance..................................................................................................................................10

3.9 Methods of data collections..........................................................................................................11

3.10 Data analysis................................................................................................................................11

CHAPTER FOUR: PRESENTATION DESIGN AND IMPLEMENTATION...........................13

4.1 Determining the requirements of the system.............................................................................13

4.2 User requirements.....................................................................................................................13

vii
4.3 Functional requirements..............................................................................................................13

4.4 Non-functional requirements.......................................................................................................14

4.5 Software Requirements................................................................................................................14

4.6 Hardware Requirements..............................................................................................................14

4.7 Proposed System design...............................................................................................................14

4.8 System Modeling...........................................................................................................................15

4.8.1 Context Diagram........................................................................................................................15

4.9 Database Design............................................................................................................................19

4.11 System testing.............................................................................................................................35

4.12 Purpose of Testing......................................................................................................................35

4.13 Conclusion...................................................................................................................................36

CHAPTER FIVE: CODING IMPLEMENTATION......................................................................37

5.0 Application Code Structure.........................................................................................................37

5.1 Sample code for login page..........................................................................................................37

5.2 Backup Data code.........................................................................................................................41

CHAPTER SIX: CONCLUSION, RECOMMENDATION, FUTURE WORKS, AND

LESSON LEARNT....................................................................................................................44

viii
6.0 Project Limitation.........................................................................................................................44

6.1 Conclusion.....................................................................................................................................44

6.2 Recommendation..........................................................................................................................45

6.3 Lesson Learnt................................................................................................................................45

6.4 Future Enhancements...............................................................................................................46

REFERENCES...................................................................................................................................47

APPENDICES.....................................................................................................................................49

Appendix one: Project Budget...........................................................................................................49

ix
 CHAPTER ONE: INTRODUCTION
1.1 Background of the Study

The stock management system is a mobile application system that handles the product

management for company equipment or any items store. The main aim of the project is to

develop a 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, miscounts and outages. It is a system for organizing better stock data than that was

used before which is generally stored in manual form books or spreadsheets. This application has

an admin component to manage the stock and maintenance of the stock system. The application

has a general organization profile, stock details, purchase details, and the remaining stock that is

presented in the organization. This application also provides the remaining balance of the stock

as well as the details of the balance of the transaction. Each new stock is created and entitled

with the name and the entry date of that stock and it can also be updated any time when required

as per the transaction or the sales are returned in case. Here the login page is created to protect

the management of the stock of the organization to prevent it from the threads and misuse the

stock. This management system can be used by staff that can enable the user to view the product

and item information that has been key-in. Staff or users can update any other information

directly by using an online system just like any other online system. The added value contained

in this system is the Product Calculation Method (PCM) which can be used by staff to key in any

item that the company bought or item in the store to make sure the actual 2 amount of that item

or product. This method will calculate the item is stored and give a recommendation about the

place the item should be stored. This method can help staff to move the item easily when they

know the actual places to keep the item.

1
1.2 Current System

During the data collection method, the researchers found out the following; The sales manager

for the supermarket records information about the products and stock on paper, later on using

the Microsoft Excel sheet program to record the whole data from the paperwork, he uses the

program to edit the information before sending the reports to the top level management. For the

paper file systems, they are kept in the file cabinets for future use. For customers placing orders,

they were recorded on paper and also stored using the paper file systems. On the matter of

payment from customers, a receipt containing the details of orders the customer was issued to

them. Information about the customers, and suppliers were also captured using the file-based

system, and processed in the Microsoft Excel sheet program.

1.3 Problem statement

The main problem that occurs in several company or retailer is a system to calculate the number

of stocks stored or needed. Based on my survey, I have found that there are a company that still

use paper-based or filing systems to save their information or details about their stocks. Heavily

manual work will be involved in managing and maintaining data which is time-consuming if the

administrators or manager want to trace the product status, product information, etc. This also

may lead to a situation where the workers forgot to update the stock in the database or worst may

lead to miscounts when using a manual system. Barcode scanner is also a device which is costly

and only can do a single task which is to scan an image where these features can be done by

using a mobile device. This application will lower the extra expenses of buying this scanner

because we can replace it with the mobile device and we can carry it anywhere and anytime.

2
1.4 Objective

The objective of the proposed system is:

• To design and develop a user-friendly system that handles the information of items or

products and calculated it to manage the information system

• To help staff to find a location and the number of stocks that have been stored

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

1.5 Scope of the study

Stock Management System (SMS) is targeted to the small or medium organizations which have

provided many stores or warehouses for managing various stock data. This system focused on

calculating the amount of stock in and out of a company. The scope a user for this system is

administrators and staff.

• Contractors/Staff - 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.

1.6 Future of the project

This application is used to show the stock remaining and details about the sales and purchases. It

gives the details about the stock on a daily based and weekly based. The details components are

described below:

3
Login page: As the 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.

Create Godwom: We can create godwom if we need to extend or if we have more than

one Godwin. We can create the god whom along with the date.

Sales details: It shows the details about the sales and the remaining stock of sales. It also shows

the details about the sales in return.

Purchase details: It shows the details about the purchase made by the organization along with

the price and dates.

4
 CHAPTER TWO: REVIEW OF THE LITERATURE

2.1 Introduction

A literature review is the formal method that can be used to review the critical points of current

knowledge including findings as well as the theoretical and methodological particular topics for

supporting issues. Products are considered the business resources for the organization. This

includes managing the product with the appropriate way to review any time as per the

requirement. Therefore it is important to have a computer-based IMS which can generate reports,

maintain the balance of the stock, details about the purchase and sales in the organization. Before

developing this application we came up with several Stock Management systems existing in the

market, which helps to give the knowledge for the development of this project. This application

software are only used by large organization but so we came up with an application which can be

used by small company for the management of their stock in production houses. After analyzing

the other stock management system we decided to include some of the common and key features

that should be included in every stock management system. So we decided to include those

things that help the small organization to adapt to this application.

2.2 Stock management system definition

A stock 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 the right decision for the recording process where only the recently used products and

popular products will be ordered. The contractors also could request any additional products that

5
 they needed. The objective of a stock management system is to make stock flows smoothly and

helps in making a decision that will minimize the total cost of stock which is distinctly different

from minimizing stock.

2.3 Comparison between existing system and stock controller inventories (2023)

This is a mobile-based application that can be considered to fulfill the requirement of the stock

management system. However, this application is not quite an intelligence application because it

does not provide QR or Barcode 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 a user can insert

an image in the database to organize the group of stock.

2.4 Stock count (2023)

This is also an example of a stock management system-based mobile application. This

application is quite interesting because it comes in two languages which is English and Bahamas

Indonesia. It contains Bahamas Indonesia language because the developer of this application

was from Indonesia. The application is intelligent because it provides a Barcode scanner

function but the interface of the application is very simple and boring. It also provides a

database for local if an emergency case happens such as a loss of internet connection or no

internet connection, the user still can access it offline.

2.5 Smart stock system

The application is not smart as the name given because it does not provide a notification function

in the application even though it contains QR and Barcode scanner to add the stock quantity.

6
 This application has an attractive interface, so the user can use the application easier than the

other application.

2.6 Summary

In summary, there is much previous research carried upon this system that is more advance than

this system. There is also a system that is identical to this system where it can notify a user of

any low-stock products in the store. There is also a system that can be run on any platform but

did not have a dedicated Android application which it is hard to be use on Android environment.

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

conducted in oversea which offers more than from our country technology. Their system has

more benefit to company where it could help to improve the in-house technology with only just

by developing an stock system

7
 CHAPTER THREE: RESEARCH METHODOLOGY

3.1 Introduction

All the steps required to analyze, create, deploy, and maintain information systems are carried

out in an organization using a methodology. Teams working on software development use the

approaches to complete the Software Development Life Cycle successfully (SDLC). Before the

overall design and execution of the computerized system, data collection techniques were

covered in this chapter.

3.2 Development methodologies

3.2.1 Waterfall methodology

System Development Life Cycle coheres to relevant phases that are important for developers, for

instance, planning, analysis, design, implementation, and maintenance which are explained in the

section below. The choice of using any of these methodologies depends on the nature of the

project. However, the methodology chosen for this project is the waterfall model because it is a

software development process that emphasizes the logical progression of steps to be taken

throughout the software development life cycle and also because it allows for early design

changes. Below are the stages involved in waterfall methodology

8
Waterfall methodology

Figure 3.2: Waterfall methodology.

3.3 Planning

In this first stage, there is a meeting with the customer to understand the requirements. This stage

is the most fundamental phase as any miscommunication or misinterpretation (at this stage) may

give rise to the software that is being developed. The key activity of project planning is the

process of clear, discrete activities and the work needed to complete each activity within a single

project.

3.4 Analyzing

As per the requirements, the software and hardware needed for the proper completion of the

project are analyzed in this phase. Such features are decided at this stage; from deciding which

computer language should be used for designing the software, to the database system that can be

used for the smooth functioning of the software.

9
3.5 Design

The requirements that are gathered in the previous phase are broken down into logical units so

that the software process becomes easy for implementation. This is the stage when the software

requirements along with the hardware requirements for every unit are identified. Then the

designs are made accordingly.

3.6 Implementation

In this phase the actual development of the software takes place. This phase is also known as

the coding and verification phase. Based on the algorithms written in the previous phase, a

software program is written. For every module, software code is written and tested, to check if

the correct output is received.

3.7 Testing

Once testing with the coding of the application is complete, the testing of the written code now

comes into the scene. Testing checks if there are any flaws in the designed software and if the

software has been designed as per the listed specifications. Proper execution of this stage

ensures that the customer interested in the created software will be satisfied with the finished

product. If there are any flaws, the software development process must step back to the design

phase.

3.8 Maintenance

This makes for the final phase of the waterfall model, where the software is organized on the

client’s side after it has undergone thorough testing. After the deployment of the software,

routine maintenance work is carried out. Once the software has been deployed, in case the

customer asks for any changes or enhancements, then the entire process is restarted.

10
 3.9 Methods of data collections

Although there are various methods of data collection, the researcher chose the two main sources

of data collection in carrying out their study. They are:

1. Primary source

2. Secondary source

The primary source refers to the sources of collecting original data in which the researcher made

use of an empirical approach such as a personal interview.

The secondary sources of data for this kind of project cannot be over-emphasized. The secondary

data were obtained by the researcher from magazines, journals, newspapers, and library sources.

Oral interview

The interview method of data collection can be defined as a systematic way of collecting data or

information from a respondent by asking questions directly from the respondent and also

collecting information to facilitate understanding.

Study of manuals

Manuals and reports based on fast products and services were obtained and studied and a lot of

information concerning the system to be produced was obtained.

Evaluation form

Some forms that are necessary and available were accessed. These include the shop's menu fast

products order form, payment receipts, etc. these forms helped in the design of the new system.

3.10 Data analysis

Descriptive analysis was employed by the researcher. The researcher examined and condensed

all or a portion of the numerical data. The creation of an online computerized or web-based

system that can accommodate all client opinions and details is in great demand after data has

11
 been gathered. When comparing a manual method with a web-based computer system, the

computerized system fared better in terms of clarity, fewer mistakes, openness, cost, security,

and multitasking.

Chapter conclusion

A summary of the development approach is provided in the chapter. The steps that will serve as a

guide in the creation of the computerized web-based system were investigated by the researcher

using the waterfall methodology. Additionally, the researcher's methods for gathering data

through evaluation of form, oral interview, and study of manual helped him or her compare the

manual and computerized products delivery systems and develop compelling arguments for the

necessity of a web-based system

12
 CHAPTER FOUR: PRESENTATION DESIGN AND IMPLEMENTATION

4.1 Determining the requirements of the system

A comprehensive system analysis was conducted to guide the development of the system. This

chapter unveils three concrete requirements that identify user requirements, functional

requirements and non- functional requirements.

4.2 User requirements

i. Input and update information about products in the stock

ii. View and search for information about different users, customers, vendors,

Products and Orders of the customers

iii. The user should be able to subscribe or log in from the company whenever he or she likes

4.3 Functional requirements

The system should perform the following functionalities;

i. The system should allow users to change passwords for security purposes

ii. The system allows users to create a password of 5 chars long when changing

their passwords

iii. The system should allow users to record all information about products

purchased, products sold, and those remaining in the store

iv. The system should be able to export all the records stored to Microsoft excel as

reports for Analysis

13
4.4 Non-functional requirements

i. The system must be able to install with ease

ii. The system must not occupy more than the required space for a normal program to disk

space

iii. It must be easy to learn and be used by a given set of users.

iv. The system must be platform independent

4.5 Software Requirements

The Software requirements for the system are summarized below;

Windows XP, windows vista, windows7 and 8.x Visual studio and RDBMS MS Access 2022

4.6 Hardware Requirements

The system's minimum hardware requirements are summarized below;

CPU of minimum Pentium 4 processor, RAM of minimum 512MB, and Hard disk 40GB

4.7 Proposed System design

The Automated Stock Management System design consists of such elements as the architecture,

modules, and components, the different interfaces of those components, and the data that goes

through that system.

It is meant to satisfy the specific needs and requirements of a business or organization through

the engineering of a coherent and well-running system.

14
4.8 System Modeling

In System modeling, systems need to be accepted by users, by having a user-friendly interface

and the system itself should be functioning. In this study, the researchers used a User case as a

model approach. The diagram below shows the users of the system and their roles in the system.

4.8.1 Context Diagram

Add products and stock
Users/Admin

Stock

Management system Place Order for Products available

Customers
Figure 4.8.1 Context Diagram

15
Level 0 Data flow diagram

Administrator/users Login Process

Login successful

Login failed
Checking Process

Product details
After login
Product Entry Data Stored
After login
Category Entry

After login
Customer details

Customer Entry
Data Stored
StoAckftEernltorygin Data Stored
Category details Data Entry

Data Stored
Data Entry

Stock Details
Data
Administrator/Entry
Users
Figure 4.8.2 Level 0 Data Flow Diagram

16
4.8.3 Meaning of symbols

Symbol Name

Process

External Entity

Data store

Data flow

The figures above give a description of the designed objects used in

developing the system. They include processes, data flows, data stores, data reports, and the

external entities involved.

4.8.4 Description of processes

Table 4.1 shows the description of the process

Processes Descriptions

Login process Deals with the details of users if they are valid

Checking process Ensures that only Valid users are authenticated

Category entry Deals with the category of products stored in the system

Product entry Deals with adding products to the system

Stock entry Deals with adding Stock to the System

Customer entry Deals with adding Customer profiles in the system

17
4.8.5 Description of data stores

Table 4.2 Shows a Description of data stores

Data stores Description

Category Category details e.g. category ID, category

name

Product details Products details e.g. product name

Stock details Stock details e.g. Product code

Customer details Customer details e.g. customer ID, customer

name

4.8.6 Description of external entities

Table 4.3 shows the Description of external entities

External entity Description

Administrator Super User that manages other users.

Sales The user that registers and manipulates product information, Stock and

Manager Suppliers

Supplier Individuals who bring a variety of Products to the Company

Customer Individuals who buy products from the company

18
4.9 Database Design

In this phase, the researchers focused on defining the data and constraints about the key entities,

it involves identifying who are the entities, what data is stored about the entities, and which

fields about the entities are unique (primary keys) in designing the database for the Stock

Management system.

Logical Design

Table 4.9.1: Structure of the product table

Field Name Data Type

Product Code Text

Product Name Text

Category Text

Weight Text

Price Number

Table 4. 9.2 shows the Structure of the ordered product table

Field Name Data Type

Order No Text

Product Code Text

Product Name Text

Weight Text

19
 Price Number

Cartons Number

Packets Number

Total Packets Number

Total Amount Number

Table 4.9.3 Shows the Structure of the customer table

Field Name Data Type

B name Text

B address Text

B landmark Text

B city Text

B state Text

B zip code Text

S name Text

S address Text

S landmark Text

S city Text

S state Text

S zip code Text

20
Table 4.9.4 Structure of Stock Table

Field Name Data Type

Stock ID Text

Product Name Text

Category Text

Weight Text

Stock Date Date/Time

Cartons Number

Packets Number

Total Packets Number

Table 4.9.5 Shows the Structure of the Stock category table

Field Name Data Type

Category ID Text

Category Name Text

Table 4.9.6 shows the Structure of the registration table

Field Name Data Type

Username Text

User Password Text

Contact No Text

21
Table 4.9.7 shows the Structure of the user table

Field Name Data Type

Username(PK) Text

User Password Text

Entity relationship diagram

The ERD below illustrates all the entities with their relations and associated attributes to make

up the Stock Management system.

22
 -To many relationships -Entity
System Implementation

The Login form

This is what allows users to input their valid login details to allow them to access the system.

The login form loads to the real user’s interface depending on who has logged in,

Figure 4.10.1 Login form

Switchboard

This is the main menu of the system

23
Figure 4.10.2 Main Menu

Registering customer

The User/admin uses this part of the interface for filling in the information of customers in the

system.

24
4.10.3 Customer Entry Form

Registering Stock

This part of the interface is where stock is added, deleted, or updated in the system

25
Figure 4.10.4: Stock Entry Form

Registering the Categories

This is the section where the User/admin adds delete or update the category of products in the

store from the system.

Figure 4.10.5 Registering the Stock

Registering Product

For this section the user/admin add deletes or updates a product in the store, categorizing the

product under a specified category added in the system.

26
Figure 4.10.6 Registering the Product

Taking orders from customers

For this section of the interface the user/admin takes the order placed by the registered customer

in the system, processes it, and later on generates an invoice, the system also charges a V.A.T tax

for the products bought by the customers.

Figure 4.10.7Taking Orders from Customers

27
Report menu

Creating Godwon

Creating Units

28
29
Creating Product Type

30
Creating Product

Inserting Opening Stock

31
Purchasing product from vendor

32
Sales product to the customer

Purchase Return

33
Sales return

34
 4.11 System testing

For the matter of component testing, the designer did it on the developing Environment

(Microsoft Visual Studio 2012), immediately after the codes has been given the ‘all clear’ in the

code walk-through. The code for the individual function was compiled and executed to see if it

completed the function that was designed.

He created a database using Microsoft Access 2012 using an OLEDB as the engine for the

connection between the forms he created and the Microsoft Access database. The system was

debugged to remove any errors. The functions that users required were designed in particular

forms based on their functionalities.

In part of bottom-up integration testing, The designer combined all components that he was

testing initially on the Integrated Environment Tool which was the Microsoft Visual Studio 2012

exported it as a stand-alone system and transferred it to a friend’s laptop, there were a few errors

that he encountered but lastly, managed to correct and solved it of which the whole system was

error-free. The system was running without any errors and it was also successfully packaged.

4.12 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 needs. 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 of testing includes:

35
 To identify 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.

4.13 Conclusion

The system was tested to ensure that errors if any are fixed and was validated on the other hand

to ensure that the system functionalities complied with the original system requirements.

It was tested at the various phases of development; Unit tests, integration tests, and system tests

were carried out to ensure that errors if any were identified and fixed. Below is a table showing

the results;

User category Interface System Response Comment

time(seconds)

Developers User friendly Very Good 2 Very Good

Users User friendly Very good 3 Very good

It was validated to ensure all the data fields accept the valid inputs, to avoid wrong user inputs.

Further validation tests were carried out on the system to verify that it met the specified user

requirements. We presented the system to the users to get feedback about the system's

performance as to whether the system met their needs or requirements.

36
 CHAPTER FIVE: CODING IMPLEMENTATION

5.0 Application Code Structure

Stock Management System was designed using Visual Studio as mentioned earlier. It provided

us with the code editor as a white blank space and the solution explorer where every code file

were kept. Code Editor is where the logic was developed into code and kept safe in the solution

explorer. In solution explorer, we kept every code file by creating a folder and adding those files

in a folder that is similar. The main folder was the Stock Management System.

5.1 Sample code for login page

Imports System.Data.OleDB

Public Class frmLogin

Private Sub frmLogin_FormClosing(ByVal sender As Object, ByVal e As

System.Windows.Forms.FormClosingEventArgs) Handles Me.FormClosing

End

End Sub

' My.User.CurrentPrincipal = CustomPrincipal

' where CustomPrincipal is the IPrincipal implementation used to perform

authentication. ' Subsequently, My. User will return identity information encapsulated in

the

CustomPrincipal object

' such as the username, display name, etc.

Private Sub frmLogin_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

End Sub

37
System.Windows.Forms.LinkLabelLinkClickedEventArgs)

End Sub

Private Sub login_button_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles login_button.Click

If Len(Trim(UserName.Text)) = 0 Then

MessageBox.Show("Please enter a user name", "Input Error",

MessageBoxButtons.OK, MessageBoxIcon.Error)

UserName.Focus()

Exit Sub

End If

If Len(Trim(Password.Text)) = 0 Then

MessageBox.Show("Please enter password", "Input Error",

MessageBoxButtons.OK, MessageBoxIcon.Error)

Password.Focus()

Exit Sub

End If

Try

Dim myConnection As OleDbConnection

myConnection = New

OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data

Source=|DataDirectory|\SI_DB.accdb;Persist Security Info=False;") Dim myCommand

As OleDbCommand

38
 myCommand = New OleDbCommand("SELECT Username,user_password FROM Users

WHERE username = @username AND user_password = @UserPassword", myConnection)

Dim uName As New OleDbParameter("@username", SqlDbType.VarChar)

Dim uPassword As New OleDbParameter("@UserPassword",

SqlDbType.VarChar) uName.Value = UserName.Text uPassword.Value =

Password.Text

myCommand.Parameters.Add(name) myCommand.Parameters.Add(uPassword)

myCommand.Connection.Open()

Dim myReader As OleDbDataReader =

myCommand.ExecuteReader(CommandBehavior.CloseConnection)

Dim Login As Object = 0 If myReader.HasRows Then myReader.Read()

Login = myReader(Login)

End If

If Login = Nothing Then

MsgBox("Login is Failed...Try again !", MsgBoxStyle.Critical, "Login Denied")

UserName.Clear()

Password.Clear()

UserName.Focus()

Else

ProgressBar1.Visible = True

ProgressBar1.Maximum = 5000

ProgressBar1.Minimum = 0

39
 ProgressBar1.Value = 4

ProgressBar1.Step = 1

For i = 0 To 5000

ProgressBar1.PerformStep()

Next

FrmMain.ToolStripStatusLabel2.Text = UserName.Text

Me.Hide()

FrmMain.Show() End

If myCommand.Dispose() myConnection.Close()

Catch ex As Exception

MessageBox.Show(ex.The message, "Error", MessageBoxButtons.OK,

MessageBoxIcon.Error) End Try

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click End

End Sub Private Sub LinkLabel1_LinkClicked(ByVal sender As System.Object, ByVal e As

System.Windows.Forms.LinkLabelLinkClickedEventArgs) Handles

LinkLabel1.LinkClicked

Me.Hide() frmChangePassword.Show() frmChangePassword.UserName.Text

=" frmChangePassword.OldPassword.Text = "" frmChangePassword.NewPassword.Text

= ""

frmChangePassword.ConfirmPassword.Text = ""

frmChangePassword.UserName.Focus() End Sub End Class

40
5.2 Backup Data code

SaveFileDialog saveBACKUP = new SaveFileDialog();

try

DialogResult Dr;

save backup.Filter = "File format (*.bak)|*.bak";

save backup.FileName = "STOCK ( BACKUP ) " +

DateTime.Now.Year.ToString() + "-" + DateTime.Now.Month.ToString() + "-" +

DateTime.Now.Day.ToString();

Dr = saveBACKUP.ShowDialog();

if (Dr == DialogResult.OK)

string s = null;

s = saveBACKUP.FileName;

SqlCommand cmd = new SqlCommand("Backup database " +

clsGlobalFunction.DatabaseName + " to disk='" + s + "' WITH STATS",

clsGlobalFunction.caster);

cmd.ExecuteNonQuery();

clsGlobalFunction.MessageBoxDisplay("Successfully Created

Backup !!!");

41
 }

catch (Exception ex)

24

clsGlobalFunction.MessageBoxDisplay(ex.Message);

Restore data codes

OpenFileDialog RestoreBACKUP = new OpenFileDialog();

try

DialogResult Dr;

RestoreBACKUP.Filter = "File format (*.bak)|*.bak";

Dr = RestoreBACKUP.ShowDialog();

if (Dr == DialogResult.OK)

string s = null;

s = RestoreBACKUP.FileName;

SqlCommand cmd = new SqlCommand();

cmd.Connection = clsGlobalFunction.caster;

42
try

cmd.CommandText = "Alter Database " +

clsGlobalFunction.DatabaseName + " SET SINGLE_USER With ROLLBACK IMMEDIATE";

cmd.ExecuteNonQuery();

cmd.CommandText = "RESTORE DATABASE " +

clsGlobalFunction.DatabaseName + " FROM DISK = '" + s + "' WITH REPLACE";

cmd.ExecuteNonQuery();

cmd.CommandText = "Alter Database " +

clsGlobalFunction.DatabaseName + " SET MULTI_USER";

cmd.ExecuteNonQuery();

clsGlobalFunction.MessageBoxDisplay("Sucussfully

Created Restored.Application is Restarted !!!");

Application.Restart();

catch (Exception ex) {

clsGlobalFunction.MessageBoxDisplay(ex.Message); }

43
 CHAPTER SIX: CONCLUSION, RECOMMENDATION, FUTURE WORKS,

AND LESSON LEARNT

6.0 Project Limitation

Since this is our first project it has some limitations. Due to less knowledge in particular fields

and limited time, we were not able to fulfill all our expectations that we expected we could do

while the project got started. We hope these limitations are considerable. Some of the project

limitations are:

 This application is not suitable for those organizations where there is the large quantity of

a products and different levels of warehouses

 This software application can generate only simple reports.  Single admin panel is only

made.

 It is not suitable for a large organizations.

6.1 Conclusion

To conclude, Stock Management System is a simple desktop-based application suitable for a

small organization. It has every basic item which is used for the small organization. It was a

successful making the application where we can update, insert and delete the item as per the

requirement. This application also provides a simple report on a daily basis to know the daily

sales and purchase details. This application matches a small organization where there are small

limited Godowns. Though it has some limitations, our team strongly believes that the

implementation of this system will surely benefit the organization.

44
6.2 Recommendation

i. The researchers recommend that as the Company establishes branches all over the nation,

the system may be made web-based such that all branches can use the system at the same time on

the Web.

ii. The researchers also recommend that the system should be upgraded to report on

products that have been hired out. The system can also be expanded to include

information requirements for human resource management.

iii. The researchers recommended that the management of the system should change

the current system of handling day-to-day operations and managing records for effective

management of records.

iv. The researchers recommend that during the implementation time, the system should be

deployed according to the precise specifications of the system for successful usage.

v. The researchers recommend that each group of users should have their password to

ensure adequate security of the system.

6.3 Lesson Learnt

Doing something for long periods always gives the good lessons. Some of the things the

designer learned are listed below:

 Learned about the IMS process.

 Learned about .NET technology, its components, and ways to implement them

 Learned to work under pressure and to be patient.

 Learned to manage the database under Microsoft SQL server 2008.

45
6.4 Future Enhancements

Since this project was started with very little knowledge about the Stock Management System,

the designer came to know about the enhancement capability during the designing process.

Some of the scope the designer can increase for betterment and effectiveness listed below:

 Interactive user interface design.

 Manage Stock Godown-wise.

 Use of Oracle as its database.

 An online payment system can be added.

 Making the system flexible in any type.

 A sales and purchase return system will be added to make the return of products.

 Lost and breakage

 Utilizing machine learning and artificial intelligence to improve stock management

and demand forecasting.

 Implementing block chain technology to improve product tracking and supply

chain transparency.

 Implementing real-time stock level tracking and monitoring, enabling more proactive

stock management and lowering the risk of stock outs.

 Providing a more thorough perspective of stock levels and supply chain processes by

integrating with other systems like sales, purchasing, and production.

 Improving mobile capabilities to enable mobile access to stock data and more

efficient stock management procedure

46
 REFERENCES

Tsai, M. J., & Peng, S. L. (2015). QR code beautification by instance segmentation (IS-QR).

Digital Signal Processing, 133, 103887.

Schmitz, T., Costa, L., Canfield, B. K., Kincaid, J., Zameroski, R., Garcia, R., ... & Moeller, T.

M. (2017). Embedded QR code for part authentication in additive friction stir deposition.

Manufacturing Letters, 35, 16-19.

Usman, A., Salsabila, R., Yulis, S., Lubis, F. Y., Safani, C., & Rafsanjani, R. (2012).

CAPITAL AND INCOME ANALYSIS IN WHOLESALE BUSINESS UD. RIZKI JAYA.

Journal of Accounting Research, Utility Finance and Digital Assets, 1(3), 254-261.

Chattopadhyay, D., Chatterjee, S. K., & Soonee, S. K. (2017). Spotlight on the spot market: A

review of the indian wholesale electricity market. The Electricity Journal, 36(1), 107239.

Nosirov, B., & Raximov, A. (2010). Development of Wholesale Food Markets. AMERICAN JOURNAL

OF SCIENCE AND LEARNING FOR DEVELOPMENT, 2(1), 47-50.

Gautam, P., Maheshwari, S., Kausar, A., & Jaggi, C. K. (2022). Sustainable retail model with

preservation technology investment to moderate deterioration with environmental deliberations.

Journal of Cleaner Production, 136128.

Murhadi, T., & Purnamasari, D. (2016). ANALYSIS OF INVESTOR LOYALTY ON STOCK

BROKERAGE COMPANIES: EMPIRICAL EVIDENCE IN INDIVIDUAL STOCK INVESTORS IN

ACEH

PROVINCE. International Journal of Economic, Business, Accounting, Agriculture

Management and Sharia Administration (IJEBAS), 3(1), 263-274.

O’Hagan, J. (2015). The Development of Retail Support Services. In Logistics And Retail

Management insights Into Current Practice And Trends From Leading Experts (pp. 197-207).
47
CRC Press.

Baldauf, C. (2014). Empirical Essays on Retail Logistics and Customer Behavior (Doctoral

dissertation, Stockholm Business School, Stockholm University).

48
 APPENDICES

Appendix one: Project Budget

Item quantity Unit price Total

amount

VB software 2012 1 20000 20000

Designing 1 30000 30000

Internet - 1000 20000

Transportation - 4000 30000

Printing 9 - 75000

Miscellaneous - - 80000

Total 255000

49