CHAPTER I

INTRODUCTION

1.1 Background of the Study

Many people in today’s generation are relying on the internet to do a lot
of different tasks. It is the most trending in today’s era where in fact, People
these days are holding some sort of gadgets and using the internet to play
games or search things and buy things that they want (Internet Provider,
2015). But of course, the internet is not just about entertainment. It is also
useful in many other things especially in the field of marketing and online
business.
One of the basic uses of the Internet for businesses is to sell products
and services. Businesses create E-commerce websites to sell anything from
cell phone contracts to books and other stuffs. Online selling eliminates the
need for the business to maintain a brick-and-mortar store and in some cases
they don't have to hold an inventory. A business can also use the Internet to
buy items and services online, such as bulk-buying office supplies or printed
materials (Balle,nd).
Online shopping is a growing trend. It's convenient and can be fitted
around busy lives. It is considered to be a very helpful way of buying products
through the internet especially during the holidays and clearance seasons. It
allows customers to enjoy a wide variety of products and items not only from a
specific store, but from a diverse storage that includes all kinds of items.
Online shopping also provides customers with a good customer service that
also occurs online (Abboud, 2014). According to Weinsiwig (2018), one of the
online business acknowledged by the amazon that will set to bloom in 2018 is
the online grocery or E-grocery as the number of the online shoppers in the
US double in a little over a year. Infographic of Modern Consumer Behavior in
an Omni-Channel World shows that 96% of 1000 surveyed consumers in the
U.S. would prefer to shop online and buy products from several brands and
companies that they cannot find or are not available for purchase in their
home countries (Wallace, nd), this considers that the technology emerging in
today’s generation would greatly affect the daily lives of the people especially
in the field of online shopping.
1
 Nowadays, and with the help of the new technology and the support of
the internet, people from all around the world started to purchase items online
by simply sitting in their homes (Nyxone, 2017). Purchasing items and
products through the Web is a very easy task to do. It is now playing a very
important role in everybody’s life especially elderly people, as well as people
with a very busy life schedule (Abboud, 2014). It provides a very comfortable
service for its customers, by being able to save the item in the personal
shopping bag, and buy it later on.
EZYMarket: An Online Store for Wet and Dry Goods is a startup
business for retail stores that focuses on selling goods online, it is a business
that sells different kinds of goods like meat, fish, vegetables and etc. that is
available on the local market. With the help of the system, it would give the
local retail stores with the opportunity of selling their products online and
deliver it around the city.
One of the features of the EZYMarket is the Administration System in
which the system allows the employee to manage the product, seller,
customers, product receives and deliveries online. The Administration System
would also to send messages and announcements to the sellers and
customers in order for them to keep updated to the business anytime.
EZYMarket also open 24 hours a day the web application is easy to use and
very accessible to all users anytime.

1.2 Statement of the Problem

With increasing number of people today selling with different kinds of
goods, people are looking for another alternative where they can sell and
promote their products. One of the alternatives is online shops, but currently
online shops today doesn’t support of selling other products (e.g. Meat, Fish,
Fruit, Vegetables and etc). With this, the developer create an Administration
System for the EZYMarket: An Online Store for Wet and Dry Goods. It gives
convenience to the user to cater and manage the receiving and delivery of the
products.
Through this system, the EZYMarket would be able to maintain and
manage the EZYMarket’s customer, seller and products information and in

2
order for the business to reduce the amount of time and effort spent dealing
with product receive and deliveries.

1.3 Objectives of the Study

The general objective of this study was to design, develop and
implement an administration system that supports the product receives and
deliveries.

Specific Objective
Specifically, the project aims:
 To design and develop an interface for EZYMarket admin module that
is responsive to different kinds of devices.
 To design and develop an interface that could cater the management
of the EZYMarket’s sellers and customers information, products,
receives and delivery.
 To design and develop an interface that could send updates,
announcements, and warnings to the EZYMarket’s sellers and
customers
 To design and develop an interface that could create sellers product
promotions.
 To provide and generate the necessary reports needed by the
EZYMarket’s employee that handle the management of the deliveries
such as delivery reports and receive reports.

1.4 Scope and Limitations of the Study

The Administration System for the EZY Online Wet and Dry Goods
focuses on providing management through this features: The system could
cater the management of the EZYMarket’s seller, customer and products
information and as well as cater the receives and deliveries anytime, it could
also provide quick search for easily accessible of information of the seller,
customer and products.
The system could be accessed through different kinds of browsers and
on any devices like personal computers, laptops, tablets and smartphones.

3
 The system could update the seller’s business information such as
their business permits and etc.
The employee can create batch delivery with 2 different types of
deliveries that could handle the wet goods and dry goods.
The system would be able to send warnings to the seller of EZYMarket
in case the seller violated the rules and regulations of the business. The
system would send announcements and updates to seller and customer.
The system would have the authority to ban and unban seller if and
only if the seller/customer violated the business terms and condition.

1.5 Significance of the Study

The significance of the system is that it would lessen the amount of
time dealing with the management of the seller, customer, and product,
receive and delivery since the user would no longer do their designated task
manually. Whereas physical market operates with designated hours, the
project is available anytime.
The purpose of the system is to help the EZYMarket by managing the
customer, seller, and products as well as the receiving and delivering the
products with the aid of technology at the same time upgrade the uses and
feature of the business.
With the use the EZYMarket as another alternative online business for
online selling that focuses on selling products it would help the local farmers
to sell their products directly to the market (farmers to market) and it would
ensure greater profitability through direct farmer to farmer, farmer to retailers
and farmer to customer communication. The vision of this project is to ensure
fair price to the farming community by devising new techniques and by
making use of online market. An application, that serves as a platform for
movement of agricultural products from the farms directly to the consumers or
retailers. This web application provides privilege for both farmers and
consumers or retailers to buy and sell the required farm products without the
involvement of a middleman at its right profitable price.

4
 CHAPTER II
REVIEW OF RELATED LITERATURE

2.1 Review of Related Concepts

A startup is a young company that is just beginning to develop.
Startups are usually small and initially financed and operated by a handful of
founders or one individual. These companies offer a product or service that is
not currently being offered elsewhere in the market, or that the founders
believe is being offered in an inferior manner. Incubators can provide startups
with both capital and advice, while friends and family may also provide loans
or gifts. A startup that can prove its potential may be able to attract venture
capital financing in exchange for giving up some control and a percentage of
company ownership, Fontinelle(2017). According to Martinez(2015),
Philippines is rising really fast. With the fastest growing economy, and growth
in Asia’s startup scene, the Philippines is making a run for it. So is it the “next
silicon valley” like what some people say since the Philippines has the most
number of Call center agencies and not just the number of call center
agencies but also the Philippines is the most suitable place for startup
business because the language, cost of living and innovative mind is never a
problem in the Philippines. EZYMarket is also a startup business since it is
only operated by 2-3 people and that is only operating locally and is solving
the common problem of the local people whereas local vendors are looking
for another alternative way of promoting their products.
E-Commerce users benefit from the advantage of online transaction
by utilizing the internet-shopping website and searching for intended
merchandise when they recognize their need for a commodity or services.
Additionally, some customers are attracted by the available information about
products or services they looking for, and they then compare alternatives and
choose desired purchase options. Online shopping became a medium for
ecommerce transactions in order to increase the quality or services provided
to customers and to increase their satisfaction by providing merchandise with
good quality at competitive prices, Sultan et al. (2011). Another trends that the
Amazon acknowledged according Weinsiwig (2018) is the e-grocery, E-

5
grocery is another kind of e-commerce wherein it sells grocery products
online.
EZYMarket is an online market but it can also consider as e-grocery,
not unlike any other online shops like Lazada that only sells dry goods,
EZYMarket on the other hand sells wet goods such as vegetables and other
farm products that is available on the local market or local grocery shops
online.
There are different types of Ecommerce in the Philippines according to
Toral (2013), One of the three major type of Ecommerce are Business to
Business (B2B), Business to Consumer (B2C) and Consumer to Consumer
(C2C). B2B offers the raw materials, parts or services companies need to
boost profits, from manufacturing industries to retail environments,
Uzialko(2017), B2C refers to the online selling of products, or e-tailing, in
which manufacturers or retailers sell their products to consumers over the
Internet, Hom(2017), and C2C e-commerce is a form of business where a
company is just involved in providing a platform for various people to use it to
interact with each other for mutual benefit, Bhasin(2018). EZYMarket is
another alternative business for wet and dry goods for local sellers and as
well as the customers and is considered to be known as E-Commerce.
EZYMarket is a B2B business and it would be the most suitable online market
business for the local sellers because it focuses on giving opportunity to the
seller to sell their product on the internet world using the third-party business
website like EZYMarket.
Today, the on-demand delivery culture is driving businesses to adopt
different strategies when it comes to their operations. After all, in the tech
world, everybody wants to work faster, smarter and more efficiently. This is
why many companies choose to redesign the way they operate on a daily
basis, cutting extra steps from their workflows to give better results to clients.
Today, on-demand delivery software solutions are placed at the center of this
culture. This creates a strong relationship between customers, deliverers and
businesses on a real-time basis, facilitating faster deliveries, improved
operational management and enhanced customer satisfaction, Serb (2017).

6
 Delivery Management System for EZYMarket manages the delivery
records of the system, with this system it tracks the fleet of the orders, and
with this the delivery production process of the business would be increased.

2.2 Review of Related System

2.2.1 Lazada
Lazada.com is an online portal site which sells a wide range of goods
from mobile phones to motorbikes—directly to South East Asian consumers
based in countries such as Indonesia, Malaysia, Thailand, Vietnam and the
Philippines. The company is led by Maximilian Bittner, a former McKinsey
consultant, (Dunne, n.d.).
Due to hygienic issue for Lazada, the Lazada’s Return Policy can be
acquired by filling up the form for returns and as well as the product was being
checked by the quality assurance agent following the checklist and guidelines
for returning the product (Lazada, n.d).
On the other hand, EZYMarket’s would also accept returns but the
market would rely on the checklist as well as the regulations created by the
management in order to accept returns.
For products that need more than one item, the delivery can be
detached and delivery time was different because Lazada cooperation with
supplier / merchant is different. As for international product shipped from
overseas suppliers or merchants require estimated delivery time of 55
calendar days, while for retail products and the market place can be seen in
the description of the estimation of each product. Associated with the
scheduling of delivery, courier in Lazada cannot schedule deliveries so
Lazada cannot guarantee delivery of your order on the date and time
specified. Deliveries are made every day except Saturdays, Sundays and
national holidays. Estimated delivery depending on the region of orders and
supplier delivery of products ordered as well as the scheduling of courier
logistic partner Lazada (Fauzan, 2017).
The same pattern as Lazada, product might be delayed or cannot be
grouped by since the creation of the batch of delivery may differ on the type of
the delivery.
7
2.2.2 Alibaba
The concept of developing a Business2Business ecommerce system
of EZYMarket is from Alibaba. Alibaba enable businesses to transform the
way they market, sell and operate. Alibaba provide the fundamental
technology infrastructure and marketing reach to help merchants, brands and
other businesses to leverage the power of the Internet to engage with their
users and customers. Our businesses are comprised of core commerce,
cloud computing, digital media and entertainment, innovation initiatives and
others, Alibaba Group (n.d).
Lazada and Alibaba are one of the existing online shopping platforms
that are still running today but they differ on the product contents. With the
idea of the platforms mentioned EZYMarket is a store that sells different kinds
of wet and dry goods such as vegetables, fish, meat and etc. virtually but with
the connection of the different sellers around the city.
2.2.3 Pushkart.ph
Pushkart.ph was co-founded Joshua Rueben Go Aragon together with
Bryan Gabriel Fausto Reyes, they want to help Filipino to enjoy shopping for
grocery without the hassle of traffic going to the grocery store and spending a
lot of time picking the right items for their basket. With Pushkart.ph now
everything is done with a simple click and customers are guaranteed that the
items they want are delivered on their doorstep. (Bam,2017)
2.2.4 MyTindahan.Net
MyTindahan.Net is an online shopping service provided by Mytindahan
Online Shopping Network, a young and dynamic enterprise based in Cebu
City, Philippines. It is conceptualized by an aspiring entrepreneur Christopher
Sapong. MyTindahan.Net’s primary offerings are bestselling grocery items
and household products available locally in the Philippines. With
MyTindahan's fast and efficient delivery, customers can enjoy shopping at
home and have the goods delivered right to their doorsteps. Filipinos abroad
can also buy products for their loved ones in Metro Cebu.
MyTindahan was inspired by Philippines’ Sari-sari Stores (Variety
Store), which can readily provide basic household and personal products to its
community. By creating a network of MyTindahan Partner-Vendors in Cebu
8
and other key cities, Mytindahan is able to offer a cost-efficient and
convenient online grocery shopping experience.
Pushkart.ph and MyTindahan.net are just startup
businesses/companies that are still existing today. Both business operates
locally. The same with the EZYMarket, PushKart and MyTindahan sells
different kinds of goods such as wet and dry goods that can be delivered right
through the customer’s doorstep. Both has the common goal: is to serve
customers as fast and easiest way of shopping groceries online. The
difference between the two is that Pushkart.ph doesn’t have partners such as
local vendors, while MyTindahan.net has. EZYMarket has partners to different
kinds of vendors/sellers locally but what the EZYMarket more focused is that
EZYMarket supports local farmers.

9
 CHAPTER III
TECHNICAL BACKGROUND
The following are the lists of tools that the developer had used in
developing the administration of EZYMarket web application.
3.1 HTML (Hypertext Markup Language)
Hypertext Markup Language (HTML) is a basic markup language in
developing the Administration System for EZYMarket. With the HTML tags the
developer could use different objects like button, textboxes, and tables to
customize the webpage. HTML is a skeleton or the foundation of a website for
creating the Administration System for EZYMarket, it contains the information
that tells the browser what is on the page in terms of text, links, where to find
images.

3.2 CSS (Cascading Styling Sheet)

Cascading Styling Sheet (CSS) is a sheet of instructions that tells the
programmer how the webpage of Administration System is organized and
what it looks like in more detail. It is the one that adds colors, structures and
style that improves the presentation of the Administration Website pages by
separating content from design. With the help of CSS, it is easy to change the
way the generated HTML output looks in an organized way. Bootstrap was
added to enhance the beautification and to make the system more responsive
and flexible to any kinds of devices.

3.3 JavaScript
JavaScript supports the HTML from static webpages into more
dynamic and interactive system. JavaScript is not only supports the web
pages but also it supports the external applications like PDF documents,
running widgets, supporting for flash applications etc. (TechArk, 2014) that is
more important in the Administration System since the system is using reports
needed for the EZYMarket.
According to (Pilott, 2013) HTML, CSS and JAVASCRIPT are the key
foundation in creating and designing for the Administration System for the
EZYMarket.

10
3.4 AJAX (Asynchronous JavaScript Technology and XML)
Ajax is a client-side script that communicates to and from a
server/database without the need for a postback or a complete page refresh.
The best definition I’ve read for Ajax is “the method of exchanging data with a
server, and updating parts of a web page – without reloading the entire page.”
Ajax itself is mostly a generic term for various JavaScript techniques used to
connect to a web server dynamically without necessarily loading multiple
pages (Segue Technologies, 2013).
Ajax supports real time updates of data without reloading or refreshing
the page of the Administration System.

3.5 Bootstrap
To be able to make the Administration System for EZYMarket
responsive, Bootstrap is needed. Bootstrap is a free and open-source front-
end library for designing Ajaxwebsites and web applications such as The
Administration System for EZYMaket. It contains HTML, CSS-based design
templates for typography, forms, buttons, and navigation and other interface
components, as well as optional JavaScript extensions. Unlike many web
frameworks, it concerns itself with front-end development only (Engel, 2018).

3.6 PHP (Hypertext Preprocessor)

In line with HTML, Hypertext Preprocessor (PHP) is a scripting
language that could be embedded in the HTML. With the help of the PHP
queries, connecting the database of the EZYMarket is much easier since it
could be used as an object-oriented language and it could interact with many
different database languages including MYSQLi.

3.7 MYSQLi
MySQLi is an object-oriented and it could easily connect with MySQL
databases and supports for multiple statements that allows to run more than
one query at a time.MySQLi is open source relational database management
system which is used on web (Gupta, 2017).

11
3.8 PHPMyAdmin
For the databases, in order for the developer to use and read database
of the EZYMarket, the developer needs to have an administrative tool for
databases that supports operations on MYSQL such as PHPMyAdmin.
PhpMyAdmin is an administrative tool for databases and c be run using
the normal web browser and it is already available with the existing local
servers such as XAMPP or WAMP servers (Schaferhoff, 2015).

3.9 XAMPP (Cross-Platform, Apache, Maria DB, PHP and Perl)

XAMPP is also known as Cross-Platform(X), Apache(A), MariaDB(M),
PHP(P) and Perl(P); with the help XAMPP server the developer can develop
and run the Administration System for the EZYMarket locally since XAMPP is
a third-party tool that can create local web server.

3.10 ATOM
Atom is a free text editor created by Github. Atom is an open source
text editor that allows the developer read, modify and improve the
Administration System pages of the EZYMarket. Atom works on different
kinds of operating systems such for Macs running OS or the later versions of
Windows 7 and 8.

3.11 PSSUQ (Post-Study System Usability Questionnaire)

Post-Study System Usability Questionnaire (PSSUQ) is another
usability quantification survey, very similar to SUS, and is developed by IBM.
PSSUQ is a research instrument that was developed for use in scenario
based usability evaluation at IBM. According to (Fruhling et. al, 2015) It is
important that instruments used in usability evaluation have shown acceptable
estimates of reliability, validity, adaptability and practicality. The environment
that the original PSSUQ instrument used at IBM to assess the user
satisfaction of the usability was enterprise-wide and networked office
application suites. The follow-up study domain was speech recognition
systems.

12
 CHAPTER IV
METHODOLOGY

4.1 Research Approach

4.1.1 Qualitative Approach

In conducting the research, several interviews were conducted at the
New Valencia City Central Market. Members of Market Vendor Association of
Valencia Inc. were interviewed to determine the problem regarding to the
business environment of the NVCCM and also Sellers/Retailers that are using
social media to sell their goods online, were interviewed of how they do the
management of their orders and deliveries. It was known that the Online
Sellers/Retailers spends a lot of time managing their orders since their
management of products, and delivery can be done manually and also
retailers can easily get scammed because their transaction is can be done
using their social media or through phone text/call. The researcher did some
investigation on what type of system should be used in order to help and
enhance the market environment. The researcher came up to the idea of
developing an application that could support the management of orders and
deliveries. This medium is called the Administration System of EZYMarket: An
Online Store for Wet and Dry Goods, an online system that aims of supporting
the management of product deliveries and orders.

4.1.2 Quantitative Approach

Using the Agile Development Methodology approach the system is
developed. After developing the system, testing has been done with the
specific end users of the system. Surveys were made using the Post-Study
System Usability Questionnaire (PSSUQ). There are 10 possible end users
who tested the system and answered the PSSUQ survey questionnaire.
PSSUQ consists of 19 items aimed to address the following five
system usability characteristics, quick completion of work, ease of learning,
high-quality documentation and online information.

13
4.2 Systems Development Methodology
A startup is a business structure created to solve a problem by
delivering a new product or service under conditions of extreme uncertainty.
Many entrepreneurs and renowned business magnates define startup as a
culture and a mentality of building a business upon an innovative idea to solve
critical pain points (Phawa, 2018). Startups are prone to experiencing rapid
growth and a strict organizational structure can limit the flexibility that startups
need to survive and stay competitive. A startup needs to be able react to
unexpected obstacles, but more important they need to be able to adapt to
their competition and the always changing demands of the market. Traditional
styles of company management are not designed to make fast changes
(Pentaguy, 2017).
Agile Development Methodology is ideally suited for the successful
development of software and execution of other projects wherein the
requirements are expected to change during the project. The Application of
Agile Project Management skills are especially appropriate for the
development of new or fast moving businesses. The agile project
management is useful for the execution of urgent projects and also useful in
the execution of new fast growing businesses or fast changing business
scenarios.

Figure 4.1: Agile Development Life Cycle (Parmar, 2013)

Agile Development Methodology is suited for developing startup

applications. According to (Lasnier, 2017), Agile methods are perfect for
startups as they can keep up with and facilitate their rapid pace of

14
development. It is a methodology that focuses on setting and reaching short
term goals, getting fast results and then adapting strategy accordingly. It has
many different components that cannot be easily distilled. It also has almost
as many definitions as it has implementations. However it generally
incorporates approaches such as self-organization, cross collaboration and
adaptive planning with short sprints and functional iterations. EZYMarket is
suited for agile methodology since EZYMarket is a startup business
application that needs fast results.

Phase I: Requirement Analysis

The first phase is requirement analysis; all possible requirements of the
system were captured and discussed by the team. In this phase the team
would undergo discussion and brainstorming in order to identify what are the
necessary information and resources needed to developed the system and
who are the possible users for the system. The researcher conducted an
interview with the possible users of the system to gather the possible problem
that may be able to use and fix for the Administration System for EZYMarket.
Objective has been identified and information needed was taken after
the developer analyze the data gathered from the interview and
brainstorming. Creating a diagram helps the developer to elaborate the
developed system process.
Use case diagram is a representation of a user's interaction with the
system that shows the relationship between the user and the different use
cases in which the user is involved specifically in the Administration System
for EZYMarket. All action of the user can do in the system is shown in the
figures below;

Figure 4.2: Create Account Functional Area

15
 Figure 4.2 shows that in order the employee to enter and use the
system, the employee would have to register their account to the system, after
fill-upping the required inputs, the system would send a verification link in
order to register the employee successfully.

Figure 4.3: Forgot Password Functional Area

In some instances, the employee can retrieve their account shown in

(Figure 4.3), the employee would have to submit their email account, the
system check first if the employee is available and is verified before the
system would give another password for the employee by sending the new
password to the employee’s email address.

Figure 4.4: Manage Seller Functional Area

16
 The employee can have the authorization to manage the seller (Figure
4.4), the employee would have the authority to update, ban and unban seller
as well as sending notification and messages. First, the employee would have
to search and view the seller’s details before the employee update the seller,
the employee can only update and upload the seller’s business credentials
such as business permit and etc. that requires to verify the seller. If ever the
seller violates the rules and regulations of the business the employee could
send notification and warning messages to the seller but if the seller cannot
be tolerated with multiple warnings then the employee would have the right to
ban the seller.

Figure 4.5: Manage Customer Functional Area

On figure 4.5, the employee can only send warnings and updates
messages to the customer.

Figure 4.6: Manage Product Functional Area

17
 Figure 4.6 shows the managing of product wherein the employee can
update the product by activating, deleting and deactivating the product.

Figure 4.7: Receive Products Functional Area

On receiving the product (Figure 4.7), the employee would search first
the seller in order to view the ordered products under the specified seller then
checks which product the employee receives. After receiving the product, the
system requires the employee who delivered the products in order to print the
receive invoice.

Figure 4.8: View Order Functional Area

18
 On view orders user case (as show in Figure 4.8), the employee can
only view the order lists and the order details, cancellation of orders can only
be done by the seller and the customer.

Figure 4.9: Batch Delivery Functional Area

On product delivery (Figure 4.9), the employee first search/create the

batch delivery with the following inputs such as the estimated departure date,
departure time, delivery representative and what would be the type of the
delivery. On the other hand, in order to add the product for a certain batch of
delivery, the seller would have to check which product belongs to the batch of
delivery. After checking and putting the ordered products to the batch, the
employee would have to choose which batch would be out for delivery, and
then the system would generate the delivery invoice containing the
information needed to for delivering the product.

19
 Figure 4.10: Acknowledge Delivery Functional Area

When the delivery is done, Figure 4.10 shows that each product would
have to be acknowledged first in before declaring the products or the
transactions are already delivered and are already received by the specified
customer, the system would require the employee who acknowledged the
products ordered.

Figure 4.11: Promo Creation Functional Area

Figure 4.12 shows that the employee can create a promo update and
delete promo.

20
 Figure 4.12: Create Announcement Functional Area

Figure 4.13 shows the Creating of announcement that could be send to

both seller and customer.

Figure 4.13: Create Section and Category Functional Area

In case, store don’t have enough section and category that may fit the
individual products, Figure 4.14 shows the creation of Section and as well as
adding of categories.

21
Phase II: Design and Prototype
The second phase is the design phase, the requirement specifications
from first phase are studied in this phase and the system design and
prototype is prepared based on defined requirements. This system design
helps in specifying hardware and system requirements and helps in defining
the overall system architecture.
After the collection of the data, the developer starts to develop the
partial front end and back end of the website, this may also include the
database design for the users and the outputs and inputs for the
Administration System for EZYMarket. After gathering all required
requirements and has been analyzed by the developer, the developer would
be going to design the prototype and develop the Administration System for
EZYMarket.
The developer created the entity relationship diagram, a graphical
representation of entities and the relationships to each other, typically used in
computing in regards to the organization of data within database of the
EZYMarket, the developer should consider if the relationship is one to one,
one to many or many to many. After identifying the tables needed for
database design, ERD is needed so that the developer would know what are
the flow and the relationship of each table shown on Appendix B: Figure 1.

Figure 4.14: Context Level Diagram

22
 To generalize the process of the developed system, the developed
system, the developer created the context level diagram (as shown in Figure
4.5), the customer would input the user credentials and submit its credentials
before the customer generate an order receipt. On the other hand, the seller
receives the lists of orders from different customers and transactions as long
as the seller acknowledges the transaction then the transaction/the
transaction details statuses would be updated to “on process which mean the
product/transactions has been acknowledge and is waiting to be received by
the center.
Before the center receive the products, the products would check the
quality of the product and the product information such as its expiration date,
its package and etc. that is already created by the EZYMarket in order to
verify the received products from the seller. After verifying the products, the
EZYMarket Employee would update and receive the product from the given
transaction and in return, the system would generate the product received
invoice and change the status to “receive to center”. After successfully
receiving the products from different seller, the Employee would choose the
received products to different kinds of batches for delivery, when the delivery
is ready and set for departure then the ordered product status to “on delivery”
and then prints the delivery invoice. Ordered product status would only
change to “delivered” only if the customer already acknowledge the product.
Dataflow diagram is also designed by the developer and are used to
graphically represent the flow of data in a business information system. DFD
describes the processes that are involved in a system to transfer data from
the input to the file storage and reports generation shown on Appendix B:
Figure 3.
The developer also designed the system data dictionary and are
provides detailed information about the EZYMarket’s data, such as standard
definitions of data elements, their meanings, and allowable values. While a
conceptual or logical Entity Relationship Diagram would focus on the high-
level business concepts, a Data Dictionary would provide more detail about
each attribute of EZYMarket concept shown on
Appendix B: Figure 4.

23
 Figure 4.15: Wireframe Design (Home Page)

The wireframe was also created by the developer. Figure 4.6 shows
the visualization tool for presenting proposed structure of the wireframe, See
Appendix B: Figure 5.

Page Name: Login Page

# Buttons, Inputs, Links Description Linkages
1 Email or Username, Password Input fields for user Redirects to home
authentication page (Appendix B:
Figure 6.4)
2 Login Button Take action for the
form
Forgot Password Link Link Redirects to forgot
password page
(Appendix B: Figure
6.2)
4 Register Link Link Redirects to forgot
password page
(Appendix B: Figure
6.3)
Table 4.1 Login Page

The developer created a landing page called Login page where user
need to input registered email and password, Login button will direct the user
to home page or the employee’s dashboard. Login page also has a link.

24
Forgot password link redirects forgot password page and a register new
account link redirect to register page as shown in table 4.1.

Page Name: Register Page

# Buttons,Inputs, Links Description Linkages
1 First name, Middle name, Last name, Input fields for Redirects to home
Email, Password and Contact Number personal information page (Appendix B:
Figure 6.4)
2 Address, Province,City, Baranggay, Input fields for
Zipcode additional information
3 Register Button Take action for the Show registration
form (Inserting to confirmation
Employee table) message
4 Login Link Link Redirect to Login
Page (Appendix B:
Figure 6.1)
Table 4.2 Registration Page

The developer created the Registration Page where users need to fill
up the required information in order to have the user the authority to login to
the system.

Page Name: Forgot Password Page

# Buttons,Inputs, Links Description Linkages
1 Email Input fields for email
authentication
2 Submit button Take action for the
form (User
authentication)
3 Forgot Password Link Link Redirects to forgot
password page.
(Appendix B: Figure
6.2)
4 Login Link Link Redirect to Login
Page (Appendix B:
Figure 6.1)
Table 4.3 Forgot Password Page

25
 In some instances the user might forget their credential, the developer
created the Forgot Password Page in order retrieve the forgotten credentials.
But before retrieving the their credentials the user would have to input the
required fields such as their Email Address then the system would have to
send email messages for account recovery.
Page Name: Home Page
# Buttons, Inputs, Links Description Linkages
1 Dashboard Link Link Redirects to Dashboard/Home
Page (Appendix B:Figure 6.4)
2 Products Lists Link Link Redirects to Product Lists Page
(Appendix B: Figure 6.5)
3 Seller Lists Link Link Redirect to Seller Lists Page
(Appendix B: Figure 6.6)
4 Customer Lists Link Link Redirect to Customer Lists
Page(Appendix B: Figure 6.8)
5 View Orders Link Link Redirect to Order List Page
(Appendix B: Figure 6.10)
6 Receive Management Link Link Redirect to Product Receive Page
(Appendix B: Figure 6.12)
7 Delivery Management Link Link Redirect to Delivery Lists Page
(Appendix B: Figure 6.14)
8 Acknowledge Delivery Link Link Redirect to Acknowledge Orders
Page (Appendix B: Figure 6.17)
9 Announcement Link Link Redirect to Announcement Page
(Appendix B: Figure 6.19)
10 Add Promo, Section and Category Link Redirect to Promo, Section and
Link Category Creation Page (Appendix
B: Figure 6.20)
11 Pending Orders Link Link Redirect to Order List (Appendix B:
Figure 6.10)
12 Pending Deliveries Link Link Redirect to Delivery Lists Page
(Appendix B: Figure 6.14)
13 Active Sellers Link Link Redirect to Seller Lists Page
(Appendix B: Figure 6.6)
14 Active Customers Link Link Redirect to Customer Lists
(Appendix B: Figure 6.8)
15 Log out Button Redirect to Login Page (Appendix
B: Figure 6.1)
Table 4.4 Dashboard/ Home Page

26
 The developer created the home page or dashboard. The user
dashboard has a main navigation panel on the right side that is Dashboard
link, Product Lists Link, Seller Lists Link, Customer Lists Link Order Lists Link,
Receive Management Link, Delivery Management Link, Announcement Link
and Promo, Section and Category creation link.

Page Name: Products Lists Page

# Buttons, Inputs, Links Description Linkages
1 Activate Button Button, Activate
product
2 Deactivate Button Button, Deactivate
product
3 Delete Button Button, Deletes
product
Table 4.5 Products Lists Page

Product lists page consists of the Lists of Products from the different
Sellers, this is where the employee can Activate, Deactivate and Delete the
products.

Page Name: Seller Lists Page

# Buttons, Inputs, Links Description Linkages
1 View Details link Link Redirect to Manage
Seller Page
(Appendix B: Figure
6.7)
Table 4.6 Seller Lists Page

Seller Lists Page consists of lists of different kinds of sellers either

active seller, deactivated or deleted sellers, the employee would have to
select first the specific seller order to user the view details link where the
employee can manage the details of the seller.

27
Page Name: Manage Seller Page
# Buttons, Inputs, Links
1 Activate Button
2 Ban Button
3 Send Message Button
4 Send Warning Button
5 Business Permit, Date Expire and
Business Permit File
6 Activate Button
7 Deactivate Button
8 Delete Button
Table 4.7 Manage Seller Page
Description Linkages
Alert, Activates seller
Modal, Bans seller
Modal, Notify or send personal
message to the seller
Modal, Warns seller
Input business credentials to
allow the seller/vendor to sell
Check button, activates product
Ex button, Deactivates product
Trash button, Deletes product

Manage Seller Page is where the employee can update the seller, it is
where the employee can send personal messages, warning messages, and
seller banning. This page is also where the employee updates the business
information of the seller such as the business permit and etc.

Page Name: Customer Lists Page

# Buttons, Inputs, Links Description Linkages
1 View Details Link Link Redirect to Manage
Customer
Page(Appendix B:
Figure 6.9)
Table 4.8 Customer Lists Page

Customer Lists page consists of lists of Customers actively using the

system. View Details link redirects the employee to the Manage Customer
page.

Page Name: Manage Customer Page

# Buttons, Inputs, Links Description Linkages
1 Send Message Button Sends personal message to the customer
2 View Order Details Modal, Views details of the checked order
Table 4.9 Manage Customer Page

28
 Manage Customer page is where the employee would be able to send
messages to a specific customer as well as the employee could check the
customer’s previous purchases.

Page Name: Order Lists Page

# Buttons, Inputs, Links Description Linkages
1 View Details Link Redirect to Order
Details Page
Page(Appendix B:
Figure 6.11)
Table 4.10 Order Lists Page

The developer developed Order Lists Page in order to view the lists of
pending orders and its details.

Page Name: Receive Product Management Page

# Buttons, Inputs, Links Description Linkages
1 View History Link Redirect to Order
Details Page
Page(Appendix B:
Figure 6.13)
2 Cross Button Modal, Shows lists of
ordered products
from the specific
seller
Table 4.11 Receive Product Management Page

Receive Product page consist of the lists of pending products to be

received from the sellers.

Page Name: Product Received History Page

# Buttons, Inputs, Links Description Linkages
1 Cross/ Add Button Modal, Opens lists of
received products
2 Ex Button Removes received
product
Table 4.12 Product Received History Page

29
 After successfully receiving the products from different kinds of seller, it
would then recorded to the product received history page.

Page Name: Delivery Management Page

# Buttons, Inputs, Links Description Linkages
1 Cross Button Modal, Opens lists of
added products from
the specific batch
2 Edit Button Edits Delivery Details
3 Estimated Departure Date, Estimated Modal content, Input
Departure Time, Delivery new delivery
Representative and Delivery Type information.
4 Delivery History Link Redirects to Delivery
History Page
(Appendix B: Figure
6.16)
5 Add Selected Product to Batch Button Opens lists of
available batches for
delivery
Table 4.13 Delivery Management Page

Delivery Management Page is where the employee could create

batches of deliveries with different kinds of batch type either the delivery is for
wet goods and dry goods. Before creating the batches for delivery, the
employee would have to input delivery details such as the estimated
departure date, estimated departure time, delivery representative and delivery
type.
Page Name: Delivery History Page
# Buttons, Inputs, Links Description Linkages
1 Cross Button Modal, Opens
delivery details
Table 4.14 Delivery History Page

After creating the creating batches of delivery, delivery history contains

lists of deliveries that are waiting to be acknowledge and is on delivery.
Cross/plus buttons opens a modal that contains details of the delivery.

30
Page Name: Acknowledge Delivery Page
# Buttons, Inputs, Links Description Linkages
1 Cross Button Modal, Opens, delivered batch
2 Deliver Link Redirects to
Acknowledge Order
Details Page
(Appendix B Figure
6.17)
Table 4.15 Acknowledge Delivery Page

Acknowledge Delivery Page contains of the list of On-going deliveries

that are waiting to be acknowledged by the customer, clicking the cross/plus
button will opens a modal that contains all the products delivered in a batch,
then by clicking the deliver button will proceed to the Acknowledge Order
Details Page (see Appendix B Figure 6.16).

Page Name: Acknowledge Order Details Page

# Buttons, Inputs, Links Description Linkages
1 Acknowledge By Input the name of the person who
acknowledged the orders.

Table 4.16 Acknowledge Order Details Page

After clicking the deliver button from the Acknowledge Delivery Page,
Acknowledge Order Details Page is where the employee inputs the name of
the customer who acknowledge the order.

31
Page Name: Announcement Page
# Buttons, Inputs, Links Description Linkages
1 Sentbox Link Redirects to Edit
Announcement Page
(Appendix B Figure
6.19)
2 Compose Link Redirects to
Announcement
Page (Appendix B
Figure 6.18)
3 Send to, Subject, Message, Details for sending
Image Attached announcement to both seller
or customer

Table 4.17 Announcement Page

In order to give updates to the customer and to the sellers, the

developer created announcement page for more updates of the system such
as the ongoing product promotions, system updates and etc., Sent box will
redirect to the lists of sent announcement. Announcement contains of
messages and attached image.

Page Name: : Promo, Section and Category Creation Page

# Buttons, Inputs, Links Description Linkages
1 Section Name Input name of the section

2 Category Name Input categories to the specific section

3 Trash Button Deletes section or deletes category

4 Edit Button Edits section name or category name

5 Promo Code, Promo Inputs Needed for creating product promotions.

Name, Date Started,
Date Ended

Table 4.18 Promo, Section and Category Creation Page

The developer created the Promo, Section, and Category Creation

Page for the system to create product promotions or voucher code, the page
32
can also add or edit the Section and Categories in case there are products
that doesn’t fit to be in the section/category.

Phase III: Development

Development phase is when the actual code is written. The developer
would create a system based on the collected requirements gathered by the
researcher in order to support the Administration System for EZYMarket.

Figure 4.16: System Development Sample Code

In the development phase, the developer gathered information on what

are the best developing tools in creating the Administration System with
further research the developer decided to use pure PHP in developing the
system together with the AdminLTE template for its administrator side. In
order for the developer develops a responsive system the developer used
Bootstrap to achieve the required responsiveness of the system.
The developer would also use XAMPP server as a third-party server in
able to run the system locally even without connecting through the internet.
Webpages under PHP would become dynamic in order to collect form data,
add, delete and modify data in database. The developer would also use AJAX

33
for real-time updating of data without refreshing the whole page and then
connects to a webserver without loading multiple pages.
The developer would also use MYSQL database in order to store and
update data such as the delivery statuses and other information needed for
the EZYMarket. PHPMyAdmin is also needed as a third party software for the
managing of the tables from the database and also it allows the developer to
create, update and remove tables from the database.

Phase IV: Testing and Debugging

In the testing and debugging stage, the website would be tested with
the other internet browsers, errors were noted by the developer and then
debug the application. The developer would have a lot of iteration and
debugging the application in different internet browsers due to the different
capabilities specially the programming language that are using. The developer
would conduct alpha and beta testing.
In the alpha testing the developer would gather and debugs all bugs
and flaws happening in the system. A proper execution of this stage ensures
that the client interested in the created software, would be satisfied with the
finished product. If there are any flaws, the software development process
must step back to the design phase. In the design phase, changes are
implemented and then the succeeding stages of coding and testing are again
carried out. In alpha testing, the system was tested to different kinds of user in
order to track and some major bugs and problem of the system for the
developer to fix before the proceeding to beta testing.

Lists of Issues, Bugs and Errors of the System

1 Replace the transaction id to transaction code displayed in

some tables.
2 Create announcement for Seller and Customer.
3 Create Batch Delivery.
4 Add, Update and Cancel function for batch delivery.
5 Add remove button in product receive history.
Table 4.19: Lists of issues, Bugs and Errors of the System

34
 After addressing and fixing the issues encountered, the developer
conducted Beta testing. The developer selected a total of 10 respondents
from Valencia City Public Market, and obtained feedbacks on the system
quality. Table 4.21 shows the feedbacks of the respondents from the survey.

Feedbacks from the respondents of Beta Testing

1 Remove button for Receive History is not working

2 No Remove button on Delivery History
3 Remove button to delivery history
4 No history lists for Acknowledge delivery
5 Create, Edit and Delete on Promo creation is not working
Table 4.20: Lists of issues, Bugs and Errors of the System during the Beta
Testing

Phase V: System Deployment

Once the functional and non-functional testing is done, the system is
then deployed into the EZYMarket environment.
On the System Deployment, all three modules was merged to become
one system, these three modules were named: EZYMarket for Customer,
EZYMarket Seller Center for the Seller and the Administration System for
EZYMarket.

Phase VI: System Maintenance

There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better
versions are released. Maintenance is done to deliver these changes in the
EZYMarket environment. System modification and preservation takes place
during and after of the system deployment to ensure the full system
functionality. Project maintenance would be the step where the developer
uploaded the updates of the EZYMarket website for the testers to update the
application.
The developer maintained the system by updating the design and
website content. The developer addresses the issues bugs and feedbacks

35
from the alpha testing. The developer replaced the transaction ID into
transaction code. The developer also created the announcement page in
order to send announcements to both sellers and customers. The developer
also replaced single delivery into batch delivery. The developer also added
the remove button in order to remove the received product. On the other
hand, the developer also fixed the addressed issues and bugs during the beta
testing, also the developer added remove button on delivery history, the
developer also added history page for the acknowledged delivery and also the
developer fixed the buttons that are not properly working.

4.3 Systems Requirements Specification

4.3.1 Functional Requirements

Functional Requirements as shown in Appendix A: Figure 2, the
employee first would login into the system. If ever employee cant logged in to
the system, the employee would have to create in order to have him the
authority to use the system.
The employee could update the seller’s business information in order
to verify the seller. The employee could also manage and update the product
information to active, deactivate and delete and also the employee could also
view the transaction details.
In case the seller violated the rules and regulations of the Business, the
employee would have the authority to give the seller warning messages to the
sellers, if the actions cannot be tolerated then the employee would have the
authority to ban the seller.
The employee could receive the products from the seller as well as the
employee would have to create a batch delivery before the employee could
add different products in a batch. If the products were already added in the
batch and are ready to be delivered, then the system would change status of
the ordered products to “on delivery” and then the system would print the
receipt for delivery together with its delivery code. In case of human error, the
employee can update and delete the batch before the ordered products would
be sent to the designated customer.

36
 Before the employee declared the ordered products to “received”, the
system would require the employee to add who acknowledged the delivery. If
the required inputs are done then the system would update the status to
“delivered”.
Creation of announcement, promo, section and categories are one of
the features for the administration system.

4.3.2 Input Requirements

The input requirements that the design needed in order to attain the
objective of the study are the following:
 Employee Registration
The employee would have to register to the system first in order to use
the system. The employee would have to submit their basic information
such as their first name, last name, middle name, email account, contact
number and their password that is not less than 6 characters.

 Login
By logging-in the account, the seller would have to log-in their
credentials such as email and password in order to use the system.
 Forgot Password
Forgot password requires email in order for the system generates the
password that can be retrieved through their submit email addresses.
 Delivery
On delivery, the system requires to create a batch delivery. The
employee would have to input the required details for delivery such as the
delivery representative, estimated date and estimated time as well as the
type of the delivery.
 Acknowledge
After sending the deliveries, employee would have to submit the name
who acknowledge the product before the system updates the ordered
products to “delivered”.

37
  Return
On the returning the product, products cannot be valid without the
reason why the product is subjected for returns.
 Promo
On promo creation the system requires the employee to input the
promo name and promo suggested percentage and the promo details.

4.3.3 Output Requirements

The output requirements that the design system needed in order to
attain the objective of the study are the following:
 The system displays seller product lists
 The system displays seller lists
 The system displays order lists
 The system displays batch lists
 The system displays delivery history
 The system displays received products
 The system displays delivered products
 The system displays announcement
 The system generate receive invoice
 The system generate delivery invoice

4.3.4 Software Requirements

Client Side:
 Browsers: IE 8.0, Mozilla Firefox 3.0, Chrome 14.0.
 Mobile Tablet Emulators: Android, IOS
 Desktop: Windows XP to latest version of windows.
Server Side:
 XAMPP would run on computers with an operating system of
Windows 7/8/8.1/10. XAMPP needed RAM (Installed Memory)
minimum of 512MB, with the compute processor speed of
minimum of 1GHz and a free space on Hard Drive: Minimum
200MB.
 PHP Hypertext Preprocessor version 5.2.4 and grater.

38
  Browser: IE 8.0, Mozilla Firefox 3.0, Chrome 14.0.

4.4 Data Dictionary

A Data Dictionary is a collection of names, definitions, and
attributes about data elements that are being used or captured in a database,
information system, or part of a research project. It describes the meanings
and purposes of data elements within the context of a project, and provides
guidance on interpretation, accepted meanings and representation (NEDN,
2016). The Data dictionary of the system can be found on Appendix B: Figure
4.

4.6 Design
In this phase the developer used all the gathered information to create
the logical design of the system.

4.6.1 Flowchart
The designed flowchart of the system is shown in Appendix A: Figure1,
Flowchart is a formalized graphic representation of a logic sequence, work or
manufacturing process, organization chart, or similar formalized structure that
occurs in the EZYMarket. Flowchart symbols are linked together using arrows
to trace the flow of direction. The purpose of a flow chart is to provide people
with a common language or reference point when dealing with a project or
process. The system would have a flowchart for the Administration System for
EZYMarket.
To start with the login account, the system authenticate the employee if
the user is a valid employee of the EZYMarket, then if not validated, the
employee would have to create an account.
The employee verifies the seller if the seller submits the required
business information such as business permit and other kinds of documents
needed for the seller to become officially a seller of the EZYMarket. The
employee would send warning to the seller if the seller violated the rules and
regulations of the system, as well as the employee can send personal
messages to the seller. The employee would also have the authorization to
ban the seller if the seller cannot be tolerated.
39
 The employee could receive products from different seller if and only if
the product is verified by the employee and the EZYMarket Quality Checklist.
On the delivery, the employee would have to add the products from the
available created batch, then after adding all the ordered products, then the
system would generate the delivery invoice and then the system would update
the status of the ordered products to “on delivery”.
Before declaring the ordered products to “delivered”, the system would
require the employee to put the name who acknowledge the product upon
delivery.
The employee can also create an announcement that can be able to
send to seller and customers of the EZYMarket. Promo creation is also done
by the employee wherein the employee would have to input the suggested
percent promo and the name of the promo as well as when the promo ends.
Adding of section and category is also done by the employee.

Figure 4.17: EZYMarket Employee Context Level Diagram

4.6.2 Context Level Diagram

In order to elaborate the process of the system, the developer created
a Context Level Diagram, the diagram shows the functionalities required by
the external entities. Employee must input its credential before the employee
would use the system. On the other hand, the seller would receive the
received invoice as well as the customer would receive an update of the
ordered products until the ordered product would be delivered.

40
4.6.3 Data Flow Diagram Level 1
The detailed diagram shown in Appendix B Figure 3, shows the flow of
the data of the system. From the seller registration, verified by the
administrator upon completing the requirements. Management of the seller,
customer and product information, as well as the management of the delivery
and receives. The chart also shows the creation of the announcement, promo,
section and category.

4.6.4 Entity Relationship Diagram

Entity Relationship diagram is a graphical representation of entities and
their relationships to each other, typically used in computing in regards to the
organization of data within database of the EZY Market, the developer should
consider if the relationship is one to one, one to many or many to many. After
identifying the tables needed for database design, ERD is needed so that the
developer would know what is the flow and the relationship of each tables
shown on Appendix B Figure 1.

4.6.5 Use Case

A use case diagram is a representation of a user's interaction with the
system that shows the relationship between the user and the different use
cases in which the user is involved specifically in the Administration System
for EZY Market.
The figure shown on Appendix A: Figure 2 shows that the employee
could manage the deliveries, receives and the acknowledgement of the
ordered products. As well as the employee can also manage the sellers
information.
The employee could manage the product statuses where when
the product is activated, deleted or deactivated. The employee can also
manage the announcement, promos, section and categories.

4.7 Project Management

The planned process in developing the system is show in Appendix C
Figure 1, EZYMarket Administration System Gantt chart. The figure show how

41
the developer planned and view the task to be done, the durations and the
sequencing of the task.
The developer created and design of the system within the span of 3
months, the developer created and developed the prototype of the proposed
system.

42
 CHAPTER V
RESULTS AND DISCUSSION
The following graphical interface discuss about the outputs of the
development and the results of the survey. It shows the functions of the
developed system.
5.1 Results
5.1.1 Modules

Figure 5.1: Login Page

Figure 5.1 Shows the login page, before the employee can use the
system, the system would require the employee its credentials.

Figure 5.2: Account Creation Page

43
 Account creation page shown in Figure 5.2 wherein the system would
ask the employee to input the employee details before the system would allow
the employee to use the system.

Figure 5.3: Dashboard Page

Figure 5.3 shows the Dashboard of the System, wherein it shows the
pending orders of the Employee, Pending Deliveries, Active Sellers and the
Active Customers. Below are the lists of the Deliveries and its statuses. On
the main navigation pane there are different labels with significant meaning on
each tabs on the Order Management tab. On the Order tab, white color
means the Order is Pending, blue means Delivered to Center, skyblue for on
Delivery and yellow is for cancelled order. On the Receive tab, red label is the
number of seller that has pending products to deliver to the center and the
yellow is the number of products to be received from the seller. On the
Delivery tab these labels signifies the remaining product to be added to the
batch deliveries, yellow for Wet Goods, red for Dry Goods and the blue one is
the pending batch deliveries. An on the other hand, the red label of the
acknowledge tab means that it has a Delivery that needs to be acknowledged.

44
 Figure 5.4: Product Lists Page

Figure 5.4 shows the lists of the products of the different kinds of the
seller, the employee would have the authority to Activate, Deactivate and
Delete the product.

Figure 5.5: Seller Lists Page

Figure 5.5 shows the Lists of the Active and Banned Seller. The
employee will have to select one seller in order to view the seller details and

45
redirects to manage seller page.

Figure 5.6: Seller Details Page Tab 1

Figure 5.6 shows the details of the seller. On the first tab, the system
would show the products of the seller wherein the employee would have to
update the status of the products in its specific seller.

Figure 5.7: Seller Details Page Tab 2

On the Second tab, Figure 5.7 shows the required input to submit by
the seller in order to be recognized by the EZYMarket as a seller of the
system, the employee can also upgrade or and downgrade the package of the
seller.

46
 Figure 5.8: Ban Seller Modal

When banning the Seller, Figure 5.8 shows a modal of banning the
seller, the employee would have to choose the seller before banning. By
clicking the ban seller, the seller would then notified that the specified seller is
banned from the EZYMarket.

Figure 5.9: Send Message Modal

Figure 5.9 shows the modal interface of sending message to both

seller and customers.

47
 Figure 5.10: Customer Details Page

Figure 5.10 shows the details of the customer, as well as the recent
purchases and orders of the customers, by clicking the view button the
system will shows a modal that contains the products from the specified
Transaction ID. On the other hand, the employee could only send message to
the customer.

Figure 5.11: Order Lists Page

48
 On the order lists page, the employee can only view the lists of orders
from the different customers, and the employee can only view the details of
the orders.

Figure 5.12: Receive Product Page

On receiving the product, Figure 5.12 shows the lists of the seller, the
employee would select which seller delivered products to the center.

Figure 5.13: Receive Product Invoice Modal

Figure 5.13 shows the modal when the employee selects the seller,
then the employee would have to input the name of the representative of the
seller and the selects which products they delivered. When the products

49
verified and approved, then the status of the ordered products would be
change to “delivered to center”.

Figure 5.14: Batch Delivery Page

After the receiving of products from the center, the employee would
then proceed to delivery. Figure 5.14 shows the list of available batches that
are on the waitlist.

Figure 5.15: Create Batch Delivery Modal

50
 Figure 5.15 shows the modal of creating the batch for delivery, the
system would require the employee to input the details of the batch delivery
such as the estimated departure date, departure time, delivery representative
and the delivery type.

Figure 5.16: Select Product Modal

After creating the batch for delivery, the plus button will show the modal
of products with its delivery type depending on the type of the batch the
employee selected. There are only 2 types of delivery types the Wet Goods
and Dry Goods.

Figure 5.17: View Batch Details Modal

51
 Figure 5.17 shows the Batch of delivery and is ready and set to depart.
The view button shows the details modal that contains the selected/added
products from different orders. In case, the employee got an error on selecting
the products to the batch, the employee can use the remove button in order to
return the selected product to the pending products. By clicking the Deliver
batch means the delivery is now waiting to be acknowledged.

Figure 5.18: Remove Batch Alert

The employee could also remove the batch from the delivery, the
products that has been registered to the selected batch will be return to its
pending state.

Figure 5.19: Acknowledge Delivery Lists

52
 To be able to declare the system as delivered, Figure 5.19 shows the
lists of the delivered products and is ready to be acknowledge. The view
button triggers the modal for acknowledge delivery details.

Figure 5.20: Acknowledge Delivery Modal

After clicking the batch of delivery, Figure 5.20 show the lists of
transaction needed to be acknowledge.

Figure 5.21: Input Alert

Figure 5.21 shows the details of the page, the system requires the
employee to input the name of the person who acknowledge the product.

53
 Figure 5.22: Sent Box Page

Figure 5.22 shows the list of the Announcement that has sent, view
button will redirect the employee to the view announcement page and the
compose button redirects the employee announcement creation page.

Figure 5.23: Compose Announcement Page

Figure 5.23 shows the creation of Announcement, that contains the

announcement type either for seller, customer or both seller and customer,
the subject, message and the attached image.

54
 Figure 5.24: View Announcement Page

Figure 5.24 shows the page where the employee can read the created
announcement.

Figure 5.25: Section and Category Page

Figure 5.25 shows the list of Section and category, in this page the
employee can create, update and remove section and category.

55
 Figure 5.26: Create Category Modal

Figure 5.26 shows the creation of category, the employee would have
to select which section the employee wants to add the category.

Figure 5.27: Create Promo Page

Figure 5.27 shows the creation of promotion and the list of the current
promo and its countdown timer when the promo will start and the promo will
end.

56
5.1.2 System Usability Result
Usability evaluation determines whether a system meets a pre-
determined, quantifiable level of usability for specific types of users carrying
out specific tasks. The self-administered questionnaire composed of multiple
separate items organized into scales, with each scale assumed to measure
an attribute or attitude dimension is a common approach to usability
evaluation. Use of multiple items to assess each dimension is essential to the
measurement process, (Fhruling and Lee, 2005). Lewis(2002) states that the
PSSUQ instrument is intended to measure the system usefulness, information
quality and interface quality of a user interface by using the 7-point scale with
19 questions questionnaire, by this it will determine its Reliability, Validity and
Adaptability of the tested system.
The developer conducted a survey in the New Valencia City Central
Market in order to determine the system usability. Members of the Members
of Market Vendor Association of Valencia Inc. took the Post Study System
Usability Questionnaire (PSSUQ). The PSSUQ is consisting of 19 questions
shown Appendix C: Figure 7. The PSSUQ divided in three parts the System
Usefulness, Information Quality and Interface Quality as shown in Table 5.2.

PSSUQ Scale Scoring Rule

Scale Scale Scoring Rule
System Usability Average Item 1-8
Information Quality Average Item 9-15
Interface Quality Average Item 16-18
Overall Average Item 1-19
Table 5.1: PSSUQ Scale Scoring Rule (Lewis,2002)

Lewis(2002), named the subscales: System Usefulness, Information

Quality, and Interface Quality. The System Usefulness sub-scale refers to a
system that is easy to use and easy to learn, allows the user to effectively
complete tasks, and allows the user to become productive quickly. The
Information Quality refers to the feedback the system provides to the user

57
such as error messages and information on how to fix problems. It also
includes information such as online help, onscreen messages and
documentation that is clearly presented. Moreover, it also measures if the
information is easy to understand, effectively helps the user complete tasks,
and is organized. The Interface Quality sub-scale deals with how pleasant the
system was to the consumer. It measures if s/he liked the system and if the
system has all the functionality and capabilities s/he expected.
To check the reliability, validity and adaptability of the system it should
have to follow the scale scoring rule as shown in Table 5.2.

Demographic of the Respondents Break Down

Participants Number of Participants
Members of the Members of Market 5
Vendor Association of Valencia Inc.
Local Vendors 5
Table 5.2: Demographic of the Respondents Break Down

The Table 5.2 shows the demographic break down of the respondents
that took the PSSUQ usability survey. 5 Members of Market Vendor
Association of Valencia Inc. took the usability survey that is led by their
Manager Mr. Atonio Robledo. Market Vendor Association of Valencia Inc.
contains of different departments, namely Central Market vendors, Vegetable
Porters, Middle Man and all vegetable deliveries from Farm to Farmers
market to Central Market.
Cronbach’s alpha, α (or coefficient alpha), developed by Lee Cronbach
in 1951, measures reliability, or internal consistency, Stephanie(2014).
Cronbach’s coefficient alpha estimates the internal consistency of a set of
items and indicates the extent to which the scale items belong to a common
core construct, Cronbach(1951).

58
 Figure 5.28: Formula of Getting the Cronbach’s Coefficient Alpha

Figure 5.28 is the formula by getting the weighted mean in order to

interpret data using Cronbach’s Coefficient Alpha interpretation range. Where
r stands for coefficient alpha; k is the number of items on the instrument that
measure that variable, sigma sub-i is the variance of one item, and sum of
sigma squared is the variance of the total score for the entire variable,
Korb(2012).

Range Interpretation
α ≥ 0.90 Excellent
0.90 > α ≥ 0.80 Good
0.80 > α ≥ 0.70 Acceptable
0.70 > α ≥ 0.60 Questionable
0.60 > α ≥ 0.50 Poor
0.50 > α Unacceptable

Table 5.3: Cronbach’s Coefficient Alpha Interpretation Range, (Stephanie,

2014).
Statistics is one way of getting the information’s organized. To have a
general view of the whole scenario of the study, statistical tool is used. This
also includes the scaling system, which was used by the proponents as a
technique to monitor the respondent’s interpretation of facts. The Likert scale
was used to interpret items in the PSSUQ questionnaire. These responses
were based on the respondents. The range and interpretation of the five point
scale are shown in the Table 5.3.

59
EZYMarket PSSUQ Survey Result
No. Question Variance
1 Overall, I am satisfied with how easy it is to use this system.
0.36
2 It was simple to use this system.
0.09
3 I could effectively complete the tasks and scenarios using this system.
0.69
4 I was able to complete the tasks and scenarios quickly using this
system.
0.44
5 I was able to efficiently complete the tasks and scenarios using this
system.
0.29
6 I felt comfortable using this system.
0.40
7 It was easy to learn to use this system.
0.61
8 I believe I could become productive quickly using this system.
0.69
9 The system gave error messages that clearly told me how to fix
problems.
0.96
10 Whenever I made a mistake using the system, I could recover easily
and quickly.
0.61
11 The information (such as on-line help, on-screen messages and other
documentation) provided with this system was clear.
0.44
12 It was easy to find the information I needed.
0.29
13 The information provided for the system was easy to understand.
0.49
14 The information was effective in helping me complete the tasks and
scenarios.
0.29
15 The organization of information on the system screens was clear.
0.56
16 The interface of this system was pleasant.
0.36
17 I liked using the interface of this system.
0.56
18 This system has all the functions and capabilities I expect it to have.
0.49
19 Overall, I am satisfied with this system.
0.25
Table 5.4: EZYMarket PSSUQ Survey Result

The Table 5.4 shows the total variance of each of the questions 1-19.
By getting the variance of each questions, this would be use to solve the
Cronbach’s Coefficient of Variance in order to get the reliability, validity and
adaptability of each usability namely Overall Usability (OVERALL), System
Usability (SYSUSE), Information Quality (INFOQUAL) and Interface Quality
(INTERQUAL).

60
 Overall Usability
0.90
0.88 0.87
0.86
0.84
0.82 0.81
0.79
0.80
0.78
0.76 0.75
0.74
0.72
0.70
0.68
OVERALL SYSUSE INFOQUAL INTERQUAL

Figure 5.29: Cronbach’s Coefficient Alpha for the OVERALL, SYSUSE

INFOQUAL and INTERQUAL

The Figure 5.29 shows that the system usefulness got a coefficient
alpha of 0.79; information quality got a coefficient alpha of 0.75; interface
quality got a weighted mean of 0.81 and overall usability got a coefficient
alpha of 0.87.
The data shows that the respondents agree on the SYSUSE with the
coefficient alpha of 0.79, this means by following the Cronbach’s Coefficient
Alpha Interpretation Range on Table 5.4, this shows that respondents agreed
that they can effectively and efficiently complete the tasks and scenarios
using this system with acceptable rate. The respondents also agree that the
system is easy to use and they fell comfortable using the design system as
shown on the individual mean of each item in Table 5.4.
On the INFOQUAL which the system got a coefficient alpha of 0.75,
this means that the respondents satisfied with the quality of information that
the system gave with acceptable interpretation rate, on the other hand
INFOQUAL rate has the lower coefficient alpha among the four scales which
means that the developer would have to improve the organization of
information of the system.
The INTERQUAL of the system got the highest coefficient alpha
among the categories with the coefficient alpha of 0.81. The data shows that

61
the system interface is acceptable by the respondents with the interpretation
rate of good, it was pleasant to use and they like using the system.
The overall quality got nearly on its interpretation rate of excellent
which has 0.87 coefficient alpha, which means that the system is reliable and
acepptable.

Overall Quality

19%
24%

Scale of 7
Scale of 6
Scale of 5

57%

Figure 5.30: Overall usability scale percentage

The Figure 5.30 shows the percentage of the scale score provided by
the respondents for the overall usability of the system. The overall score is
based on the items 1-19. The figure shows that the respondents rate the
system with scale of 7 is 24%, scale of 6 is 57%, scale of 5 is 19% the rest of
the scale is 0%.

62
 System Usability
18% 17%

Scale of 7
Scale of 6
Scale of 5

65%

Figure 5.31: System Usefulness scale percentage

The Figure 5.31 shows the percentage of the scale score provided by
the respondents for the System Usefulness of the system. The overall score is
based on the items 1-8. The Figure shows that respondents who rate the
System usefulness of the system in the scale of 7 is 17%, the scale if 6 is
65%, scale of 5 is 18% the rest of the scale is 0%.

System Quality
1%

21%
29%

Scale of 7
Scale of 6
Scale of 5
Scale of 4

49%

Figure 5.32: Information Quality scale percentage

The Figure 5.32 shows the percentage of the scale score provided by
the respondents for the Information Quality of the system. The overall score is
63
based on the items 9-15. The Figure shows that respondents who rate the
Information Quality of the system in the scale of 7 is 29%, the scale if 6 is
49%, scale of 5 is 21% and scale of 4 is 1% the rest of the scale is 0%.

Interface Quality
13%

37%

Scale of 7
Scale of 6
Scale of 5

50%

Figure 5.33: Interface Quality scale percentage

The Figure 5.33 shows the percentage of the scale score provided by
the respondents for the Interface Quality of the system. The overall score is
based on the items 9-15. The Figure shows that respondents who rate the
Interface Quality of the system in scale of 7 is 37%, the scale if 6 is 50%,
scale of 5 is 13% and the rest of the scale is 0%.

64
 CHAPTER VI
Conclusion and Recommendations
6.1 Conclusions
EZYMarket Survey Result
Scale Coefficient Alpha
System Usefulness (SYSUSE) 0.79
Information Quality (INFOQUAL) 0.75
Interface Quality (INTERQUAL) 0.81
Overall (OVERALL) 0.87
Table 6.1: EZYMarket Survey Result

In the result of conducted survey for the Administration System for

EZYMarket, the System Usefulness scored the coefficient alpha of 0.79,
Information quality scored the coefficient alpha of 0.75, Interface Quality score
the coefficient alpha of 0.81 and over all scored the 0.87 as shown in Table
6.6. The PSSUQ says that the highest the mean the excellent the satisfactory
of the user to the system with the coefficient alpha of 1 and the unacceptable
satisfactory of 0, (Stephanie,2014). Base from the result of the study the
system has a nearly excellent rating from the system. Therefore the
EZYMarket designed process is more accurate, reliable and faster and the
respondent has a high expectation about the system.

6.2 Recommendations
After the implementation of the Administration System for EZYMarket,
additional enhancement where recommended to improve the system. The
recommendations are dicussed below:
Enhancing the system human and computer interation, the system
must consider the HCI (Human Computer Interation) rules in developing a
website to make the Administation System more user-friendly and dynamic for
the users.
In order to accommodate some reports wherein some cases product
ordered may be subjected for returns, the system will have its management
on returns.

65
 For now, the Administration System focus on one area only which is
the Valencia City, hence the developer suggested to create multiple center
where sellers and customer can be reached easily.

66