Villaba, Leyte Livestock Farmers, Buyer/Consumer Marketplace System

A Capstone Project Proposal

Presented to the

Faculty of Bachelor of Science in Information Technology

Computer Studies Department

Eastern Visayas State University – Ormoc City Campus

In partial Fulfillment

of the Requirements for the Degree of

Bachelor of Science in Information Technology

by:

Catalonia, Christian Joy L.

Catalonia, Roldan L.

Baylosis, Mary Grace D.

Engr. Joseph Jaymel S. Morpos, MSIT

Capstone Project Adviser

November 2022

i
Abstract
Mobile Application is the most recent system which is slowly taking the marketplace
nowadays, this raises the professional interest due to its impact on further development of how
application boosts the field of e-marketing on the aspect of global economy and networks. Mobile
application has the potential to become the substitute of traditional marketing. As proponents gathered
information, they have found out that traditional marketing costs a lot of time and effort which is
leading to high losses to the merchants causing inconvenience, limited access and high maintenance.
The proponents came up with an idea of upgrading the traditional marketing style into an electronic
marketing by building a mobile application system which has features that intends to improve the life
of merchants and the consumer.
Through the development of this app, this renders high productivity and convenience with
high profit margin. In conclusion, the Livestock Farmers, Buyer/Consumer Marketplace System is a
functional system that meets the set targets and specifications that will provide better and more
advantageous service. The following enhancements are suggested by the proponents to improve the
system: payment gateway, subscription fee, and lastly is the inclusion of big livestock types such as
buffalo and cow.

ii
Table of Contents
Abstract…………………………………………………………………………………………….…..i
1.0 Capstone Project Description………………………………………………………………….…1
1.1 Overview of the Current State Technology/Background of the Study…………………….…..1
1.2 Capstone Project Objectives……………………………………………………………………...2
General Objectives……………………………………………………………………….……2
Specific Objectives………………………………………………………………………….…2
1.3 Scope and Limitation of the Project..............................................................................................3
1.4 Significance of the Capstone Project…………………………………………………………….3
2.0 Review of Related Literature……………………………………………………………….…..4-5
3.0 Conceptual Framework……………………………………………………………………….…..6
4.0 Mobile Application Marketplace System for Backyard/Federation Livestock Raisers in
Villaba………………………………………………….………………………………………………7
4.1 System Overview…………………………………………………………………………….......7-8
4.2 System Objectives………………………………………………………………………….……...8
4.3 System Functions...................................................................................................................……..8
Administrator…………………………………….………………………………..….…….9-12
Merchant……………………………………………………………………………......…11-18
Consumer/User……………………………………………………………………….…...12-18
4.4 System Scope and Limitation…...................................................................................................19
Scope…………………………………………………………………………….….…….….19
Limitation….............................................................................................................................19
4.5 Physical Environment and Resources…………………………………………………........19-20
Hardware Resources……………………………………………………………….………...19
Software Resources…………………………………………………………………….….....20
4.6 Architectural Design………………………………………………………………………….…21
Functional Decomposition Diagram…………………………………………………….…...21
System Object Modeling………………………………………………………………….…………22
Use Case Diagram………………………………………………………………….………...22
Use Case Diagram for Administrator……………………………………………….…….….23
Use Case Diagram for Canteen Owner…................................................................................23
Use Case Diagram for Member…………………………………………………….…….…..24
Data Flow Diagram……………………………………………………………………….…….…...25
Program Flowchart………………………………………………………………….………...…….26

iii
System Flowchart…........................................................................................................................26-
31
Data Design...........................................................................................................................................32
Entity-Relationship Design.......................................................................................................32
Data Dictionary...............................................................................................................................33-35
5.0 Design and Implementation Issues...............................................................................................36
Design Issue..............................................................................................................................36
Implementation Issue................................................................................................................36
6.0 Results and Observations..............................................................................................................37
System Testing.....................................................................................................................37-
38
Integration Testing...............................................................................................................38-40
Acceptance Testing..............................................................................................................40-43
7.0 Conclusions and Recommendations.............................................................................................44
Appendix A...........................................................................................................................................45
Data Flow Diagram...................................................................................................................45
Program Flowchart..............................................................................................................46-51
Appendix B...........................................................................................................................................52
Conceptual Framework........................................................................................................52-53
Appendix C..........................................................................................................................................54
Web Application Diagram.......................................................................................................54
Appendix D..........................................................................................................................................55
System Architecture.................................................................................................................55
Appendix E..........................................................................................................................................56
Appendix F.....................................................................................................................................57-59
Appendix Resource.............................................................................................................................60
Personal Vitae…………………………………………………………………..………..…………

iv
List of Tables
Table 4.6.16 Data Dictionary for Administrator....................................................................................32
Table 4.6.17 Data Dictionary for Merchant……...................................................................................32
Table 4.6.18 Data Dictionary for User...................................................................................................33
Table 4.6.19 Data Dictionary for Posts…..............................................................................................33
Table 4.6.20 Data Dictionary for Sold Products....................................................................................34
Table 6.0.21 System Testing............................................................................................................36-37
Table 6.0.22 Integration Testing…………...........................................................................................37
Table 6.0.23 Forgot Password Generated Email....................................................................................38

Table 6.0.24 Registration Email Confirmation via

Email…………......................................................38
Table 6.0.25 Transaction Logs………...................................................................................................38
Table 6.0.26 Manage Account...............................................................................................................38
Table 6.0.27 Manage Request……........................................................................................................39

v
List of Figures
Figure 4.3.0 System Functions................................................................................................................8
Figure 4.3.1 Login Authenttication.........................................................................................................9
Figure 4.3.2 Sign Up for Merchant........................................................................................................10
Figure 4.3.3 Reset Password for Admin................................................................................................11
Figure 4.3.4 Admin Dashboard..............................................................................................................12
Figure 4.3.5 User’s & Merchant login authentication…………….
………………………………………….13
Figure 4.3.6 User’s Registration Process...............................................................................................14
Figure 4.3.7 User’s Password Recovery................................................................................................13
Figure 4.3.8 User & Merchant Side Dashboard……………………………………………………….13
Figure 4.3.9 User & Merchant Main Dashboard / Posted Livestock.....................................................14
Figure 4.3.10 User & Merchant Posting/Listing……………................................................................14

vi
 1.0 Capstone Project Description

1.1 Overview of the Current State of Technology / Background of the Study

One of the primary forces behind national development and one of the Philippine economy's
supporting forces is agriculture. The primary source of income for the majority of Filipino families in
rural areas of the Philippines is agriculture, specifically livestock raising. The traditional
backyard/federation raisers, who account for over 80% of the country's livestock population, dominate
the Philippine livestock business (Posas et al., 1995). The Philippines is also known for having the
highest per capita meat consumption in South East Asia, creating a sizable market for cattle farmers
there.
According to Mr. Renato N. Casas (2022), the director of the agriculture office of the
municipality of Villaba, a town in the province of Leyte whose economy is heavily dependent on
agriculture, with livestock farming accounting for 30% of the 3,200 farmers there. Several farmers are
hesitant to get involved in livestock raising despite the large number of backyard and federation
livestock raisers in the town for the following reasons: 1.) lack of direct access to customers or
consumers. 2.) a protracted marketing process for livestock that makes it more expensive for livestock
farmers to transport and store their animals, which results in a loss. According to a study by Dana et
al. (2021), some farmers are ceasing operations due to low profitability in the absence of an efficient
marketing plan.
Due to the challenges with the current traditional marketing system, a new marketing system
must be implemented. It is possible to establish an organized market called the "Electronic
Marketplace" in the area of agriculture, specifically in the trading of animals (Strzbicki, Dariusz,
2015). With its acceptance, the way the traditional market is structured and how its rules are applied
will change. facilitating hassle-free transactions by establishing remote negotiations that do not
require the buyers' or sellers' physical presence.

1
1.2 Capstone Project Objectives
1.2.1 General Objective
Creating a mobile application marketplace system for Villaba's livestock farmers .
1.2.2 Specific Objectives
The specific goal of this project is to develop the following:

 In Marketing Pigs, remove the storage and transportation costs.

 Create a direct line of communication between farmers and consumers.

2
1.3 Scope and Limitations of the Project
This study will concentrate on the issue of how to sell cattle directly to purchasers or
consumers while making significant profits, which is a challenge encountered by 960 livestock raisers
in Villaba, Leyte. The study's goal is to find ways to improve the community's current cattle
marketing system. Knowing the location of livestock farmers, providing the number of livestock
raised in backyards or by federation raisers, and gathering data on the traditional marketing strategy
employed by livestock farmers will be the main focuses of the study. The study will exclude,
however, providing for livestock farmers outside of Villaba and learning about their earnings.

1.2 Significance of the Capstone Project

Agriculture is a field that is expanding, and it is urgently necessary to create a marketplace

system that will enable quick and easy transactions. The Marketplace System will assist in lowering
the expenses of transport and storage, providing significant earnings to the farmers in comparison to
traditional livestock marketing, enabling effective and efficient marketing of animals with high profit.
The researchers want to make it clear to the public that information technology is the most important
factor in the development and growth of society. In addition, people will be made aware of the value
of information technology in developing systems that provide relief and convenience by means of the
planned system.

3
2.0 Review of Related Literature

Coming up with something that will help in giving solutions to the growing problem of
Backyard/Federation Livestock Raisers on how to market their products in a profitable and efficient
way is crucial. According to the study of Yarte, Dana Mae et. al., (2018) entitled ‘Marketing of
Livestock in Sta. Maria, Bulacan, 2020’ of Municipal Agriculture Office in Sta. Maria, Bulacan,
majority of livestock raisers are backyard/federation raisers whose location is far from the town, and
directly transporting their produce to the market will cost them much. In addition, on the study of
Manipol, Flores et. al., (2014) it was proven that the demand of meat on the market is high, but due to
the lack of effective marketing tools that will give connection between farmers and the
buyer/consumer some farmer ended up losing profit. For this reason, some farmers in Villaba prefer
to slaughter their livestock and lend them to people because of lack access to the market. Moreover,
people usually pay in long term and it’s rare for some to pay in cash rendering farmers low profit thus
leading to some in quitting the livestock raising journey.

Moreover, the study of Kotler, Philip et. al (2021) entitled ‘Atmospherics as a Marketing
Tool’ states, there are five factors that tells why effective marketing tool is important: 1) the number
of products sold decreases, 2) the growth in company appearance also decreases, 3) the changes that
buyers/consumers want, 4) the competition is getting sharper., 5) too much expenses on marketing.
The current marketing system for agricultural products, including livestock is monopolistic and
exploitative said (Ostaev, Gogolev et. al., 2019; Sharma, Burark, 2019) on their study entitled
‘Agricultural Marketing in Rajasthan: Status, Problems and Remedies’. To avoid heavy costs on
marketing and prevent much losses on the Farmers side a marketing channel which will facilitate the
flow and transfer of products from the producer to the buyers/consumer must be created (Printezis,
Iryna & Grebitus, Carola, 2018). Same instances are happening with the Backyard/Federfation
Livestock Raisers in Villaba for the farmers are suffering with the current marketing system which is
currently being used.

To prevent more profit loss on the side of backyard/federation livestock raisers an

implementation of smooth, reliable, and fast Marketing System Platform is crucial. To do this, the
proponents will have to design a system that will perfectly fit with the farmers need, with that in
mind, the proponents will develop a mobile application that will build direct connection between
livestock raisers and buyers/consumers. In the study of Subagyo, Ardiansyah (2020) entitled
‘Prototype of Integrated Livestock Recording Application with Animal Identification and
Certification System in Kebumen’ it is mentioned that the use of mobile application system which is
equipped with a selection of cash or non-cash payment methods (transfers) that will base to the wishes
of the buyers is crucial to make payment transactions between buyers and sellers smooth and easier.
This means that in today’s world new types of transaction exists which can be integrated in building
system.

The proponents will develop a mobile phone application system is suitable for the needs of
the backyard/federation livestock raisers in connecting directly to the buyers/consumer. In contrast,
the high numbers of android users have increased which led them to grow exponentially and achieve
great success in terms of using mobile application platforms (Guerrouj & Baysal, 2016). In
addition, due to its nature of application being applied on budget friendly devices, Android is the most
common used operating system in most mobile devices and brands on which most of the
Backyard/Federation Livestock Raisers have access with. Because of this, the proponents focuses

4
only in developing application system specifically for android platform on which future project
proponents can freely apply their ideas in developing application for other Operating System platform
to give application access to all users.

Furthermore, the study of Afandi (2021) entitled ‘Impact of Mobile Payment Applications on
Business: Financial Inclusion and Innovation – The Case of Mpesa in Kibera Slum, Kenya’, states
that the adoption of Mobile Application placed on android platform surely boosted transaction and
connection between buyers/consumers and farmers. It has always been crucial to observe things
which can be used to provide comfort and improvement in the current state of marketing livestock. In
the case of Villaba’s Backyard/Federation Livestock Raisers, it was observed that farmers are deeply
disappointed on the existing marketing system of livestock due to massive profit lose. Moreover, the
study of Subagja, (2005) entitled ‘Research Initiative from Engineering Management and R & D
Management to the Management of Innovation: Innovate Success of Today and Tomorrow’, stated
that ‘the government should think of seeking effective marketing strategy for in traditional marketing,
involvement of many market participants will only make the distribution patterns long and
disorganized’. Therefore, it was just and reasonable for the Backyard/Federation Livestock Raiser in
Villaba to have its own marketplace, in fact, livestock marketing process on the Philippines should be
changed to be equipped with technology such as e-payment/cashless payment that shall provide
efficient, directed and reliable transaction between farmer and buyer/consumer. For this time, people
are already aware of the efficiency and reliability of online shopping platforms, the same idea should
not be neglected and must be applied to the livestock marketing in the country, it shall be applied
primarily as an experimental stage to give way for further observation and adjustments.

The proponents are aiming to modernize and change the traditional and manual marketing
system in selling livestock in Villaba. With Mobile Application System that will act as a Marketplace
enabling interaction between Backyard/Federation Livestock Raisers and Buyer/Consumer. The
proponents believes that a development of mobile application system with dual payment method will
provide an easier, reliable, and efficient way of buying and selling livestock for Farmers and
Buyers/Consumers in Villaba. The process of creating and delivering value to buyers/consumers by
serving them through application will give satisfaction to the buyers/consumers (Waluyo,et. al.,2018).
Technology is the way in making life easier and comfortable when talking about service (Mahzabeen,
2019). The same with the plan of the proponents which would bring reliability and efficiency to the
livestock farmers involved in Backyard/Federation Livestock Raising journey.

5
3.0 Conceptual Framework

The Livestock Raisers will utilize a mobile application system put on their phone to manage
orders and promote their livestock; buyers and consumers can also use this application to order
products such as livestock. For information on the system's architectural design, please see Appendix
B.

In partnership with the Department of Agriculture Office of Villaba, the proponents

brainstormed with the Federation of Farmers organizations in Villaba to identify the issues, the
location, and other factors that needed to be taken into account while putting the idea into action. The
proponents conducted formal interviews with the intended respondents as a method of data collection.

Additionally, the information gathered from the respondents was examined to acquire a sense
of how the project will ultimately proceed. As a result, the proponents developed the model that is
shown in Appendix B, which uses the input-process-output model to demonstrate the study's
conceptual framework.

6
4..0 Mobile Application Marketplace System for Backyard/Federation Livestock Raisers in
Villaba
The Mobile Application Marketplace System for Pig Farmers in Villaba is a Mobile
Application based system aim to build a systematic, well-planned, smooth flow, and automated
system that will cater the buying and selling of Livestock.
The following are the overall application specification and functional requirements of the software to
be developed:

 Requires the seller/merchant to upload or embed the image of any livestock/product they are
posting.
 Allow every user to register and use their active email only once.
 Requires email verification upon registration.
 Allow merchants or the Backyard/Federation Livestock Raisers to post their livestock for
sale.
 The system allows the user to order any livestock.
 Normal user can apply to become a certified merchant/Livestock Raiser provided the required
certificate from the Federation and Department of Agriculture.
 Allows communication to both Livestock Raisers and normal consumer through the supplied
contact information.
 Applies e-payment platform such as g-cash, paymaya etc. & bank transfer option.
 Admin/Developers can deny or confirm the merchant application of every user if presented
documents proves to be invalid or for any other reason.

4.1 System Overview

The following are the system’s main feature and capabilities

 Livestock Ordering
Let’s the consumer/user to view and order livestock posted for sale.

 User Registration
Any consumer who uses the app will be asked by the system to enter their registered
account and to register with the use of their active email address only once.

 Email Verification
The system sends an email verification to the email address provided by the user,
verified email will give access to the registered account.

 Livestock Posting
Allows the system to display the livestock posted by the merchant.

 Picture Uploading
Requires the merchant to upload/insert pictures of the livestock that they are posting.

 Consumer & Merchant Communication

7
 Using the system chat box, this allows the consumer/merchant to send messages to
each other for the purpose of verification and monitoring.

 Order Monitoring
Allows the customer and the merchant to have constant communication through the
presented contact information of the merchant in order to give clear update of the
order to both the merchant and consumer.

 E-payment Method/Fund Transfer

The system will present the e-wallet account or bank acct. # of the merchant for the
customer to pay before the delivery of the order.

4.2 System Objectives

The system is developed to help the Backyard/Federation of Livestock Raisers in Villaba on

selling their livestock in a fast, efficient, and reliable way, with that said, the system must meet the
following specific requirements:

 Manage or display the posting/listing of the merchant or Backyard/Federation of

Livestock Raisers.
 Allow the merchant or Backyard/Federation of Livestock Raisers to post their
livestock for sale.
 Automatically send email verification to the email address provided upon registration.
 Can upload picture of the livestock for sale.
 Consumer/user and Merchant or Backyard/Federation of Livestock Raisers can
communicate with each other.
 Can present important information of the merchant to the consumer/user. Ex: Bank
Account #, E-wallet # of the developer, address, location, and name of the farm and
its crucial members.
 Admin/Developers can confirm/deny the merchant application of any user.

4.3 System Functions

Payment Info
Livestock
Order/Purchase Details
Raiser/Merchant info.
  0.0
Administrator
Livestock   Buyers/
Product Details Customers Info  
Marketplace Customers
Livestock
  System
Raiser/Merchant
Order/Purchase Details Payment Info

Revenue
Figure 4.3.1 The Overall system function

8
 This Diagram illustrate or shows the role of each user inside the system.

Administrator’s Web-based Application

1. Login authentication.

Figure 4.3.1 System Administrator’s Web Application log in page.

The agriculture office staff or the programmer would be the only qualified individuals based on
the actual field where the system will be deployed, and they would be in charge of every merchant
application that will be accepted based on the validity of the documents they have submitted or
presented to the staff at the office. Because of this, the developers of the administrator's web
application only allowed for one administrator account. The web application log-in page for the
administrator is shown in Figure 4.3.1. It is intended to be understandable and familiar to all users.
The page requests the administrator's login password and verifies that it corresponds with the
administrator's password kept in the system's database.

9
 2. Sign up for Merchant.

Figure 4.3.2 Merchant’s Sign-Up Page.

The Market Place System administrator may register their login information in this section.
The administrator's full name must be entered. The administrator must enter their first and last names,
address, phone number, email address, and password on the page. A pop-up message stating that the
user information has been successfully registered will show after completing all the fields and
pressing the sign-up button. This just indicates that the newly registered merchant can now begin
having access to the mobile application for merchant.

10
 3. Reset password for administrator.

Figure 4.3.3 System Administrator's reset password page.

In the event that the administrator forgets the password, the password recovery option enables the
administrator to set a new password. But the administrator needs to provide the proper email address
and make sure it matches the one they used to sign up in order to modify or recover the password. The
password reset interface is depicted in Figure 4.3.3 above.

11
4. Admin Dashboard

Figure 4.3.4 Admin Dashboard Interface

The administrator can examine all of the registered/accredited merchants' details on

this page. The data shown in the dashboard is illustrated in Figure 4.3.4 above.

12
User’s & Merchant Mobile Application
1. User’s & Merchant login authentication

Figure 4.3.5 User’s and Merchant application log in screen.

The program requires the email address and password that were registered with the system for the
User and Merchant to log in. Only if the user and merchant are able to accurately enter their email and
password can they log in and utilize the application.

13
 2. User’s registration process

Figure 4.3.6 User’s registration application screen.

The user must enter all the required data that is requested in the system's input forms in order
to register or create an account. Users can only register an email once, and it is completely forbidden
to use an individual email more than once.

14
 3. User’s password recovery

Figure 4.3.7 User’s password recovery screen.

If a user forgets their password, they can generate a new one using the password recovery
option. However, the user's email address must be entered correctly and must match the email they
used to sign up in order to reset or recover their password. The password reset interface is displayed in
Figure 4.3.7 above.

15
4. User & Merchant Side Dashboard

Figure 4.3.8 User & Merchant side Dashboard.

The user and merchant information, including Full Name & Email, is displayed on
the side dashboard. This column also has other possibilities. The side Dashboard's user
interface is displayed in Figure 4.3.8 above.

16
 5. User & Merchant Main Dashboard / Posted Livestock

Figure 4.3.9 User & Merchant Main Dashboard.

There is a slight difference on the main dashboard of the normal user because they can only
see the products being set for sale and place orders for them as well as contact the merchant. The main
dashboard displays all the products being set for sale by merchants. The interface for the user and
merchant's Main Dashboard is displayed in Figure 4.3.9 above.

17
6. User & Merchant Posting/Listing

Figure 4.3.10 Merchant Listing Option

When the sell button is hit, fields that must be correctly filled out by the merchant in
order to list something for sale are displayed. The sale button's user interface may be seen in
Figure 4.3.10 above.

18
4.4 System Scope and Limitations

The town of Villaba is the location of the area where the system will be deployed,
considering the objective of the system which is to help the Backyard/Federation of Livestock Raisers
in Selling their livestock in a fast, reliable, efficient, and modest way, there will be areas that are
beyond the scope of the system. In here the scope and limitations of the systems will be discussed.

Scopes of the system:

 System accepts Agricultural products such as livestock and crops to be posted.

 Verified merchants can post their produced livestock and crops.
 The system displays the farm address/landmark and the contact # of the
merchant.
 System accepts photos uploaded by merchants.
 Any type of email address can be accepted by the system upon registration but
can only be used once.
 Normal user can apply to become a merchant by supplying/submitting the
required documents personally to the office of the admin/programmer.
 Admin can confirm or deny normal user’s application to become a
merchant/seller.

Limitations of the system:

 The system does not allow multiple system administrator’s account for it will just
ruin the systems objectives and function, also on the design of the system
administrator’s signup process, only email account of the administrator is
required to recover the password.
 Other Agricultural products such as dry goods are not supported by the system,
the system is solely developed to cater livestock and crops.
 The e-payment method being offered by the system shall be done manually by
the consumer/customer. Ex: Gcash transaction or bank transfer transaction.
 Add to cart option shall not be available for livestock grows constantly & crops
dry out unlike dry goods.

4.5 Physical Environment and Resources

There are sets of hardware and software resources including target user requirements that
are needed to implement and execute the system.

Hardware Resources

1. Smartphone (Android) – The Mobile Application System will be installed on a

mobile computing device, a smartphone, and an Android smartphone is the specific
model that must be used.
2. Desktop/Laptop (Personal Computers) – A desktop or laptop computer is an end user
computer that is made to be used by people who are not computer experts. Most people can
easily operate and get familiar with its functionalities. The system administrator will use
desktop and laptop PCs to access the web-based system administrator program.

19
 The system must meet at least the bare minimum specifications for each hardware
peripheral in order to be completely functional. Process degradation could occur as a result of
hardware needs issues.

Software Resources

1. Desktop/Laptop operating system (Windows 7 to Windows 10 version release or any

Linux distros) – The operating system for the administrator's web-based application.

2. Firebase Database – a relational database service that is used to store data.

3. Android 7 (Nougat) to Android 11 (R) Operating System – Operating system for the
farmers' and consumers'/buyers' mobile applications.

4. Browsers (Google Chrome, Mozilla Firefox, Brave, Microsoft Edge etc.) – when using the
web-based application's intended browser.

Use of the following software is necessary. A missing component could lead to system
failure and improper operation of the application.

Target User Requirements

The application requires users who will validate and process numerous data to make the
system fully functional. Therefore, users must meet these special set of skills:

1. Administrator – media and information fundamental skills prior experience with

computers and cellphones, industry knowledge, and interpersonal skills (is concerned
with working with people).
2. Merchant/Farmer – knowledge of media and information in general, understanding of
how smartphones work, expertise in his field of work, and people skills

3. Consumer/Buyer – knowledge of smartphone interaction.

In order to minimize misinformation in the workplace, administrators should first

learn about media and data information. Administrators must, if at all feasible, possess
basic, intermediate, and advanced expertise in order to engage with computers and
cellphones. Additionally, simple typing, navigation, and troubleshooting techniques
should be understood and practiced. In addition, Merchants need to have a foundational
understanding of the program in order to handle daily interactions on it. Finally,
consumers and buyers must possess the necessary skills to interact with smartphones.
Simple smartphone navigation and strong reading memory will simplify duties at hand.

4.6 Architectural Design

20
 Functional Decomposition Program

Villaba, Leyte Livestock Farmers & Buyer’s/Consumers Marketplace System

WEB BASED MOBILE-APP

MERCHANT CONSUMER

Login Login
ADMIN

Login Dashboard Dashboard

Post
Register Product
View Posted
Merchant Product
View Posted
Product
Monitor the
Order
registered users
Order
Message
Log Out
Check for Merchant
Orders via
Chat
Pay Order
Receive
Apply to be
Payment
Merchant

Logout Logout

Figure 4.6.1 Functional Decomposition Diagram

This diagram shows the full function as well as any additional activities that may be
necessary. It represents each part of the system separately to allow for a thorough analysis. It is an
illustration of the system's capabilities to go from the primary role to the supporting jobs.

Object Modeling

21
 A system object model is a digital representation of each class or entity's objects and
relationships. It depicts the elements of a software system.

Use Case Diagram

REGISTER

LOGIN

MANAGE ACCOUNT

VIEW TRANSACTION HISTORY

DASHBOARD

CONSUMER MERCHANT
EMAIL NOTIFICATION

MAKE PAYMENT

RECEIVE PAYMENT

OTHER SERVICES

LOGOUT

Administrator
Figure 4.6.2 Use Case Diagram
The relationship between the administrator, consumer, and merchant is depicted in the
diagram. It displays the many jobs and how they fit into the overall structure. Each role embodies the
system's capabilities.

LOGIN AND LOGOUT

22 UPDATE
 MANAGE ALL USERS ACCOUNTS
EDIT

DELETE

MANAGE MERCHANTS ADD NEW

MERCHANT

ANNOUNCEMENT
ADMIN

Figure 4.6.3 Use Case Diagram for Administrator

The administrator's job is depicted in the above figure. It displays the many modules and
administrator

LOGIN AND LOGOUT

POST PRODUCT

VIEW PRODUCT
LISTING/POSTING

MONITOR EVERYDAY
FOR MESSAGE ORDER

RECEIVE PAYMENT

MERCHANT RECEIVE CONFIRMATION VIA

EMAIL

VIEW TRANSACTION HISTORY

Figure 4.6.4 Use Case Diagram for Merchant

The position of the merchant is depicted in the above figure. The various modules and
functions of the merchant are displayed.

LOGIN AND LOGOUT

23
 UPDATE
MANAGE ACCOUNT
CHANGE PASSWORD

VIEW TRANSACTION HISTORY

VIEW POSTING/LISTING

ORDER PRODUCT

MEMBER
VIEW ANNOUNCEMENT

MAKE PAYMENT PAY MERCHANT

SEND MESSAGE TO THE MERCHANT

RECEIVE CONFIRMATION VIA EMAIL

REGISTRATION

Figure 4.6.5 Use Case Diagram for Consumer/User

The role of the consumer or user is depicted in the above figure. It displays the many
consumer/user modules and their functions.

24
Data Flow Diagram
It serves as a visual representation of how data moves through a system as it passes through a
process. The user logs in first, then the subsequent procedures are taken when they have accessed
their account.

Figure 4.6.6 Data flow Diagram

The image up top is a representation of the system's data flow diagram, which shows how
each entity's user flow information is represented. It displays the data flow that this system generates.

25
Program flowchart

A system program is graphically represented in a program flowchart. It demonstrates how the

project's various activities and steps fit into the overall flow of the program. To represent each type of
process, a different symbol is used.
Administrator Login

Y Merchant
Dashboard

Error Invalid
Credentials

Figure 4.6.7 Administrator Login Program Flowchart

The administrator login is depicted in the above chart. The system flow of the administrator
login is covered. The administrator must enter their email address and password to log in before they
can enter the system.

26
Administrator Dashboard, Update Users/Merchant info and Logout

Figure 4.6.8 Administrator Dashboard, Update

Consumer/Users and merchant Information and Logout Program Flowchart
The dashboard, the flowchart for updating user/consumer and merchant information, and the logout
process are all displayed in the graphic above. The dashboard, where you can edit all of the users'
information, will be immediately accessible after the administrator has entered their username and
password.

27
Manage and Search User/Merchant

Figure 4.6.9 Manage and Search User/Merchant Program Flowchart

The graphic above shows the software flow for managing user/customer and merchant
accounts. This explains how to update and alter all of the personal information of both consumers and
merchants, as well as search their emails.

28
Merchant Account

Figure 4.6.10 Merchant Account Program Flowchart

The flowchart for the merchant account program is displayed above. It features the merchant
dashboard, which displays the listing for the business, additional products listed by other businesses,
and the history of business transactions.

29
Product Selling/Posting/Listing

Figure 4.6.11 Product Selling/Posting/Listing Program Flowchart

The program flow for adding and posting products for sale is depicted in the diagram above.

Product Ordering and Payment

Figure 4.6.12 Product Ordering and Payment Program Flowchart

The flowchart for the Product Ordering and Payment feature of the other service program is
the one that is displayed above. When placing an order for a product, the customer or user should get
in touch with the seller so they can communicate, have the money sent to the seller's bank or e-wallet
account, and have the seller approve the order.

30
Consumer/User Account Login

Figure 4.6.13 Consumer/User’s Login Program Flowchart

The program flowchart for the consumer's or user's login information is depicted in the
diagram above. Before accessing the system, registration is necessary.

Merchant & User transaction Log/History

Figure 4.6.14 Merchant & User Transaction Log/History Program Flowchart

The transaction log process is depicted in the diagram above. The past transactions can be
viewed by the user and the merchant.

31
Data Design
Entity-Relationship Diagram
A model that offers a visual basis for database design is an entity-relationship diagram. This
model demonstrates the relationships between these data.

Figure 4.6.15 Entity-Relationship Diagram

The relationship of the tables in the system is depicted in the above figure. The connector
demonstrates how the tables are related to one another using their respective foreign and reference
keys.

32
Data Dictionary

This section contains a list of definitions for the database data objects that will be utilized in
the program's development. It comprises records of data attribute names that are explained by type,
size, and description.

ADMIN

Fieldname Data Type Field size Description

Email Varchar 255 Primary Account ID of

Admin
Password Varchar 255 Password for the
Account
register_date timestamp Registration Date
Table 4.6.16 Data Dictionary for Accounts

MERCHANT
Fieldname Data Type Field size Description

Email Varchar 255 Primary Account ID of

Merchant
Password Varchar 255 Merchant Account
Password
First_name Varchar 255 First Name of Merchant
Last_name Varchar 255 Last name of Merchant
Address Varchar 255 Address of Merchant
Farm Address Varchar 255 Merchant Farm Address
Phone_number Integer 20 Mobile Number of
Merchant
e-wallet accounts Varchar 255 Bank Account Number
or E-wallet Account
Information
Role Varchar 255 A system role
register_date timestamp Registration Date
Table 4.6.17 Data Dictionary for Accounts

33
USER
Fieldname Data Type Field size Description

Email Varchar 255 Primary Account ID of

User
Password Varchar 255 Password for the user
account
First_name Varchar 255 First name of User
Last_name Varchar 255 Last name of User
Address Varchar 255 Address of User
Phone_number Integer 20 Mobile Number of
User
Role Varchar 255 A system role
register_date timestamp Registration Date
Table 4.6.18 Data Dictionary for Accounts

POSTS
Fieldname Data Type Field size Description

Picture Varchar 255 Image of Products

Title Varchar 255 Name of Products

Price Varchar 255 Price of Products

Description Varchar 255 Description of
Products
Merchant_name Varchar 255 Merchant Name
Email Varchar 255 Merchant Email
Address Integer 20 Merchant Address
number Varchar 255 Mobile Number of
Merchant
Bank accounts Varchar 255 Merchant Bank
Account Number
e-wallet accounts Integer 255 Merchant E-Wallet
Accounts
posting_date timestamp Date of the Posting or
Sale
Table 4.6.19 Data Dictionary for Accounts

34
SOLD_PRODUCTS
Fieldname Data Type Field size Description

Customer_email Varchar 255 Email for customer

Merchant_email Varchar 255 Email of Merchant

Product_name Varchar 255 Product Name

product_type Varchar 255 Product Type
price Integer 255 Product Price
quantity Integer 255 Products that the
customer has
purchased in total
Amount_paid Integer 255 Total sum paid by the
customer
date_sold timestamp Sale Date of the
Product
Table 4.6.20 Data Dictionary for Accounts

35
5.0 Design and Implementation Issues
The system's developers and creators ran into some issues with the technology that was being
used, some of which are related to the system's mobile application. The following is listed:
Implementation Issue:

 There is no payment gateway available for use on the system - Customers won't
be able to make payments directly through the application. In response to the concern,
the supporters immediately added the merchant's bank details and E-wallets to the
display.

 The admin system table cannot display information from the database. – The
merchant database's contents cannot be seen in the admin system table. In order to
view the merchant's information and assist in the creation, updating, deletion, and
insertion of data, the proponents instantly embraced the firebase dashboard in
response to the problem.

Design Issue:

 Text Information Too Big – Because the displayed text is too large, the advocates
decided to reduce its size so that it would be more appealing and appealing to the
user.

 Simple Alert Message – The alert message is brief and straightforward. The alarm
message was updated by the supporters to look more appealing.

36
6.0 Results and Observations
This chapter presents, analyzes, describes, and interprets the data collected from various trial
processes in an organized and thorough way. The logging and analysis procedures seek to accurately
display the data by presenting it in an understandable format.
System Testing
System testing is a type of software testing that verifies the system that an application performs tasks
as designed. It will check every kind of user input that produces the intended output of the system.

Test
Case Testing Components Test Objectives Results
ID
Administrator can successfully log
T-1 Administrator Login Attained
in.

Administrator Fresh Administrator is successful in

T-2 Attained
Register registering.

Administrator Reset
T-3 successful password reset Attained
Password

Administrator Allow the user to explore the

T-4 Attained
Dashboard dashboard.

Administrator Create,
Add a merchant account to change
T-5 Update, Delete in Attained
any merchant information.
Merchant.

The merchant can successfully log

T-6 Merchant Login Attained
in.

Allow the merchant to explore the

T-7 Merchant Dashboard Attained
dashboard.

Merchant Fresh Admin has the ability to register

T-8 Attained
Register merchants

The ability of the merchant to

T-9 Merchant Post Product Attained
upload products with information

Merchant Check
T-10 Merchant has access to the profile Attained
Profile

The ability of the merchant to

T-11 Merchant message Attained
receive customer messages

change a product's status when it

T-12 Product Status Attained
sells

T-13 Customer Login Customer successfully logs in Attained

Customer Fresh The customer was successful in

T-14 Attained
Register registering.

37
 Allow customers to explore the
T-15 Customer Dashboard Attained
dashboard.

Customer View Customers have access to the goods

T-16 Attained
Product that merchants have posted

Customer can place product orders

T-17 Customer Order Attained
through message

Customer can send and receive

T-18 Customer message Attained
messages

T-19 Customer Profile Clients have access to profiles Attained

Customers and merchants can view

T-20 History Log Attained
the history log.

Table 6.0.21 System Testing

The result of this testing is successful. Almost all system functions are working properly as expected.

Integration Testing
Integration testing is a phase of software engineering in which software modules were
combined and tested as a group. It is meant to check the combinations of different units and their
interactions.

Module: User Account

No. Test Case Objective Test Case Output Result

1. To create account to access Log in to the The main Attained

the system. account after dashboard will
completing the be redirected to
required field. the user.
Table 6.0.22 User Account

38
Module: Forgot password generated email

No. Test Case Objective Test Case Output Result

1. To create a new password To reset your The user will Attained

for the user who has password, click get an email to
forgotten theirs. reset button reset their
password.

Table 6.0.23 Forgot Password Generated Email

Module: Registration Email Confirmation via Email

No. Test Case Objective Test Case Output Result

1. To verify the email address The administrator Email Attained

that the user or merchant will register the confirmation
provided when registering merchant users. will be sent to
the merchant.
Table 6.0.24 Notification via Email

Module: Transaction Logs

No. Test Case Objective Test Case Output Result

1. To keep data safe and view Viewing the The user can Attained
previous transactions. transaction log by view their
clicking the button. transactions
after being
redirected to
the transaction
log page.
Table 6.0.25 Transaction Logs

Module: Manage Account

No. Test Case Objective Test Case Output Result

1. To update, edit, and remove An administrator The database's Attained

users from the user account. has the power to data is
add, edit, and continually
delete users. added to,
modified, and
deleted.
Table 6.0.26 Manage Account

39
Module: Manage Request

No. Test Case Objective Test Case Output Result

1. To approve each merchant Accept every All requests Attained

application request that has merchant have been
been pending and whose application request granted, and
requirements have been that their accounts
personally presented in the includs personally created.
pending table. presented
requirements.
Table 6.0.27 Manage Request

Acceptance Testing

The end user rates and validates the software during this kind of testing. The primary goal of
this testing is the validation of the entire business flow. This section makes use of the Likert scale.
(For a questionnaire, see Appendix E.)
Farmers and consumers were enlisted to assist in the testing and data collection processes. The results
were presented in textual commentary and tabular form. A total of 15 respondents took part in the
survey, which was conducted across several sites in Villaba, Leyte.

Graphical User Interface Evaluation

Answer Number of Respondents Percentage

Yes 18 90%

No 2 10%

Total 20 100%

Table 6.0.28 Frequency distribution of question it is simple to use this application

According to Table 6.0.28, 90% of respondents who tested the program said it was easy to
use. 10% of respondents reported difficulty utilizing the

40
 Table 6.0.29 Frequency distribution of question it was easy to find the information I needed

According to Table 6.0.29, 85% of respondents believe it is simple to access the information
displayed. While 15% of the respondents struggle to locate the information they seek.

Answer Number of Respondents Percentage

Yes 16 80%

No 4 20%

Total 50 100%

Table 6.0.30 Frequency distribution of question the organization of information on the application
screen was clear
According to Table 6.0.30, 80% of respondents believe the information on display is well
organized. The organization of the information, according to 20% of the respondents, is not adequate.

Answer Number of Respondents Percentage

Yes 19 95%

No 1 5%

Total 20 100%

Table 6.0.31 Frequency distribution of question the interface of this application was pleasant
Table 6.0.31 shows that 95% of respondents were completely satisfied with the application's
user interface (UI), while only 5% were not.

Answer Number of Respondents Percentage

Yes 17 85%

No 3 15%

Total 20 100%

Answer Number of Respondents Percentage

Yes 19 95%

No 1 5%

Total 20 100%

Table 6.0.32 Frequency distribution of the question: I liked using the interface of this application
Table 6.0.36 shows that 95% of respondents enjoy using the application's user interface (UI),
while only 5% do not.

41
User Experience Evaluation

Answer Number of Respondents Percentage

Yes 8 40%

No 12 60%

Total 20 100%

Table 6.0.33 Frequency distribution of question I found the application complex to use

According to Table 6.0.33, 40% of respondents thought the application was difficult to use.
While 60% of respondents claim that the application is simple to use.

Answer Number of Respondents Percentage

Yes 12 60%

No 8 40%

Total 50 100%

Table 6.0.34 Frequency distribution of question it was easy to learn and use this application
According to Table 6.0.34, 60% of respondents find the application simple to understand and
operate. 40% of respondents claim that the application is difficult to learn.

Answer Number of Respondents Percentage

Yes 13 65%

No 7 35%

Total 20 100%

Table 6.0.35 Frequency distribution of question this application has all the functions and capabilities
I expect it to have
According to 65% of the respondents, the application has all the desired features and
functionalities, as shown in Table 6.0.35. 35% of respondents said they were still unsatisfied with the
features and abilities the application offered.

42
 Answer Number of Respondents Percentage
Yes 15 75%

No 5 25%

Total 20 100%

Table 6.0.36 Frequency distribution of question I found the various functions in this application were
well integrated
According to Table 6.0.36, 75% of respondents believe the application's features are
effectively integrated. 25% of them disagreed, though.

Answer Number of Respondents Percentage

Yes 9 45%

No 11 55%

Total 20 100%

Table 6.0.37 Frequency distribution of question I think I would need the support of a technical person
to be able to use this application
Table 6.0.37 shows that 55% of respondents do not require any assistance using the
application, while 45% of respondents need technical assistance to be able to use it.

Answer Number of Respondents Percentage

Yes 15 75%

No 5 25%

Total 20 100%

Table 6.0.38 Frequency distribution of question I would imagine that most people would learn to use
this application quickly

Table 6.0.38 shows that while 25% of respondents disagree, 75% of respondents believe that
most people would pick up on this application quickly.

Therefore, based on the information provided above, the application's proponents draw the
conclusion that the survey's general respondents accepted the application.

7.0 Conclusion and Recommendations

Conclusion

43
 The Livestock Farmers & Buyers/Consumers Marketplace System in Villaba, Leyte is a
system that complies with all the established goals and requirements. Numerous problems
emerged during the system development process, delaying even minor advancements and
virtually compromising the system's efficacy. Some of the system's features and capabilities
almost went unnoticed along the way because of the challenges the proponents faced using the
newly adopted database and programming language. In order to properly comprehend the
challenges of completing the project on time, proponents sought advice from others and on the
internet.

In general, the test results were satisfactory. The system offered more helpful and superior
service. The mentioned tasks were completed. During testing, the intended audience members offered
insightful feedback. The system will have a significant impact on the local farmers and customers
thanks to its features and elements. Farmers won't have to worry about selling their goods anymore
because a new selling channel has been established. Finally, despite the positive feedback, there is
still much that can be done to improve the system so that it can offer more services.

Recommendations
The following suggestions are solely based on how the proponents believe future researchers
can apply their findings to enhance the system:
The app needs a payment gateway first in order to have direct access to e-wallets and bank
accounts. platforms that make all users' lives easier.
The second recommendation is that the system charge a subscription fee, with the money
raised going toward future agricultural research and development.
The supporters also wished for the system to be improved so that it could accommodate other
large livestock, like cows and buffalo, since transporting and processing these kinds of livestock takes
a lot of time.

44
Appendix A
Data Flow Diagram
It serves as a visual representation of how data moves through a system as it passes through a
process. The user logs in first, then the subsequent procedures are taken when they have accessed
their account.

Data flow Diagram

45
Program flowchart

A system program is graphically represented in a program flowchart. It demonstrates how the

project's various activities and steps fit into the overall flow of the program. To represent each sort of
process, a different symbol is utilized.
Administrator Login

Y Merchant
Dashboard

Error Invalid
Credentials

Administrator Login Program Flowchart

46
Administrator Dashboard, Update Users/Merchant info and Logout

Administrator Dashboard, Update

Consumer/Users and merchant Information and Logout Program Flowchart

47
Manage and Search User/Merchant

Manage and Search User/Merchant Program Flowchart

48
Merchant Account

Merchant Account Program Flowchart

Product Selling/Posting/Listing

49
 Product Selling/Posting/Listing Program Flowchart

Product Ordering and Payment

Product Ordering and Payment Program Flowchart

Consumer/User Account Login

Consumer/User’s Login Program Flowchart

50
Merchant & User transaction Log/History
Merchant & User Transaction Log/History Program Flowchart

Appendix B
Conceptual Framework

User & Merchant

Ordering of Livestock Database

Livestock raiser’s location Merchants & Buyers/Consumer’s

info. & Location
Posting of Livestock for sale Livestock’s info. & Location
and Sold livestock’s Record
Mobile App

Admin

Managing of merchant
Application.

Web App

51
Conceptual Framework

52
 PIG FARMER/CONSUMER MARKET

PROBLEM SOLUTION

Farmer lacks direct access to pig consumer and Pig Farmers/Consumer

consumer lacks connection to the farmer, middlemen Marketplace Mobile Application
arrive creating a monopoly effect and making artificial System
price increase on the pigs being sold to the market

PLANNING
Pig Farmers/Consumer
Marketplace Mobile Application
System

DEVELOPMENT

TESTING

UNIT TESTING INTEGRATION TESTING SYSTEM TESTING

END-USERS
COMMENTS/RECOMMENDATIONS

System’s defense panel

Pig farmers DEPLOYMENT

Pig consumers

Figure 2

53
Appendix C
WEB APPLICATION ARCHITECTURE
Since it is a web-based program, it can be seen from the example below that both the web
system and the administrator are linked to the internet. All user data is entered by the administrator
into the online system, where it is then stored in the database. However, the customer and the
merchant will be using a mobile application where they can perform a variety of tasks. Merchants can
advertise their products, accept consumer communications, and provide all the information required to
complete a sale. Customers can also message merchants to place orders for the goods they see listed
by those merchants. Through the g-cash application platform, payments will be made.

Input Data

Display results ADMINISTRATOR

REQUEST

WEB SYSTEM

Consumer &
Admin

Mobile App
Database
Server

RESPONSE

54
Appendix D
SYSTEM ARCHITECTURE
The various user categories and the network-connected system are shown in the diagram
below. They are the member and the administrator. The database that holds information is on the
server.

Administrator

-Manage
Customer &
Merchant’s
Account
Server

-Consumer &
Merchant Login
& Personal
Customer & Merchant Information
-Transactions
-Manage Database
Transaction -Admin Login
-Ordering Information
-Make
Payment
-Posting
-Other Services

55
 Appendix E

Survey Questionnaire
Republic of the Philippines
Eastern Visayas State University – Ormoc City Campus
Brgy. Don Felipe Larrazabal, Ormoc City

Usability Questionnaire
(Villaba, Leyte Livestock Farmers & Buyer’s/Consumers Marketplace System )
Name (optional): ___________________________ Contact #: _______________

Instruction: Kindly check the box based on your experience using the application.

Graphical User Interface (GUI) Design Evaluation

Questions YES NO

1. This application is easy to use.

2. 2. I had no trouble locating the data I needed.

3. The information was clearly organized on the application

screen.
4. This application had a pleasant user interface.

5. The application's user interface was pleasant to use.

Note: The “interface” includes those items that you use to interact with the application. For example, some components of
the interface are the keyboard, the mouse and screens/touchscreens (including their graphics and language.)

User Experience Evaluation

Questions YES NO

1. 1. The application was difficult for me to use.

2. This application was simple to understand and operate.

3. This application provides all the features and qualities

that I was hoping for.
4. I felt this application's many features were well-
integrated.
5. To be able to utilize this application, I believe I would
want the assistance of a technical expert.
6. The majority of individuals, in my opinion, would
probably pick up using this program soon.

56
Appendix F

TESTING DOCUMENTATION
The marketplace application will be tested by people chosen at random to see if it functions
properly.

The farmer in the image above tried out the merchant side application and used it without any issues.

57
58
One of the volunteers that tested out the admin web application and was able to use it easily is
depicted in the photo above.

59
Appendix Resource
REFERENCES
Dana Mae T. Yarte (Key Accounts Manager, Philchema Inc.) Charis Mae T. Neric et. al (Assistant
Professor, UP Los Baños
Marketing of Native Pigs in Sta. Maria, Bulacan 2020, p. 1

Philip Kotler (Professor of Marketing, Northwestern University)

Atmospherics as a Marketing Tool, p. 52-53

Iryna Printeziz (Marrison School of Agribusiness) Carola Grebitus (W. P. Carey School of Business)
Marketing Channels for Local Food, p. 162

Gladys Wanjiku Thuita (Riara University, Kenya)

Impact of Mobile Applications and Transfers on Business: Financial Inclusion and Innovation – The
Case of Mpesa in Kibera Slum, Kenya. p. 178

60
 PERSONAL VITAE

PERSONAL DETAILS
Name : Roldan L. Catalonia
Address : Brgy. Pob. Del Norte, Villaba, Leyte
Contact Number : 09300244373
Email Address : Roldan.catalonia@evsu.edu.ph
Marital Status : Single
Nationality : Filipino
Date of Birth : February 17, 1997
Place of Birth : Brgy. Pob. Del Norte, Villaba, Leyte

EDUCATION
College
2018-2022
EASTERN VISAYAS STATE UNIVERSITY-ORMOC CITY CAMPUS
Bachelor of Science in Information Technology

Senior High School

2016-2018
WESTERN LEYTE COLLEGE ORMOC

Junior High School

2012-2016
MERIDA VOCATIONAL SCHOOL

Primary
2006-2007
MERIDA CENTRAL SCHOOL

2007-2009
BANILAD ELEMENTARY SCHOOL (CEBU CITY)

2009-2012
MERIDA CENTRAL SCHOOL

ACHIEVEMENTS & TRAININGS

 Attended “Videography Fundamentals with basic video editing” Workshop at CICTE

Western Leyte College in 2018.
 Computer System Servicing NCII Holder
 Attended TESDA Online Trainings:
 Microsoft Digital Literacy
 Beauty Care Services NCII (Nail Care)
 Intro to Front Office Services

61
  Monitoring Health Status of Household Members Under Your Area of
Service Coverage

PERSONAL DETAILS
Name : Carl C. Bastida
Address : Sto. Rosario Matag-ob, Leyte
Contact Number : 09631873065
Email Address : carl.bastida@evsu.edu.ph
Marital Status : Single
Nationality : Filipino
Date of Birth : June 16, 2000
Place of Birth : Matag-ob, Leyte

EDUCATION
College
2018-2022
EASTERN VISAYAS STATE UNIVERSITY-ORMOC CITY CAMPUS
Bachelor of Science in Information Technology

Senior High School

2016-2018
WESTERN LEYTE COLLEGE ORMOC

Junior High School

2012-2016
MATAG-OB NATIONAL HIGH SCHOOL

Primary
2006-2012
STO. ROSARIO ELEMENTARY SCHOOL

ACHIEVEMENTS & TRAININGS

 Attended “Videography Fundamentals with basic video editing” Workshop at CICTE

Western Leyte College in 2018.
 Computer System Servicing NCII Holder
 Consistent honor student from elementary to high school.

62
PERSONAL DETAILS
Name : Christian Joy L. Catalonia
Address : Brgy. Pob. Del Norte, Villaba, Leyte
Contact Number : 09363919056
Email Address : christianjoy.catalonia@evsu.edu.ph
Marital Status : Single
Nationality : Filipino
Date of Birth : May 31, 1998
Place of Birth : Brgy. Pob. Del Norte, Villaba, Leyte

EDUCATION
College
2018-2022
EASTERN VISAYAS STATE UNIVERSITY-ORMOC CITY CAMPUS
Bachelor of Science in Information Technology

Senior High School

2016-2018
HOLY CHILD HIGH SCHOOL

Junior High School

2012-2016
HOLY CHILD HIGH SCHOOL

Primary
2006-2012
VILLABA SOUTH CENTRAL SCHOOL

ACHIEVEMENTS & TRAININGS

Technical Skills
● Computer Literate
● Oriented in Computer Programming such as:
o C
o PHP
o JavaScript
o HTML
o CSS
o Laravel Framework (PHP)
o React-Native (JavaScript)
o Visual Basic
● Oriented in Microsoft Office applications such as:

63
o Microsoft Office Word
o Microsoft Office Excel
o Microsoft Office Powerpoint

64