CHAPTER I

INTRODUCTION

Problem Background

In today’s world, digital technologies have advanced more rapidly than any

innovation in our history. Technology is just like the vein of society. It allowed us

to automate tasks, communicate efficiently, trade businesses conveniently, and

more. With just a few clicks, you can instantly pay your bills, purchase items, and

transact businesses through online gadgets.

As e-commerce platforms have slowly crept into our daily lives today, it is

now the most popular method of conducting business due to their quick and

simple access. In contrast to traditional stores, buyers can quickly browse

through a massive product database without having to leave their homes. Putting

the establishment’s items online has further advantages. E-commerce helps big

and small businesses gain more exposure by accessing even global audiences

via the internet and search engines. Different industries are indulging in this new

approach, such as food, beverages, and even the arts, especially the pottery

industry.

Pottery is a type of decorative art that shows the potters’ brilliance

through their impressive art pieces using clay and is hardened with heat. The

potters of Barangay Binogawan in Calape, Bohol, are famous for their durable

and impressive clay pots that come in different sizes and designs. The traditional

way of crafting their designs using clay is still existing. The products are available

in their pottery chambers and can be purchased anytime, and they display their

1
products in the market. But this strategy needs to be elevated because some

customers who want to avail of these clay pots are from other towns, and

traveling is a hassle for them. And also, some clients prefer customized art

pieces that need much time to finish. There are also other instances when there

are many orders, but only a few available products are available. This is not very

easy for both the establishment and the clients.

With this, the researcher created HandyPot, an innovative online

shopping system that sells handmade pot products designed by the potters of

Barangay Binogawan. This system serves as a business medium for prospective

clients and potters. The clients can order their desired products with ease. The

handmade pots will be displayed in the system, making it easier for the

customers to view the available pots in the store. This will lessen the hassle of

the customers selecting the products they want to buy. Customers can request

the products to be customized. The automation of this system will help both the

user and the establishments to reduce manual work in selling and gain profits as

well. This will also boost the tourism sector in the Municipality of Calape,

particularly in the pottery industry.

Project Description

HandyPot is a mobile-friendly website that sells handmade pot products

online. This digital platform offers various kinds of clay pots that come in different

sizes and designs. To access the website, users must create an account first

and log in; once done, they can see the dashboard, which contains the essential

2
functions in the system, such as the products, users section, and the

establishment’s information. Customer can also order their desired products and

pay through cash on delivery. For security, the admin is the only authorized

person to manage the system, like the products section, whether to add, update

or delete it.

On the other hand, customers also can update their information on the

registered customer section. The admin also manages the inventory of the

products in the system. This website is created using PHP, HTML/CSS,

JavaScript, and Bootstrap programming languages. The data entered into the

system are stored in the database.

Project Objectives

This study aimed to promote the pottery industry in Barangay Binogawan,

Calape, Bohol, and also help potters profit by selling their products online.

• To develop a digital platform that will modify the strategy by selling the

products to a broader target audience and be known worldwide;

• To increase the sales of the potters and improve their business;

• To provide a more accessible way for the customers to purchase the

products without any hassle;

• To measure the level of usability and acceptability in implementing

the web application for pottery.

3
Scope and Limitation of the Study

This study investigated the process involved in developing the HandyPot

website for the potters of Barangay Binogawan in Calape, Bohol using the

concept of a database. The researcher aimed to cater the services to Calape

residents only. This online platform is intended for customers who want to

purchase the handcrafted clay pots displayed in the establishment. Users must

create an account to access the website. An Internet connection is required to

transact with the system. The items are shown in the products section according

to their size and design and can be purchased by adding them to the cart. Once

added, it can also be updated and proceed to checkout. The administrator

manages the backend. Payment is through Cash on Delivery. Cancellation of

orders is not applicable upon approval by the admin. The admin does not

entertain the customization of products.

Significance of the Study

This research is primarily intended to develop a mobile application that is

necessary for two reasons:

First, the customers can get to the products being sold more easily. They

may quickly search for and purchase the preferred product they want. It is far

more convenient for them to buy it while most retail establishments are still

closed. It also saves time because the system allows users to purchase the

merchandise immediately from the establishment.

4
 Second, it is quick and dependable since the services provided are more

organized and well-executed, making the transaction easier for both the

customer and the administrator.

Theoretical Background

This study is anchored on the Automata Theory. According to the

published book by John E. Hopcroft (2006) et al. entitled “Automata Theory,

Languages and Computation 3rd edition, automata theory is the study of abstract

computing devices or “machines.” Before there were computers, in the 1930”s, A.

Turing studied an abstract machine that had all the capabilities of today’s

computers, at least as far as in what they could compute. Turing’s goal was to

precisely describe the boundary between what a computing machine could and

could not do; his conclusions apply to his abstract Turing machine and today’s

real machines. In the 1940s and 1950s, simpler kinds of machines, which we

today call “finite automata,” were studied by several researchers. These

automata originally proposed to model brain function were extremely useful for

various other purposes. In 1969, S. Cook extended Turing’s study of what could

and could not be computed. Cook was able to separate those problems that can

be solved efficiently by computer from those problems that can, in principle, be

solved but, in practice, take so much time that computers are useless for all but

minimal instances of the problem. The latter class of problems is called

“intractable” or “NP-hard.” It is highly unlikely that even the exponential

improvement in computing speed that computer hardware has been following

5
(Moore’s Law”) will significantly impact our ability to solve large instances of

intractable problems. All of these theoretical developments bear directly on what

computer scientists do today. Some concepts, like finite automata, and certain

kinds of formal grammars, are used in designing and constructing essential

software. Other concepts, like the Turing machine, help us understand what we

can expect from our software. Especially the theory of intractable problems lets

us deduce whether we are likely to be able to meet a problem “head-on” and

write a program to solve it (because it is not in the intractable class) or whether

we have to find some way to work around the intractable problem: find an

approximation, use a heuristic, or use some other method to limit the amount of

time the program will spend solving the problem.

The researcher chose this theory because it develops methods by which

computer scientists can describe and analyze the dynamic behavior of discrete

systems in which signals are sampled periodically. The way that determines the

behavior of these discrete systems is that the system is constructed from storage

and combinational elements. The most general and powerful automata are the

Turing machine.

Moreover, this study is also based on the Relational Database Theory.

According to the published paper of Dr. Edgar. F. Codd entitled “A Relational

Model of Data for Large Shared Data Banks” (1970), a relational database store

data in a series of tables so that the data models a mathematical theory of

relations. The model allows for queries based on projection, selection, and join,

among other operations, and connects the data in the tables using keys. The

6
queries are expressed in a standard syntax common to all various vendors of

relational databases. The theory of relations states that data is arranged as

various sets of tuples, called relations, where a tuple is a collection of values for

attributes. A relation states which attributes it collects.

The researcher chose Relational Database Theory because of its ability to

create meaningful information by joining the tables. Joining tables allows the

users to understand the relationships between the data or how the tables

connect. SQL includes the ability to count, add, group, and combine queries. It

provides an interface between users and applications and the database, as well

as administrative functions for managing data storage, access, and performance.

This database is powerful as it deals with relations, making data manipulations

easier than any other database. It has the features of data entry, data deletion,

and creating of new entries and records, etc. the database provides the ease of

accessing and maintaining data easily. It allows users to establish links between

different data sets within the database and use these links to manage and

reference related data. Many relational databases use SQL to perform queries

and maintain data.

Review of Related Literature

According to an article in statista.com entitled “E-commerce worldwide,” e-

commerce has become an indispensable part of the global retail framework over

the last few years. Like many other industries, the retail landscape has

undergone a substantial transformation following the advent of the internet.

7
Thanks to the digitalization of modern life, consumers from virtually every country

now profit from the perks of online transactions. As internet access and adoption

are rapidly increasing worldwide, and with nearly five billion global internet uses,

the number of people making purchases online is ever-increasing.

Further, Vince Bunxo (2022) on www.scribd.com entitled “Thesis Chapter

1” the Philippines, with more than 39.4 million internet users, ranked 16 th in the

world and penetrating an estimate 33% internet users against its total population

(Internet Live Stats, 2015). Moreover, when learning more about what they need

to buy, Filipinos are among the most active in the Asia-Pacific region in using the

internet for product research and sharing online deals (Lucas, 2012). However,

despite the acceptance of e-commerce in western countries, the rise of online

stores, product research, and technological advancement, the shopping habits of

Filipinos remain traditional.

In an article published by Statista Research Department on statista.com

(2021), in the third quarter of 2020, social networking mobile apps were popularly

used among 98.2 percent of internet users in the Philippines, according to

Datareportal. Other popular mobile apps were chat apps, entertainment or video

apps, games, and shopping apps.

According to a document uploaded on scribd.com entitled “Social Justice

Project,” there is a massive demand for Nepali handmade ceramic products in

the national market due to their improved quality. Buyers are willing to pay a

premium price for handmade goods propelling exports. Ceramics has a

contribution to exports, too. These products are exported as handicraft products

8
to many countries. According to a daily newspaper, exports of ceramic products

surged 45 percent in the first five months of fiscal 2016-2017, reflecting a

rebound from the earthquakes of 2015 and increased demand for handmade

goods in the international market, according to the latest statistics of the

Federation of Handicraft Associations of Nepal (FHAN). The US is the largest

importer of Nepali ceramic products. Another large importer of Nepali ceramic

products is Germany. These all show a huge scope of pottery business in

international markets.

The book of Skibo and Feinman (1999) entitled “Pottery and People” show

an interconnected relationship between pottery and people from around the

world. Several researchers have given their views on different aspects of pottery,

such as manufacturing, production, distribution, consumption, specialization, and

standardization. The book is a blend of varieties of pottery cultures from different

parts of the world, and people of tremendous differences who are involved in

pottery-making culture are introduced. It shows how pottery is integral to people

belonging to certain castes and tribes.

Additionally, the insertion sort algorithm was used in this study. It is a

sorting algorithm that places an unsorted element at its suitable place in each

iteration. It can be used to insert product and their information. The updated

information will quickly be inserted through this approach. Aside from that, the

comb sort algorithm was also used. It is an in-place sort algorithm that repeatedly

reorders different pairs of items. This algorithm can be applied in the search

button of the system, wherein it is easy for the user to search for the product.

9
 Furthermore, the first-in and first-out algorithms were used too. It is a

method for handling data structures where the first element is processed first,

and the newest element is processed last. This algorithm allows the system to

decide which transaction is first accommodated or served and which will be the

first to go out.

This study is anchored with a legal foundation in the DTI-DOH-DA Joint

Administrative Order No.01 series of 2008 entitled “Rules and Regulations for

Consumer Protection in a Transaction Covered by the Consumer Act of the

Philippines Means Under the E-Commerce Act (R.A. 8792)” mandatorily requires

that all retailers, sellers, distributors, suppliers or manufacturers engaged in

electronic commerce with consumers must ensure compliance with the

requirements for safe and good quality of devices under Title II of the R.A. 7394.

Therefore, all concerned establishments are strongly reminded that the online

selling of medical devices and supplies without the corresponding authorizations

issued by the FDA is strictly prohibited. Also, the public is advised not to

purchase unregistered or violative medical devices, and supplies sold or offered

through online platforms. All FDA Regional Field Offices and Regulatory

Enforcement Units are directed to conduct exhaustive monitoring of all online

platforms to ensure full compliance with this circular and to pursue and

implement immediate regulatory and enforcement actions as warranted.

[11:2021]

10
DEFINITION OF TERMS

Admin - the person who manages the backend of the system.

Cash on delivery - payment method used in the system.

Comb sort algorithm - an in-place sort algorithm that repeatedly reorders

different pairs of items.

Clay pots - items that are available for purchase in the system.

Customer - refers to people who buy the products on sale.

E-commerce - the process of buying and selling goods and services.

First-in, First Out (FIFO) algorithm – a method for handling data structures

where the first element is processed first, and the newest element is processed

last.

Insertion sort algorithm - a sorting algorithm that places an unsorted element at

its suitable place in each iteration.

Potters - the people who design the pots to be purchased.

Pottery - the art of creating art pieces through clay pots.

Technology - a new strategy used in improving the pottery

business.

11
 Database Server

CHAPTER II

METHODOLOGY

BLOCK DIAGRAM

Log in
Log in Customer Track Order

Register Payment method

Update Cart
Wishlist View
Add to cart Products

Log in
Update Information

Manage Order

Manage customer
Insert products
Admin Manage Products

Figure 1.0 Block Diagram

12
 The block diagram illustrates the system's processes and how data flows.

The system comprises two actors: the customer and the administrator. All of the

information submitted by the registered customer is saved on the database

server.

It is necessary for the customer first to create an account to log in. When

customers log in to the system, they can select or explore products and add them

to their cart. However, if they have yet to decide to purchase the product, they

can save it on their wish list and reaccess it if they want to buy it. With that,

customers will save time browsing the product. The customers could also update

their cart if they wanted something to add or remove. After adding the order/s to

the cart, the customer may proceed to the payment method. After the payment

method, customers can access their order history by clicking on their profile first.

Then, they click the order history button, where they can see their orders.

Further, the customer can track their order using the track button, and they can

also update their profile.

The administrator, on the other hand, must first log in. The admin can see

all of the customer's registered data. He also manages the ordered product,

whether it is pending, in process, or delivered, and also update the system's

product list (added, edited, or deleted). Moreover, the admin may manage users,

which includes adding, editing, and deleting customer data and managing and

seeing customers.

13
CLASS DIAGRAM
1…*
1…*
1 1
userlog products
1
id users id
userEmail productName
userip id productPrice
loginTime name productDescription
logout email productImage1
status contactno productImage2
password productImage3
deliveryAddress shippingCharge
1 1 1 deliveryState productAvailability
deliveryCity postingDate
deliveryPincode updationDate
productreviews billingAddress
1…* 1…*
billingState
id billingCity 1…*
productId billingPincode 1
quality regDate
updationDate orders
price
value
1…* 1 id
name
1 userId
summary
productId
review
quantity
reviewDate
orderDate
paymentMethod
1 orderStatus
wishlist

id 1 1…*
1…*
userId 1
productId
postingDate orderstrackhistory
1 1
id
admin 1 orderId
status
id remark
username postingDate
password 1
creationDate
updationDate

Fig. 2.0 Class Diagram

14
PROJECT MANAGEMENT

Materials and Resources

The following are the materials and resources needed to create the

website. This includes the materials that are needed for the circuit and

documentation.

Materials/Resources Quantity Cost in ₱

Printer (Epson L20) 1 4, 000.00

Ink 178.00

Bond paper 500 sheets 185.00

Laptop (Acer) 1 17,000.00

Flash drive 16 GB 1 500.00

Prepaid Load (Internet) 5000.00

Folder 8.00

Metal Clip 2 pcs. 2.00

Fastener 2 pcs. 2.00

Android phone 7,000.00

Total Cost 33, 875.00

Table 2.0 Material and Resources

Printer (Epson L20) – It has a nominal voltage AC 120/230 V, a

frequency of 50/60 Hz, and a power consumption operational of 10 watts. The

15
Epson L20 brings speedy performance with low turning costs. They are used for

printing the materials necessary to build the system’s documentation.

Ink – It is a gel, sol, or solution that contains at least one colorant, such as

a dye or pigment, and is used to color a surface to produce an image, text, or

design.

Bond paper – is where the documentation is written and needed for

printing.

Laptop (Acer) - Acer Aspire is a Windows 10 laptop with a 15.60-inch

display that has a resolution of 1920x1080 pixels. A Core i7 processor powers it

and comes with 8GB of RAM. The Acer Aspire packs 1TB of HDD storage.

Graphics are powered by Intel HD Graphics 620. Connectivity options include

Wi-Fi 802.11 ac, with 3 USB ports (2 x USB 2.0, 1 x USB 3.0), HDMI Port, Multi

Card Slot, Headphone and Mic Combo Jack, and RJ45 (LAN) ports.

Flash Drive 16 GB- A flash drive is a small, portable storage device that

connects to computers and other devices using a USB Type-A plug built into the

drive. Flash drives work similarly to solid-state drives or SSDs, and some call

them SSDs. However, SSDs are typically not portable.

Android Phone Realme C15 has a quad rear camera setup and is

powered by a 6,000mAh battery with 18W Quick Charge support. The phone

runs on Android 10-based company's proprietary Realme UI and has a 6.5-inch

HD+ display with 720 x 1,600 pixels resolution.

Internet (40 Mbps) – 40 MBps downloads 5MB a second. It can get a

700MB standard definition movie at full speed in 2 minutes and 20 seconds. It is

16
a system architecture that has revolutionized communications and methods of

commerce by allowing various computer networks around the world to

interconnect.

Operating System (Windows 10 64-bit) –Windows 10 is a Microsoft

operating system for personal computers, tablets, embedded devices, and the

internet. Windows 10 features built-in capabilities that allow corporate IT

departments to use mobile device management (MDM) software to secure and

control devices running the operating system. Moreover, it established a user

interface and executed and provided services or application software.

XAMPP Database Server –is a free and open-source cross-platform web

server solution stack package developed by Apache Friends, consisting mainly of

the Apache HTTP Server, MariaDB database, and interpreters for scripts written

in PHP and Perl programming languages. It is where all the data from the system

is saved.

Atom – it is a concurrent programming language intended for embedded

applications. Atom features compile-time task scheduling and generates code

with deterministic execution time and memory consumption, simplifying worst-

case execution time analysis for applications that require hard real-time

performance.

17
 GANTT CHART
TASKJan
Feb
March
April
May
June
July
1234123412341234123412341234Submission of Thesis 1 TitleTitle ApprovalTitle
HearingPlanningDesigningDevelopmentTestingDocumentationRevisingFinalizing
Table 2.1 Gannt Chart

18

Table 2.0 Gannt Chart

PROTOTYPE DESIGN

Preview 1.0 Home Page

Preview 2.0 Footer

19
Preview 3.0 Product Page

Preview 4.0 Product Details

20
 Preview 5.0 About Us Page

Preview 6.0 Sign-in & Sign-up Page

21
Preview 7.0 Forgot Password Page

Preview 8.0 Customer Homepage

22
 Preview 9.0 Customer Wishlist

Preview 10.0 Customer Shopping Cart

23
Preview 11.0 Customer Billing & Delivery Address Information

Preview 12.0 Customer Payment Method

24
Preview 13.0 Customer Order History

Preview 14.0 Customer Tracking Order

25
 Preview 15.0 Customer Profile

Preview 16.0 Customer Pending Orders

26
Preview 17.0 Customer Track Order

Preview 18.0 Admin Login

27
 Preview 19.0 Admin Dashboard

Preview 20.0 Admin Manage Today’s Orders

28
 Preview 21.0 Admin Manage Pending Orders

Preview 22.0 Admin Manage In-Process Orders

29
Preview 23.0 Admin Manage Delivered Orders

Preview 24.0 Admin Manage Users

30
Preview 25.0 Admin Insert Products

Preview 26.0 Admin Manage Products

31
Preview 27.0 Admin Profile

32
SUBSYSTEM DESIGN

users

[New user] = add_new_info

id
name
email
contactno
password
deliveryAddress
deliveryState
deliveryCity
deliveryPincode
billingAddress
billingState
billingCity
billingPincode
regDate
updationDate

New Account

Customer

Fig. 3.0 Customer Registration

33
 users

[Customer login] = customer_login

email
password

Login Successfully / Unsuccessfully

Customer

Fig. 4.0 Customer Login

34
 users

[Customer Reset Password] =

customer_reset_password

email
contactno
password

Display Validation

Customer

Fig. 5.0 Customer Reset Password

35
 products

[Product] = product_info

id
productName
productPrice
productDescription
productImage1
productImage2
productImage3
shippingCharge
productAvailability
postingDate
updationDate

Product Information

Customer

Fig. 6.0 Customer View Product

36
 products orders

[Product] = product_info

[Add to cart] =
add_to_cart

id
productName
productPrice
productDescriptio
n id
productImage1 userId
productImage2 productId
productImage3 quantity
shippingCharge orderDate
productAvailability paymentMethod
postingDate orderStatus
updationDate

Added Product to Cart

Customer

Fig. 7.0 Customer Add to Cart

37
 orders orders

[Cart] = view_cart

[Payment] = payment

id
userId
productId
quantity
orderDate id
paymentMethod userId
orderStatus productId
quantity
orderDate
paymentMethod
orderStatus

Checkout Payment

Customer

Fig. 8.0 Customer Checkout Payment

38
 orders

[View order history] = view_order_history

id
userId
productId
quantity
orderDate
paymentMethod
orderStatus

Display Order History Information

Customer

Fig. 9.0 Customer Order History

39
 users

[View profile] = view_profile

id
name
email
contactno
password
deliveryAddress
deliveryState
deliveryCity
deliveryPincode
billingAddress
billingState
billingCity
billingPincode
regDate
updationDate

Display Profile Information

Customer

Fig. 10.0 Customer View Profile

40
 users

[Update profile] = update_profile

id
name
email
contactno
password
deliveryAddress
deliveryState
deliveryCity
deliveryPincode
billingAddress
billingState
billingCity
billingPincode
regDate
updationDate

Updated Profile Information

Customer

Fig. 11.0 Customer Update Profile

41
 users

[Update Password] = update_password

id
name
email
contactno
password
deliveryAddress
deliveryState
deliveryCity
deliveryPincode
billingAddress
billingState
billingCity
billingPincode
regDate
updationDate

Updated Password

Customer

Fig. 12.0 Customer Update Password

42
 users

[Update Billing Address] =

update_billing_address

id
name
email
contactno
password
deliveryAddress
deliveryState
deliveryCity
deliveryPincode
billingAddress
billingState
billingCity
billingPincode
regDate
updationDate

Updated Billing Address

Customer

Fig. 13.0 Customer Update Billing Address

43
 users

[Update Delivery Address] =

update_delivery_address

id
name
email
contactno
password
deliveryAddress
deliveryState
deliveryCity
deliveryPincode
billingAddress
billingState
billingCity
billingPincode
regDate
updationDate

Updated Delivery Address

Customer

Fig. 14.0 Customer Update Delivery Address

44
 orders

[View pending order] = view_pending_order

id
userId
productId
quantity
orderDate
paymentMethod
orderStatus

Display Pending Order Information

Customer
Fig. 15.0 Customer View Pending Order

wishlist

[View Wish Lists] = view_wish_lists

id
userId
productId
postingDate

Display Wishlist Information

Fig. 16.0 Customer View Wishlist

Customer

45
 ordertrackhistory

[Track order] = track_order

id
orderId
status
remark
postingDate

Display Track Order Information

Customer

Fig. 17.0 Customer Track Order

admin

[Admin login] = admin_login

username
password

Login Successfully / Unsucessfully

Admin
Fig. 18.0 Admin Login

46
 admin

[Update profile] = update_profile

id
username
password
creationDate
updationDate

Updated Admin Profile

Admin

Fig. 19.0 Admin Update Profile

admin

[Update password] = update_password

id
username
password
creationDate
updationDate

Updated Admin Password

Admin
Fig. 20.0 Admin Update Password

47
 orders

[Update today’s orders] = update_today’s_orders

id
userId
productId
quantity
orderDate
paymentMethod
orderStatus

Display Updated Today’s Orders Information

Admin

Fig. 21.0 Admin Update Today’s Orders

orders

[Update pending orders] = update_pending_orders

id
userId
productId
quantity
orderDate
paymentMethod
orderStatus

Display Updated Pending Orders Information

Admin
Fig. 22.0 Admin Update Pending Orders

48
 orders

[Update in-process orders] = update_in-process_orders

id
userId
productId
quantity
orderDate
paymentMethod
orderStatus

Display Updated In-Process Orders Information

Admin

Fig. 23.0 Admin Update In-Process Orders

orders

[Update delivered orders] = update_delivered_orders

id
userId
productId
quantity
orderDate
paymentMethod
orderStatus

Display Updated Delivered Orders Information

Admin Fig. 24.0 Admin Update Delivered Orders

49
 products

[Insert Product] = insert_product

id
productName
productPrice
productDescriptio
n
productImage1
productImage2
productImage3
shippingCharge
productAvailability
postingDate
updationDate

New Product Added

Admin

Fig. 25.0 Admin Insert Product

50
 products

[Update Products] = update_products

id
productName
productPrice
productDescriptio
n
productImage1
productImage2
productImage3
shippingCharge
productAvailability
postingDate
updationDate

Product Updated

Admin

Fig. 26.0 Admin Update Product

51
 products

[Remove Product] = remove_product

id
productName
productPrice
productDescriptio
n
productImage1
productImage2
productImage3
shippingCharge
productAvailability
postingDate
updationDate

Product Remove

Admin

Fig. 27.0 Admin Remove Product

52
PROGRAM FLOWCHART

Start

Sign Up

Enter information (full

name, email address, False
contact number,
password, confirm
password)

If data
entered is
valid

True

Account has been created

Save customer
information in
database ‘users’

.
End

Fig. 28.0 Customer Registration

53
 Start

Login (enter username

and password)

False
Check if fields are
valid?

True
Retrieve customer
information (email &
password) from ‘users’
table database

If email &
password equal to False
email & password
from ‘users’ table
database

True

Home Interface

End

Fig. 29.0 Customer Login

54
 Start

Sign in Page

Click forgot password

Reset Password
False (Enter email, contact,
password, confirm
password)

If new password
& confirm
password is
equal

True

Password Reset Successfully

Reset password save to

database table ‘users’

End

Fig. 30.0 Customer Reset Password

55
 Start

Login

Home Interface

All Products

Retrieve data from

the database table
‘products’

View products (products

name, price, description,
product image1, product
image2, product image3,
shipping charge, product
availability)

End

Fig. 31.0 Customer View Product

56
 Start

Login

Homepage

Select All Products

Retrieve data from

the database table
‘products’

Choose Product

False
Do you want to
add this cart?

True

View My Cart Details

END

Fig. 32.0 Customer Add to Cart

57
 Start

Login

Home Interface

Proceed to My Cart

View My Cart Details

Do you want to False

check out?

True

Submit payment method

(Cash on delivery)

Save payment method in

‘orders‘ table in Database

End

Fig.33.0 Customer Checkout Product

58
 Start

Login

Home Interface

Proceed My Account

Order History

Retrieve data from

the database table
‘orders’

View product information

(image, product name,
quantity, price per unit,
delivery charge, grand total,
payment method, order date)

End

Fig. 34.0 Customer View Order History

59
 Start

Login

Home Interface

Proceed My Account

Retrieve data from

the database table
‘users’

View profile (name, email

address, contact number)

End

Fig. 35.0 Customer View Profile

60
 Start

Login

Home Interface

Proceed My Account

Update profile
Retrieve data
(fullname, mobile
from the database
number)
table ‘users

False
Check
fields if
valid

True

False

Check if id == True
Save changes to
id from users users table in the
table in database
database

End

Fig. 36.0 Customer Update Profile

61
 Start

Login

Home Interface

Proceed My Account

False Update password (current password,

new password, confirm password)

False

If current password equal to

current password from ‘users’
table database

True

If new password equal to

confirm password

True

Password Changed Successfully!!

Update password to database table ‘users’

End

Fig. 37.0 Customer Update Password

62
 Start

Login

Home Interface

Proceed My Account

Update billing
address (billing
Retrieve data
address, billing
from the database
state, billing city,
table ‘users
billing pin code)

False
Check
fields if
valid

True

False
Save billing
Check if id == True information to
id from users database table
table in ‘users’
database

End

Fig. 38.0 Customer Update Billing Address

63
 Start

Login

Home Interface

Proceed My Account

Update delivery
address (delivery
Retrieve data
address, state,
from the database
delivery city,
table ‘users
delivery pin code)

False
Check
fields if
valid

True

False
Save delivery
Check if id == True information to
id from users database table
table in ‘users’
database

End

Fig. 39.0 Customer Update Delivery Address

64
 Start

Login

Home Interface

Proceed My Account

Pending Order

Retrieve data from

the database table
‘orders’

View product information

(image, product name,
quantity, price per unit,
delivery charge, grand total,
payment method, order date)

End

Fig. 40.0 Customer View Pending Order

65
 Start

Login

Home Interface

Proceed Wishlist

Retrieve data from

the database table
‘wishlist’

View wishlist product (image,

product name, price per unit)

End

Fig. 41.0 Customer View Wishlist

66
 Start

Login

Home Interface

Proceed to Track Order

Retrieve data from the

database table ‘orders’

False Enter (order id,

registered email)

If entered
information
is valid

True

View product information (image,

product name, quantity, price per unit,
delivery charge, grand total, payment
method, order date)

End

Fig.42.0 Customer Track Order

67
 Start

Login (enter username

and password)

False
Check if fields are
valid?

True
Retrieve admin
information (username &
password) from ‘admin’
table database

If username &
password equal to
False
username &
password from
‘admin’ table
database

True

Dashboard

End

Fig. 43.0 Admin Login

68
 Start

Login

Dashboard

Proceed My Profile

Update profile Retrieve data

(username) from the database
table ‘admin’

False
Check
fields if
valid

True

False
Update admin
Check if id == True information from
id from admin the database
table in table ‘admin’
database

End

Fig. 44.0Admin Update Profile

69
 Start

Login

Dashboard

Proceed My Profile

False Update password (current password,

new password, confirm password) False

If current password equal to

current password from ‘admin’
table database

True

If new password equal to

confirm password

True

Your password successfully changed

Update password to database table ‘admin’

End

Fig. 45.0 Admin Update Password

70
 Start

Login

Dashboard

View Today’s Order detail False

Retrieve Pending order

info from ‘orders’ table in
database

View pending order info (id, name,

Email/contact, Delivery address,
product, quantity, amount, order date)

If id== to the
orders id in
database

True

Update order detail (Order

status, and Remark)

Today’s Order Updated

End

Fig. 46.0 Admin Update Today’s Orders

71
 Start

Login

Dashboard

View Pending Order detail False

Retrieve Pending order

info from ‘orders’ table in
database

View pending order info (id, name,

Email/contact, Delivery address,
product, quantity, amount, order date)

If id== to the
orders id in
database

True

Update order detail (Order

status, and Remark)

Pending Order Updated

End

Fig. 47.0 Admin Update Pending Orders

72
 Start

Login

Dashboard

View In-Process Order detail False

Retrieve Pending order

info from ‘orders’ table in
database

View pending order info (id, name,

Email/contact, Delivery address,
product, quantity, amount, order date)

If id== to the
orders id in
database

True

Update order detail (Order

status, and Remark)

In-process Order Updated

End

Fig.48.0 Admin Update In-process Orders

73
 Start

Login

Dashboard

View Delivered Order detail False

Retrieve Pending order

info from ‘orders’ table in
database

View pending order info (id, name,

Email/contact, Delivery address,
product, quantity, amount, order date)

If id== to the
orders id in
database

True

Update order detail (Order

status, and Remark)

Delivered Order Updated

End

Fig. 49.0 Admin UpdateDelivered Orders

74
 Start

Login

Dashboard

Proceed to Manage Users

Retrieve users’ information

from the database table
‘users’

View users (name,email, contact number,

delivery address, billing)

Delete user
information (name,
email, contact
number, delivery
address, billing

False True
Delete user information from the
database table ‘users’

End

Fig. 50.0 Admin Manage Users

75
 Start

Login

Dashboard

Proceed to Insert Products

Fill the needed

information in inserting
product (Product name,
Price, Description, False
delivery charge, product
availability, product
image)

If product
information is valid

True

Product Added Successfully

Save product information

to database table
‘products’

End

Fig. 51.0 Admin Insert Products

76
 Start

Login

Dashboard

View product info

Update product
information (Product
name, Product price, Retrieve product
product description, information from
availability, delivery the database
charge, image) table ‘products’

False
Check
fields if
valid

True

False
Update product
Check if id == True information from
id from the database table
products table ‘products’
in database

End

Fig. 52.0 Admin Update Product

77
 Start

Login

Dashboard

View product info

Retrieve products
information from the
database table ‘products’

View product details (Product name,

Product price, product description,
availability, delivery charge, image)

Delete product
details (Product
name, Product price,
product description,
availability, delivery
charge, image)

False
True
Delete product information from the
database table ‘products’

End

Fig. 53.0 Admin Remove Product

78
TESTING AND DATA GATHERING

Testing

The study employed two questionnaires, one for testing the system's

usability and the other for testing the website, both of which were created by the

researcher. The researcher used the Lewis, J. R. questionnaire for system

usability and the IBM Computer Usability Satisfaction Questionnaires:

Psychometric Evaluation and Instructions for Use. There are 19 items or

indications in this questionnaire, which can be found in Appendix A.

Respondents, were asked to score the system’s utility on a scale of 1 to 7 to

indicate their level of agreement or disagreement.

Table 2.2 Interpretative Guide for System Usability

Scale Range Description Interpretation

Strongly The respondent strongly believed in the
7 6.16 – 7.00
Agree usability of the system.
The respondent believed in the usability
6 5.30 – 6.15 Agree
of the system.

Tend to The respondent tends to believe in the

5 4.44 – 5.29
Agree usability of the system.
Neither
The respondent is neutral in trusting that
4 3.58 – 4.43 Agree nor
the system is usable.
Disagree
Tend to The respondent tends not to trust that the
3 2.72 – 3.57
Disagree system is usable.

The respondent believes that the system

2 1.86 – 2.71 Disagree
is not usable.

Strongly The respondent strongly believed that the

1 1.00 – 1.85
Disagree system is not usable.

79
 The researcher, on the other hand, used the Massachusetts Institute of

Technology's Web Usability Survey to assess the website's usability in the areas

of navigation, functionality, user control, language, and content, online help and

user guides, system and user feedback, consistency, error prevention and

correction, and architectural and visual clarity. The questionnaire can be found in

Appendix B. There are 43 items in this questionnaire: five (5) for navigation, three

(3) for functionality, five (5) for user control, seven (7) for language and content,

six (6) for online help and user guides, three (3) for consistency, seven (7) for

error prevention and correction, and seven (7) for architectural and visual clarity.

Respondents were asked to rate each item on a scale of 1 to 5 to indicate their

agreement or disagreement with the website’s usefulness.

Table 2.3 Interpretative Guide to the Web Usability

Scale Range Description Interpretation

The respondents strongly believe and are
confident that the website is excellent in
5 4.21 – 5.00 Excellent
all aspects of design, development, and
implementation.
The respondents believe and are
confident that the system is very usable.
They are also confident that if ever the
Very
4 3.41 – 4.20 website may have minor inconsistencies
Good
and aesthetic issues, these are
manageable and will not affect the
performance of the proposed system.
The respondents believe and are
confident that the system is usable. They
are also confident that if ever the website
3 2.61 – 3.40 Good
may have problems; these are non-critical
and will not cause major confusion or
irritation.

80
 The respondents are neutral in trusting
that the website is usable. They also
believe that a serious problem occurring
2 1.81 – 2.60 Fair
in the website that needs a high priority to
fix can cause a user to make a significant
error.
The respondents believe that the website
1 1.00 – 1.80 Poor is not usable. They also believe that the
website has a severe problem.

. The employees of HandyPot responded to questionnaires for system

usability in Calape, Bohol, while the said establishment's customers also

answered questionnaires for web usability.

Data Gathering

The researcher's purpose was to assess the usability of the system and

website she designed. The researcher asked the owner's permission to explain

and demonstrate the system to the staff and distribute the questionnaire. After

gaining approval, the researcher gathered all of the personnel. She

demonstrated the system's functions, which included the client's information

profile, add-to-cart information, updated cart information, payment information,

and order tracking information. The researcher provided the personnel ample

opportunity to investigate the system independently. She then used

questionnaires to collect feedback on how useful the system was. The four (4)

respondents were chosen using purposeful non-probability sampling.

Further, the researcher presented the website to clients of the said

establishments for the web usability test. Customers were also given enough

time to peruse the website before being asked to fill out a web usability survey. A

81
convenience non-probability sampling method was used to select thirty (30)

people.

CHAPTER III
82
 DATA PRESENTATION AND ANALYSIS

This chapter deals with the presentation, analysis, and interpretation of

gathered data from the testing of the system and web usability of HandyPot.

SYSTEM USABILITY

It is necessary to test the system’s usability to get a sense of how users

feel about the usability of the website under test. It facilitates early evaluation of

whether the system satisfies user expectations. By doing user tests, the

researcher can identify the actual issues and determine which aspects need to

be enhanced or addressed. Moreover, for a system to be usable, it has to have a

fast connection, be well designed, have a complete description and test, be easy

to use, have friendly and meaningful information interaction, and have a unique

style. Developers consider user-friendliness to be the most significant factor for a

successful system.

Table 3.0 shows the respondent’s assessments of the system’s usability

survey. It reveals that all indicators got “Strongly Agree” descriptive ratings. This

means that the respondents highly approve of the system's function and

characteristics, indicating that it matches their expectations. In such a way, the

system is simple to use, understandable and aids in the productivity and

efficiency of their work.

Table 3.0 System Usability Result

N=4

83
 Weighte Descriptive
Indicators
d Mean Rating
1. Overall, I am satisfied with how easy it is to 7.00 Strongly Agree
use this system.
2. It was simple to use this system. 7.00 Strongly Agree
3. I can effectively complete my work using this 7.00 Strongly Agree
system.
4. I can complete my work quickly using this 6.75 Strongly Agree
system.
5. I can efficiently complete my work using this 6.75 Strongly Agree
system.
6. I feel comfortable using this system. 7.00 Strongly Agree
7. It was easy to learn to use this system. 6.75 Strongly Agree
8. I believe I became productive quickly using 7.00 Strongly Agree
this system.
9. The system gives error messages that clearly 6.50 Strongly Agree
tell me how to fix problems.
10. Whenever I make a mistake using the 6.50 Strongly Agree
system, I recover easily and quickly.
11. The information (such as online help, on- 6.50 Strongly Agree
screen messages, and other documentation)
provided with this system is clear.
12. It is easy to find the information I need. 6.75 Strongly Agree
13. The information provided for the system is 7.00 Strongly Agree
easy to understand.
14. The information is effective in helping me 6.75 Strongly Agree
complete the tasks and scenarios.
15. The organization of information on the 6.75 Strongly Agree
system screens is clear.
16. The interface of this system is pleasant. 6.50 Strongly Agree
17. I like using the interface of this system. 7.00 Strongly Agree
18. This system has all the functions and 6.50 Strongly Agree
capabilities I expect it to have.
19. Overall, I am satisfied with this system. 6.75 Strongly Agree

Composite Mean 6.78 Strongly Agree

Legend: 6.16 - 7.00 Strongly Agree 2.72 - 3.57 Tend to Disagree
5.30 - 6.15 Agree 1.86 - 2.71 Disagree
4.44 - 5.29 Tend to Agree 1.00 - 1.85 Strongly Disagree
3.58 - 4.43 Neither Agree nor Disagree

84
 Table 3.0 also shows the composite mean of 6.78, which denotes

“Strongly Agree.” This result illustrates that the system offers the respondents a

very high level of satisfaction. The system is smooth, easy to operate, effective,

clear, and evident. Aside from that, all respondents highly agreed with the

proposed system's effectiveness, functions, and ease of use.

WEB USABILITY

It is crucial to run a web usability test to see whether call-to-action buttons

and design features are effective. Through testing a website's usability, the

researcher can determine whether the website is fully functional or need some

enhancement. In this way, the researcher can improve the web's usability and

make the web more user-friendly.

Table 3.1 presents the results of the respondents’ survey on web usability.

The first component, the navigation, reveals that all indicators got “Excellent”

descriptive ratings. This means that the respondent highly believes that the

navigation component is beneficial in that site, accommodates novice to expert

users, and the link to the site’s main is coherently identified. Major parts of the

site are directly accessible from the main page, location within the site is

presented evidently, and a search function button is provided to easily find what

the client wants. For the functionality component, all indicators got “Excellent”

descriptive ratings. This states that the system’s functionality is high, indicating

that functions are clearly labeled and essential functions are available without

leaving the site. Plug-ins are only utilized if they provide value.

85
 Table 3.1 Web Usability Results
N = 30

Weighted Descriptive
Indicators Mean Rating
I. Navigation
1.1 Current location within the site is shown clearly. 4.87 Excellent
1.2 Link to the site’s main page is clearly identified. 4.90 Excellent
1.3 Major/important parts of the site are directly accessible 4.90 Excellent
from the main page.
1.4 Easy to use Search function is provided, as needed. 4.43 Excellent
1.5 Site accommodates novice to expert users. 4.93 Excellent
Composite Mean 4.81 Excellent
II. Functionality
2.1 Functions are clearly labeled. 4.97 Excellent
2.2 Essential functions are available without leaving the site. 4.87 Excellent
2.3 Plug-ins are used only if they add value 4.43 Excellent
Composite Mean 4.76 Excellent
III. User Control
3.1 Site reflects the user's workflow. 4.93 Excellent
3.2 Users can cancel any operation. 4.83 Excellent
3.3 Clear exit point is provided on every page. 4.77 Excellent
3.4 Per page loads moderately to accommodate slow 4.87 Excellent
connections.
3.5 Currently used browsers are supported. 4.80 Excellent
Composite Mean 4.84 Excellent
IV. Language and Content
4.1 Important information and tasks are given prominence. 4.67 Excellent
4.2 Information of low relevance or rarely used information is 4.63 Excellent
not included.
4.3 Related information or tasks are grouped: on the same 4.83 Excellent
page or menu or in the same area within a page.
4.4 Language is simple, without jargon. 4.87 Excellent
4.5 Paragraphs are brief. 4.80 Excellent
4.6 Links are concise, expressive, and visible—not buried in 4.70 Excellent
text.
4.7 Terms are defined. 4.60 Excellent
Composite Mean 4.73 Excellent
V. Online Help and User Guides
5.1 It is always clear what is happening on the site - - visual 4.70 Excellent
hints, etc.
5.2 Users can receive email feedback if necessary. 4.67 Excellent
5.3 Confirmation screen is provided for form submittal. 4.83 Excellent
5.4 All system feedback is timely. 4.33 Excellent
5.5 Users are informed if a plug-in or browser version is 4.50 Excellent
required.
5.6 Each page includes a “last updated” date. 4.37 Excellent
Composite Mean 4.56 Excellent

86
 Weighted Descriptive
Indicators Mean Rating
VI. Consistency
6.1 The same word or phrase is used consistently to 5.00 Excellent
describe an item.
6.2 Link reflects the title of the page to which it refers. 4.67 Excellent
6.3 Browser page title is meaningful and reflects the main 4.40 Excellent
page heading.
Composite Mean 4.69 Excellent
VII. Error Prevention and Correction
7.1 Users can rely on recognition, not memory, for 4.37 Excellent
successful use of the site.
7.2 Site tolerates a reasonable variety of user actions. 4.87 Excellent
7.3 Site provides concise instructions for user actions, 4.50 Excellent
including entry format.
7.4 Error messages are visible, not hidden. 4.90 Excellent
7.5 Error messages are in plain language. 4.93 Excellent
7.6 Error messages describe actions to remedy a problem. 4.20 VG
7.7 Error messages provide a clear exit point. 4.90 Excellent
Composite Mean 4.67 Excellent
VIII. Architectural and Visual Clarity
8.1 Site is organized from the user’s perspective. 4.93 Excellent
8.2 Site is easily scannable for organization and meaning. 4.50 Excellent
8.3 Site design and layout are redundant only when required 4.53 Excellent
for user productivity.
8.4 White space is sufficient; pages are not too dense. 4.97 Excellent
8.5 Unnecessary animation is avoided. 4.87 Excellent
8.6 Colors used for visited and unvisited links are easily seen 4.67 Excellent
and understood.
8.7 Bold and italic text is used sparingly. 4.53 Excellent
Composite Mean 4.71 Excellent
Aggregate Mean 4.72 Excellent
Legend: 4.21 - 5.00 Excellent 1.81 – 2.60 Fair
3.41 – 4.20 Very Good 1.00 – 1.80 Poor
4.44 - 5.29 Good

For the user control component, all indicators got the “Excellent.” This

means that respondents highly believe the system has a high level of user

control, implying that the site reflects their workflow so that processes are

coherent and guide users properly and currently used browsers are supported.

87
 All indicators got “Excellent” descriptive ratings for language and content.

This describes the system's proper use of language, with the highest weighted

mean of language and content and the lowest weighted mean of the system

defining its terms. With each plan, the system gives adequate explanations and

descriptions. Still, some easily understood terms are not defined to avoid

cluttering the system interface with extraneous terminology or descriptions.

For online help and user guides, all indicators got “Excellent” descriptive

ratings. The system’s online help and user guides are very good. Such a way

that the system gives the user enough time to double-check their information

before submitting the form via a confirmation dialog to avoid incorrect details, and

all system feedback is timely in terms of responding.

For consistency, all indicators got “Excellent” descriptive ratings. This

means that the system is strongly high in its consistency by using the same word

or phrase to describe an item to avoid confusion as well as browser page title is

clearly shown on the browser page and reflects on the main page heading.

For error prevention and correction, all indicators got the “Excellent”

descriptive ratings except indicator 7.6 (Error messages describe actions to

remedy a problem), which got a weighted mean of 4.20. This means that the

system’s error prevention and correction deliver error messages in plain

language successfully. It gives the client enough information on what error has

occurred. Further, the system must adequately initiate an error validation

because error messages describe actions to remedy a problem, not to add.

88
 Lastly, all indicators got “Excellent” descriptive ratings for architectural and

visual design. This implies that the system is strongly high in its architectural and

visual clarity as both are indicated with “Excellent” interpretation. The system

displayed sufficient white spaces, the pages were not too dense to visualize, and

the site was easily scannable for organization and meaning.

Table 3.2 Summary of Web Usability Evaluation

N = 30

Components of Web Usability Composite Mean Description

I. Navigation 4.81 Excellent
II. Functionality 4.76 Excellent
III. User Control 4.84 Excellent
IV. Language and Content 4.73 Excellent
V. Online Help and User Guides 4.56 Excellent
VI. Consistency 4.69 Excellent
VII. Error Prevention and Correction 4.67 Excellent
VIII. Architectural and Visual Clarity 4.71 Excellent
Aggregate Mean 4.72 Excellent
Legend: 4.21 – 5.00 Excellent 1.81 – 2.60 Fair
3.41 – 4.20 Very Good 1.00 – 1.80 Poor
2.61 – 3.40 Good

Table 3.2 shows the summary of the respondent’s survey of web usability.

It reveals that all indicators got the “Excellent” descriptive ratings. This means

that respondents highly believe that the web usability of the system is

outstanding in its design, development, and implementation. Also, it indicates

that the respondents are very satisfied with its capabilities, functions, ease of

use, and simplicity of the proposed system in terms of navigation, functionality,

89
user control, language and content, online help and user guides, consistency,

error prevention and correction, and architectural and visual clarity.

90
 CHAPTER IV

FINDINGS, CONCLUSION, AND RECOMMENDATION

Findings

Based on the survey conducted by the researcher, the respondents were

satisfied with the features and functionalities of the HandyPot system. This

digital platform enabled the valued customers of the potters in Barangay

Binogawan, Calape, Bohol, to shop for pot products online with no hassle in just

a few clicks. The customers were provided a good quality product from the

Binogawan potters, which sparked more interest online. It modified the strategy

of selling the products in physical stores to reach more clients from a broader

perspective. Furthermore, it helped the business to increase its sales by

engaging in this new method. The pottery industry is also improved by

incorporating the historical aspect of pottery that deserves to be appreciated and

enriched for a long time.

System Usability

In general, the system usability of the proposed system is outstanding in

terms of efficiency in mobilizing the strategies to elevate the selling point of the

establishment. It generated positive reviews for adapting to the more advanced

way of purchasing pot products. It is easier for the potters to introduce their

crafts to their customers and create a systematic relationship. The system is

easy to use and manipulate since the operations run smoothly. All the

information entered into the system is stored in an organized state in the

91
database. All the navigation elements are visible on the platform and are easy to

manipulate. Overall, it shows that the respondents have faith in the system’s

functionalities and capabilities, which is excellent in terms of its design, efficacy,

advancement, and execution.

For web usability, the descriptive ratings indicate that the system is

reliable in making transactions and upholds a pleasant user experience for the

customers of Binogawan potters. It serves as an avenue to connect with a

wide range of potential clients with its additional features that are precise and

accurate. Finally, it indicates that the respondents are very satisfied with its

capabilities, functions, accessibility, simplicity, and convenience.

Conclusions

Based on the findings, the researcher concludes that HandyPot is a well-

implemented and easy-to-use system. The Binogawan potters reached out to a

broader range of prospective clients through this platform. Clients from other

barangays were able to purchase the pot products easily. It saves time and effort

to pre-order the items with the emergence of this system. The alternative mode

of payment through COD is also effective since it is advantageous to prevent

untimely situations. The database secured the stored information in the system

and assured the clients of its confidentiality. The potters of Barangay Binogawan

were able to organize data, ensure accuracy in inputs, and maintain security to

foster trust among clients and the company itself. The users' data is accurately

and securely recorded in the system, and automating manual operations within

92
the establishment also improves them. Building an advanced yet economical web

channel assisted the company in increasing its sales potential. Additionally,

because customers can explore and buy things without having to go to the store

in person, it frees up time and makes it more comfortable and hassle-free for

them to do so. Besides that, users can keep track of their transactions once

they've been approved, which makes it more accessible. In contrast to the

current system, transactions will proceed swiftly and effectively, which will be

advantageous to both the user and the establishment. Additionally, the system

obtains positive feedback from the respondents, indicating that both users and

the establishment have confidence in the system's usability and that of its

website.

93
Recommendations
After a thorough development and implementation, it is highly

recommended that the "HandyPot" system be implemented to provide

customers with a more effective and reliable way of handling online orders and

payments. The administrator must also add options for an E-wallet or remittance

mode of payments if customers request to pay it instantly to ensure that their

order will be made. The establishment must modify the "HandyPot" system to

properly enforce its standard operating procedure for managing operations and

transactions to boost sales and eliminate errors in order monitoring and

payment. All files must be stored in a database like Cloud storage for record-

keeping and quick data retrieval. And to secure the establishments' data,

particularly that of their customers, in an emergency. Finally, the workforce of

"HandyPot" must be trained to use the automated system to ensure that they

have enough knowledge and information to become familiar with the newly

implemented system.

94
APPENDICES

95
 APPENDIX A

QUESTIONNAIRE FOR SYSTEM USABILITY OF HandyPot

This research questionnaire contains two parts. The first part focuses on

your demographic profile, and the second part asks for your opinion and

assessment of the system’s usability developed by the researcher.

I. Demographic Profile

Name (Optional): Sex:

Age: Civil Status:

Position: Years of Service:

II. System Usability

Interpretative Guide of the System Usability

Weight Description Acronym Interpretation

Strongly The respondents strongly believe and
7 Agree SA are confident that the system is very
usable.
6 Agree A The respondents believe and confident
that the system is usable.
5 Tend to TA The respondents tend to believe that
Agree the system is usable.
Neither The respondents are neutral in trusting
4 Agree nor N that the system is usable.
Disagree
3 Tend to TD The respondents tend not to trust that
Disagree the system is usable.
2 Disagree D The respondents believe that the
The system is not usable.
1 Strongly SD The respondents are strongly
Disagree confident that the system is not usable.

96
Instruction: Put a check mark () on the column corresponding to your

answer or response.

Criteria for System Usability SA A TA N TD D SD

(7) (6) (5) (4) (3) (2) (1)
1. Overall, I am satisfied with how easy
it is to use this system.
2. It was simple to use this system.
3. I can effectively complete my work
using this system.
4. I can complete my work quickly
using this system.
5. I can efficiently complete my work
using this system.
6. I feel comfortable using this system.
7. It was easy to learn to use this system.
8. I believe I became productive
quickly using this system.
9. The system gives error messages
that clearly tell me how to fix
problems.
10. Whenever I make a mistake using
the system, I recover easily and
quickly.
11. The information (such as online help,
on-screen messages, and other
documentation) provided with this
system is clear.
12. It is easy to find the information I need.
13. The information provided for the
system is easy to understand.
14. The information is effective in helping
me complete the tasks and scenarios.
15. The organization of information on the
system screens is clear.
16. The interface of this system is pleasant.
17. I like using the interface of this system.
18. This system has all the functions
and capabilities I expect it to
have.
19. Overall, I am satisfied with this system.

97
 APPENDIX B

QUESTIONNAIRE FOR WEB USABILITY OF HandyPot

This research questionnaire contains two parts. The first part focuses on your

demographic profile, and the second part asks for your opinion and assessment

of the usability of the web that the researcher has developed.

I. Demographic Profile

Name (Optional): Age:

Sex: Civil Status:

II. Web Usability

Interpretative Guide to the Web Usability

Weight Description Acronym Interpretatio

n
The respondents strongly believe and are
5 Excellent E confident that the website is excellent in all
aspects of design, development, and
implementation.
The respondents believe and are confident
that the system is very usable. They are also
4 Very VG confident that if ever the website may have
Good minor inconsistencies and aesthetic issues,
these are manageable and will not affect the
performance of the proposed system.
The respondents believe and confident that
the system is usable. They are also confident
3 Good G that if ever the website may have problems,
these are non-critical and will not cause
major confusion or irritation.
The respondents are neutral in trusting that
the website is usable. They also believe that
2 Fair F a serious problem occurred in the website
that needs a high priority to fix than can
cause
a user to make a significant error.
The respondents believe that the website is
1 Poor P not usable. They also believe that the
website has a severe problem.

98
Instruction: Put a check mark () on the column that corresponds to your

answer o r response.

WEB USABILITY CRITERIA E VG G F P

(5) (4) (3) (2) (1)

I. Navigation
1.1 Current location within the site is shown clearly.
1.2 Link to the site’s main page is clearly identified.
1.3 Major/important parts of the site are directly
accessible from the main page.
1.4 Easy to use Search function is provided, as needed.
1.5 Site accommodates novice to expert users.
II. Functionality
2.1 Functions are clearly labeled.
2.2 Essential functions are available without leaving the
site.
2.3 Plug-ins are used only if they add value
III. User Control
3.1 Site reflects user’s workflow.
3.2 User can cancel any operation.
3.3 Clear exit point is provided on every page.
3.4 Per page loads moderately to accommodate slow
connections.
3.5 Currently used browser is supported.
IV. Language and Content
4.1 Important information and tasks are
given prominence.
4.2 Information of low relevance or rarely
used information is not included.
4.3 Related information or tasks are grouped: on the same
page or menu or in the same area within a page.
4.4 Language is simple, without jargon.
4.5 Paragraphs are brief.
4.6 Links are concise, expressive, and visible—not buried

99
 in text.
4.7 Terms are defined.
V. Online Help and User Guides
5.1 It is always clear what is happening on the site - -
visual hints, etc.
5.2 Users can receive email feedback if necessary.
5.3 Confirmation screen is provided for form submittal.
5.4 All system feedback is timely.
5.5 Users are informed if a plug-in or browser version is
required.
5.6 Each page includes a “last updated” date.
VI. Consistency
6.1 The same word or phrase is used consistently to
describe an item.
6.2 Link reflects the title of the page to which it refers.
6.3 Browser page title is meaningful and reflects t h e
main page heading.
VII. Error Prevention and Correction
7.1 Users can rely on recognition, not memory, for
successful use of the site.
7.2 Site tolerates a reasonable variety of user actions.
7.3 Site provides concise instructions for user actions,
including entry format.
7.4 Error messages are visible, not hidden.
7.5 Error messages are in plain language.
7.6 Error messages describe actions to remedy a
problem.
7.7 Error messages provide a clear exit point.
VIII. Architectural and Visual Clarity
8.1 Site is organized from the user’s perspective.
8.2 Site is easily scannable for organization and
meaning.
8.3 Site design and layout are redundant only when
required for user productivity.
8.4 White space is sufficient; pages are not too dense.
8.5 Unnecessary animation is avoided.
8.6 Colors used for visited and unvisited links are easily
seen and understood.

100
8.7 Bold and italic text is used sparingly.

101
APPENDIX C

102
103
104
105
106
107
108
 APPENDIX D

SYSTEM USABILITY COMPUTATION

109
WEB USABILITY COMPUTATION

110
 BIBLIOGRAPHY

1. Hopcroft, J. (2006) “Introduction to Automata Theory, Languages and

Computation 3rd edition: Chapter 1 Automata Methods and the Madness p.1
URL: John E. Hpcroft, Rajeev Motwani, Jeffrey D. Ullman-Introduction to
Automata Theory, Languages and Computations-Prentice Hall (2006).pdf
2. Harkins, S. (2003) “Relational Databases: The inspiration behind this
theory.”TechnologyAdvice.URL:https://www.techrepublic.com/article/relational-
databases-theinspiration-behind-the-theory/
3. Coppola, D. (2021). “E-commerce worldwide.” Statista.com URL:
https://www.statista.com/topics/871/online-shopping/
4. Bunxo, V. (2022). “Thesis Chapter 1.pdf”. scribd.com URL:
https://www.scribd.com/document/317265451/Thesis-Chapter-1.pdf p.4

5. Statista.com (2021). “Philippines: mobile apps users by 3 rd quarter of 2020.

Statista Research Department.URL:
https://www.statista.com/statistics/1155444/philippines-mobile-apps-usage- by-
type-of-app/#statisticContainer
6. Arshiya. (2019). Social Justice Project:VariousOther
Opportunities.scribd.com.URL:https://www.scribd.com/document/441170224/
SOCIAL-JUSTICE-PROJECT
7. Feinman, G., Skibo, J. (1999). Pottery and People. University of Utah Press.
www. amazon.com
8. FDA Circular No. 2020-010. (2020.) Rules and Regulations for Consumer
Protection in transactions covered by the Consumer Act of the Philippines. URL:
https://www.fda.gov.ph/wp-content/uploads/2020/03/FDA-Circular-No.2020-
010.pdf

111
 CURRICULUM VITAE

PERSONAL DATA

Name : Jena T. Niones

Date of Birth : January 29, 1994

Place of Birth : Magsaysay,Kitaotao,Bukidnon

Age : 27

Sex : Female

Religion : Roman Catholic

Civil Status : Married

Citizenship : Filipino

Height : 5’5”

Weight : 55 kgs.

Language Spoken : English, Cebuano, Tagalog

FAMILY BACKGROUND

Father’s Name : Nestor Torregosa

Mother’s Name : Remegia Torregosa

EDUCATIONAL ATTAINMENT

Elementary : Tabok Elementary School

Tabok,Danao, Bohol

2005-2006

112
Secondary : Cantubod High School

Cantubod, Danao, Bohol

2009-2010

Tertiary : Bohol Island State University Calape Campus

San Isidro, Calape, Bohol

2020-2021

WORK EXPERIENCE

Sales Crew : E&B Foods Inc.

Cebu City

November 2012 - May 2013

Sales Agent : Ayala Department Store (Apparel)

Ayala, Cebu City

July 2013 - January 2014

113