You are on page 1of 62

STI College - Rosario

COMPUTERIZED SALES AND INVENTORY SYSTEM

FOR

R.B. ARCA HOUSEWARE

BY:

Laban, Mark Angelo

Perucho, Marcha

Ponsones, Marjorene

Prodigalidad, Hazel

Romanillos, Mary Joy

TO:

Mrs. Imelda Tolentino


Table of Contents

CHAPTER 1 5

1.0 Introduction 5

1.1 Background of the Study 5

1.2 State of the Problem 6

1.2.1 General Objectives 6

1.2.2 Specific Objectives 7

1.3 Significance of the Problem 8

1.3.1 Owner 8

1.3.2 Customer 8

1.3.3 Employee 9

1.3.4 Research Proponents 9

1.4 Scope and Limitations of the Study 9

1.4.1 Scope 9

1.4.2 Limitation 9

CHAPTER 2 11

2.0 Methodology of the Study 12

Page | 2
2.1 System Development Life Cycle 12

2.1.1 Planning Phase 13

2.1.2 Analysis Phase 13

2.1.3 Design Phase 13

2.1.4 Coding Phase 14

2.1.5 Testing Phase 14

2.1.6 Maintenance Phase 14

CHAPTER 3 15

3.0 Data Gathering Procedures and Output 15

3.1 Interview 15

3.1.1 Scope of Interview to the Manager 15

3.2 Observe 15

CHAPTER 4 16

4.0 The Existing System 16

4.1 Company Background 16

4.2 Description of the System17

4.3 Context Diagram (Existing) 18

4.4 Data Flow Diagram (Existing) 19

Page | 3
4.5 Data Dictionary 20

4.6 Problem Areas 21

CHAPTER 5 23

5.0 The Proposal System 23

5.1 System Overview 23

5.2 Process Specification 24

5.2.1 Context Diagram (Developed) 24

5.2.2 Data Flow Diagram (Developed) 25

5.2.3 Data Dictionary 26

5.3 Data Specification 28

5.3.1 Entity Relationship Diagram 28

5.3.2 Tables/Files Layout 31

5.4 Screen Layout Specifications 34

Page | 4
CHAPTER 1

1.0 INTRODUCTION

Nowadays people want to be a modernize and live to a comfortable life, so that

the generation today comes a lot of technology and having technology there would be

systems ahead on it. System could easily make people’s life easier because from a

filling document we could turn it from a computerized to make people get quick

answers.

System could evenly help the most in the field of business, especially for the

information, billing, payroll etc. There are people being able to make a system for the

betterment of the manual system and to become more advance of the company.

System is worldly use by now, so that the interesting background of the system

could make people and students learn from it, to create more than develop or advance

than the old one, to get more demand, more money and greater known personality of

the innovator. As long as the industry continue for being modernized, the system

builders will also increased until they reach to the point that the industry is full of

system and they can no longer need the use of human force.

1.1 BACKGROUND OF THE STUDY

Sales and Inventory System is a solution for management of small and

medium-sized business. It is use to create sales orders, product orders, payment

receipts and any kind of reports for the management of the business. Sales and

Page | 5
Inventory System is also used for easily monitoring of the stocks, updating the

price and quantity of the items stored at the warehouse.

R. B. Arca Houseware is a direct selling business of plastic wares which is

named after the name of the owner Rosario Barrera Arca. It was established in the

year 1987 and located near Saint Augustine Church, Tanza, Cavite.

R. B. Arca Houseware produces different products like household

equipments and plastic wares. According to the nephew of the owner, they are

still using the traditional system by the used of paper and a pen.

When processing the inventory of the products, they still manually

counting the stocks and sometimes they don’t even give attention to the missing

stocks or products because they don’t have a proper monitoring in the warehouse.

1.2 STATEMENT OF THE PROBLEM

The researchers find the problems that encountered by the consumer

through the manual system of the R. B. Arca Houseware. Some of the problem

encountered is difficulty/incorrect counting of stocks, inappropriate list of tally

from warehouse to the store, inaccurate result of sale for monthly inventory and

incorrect info of products

1.2.1 GENERAL OBJECTIVES

The general objective of the study is to design develop and

implement Sales and Inventory System of R. B. Arca Houseware.

Page | 6
1.2.2 SPECIFIC OBJECTIVE

 To create a module that will determine the critical point of

items.

This module will display warning when it reached the

critical point for items and this is monitored by its optimal level

whether under-stock, overstocked or out of stock.

 To develop a module that will generate reports.

The module is design for producing sale and inventory

printing reports. The sales report shows the everyday and monthly

profit. An inventory reports tackle for the damage and the lost

items, this report shown for management for what is the most

profitable items and it will make the management more informed

for business decision.

 To develop a module that will handle sale transaction.

The module help the owner, admin for specification to

easily compute the sales, and for the monthly profit result for it is

accurate for the previous result. And it could minimize time

consumption in checking stocks from the warehouse in and out.

 To create a module that will manage the supplier and the

product records.

Page | 7
This module must be update through that there are lot of

product in and a different supplier. This could help the consumer

especially with comes with satisfaction always the best, and the

system must produce up to date results.

1.3 SIGNIFICANCE OF THE STUDY

This study will be beneficial to the customer, employee and especially to

the owner of the store.

This study will become a source of opportunity likely for those who afraid

to raise a business even if it if a small or large business. This could create and

give an insight that business now-and-then are not so hard in terms for product

inventory or sales computing operation.

1.3.1 OWNER

Information and reports that created by the computerized system

will help the business owner to analyze the possible problems that can

affect the business growth. It will also give support to the business owner

to manage the business effectively.

1.3.2 CUSTOMER

Computerized system will help to get the fast information of

product availability.

Page | 8
1.3.3 EMPLOYEE

The employees would be able to serve and perform a fast action in

terms of checking the availability of the items and stocks in the

warehouse.

The computerized system could also help them in monitoring the

out of stock products and it is also help them to determine the movement

of the products from the time they will receive a new delivery from

suppliers until the product has been purchased.

1.3.4 RESEARCH PROPONENTS

The study will enhance the teamwork and the cooperation with all

the members of the group. It exposed them in a self directed learning

environment which they will be trained in problem solving by applying

their knowledge in the possible problems that they may encountered in

doing the project.

1.4 SCOPE AND LIMITATION OF THE STUDY

1.4.1 SCOPE

 Monitoring of Available Stocks

Items are monitored by its optimal level if it is under-stock,

overstock and out of stocks, when it reach of its critical point

display on the items.

Page | 9
 Sales Monitoring

Items are monitored for how many items sale and how

many are left. Includes updating prices for barcode and the

product quality it has.

 Generation of Reports

Sales and inventory reports sees the monthly sales, the total

lost and damaged items and miscounted items are show to its

printed reports.

 Documented List of Product/Items

Items are documented and monitored by product name.

 Monitoring of Items Pulled-out

Items are monitored from warehouse for how many items

should out and items deliver in the warehouse.

 Management of Customer and Supplier Info

Info from the customer is a must for delivery and return

product operation. And supplier should be know, for it is the

one who giving us product, should also know that product must

be tested my higher organization that deals in health security.

Page | 10
1.4.2 LIMITATION

 Online ordering does not covered by the system.

This could be face-to-face transaction and not by online,

this is a system for sales and inventory and does not dealing

with any online/wifi connection used to transaction.

 The system does not include online payment

The system is not for any special operation or special

reading for payment like credit cards. This is only for cash

transaction.

 The system should be in full/cash payment only

This system does not accept installment and online or

delivery payment.

 The system is exclusively to the owner and authorized

personnel only

The info in this system is not able to share to the customer

and does not access any person who’s not in charge in the

system.

 The system does not include payroll operation.

The payroll operation does not cover in this system. This

system is for sales an inventory of items only.

Page | 11
CHAPTER 2

2.0 METHODOLOGY OF THE STUDY

2.1 SYSTEM DEVELOPMET LIFE CYCLE (SDLC)

For the development of the computerized system of the R.B. Arca

Houseware, the System Development Life Cycle Model will be use by the

research proponents as their methodology.

Iterative waterfall is a System Development Life Cycle Model that

processes the simple implementation of the software requirements before it

proceeds to the next phase. If the development system has an error or

problem, the Iterative Waterfall model accepts the expected changes and

reviews to the projects.

PLANNING

ANALYSIS

DESIGN

CODING

TESTING

MAINTENANC
E

FIGURE NO.1: SDLC ITERATIVE WATERFALL MODEL

Page | 12
2.1.1 PLANNING PHASE

Planning Phase is the process where the proponents need to

define what is the specific problem and work needed to complete

the project.

The research proponents will apply this phase by gather

some requirements and information about the process of the sales

and inventory system of the business that will help them to

produce a system. Including the observation of the proponents to

the store and interviewing the manager or the owner of the

business.

2.1.2 ANALYSIS PHASE

This phase is the process where the requirements needed

for the project, is fully understand of the proponents and in this

phase also the processing of the requirements of the new system.

In this phase, the research proponents will examine the

need for possible software automation in the given manual system.

2.1.3 DESIGN PHASE

This phase involves the design of the solution system based

on the requirements defined and the decisions made during the

Analysis Phase.In this phase, the database design and the data

structure design is required. The research proponents will create an

Page | 13
appropriate design that solution for the problem that they

encountered.

2.1.4 CODING PHASE

In coding phase, the design will be decoded into a machine

–readable form. The research proponents will use the programming

tools like compilers, interpreters and debuggers. For coding

purpose different high level languages like C# and JAVA are used.

2.1.5 TESTING PHASE

In this phase, the system design will finally translated into

machine language. The proponents will test the developed system

to reveal some errors and bugs and to ensure that the developed

system will meet the expected output.

2.1.6 MAINTENANCE PHASE

Maintenance Phase is the process where the proponents

will discuss the functions of the developed system to the client and

to familiarized how the system works.

The developed system may have some changes when the

client starts to use it. The said changes will caused by an

unexpected input values into the system.

Page | 14
CHAPTER 3

3.0 DATA GATHERING PROCEDURES AND OUTPUT

Data Gathering is the process that collects some information or facts thorough

the use of interview, survey, observations, and research.

3.1 INTERVIEW

Interview is a conversation between two or more people, where the

interviewer will ask questions to the interviewee to get information and opinions

about the possible problem of the company. They conducted an interview with the

company manager Mr. Wilmer B. Arca, to know how the existing system works.

3.1.1 SCOPE OF INTERVIEW TO THE MANAGER

 The background of the company

 The total employee of the company

 How they process the inventory of the stocks and display items

 How they process the monitoring of sales

3.2 OBSERVE

The Observation refers to the collecting data where the company is visually

examined. In other words, it refers to watching, listening and taking some notes of

anything to gain some information. This is what exactly the proponents will do in the

existing system.

Page | 15
CHAPTER 4

4.0 THE EXISTING SYSTEM

In Sales and Inventory system, the current system of the R.B Arca Houseware

based on our observations from the research was done through writing down the lists

of the material’s which have been returned to the supplier, receiving new products

and purchased by the dealers. The said inventory of stocks was conducted every

once a month.

The employees used to count their stocks every week, so the owner of the

Houseware determined how fast and slow is the products was sold.

The major problem of the owner to the existing system was the slow counting

of the products during the inventory.

4.1 COMPANY BACKGROUND

The R.B. Arca Houseware was named after its owner, Rosario Barerra Arca. It

is established in the year 1987and located near Saint Augustine Church, Tanza,

Cavite and lately transferred to the Tanza Public Market Tanza, Cavite. Then

according to the manager of the store, those past few years, the approximately start-

up money is ₱30,000.

R.B. Arca Houseware produces different kinds of plastic wares and household

equipments and they earn their profit approximately ₱150,000 to ₱180,000 if it is

pick season (December) and for ordinary day ₱55,000 to ₱80,000 a month.

Page | 16
The R.B. Arca Houseware is compose of the 8 staff worker which is Wilmer

Barrera nephew of the owner, Anna, Cecille, Lani, Micheal, Mark, James the sales

lady and sales boy and Ate Aurie the Manager.

There are many people choosing their products not just because of the low

price and the quality of the products but also the good personality and approachable

staffs. As for now, they still serving people within 33 years and still counting.

4.2 DESCRIPTION OF THE SYSTEM

Sales and Inventory system covers the sale transaction and counting of the

products/items that was receive from the suppliers and distributed to the customer.

This enables the improvement of the manual system that has been use by the owner as

they conduct their Sales and Inventory. Sales monitoring is use to keep and maintain

the sales and stocks of each items.

This will also generates reports that will be use when analyzing the problems

encountered from the dealers performance to determine the total sales of the R.B Arca

Houseware.

Page | 17
4.3 CONTEXT DIAGRAM (EXISTING)

CUSTOMER CHECKER

Purchase Order Item


Status Info Status

Receipt Item
Status

R.B. ARCA
HOUSEWARE SYSTEM

Sales &
Sales Order
Inventory Info Order
Reports Info
Info

Inventory
STORE Sales
Info Inventory
Info
MANAGER Info

SALES MAN
SALES
PERSONNEL

Fig.No.2: Context Diagram INVENTORY


(Existing) PERSONNEL

Page | 18
4.4 DATA FLOW DIAGRAM (EXISTING) CANCELLED
PURCHASE INFO

ORDER INFO ORDER INFO


1
CUSTOMER
` GET ORDER
ORDER INFO

RECEIPT 3 2
PAYMENT
CHECK
PURCHASE AVAILABILITY
PURCHASE
ITEM
STATUS
ITEM INFO
ITEM STATUS
4
CHECK ITEM ITEM INFO
STATUS CHECKER

CANCEL ITEM STATUS


PURCHASE
SALES
INFO
INVENTORY
INFO

INVENTORY
6 INFO

PREPARE SALES &


1 SALES INVENTORY 2 INVENTORY
RECORDS
SALES INVENTORY
RECORD RECORD
7

GENERATE
REPORTS
SALES INVENTORY
RECORD RECORD

SALES AND INVENTORY


REPORTS

STORE
MANAGER
Fig.No.3: Data Flow Diagram
(Existing)

Page | 19
4.5 DATA DICTIONARY

tblCustomer

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


Unique Number Id for all
CustomID Varchar 5 Customers
CustomFirstName Varchar 50 First name of the customer
CustomLastName Varchar 50 Last name of the customer
CustomAddress Varchar 100 Address of the customer
CustomContact Integer 15 Contact number of the customer

tblProduct

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


Unique ID Number of the
ProductID Int 5 products
ProductName Table.No.5.2.3.1:
Varchar Customer
50 Table Name of the product
ProductType Varchar 50 Type of the product
ProductPrice Double Price of the product
SuplierPrice Double Supplier price of the product
ProductDescriptio
n Varchar 100 Description of the product
CriticalLvl Int Critical level of the Product
Table.No.5.2.3.2: Product
Table

tblSupplier

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


SupplierID Int 5 Unique Id number of the supplier
supplierName Varchar Name of the Suplliers
SupplierAddress Varchar Adress of the suppliers
SupplierContact Int 15 Contact number of the supplier
Table.No.5.2.3.3: Supplier Table

Page | 20
tblStock

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


StockID Int 5 Stock ID of the Product
ProductID Int 5 ID number of the Product
StockQty. Int Quantity of the Stock
Remarks varchar Remarks

Table.No.5.2.3.4: Stock Table

tblSales

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


TransacNo. Int 5 Transaction number
ID Number Of the
CustomID Int 5 customer
Date Date Date of transaction
ProductID Int 5 ID Number Of the product
Qty. Int Quanity
TotalPrice Double Tota Price
Table.No.5.2.3.4: Stock Table

4.6 PROBLEM AREAS

Some of the customer of R.B Arca Houseware are not satisfied through the

system they are currently using because of the difficulty and slow in computing the

amount of payments. The R.B Arca itself shared that sometimes they could not plot the

correct tally for their sales and improper monitored for their product for inventory matter.

Some of the common problems that the customer encounter, first and for most

difficulty in counting items/products. Inappropriate records of sales. Undetermined level

of product that are understock, out of stock, overstock. Slow process of issuing receipt.

Difficulty in generating reports in sales and inventory with improper less of product.

Lack of security and time consuming. And inconsistency in data entry, room for errors

Page | 21
and incorrect information. Reduction in sharing information and customer service. And

for the major problem of the system (traditional system) is slow retrieval of data. The

information of customer are stored in different parts of sites/book pages and takes a long

time to retrieve or find the data. This can take up to 30 minutes in finding the relevant

information of the client especially in delivery or return product issue from customer.

Page | 22
CHAPTER 5

5.0 The Proposal System

The propose system is Sales and Inventory that compute, count and generate

reports for the product and sales.

5.1 System Overview

The Sales and Inventory System states that the difficulty of

counting/monitoring of stocks and difficulty in computing sales has a solution for now.

This system is capable to avoid excess inventory by accurately predicting

customer demand. and often carries to company certain amount of safety stock or excess

inventory to guard against delivery delays or unexpected demand for a particular items.

It helps to carry more safety stock than necessary can be expensive, because the extra

inventory takes up warehouse space and can result in a higher tax bill.

The main purpose for this developed system is to reduce the total amount

of inventory the company needs to keep on hand at any one time. And to reduce time and

manpower to invent the products for the specific company.

Page | 23
5.2 PROCESS SPECIFICATION

5.2.1 CONTEXT DIAGRAM (DEVELOPED)

CUSTOMER CHECKER

Purchase Order Item


Info Info Status

Item
Info
Receipt Item Item
Status Info

COMPUTERIZED SALES
AND INVENTORY
SYSTEM

Sales &
Inventory
Reports Order Confirmed
Info Order Info
Product
Needed
MANAGER SUPPLIER
Fig.No.5: Context Diagram
(Developed)

Page | 24
5.2.2 DATA FLOW DIAGRAM (DEVELOPED)

RECEIPT
1 SALES
CUSTOMER

ORDER INFO SALES INFO

ITEM INFO 1 2
PAYMENT
CHECK
AVAILABILITY PURCHASE
ITEM

ITEM STATUS
INVENTORY
3
INFO
ITEM INFO
CHECK
CHECKER ITEM
STATUS
ITEM STATUS 2 INVENTORY

PURCHASE CANCELLED
4
INFO PURCHASE INFO
CANCEL
PURCHASE

INVENTORY
SALES RECORDS RECORDS
5

GENERATE
MANAGER REPORT
SALES &
INVENTORY
REPORTS
SUPPLIER
6 ORDER
PRODUCT
NEEDED INFO
ORDER
PRODUCT
CONFIRMED
7
ORDER INFO

DELIVER &
RECEIVE
Fig.No.4: Data Flow Diagram PRODUCT DELIVERY
(Developed) INFORMATION

Page | 25
5.2.3 DATA DICTIONARY

tblCustomer

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


Unique Number Id for all
CustomID Varchar 5 Customers
CustomFirstName Varchar 50 First name of the customer
CustomLastName Varchar 50 Last name of the customer
CustomAddress Varchar 100 Address of the customer
CustomContact Integer 15 Contact number of the customer

tblProduct

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


Unique ID Number of the
ProductID Int 5 products
ProductName Table.No.5.2.3.1:
Varchar Customer
50 Table Name of the product
ProductType Varchar 50 Type of the product
ProductPrice Double Price of the product
ProductDescriptio
n Varchar 100 Description of the product
CriticalLvl Int Critical level of the Product
Table.No.5.2.3.2: Product
Table

tblSupplier

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


SupplierID Int 5 Unique Id number of the supplier
SupplierName Varchar Name of the Suplliers
SupplierAddress Varchar Adress of the suppliers
SupplierContact Int 15 Contact number of the supplier
Table.No.5.2.3.3: Supplier Table

Page | 26
tblStock

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


StockID Int 5 Stock ID of the Product
ProductID Int 5 ID number of the Product
StockQty. Int Quantity of the Stock
Remarks varchar Remarks

Table.No.5.2.3.4: Stock Table

tblSales

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


TransacNo. Int 5 Transaction number
ID Number Of the
CustomID Int 5 customer
Date Date Date of transaction
ProductID Int 5 ID Number Of the product
Qty. Int Quanity
TotalPrice Double Tota Price
Table.No.5.2.3.5: Sales Table

tblSupply

FIELD NAME DATA TYPE FIELD SIZE DESCRIPTION


SupplyID Int 5 ID number of the Supply
ProductID Int 5 ID Number of the Product
SupplierID Int 5 ID number of the Supplier
Qty. Int Quantity of the Supply
DateAdded Date Date added the supply
Table.No.5.2.3.6: Supply Table

5.3 DATA SPECIFICATIONS


Page | 27
5.3.1 ENTITY-RELATIONSHIP DIAGRAM

CustomID

CustomFirstName

CustomLastNam
e
CUSTOMER

CustomAddr
CustomCon ess
tact
buy
ProductID
ProductTyp
e
ProductNa
PRODUCT me

ProductPric
e
Critical ProductDescriptio
Level n

Figure.No.5.3.1.1: Customer and Product

StockID
Page | 28
ProductID

ProductID

ProductType

ProductName

ProductDescription

CriticalLevel

ProductPrice

Figure.No.5.3.1.2: Stock and Supply

SupplierID

SupplierNAme Page | 29
SupplierAddress
Figure.No.5.3.1.3: Supplier and Supply

5.3.2 TABLES/FILES LAYOUT

Page | 30
Figure 5.2.3.1 Sample Receipt for the Customer

Page | 31
Figure 5.2.3.2 Sample Copy Delivery Receipt for the R.B. Arca Houseware

Page | 32
Figure 5.2.3 Sample Copy of Delivery Receipt for the Supplier

Page | 33
5.4 SCREEN LAYOUT SPECIFICATIONS

Figure 5.4.1 Log-In Screen

This module will be the screen that you will first encounter in this system. This

module contains two buttons namely “LOG IN”. The screen will prompt the user to input

User ID and a correct Password to be given access in the system.

Page | 34
Figure 5.4.2 Main Menu Screen

This module allows the user to access Inventory, Sales, Reports, User Log,

Manage User Account, Manage Supplier, Manage Items, About and the Notification

Buttons. The users may also log-out their account after accessing their desired Modules.

Page | 35
Figure 5.4.3 Notification Screen

This module shows all the notification about the delivery schedules and the

products that are on the Critical Level so that the user will be aware on their stocks and

delivery schedules.

Page | 36
Figure 5.4.4 Inventory Information Screen

This module allows the user to see the inventory details of the remaining

products. The user may also search the specific product name by clicking the “Search

Item” button.

Page | 37
Figure 5.4.5 Inventory Information Screen

This module allows the user to see the inventory details of the remaining

products. The user may also search the specific product name by clicking the “Search

Item” button. And the user may send the inventory information to the inventory reports.

Page | 38
Figure 5.4.6 Sales Information Screen

Page | 39
This module allows the user to see the Sales details of the Sold Products. The

module also view the information between the date covered.

Figure 5.4.7 Sales Information Screen

Page | 40
The user may send the Sales information to the Sales reports.

Figure 5.4.8 Reports Screen

Page | 41
This module shows two buttons to click to view the inventory and sales report.

The Admin, Owner and all users are allowed to view this module and to print the reports.

Figure 5.4.9 Inventory Report Screen

This module allows the user to print the Inventory Report.

Page | 42
Figure 5.4.10 Sales Report Screen

Page | 43
This module allows the user to print the Sales Report.

Figure 5.4.11 User Log Screen

Page | 44
This module allows the Admin and Owner to view the list of user logged-in on

the system. It shows the Date Logged-in, the User Name and the position of the user.

Figure 5.4.12 Add User Account

Page | 45
This module allows the Admin and Owner to create new account with the

restriction depending on which checkbox has been checked. TheAdmin and Owner must

filled-up the textbox provided. If there's an empty field, the system will notify the user

with "All fields should not be empty". After filling up the corresponding textbox, the user

must click the "Save" button to save the users account.

 Add - add the user's information and account

 Cancel - cancel all the information that the user input and close the window.

Page | 46
Figure 5.4.13 Edit User Account Screen

This module allows the Admin and Owner to edit/update their information that has

been filled-up on their account. The Admin and Owner must log-in first before editing

their account. The user also need to re-type their password so that the edited information

will be saved.

 Save - save the edited information of the user.

 Cancel - cancel all the information that the user has input and close the window.

Page | 47
Figure 5.4.14 Delete User Account Screen

This module allows the Admin and Owner of the store to delete the user account by

searching the user ID.

Figure 5.4.14 Delete User Account Screen

Page | 48
Figure 5.4.15Delete User Account Screen

The system will notify the Admin or the Owner with "Are you sure you want to

delete this User Account" before deleting.

 Delete - delete the selected user account.

 Cancel - cancel deleting account and close the window.

Page | 49
Figure 5.4.16 List of User Accounts Screen

This module displays the list of all user accounts. The Admin and Owner may

search the user ID of the specific username to check if that username is in the list.

 Search User ID - search the user ID from the list of user accounts.

Page | 50
Figure 5.4.17 Manage Supplier Screen

This module allows the user to view supplier informations, add, edit and delete

informations of the supplier.

Page | 51
Figure 5.4.18 Manage Supplier Screen

This module displays the list of all suppliers. Only the Admin and Owner are

allowed to open this module. They may search the supplier name to view the supplier

informations.

Search Supplier Name - allows the admin and owner to view supplier

informations.

Page | 52
Figure 5.4.19 Add Supplier Screen

This module allows the Admin and Owner to add supplier by adding supplier

information, they must filled-up the textbox provided. If there's an empty field, the

system will notify the Admin and Owner with "All fields should not be empty" before

selecting the add button.

Add - add the supplier information

Cancel - cancel all the information that the user input and close the window.

Page | 53
Figure 5.4.20 Edit Supplier Screen

This module allows the admin and owner to edit the information of the supplier.

All fields should not be empty before selecting the save button.

 Save - saves the edited information.

 Cancel -cancel all the information that the user input and close the window.

Page | 54
Figure 5.4.21 Delete Supplier Screen

This module allows the Admin and Owner to delete the selected supplier. The

system will notify the Admin and Owner with "Are you sure you want to delete this

supplier information?" before deleting the information.

 Delete - delete the selected supplier information.

Page | 55
 Cancel - cancel all the information that the user input and close the window.

Figure 5.4.22 Manage Items

This module allows the user to view the list of all items. The Admin, Owner and

the Inventory Personnel are allowed to add, edit and delete items.

Page | 56
Figure 5.4.23 List of Items Screen

This module displays the list of all items that are available in the store. The user

may search the product ID of the items.

 Search Product ID - search the product ID from the list of items.

Page | 57
Figure 5.4.24 Add Items Screen

Page | 58
This module allows the authorized personnel to add items. The user must filled

-up all the TextBox, ComboBox and NumericUpDown. If there's an empty field, the

system will notify the personnel with "All fields should not be empty" before adding

items.

 Add - add the items to the list of items.

 Cancel - cancel all the information that the user input and close the window.

Page | 59
Figure 5.4.25 Edit Items Screen

This module allows the authorized personnel to edit items. The personnel may

search the item to be edit. All fields should not be empty.

 Save - saves the edited information of items.

 Cancel - cancel all the information that the user input and close the window.

Page | 60
Figure 5.4.26 Delete Items Screen

This module allows the authorized personnel to delete selected items. The system

will notify the personnel with "Are your sure you want to delete this item information?"

before deleting the item.

 Delete - delete the selected items.

 Cancel - cancel all the information that the user input and close the window.

Page | 61
Figure 5.4.27 About Screen

This module allows the user to view the information about the company and the

developers.

Page | 62

You might also like