CHAPTER III

TECHNICAL BACKGROUND

This study is qualitative in which it centres on the events that the

respondents had encountered during food ordering online in this pandemic time. In this

concern, the proponents found this an opportunity to help the café/restaurant that the

researchers chosen. In admin system it can add, update and delete (categories, dishes,

and beverage on the menu), it may also view and update sales and inventory, also

can view payment details, reports, and ratings from the customers. The customers also

receive notification if the order is accepted or cancelled. In users system can view or

search items, augment cart, place orders, and can process a payment they can choose

a payment method (Cash on delivery, GCASH). User also can choose order method

(Dine-in, Pick up, and delivery), and leave a ratings.

This presents the figures of the existing system and proposed system namely the

context diagrams, diagram, child diagrams, entity relationship, normalization, un-

normalization and data dictionary.

To fully implement the propose project the proponents needs to characterize

what are the segments, the programming determination and the flow use to the system

and how the propose project works.

Narrative Explanation of the Existing System

Since the administration of the CAFÉ’ BOS, it has been using a manual system,

and obviously its time consuming and hassle to use in terms of speed, reliability,

accuracy, and efficiency. The administration is seeking a better way that will help them

handle the ordering and delivery better, more efficiently, and more conveniently for them

and for the customers.

Cashier
Process

Order details
Payment

Order Details

Customers Staff
Chef
Payment

Served

Fig. 1 Context Diagram of Existing System

Context Diagram of Existing System (Fig.1) :

The explanation within the context diagram of the existing system is that the

customers will order manually to the staff, and after they made an order they'll place a

payment. The staff will give the order details and payment to the cashier and therefore

the cashier will forward the order to the chef, afterwards, the chef will serve the order

to the customers.
Narrative Explanation of the Proposed System

Online food ordering system is the proposed system, which would make the

manual system more convenient and time-saving. In this proposed system gives

restaurants the ability to increase sales and expand their business by giving customers

the facility to order food online and it will also allow the restaurants too quickly and

easily manage an online menu which customer can browse and use to place orders with

just a few clicks. There will be a system administrator who will have the right to add and

manage user accounts, a manager who will be managing delivery boy, products and

orders.
 Admin Staff
Accept or decline

Order details
Process

Order
Customers 0
Delivery
CAFÉ BOS online food
Dine in or delivery
ordering system

Served
Cash on delivery

FIGURE 2.CONTEXT DIAGRAM OF PROPOSED SYSTEM

Context Diagram of Proposed System Fig.2)

Context Diagram of Proposed System (Fig. 2) : The proposed enhancement of

existing manual system goes to be an online Food Ordering System. Its function is to

view menu, add to cart, place order and it also includes payment methods (Gcash and

Cash on delivery) and order method (delivery and dine in). By this system it will be very

useful during this this time of pandemic, using this system, this café can still operates

while following the pandemic protocols.

Diagram 0 of existing process (Fig.3)

The diagram of the proposed system is stated in the figure below. The figure

shows how the proposed system works within the user’s registration of the new system.

Before purchasing, the user has to register an account to achieve access to the web

site, after creating an account the user has to log in, upon creating an account it

will automatically reflect within the database, the database will quickly respond that the

user have successfully created an account. Just in case the user forgot their passwords,

they still have a choice to recover them by entering forgot password button, your

previous account within the database are going to be updated.

Request for Check for

Registration Registration
\
USER Registration user_id
Response Response
Accept/reject

Request for Login Check for Login

Login
Response Accept/reject Response

Request for get password Check for new password

Forgot
Password
Response Accept/reject Response

Fig.3 Diagram 0 of existing process

Child Diagram of Process 1 (Fig.4)

The flow diagram of the proposed system is stated within the figure below. The

figure shows how the proposed system works within the user’s interface of the new

system, this technique includes the method that the users can view or search

items, augment cart, place orders, and can process a payment they can choose a

payment method (Cash on delivery, GCASH). User also can choose order method

(Dine-in, Pick up, and delivery), and leave a ratings.

Fig.4 Child Diagram of Process 1

Check for
Show Categories Show categories
Show/Search
USER category_id
Response
Category
Response
Accept/reject m
Request for Check for
Available Dish Available Dish

Dishes
Response Response
Accept/reject
order_id
Check for order
detail
Request for food order

Add to cart
Response Response
Accept/reject

Check for placing the

Request for placing the order
order
Place Order
Response Response
Accept/reject
Child Diagram of Process 2 (Fig.5)

The flow diagram of the proposed system is stated within the figure below. The

figure shows how the proposed system works within the admin’s interface of the new

system. In the admin interface, it can add, update and delete (categories, dishes, and

beverage on the menu), admin can also manage users and also the delivery guy, it may

also view and update sales and inventory. Admin also can view payment details,

reports, and ratings from the customers. If customers have already placed orders the

admin will notify the customer if the order is accepted or cancelled.

s ADMIN
Request for Login
0

LOGIN

Response accept/reject

Product manage
(Add, update, Delete) 1 Check product detail
admin_id
MANAGE
PRODUCTS
Response accept/reject Response

Request for view order Check payment detail

admin_id
2

VIEW ORDER
Response accept/reject

Check Active/Deative
Active/Deactive Delivery boy delivery_boy
3

MANAGE DELIVERY
Response
Response

Request review for payment

Check payment detail
4 admin_id
Response accept/reject
VIEW PAYMENT
Response
Response

View report/ratings Generate report/ratings

5

REPORTS/RATING
Response
S
Generate report/ratings

Fig.5 Child Diagram of Process 2

 user_id First_Name Last_Name Middle_Name

rating
ID Account_Status

Rating rate Customer

order_id Password
Email

dish_detail Username
_id
Phone Number

has

menu_i ID qty order_id ID menu_id

d
category_id
image
Menu has Order Details
place

Status amt no of serving total_amt

belong
s

Fig.6 Entity Relationship of the Proposed System

order_n payment_i
Category msg amt
umber d

amt
user_id
user_id
category status Order status
_id Payment id
added_on

order_date
type

process
process
id name

email_addr
description ess

contact_usn Site username

update User
fo Information
password
address

name id contact
user_id
APPENDICES

TABLE 2: NOMALIZATION

UNFORMALIZED

admin banner

category contact_us

coupon_code delivery_boy

dish dish_cart

dish_details order_details

order_master order_status

rating setting

user wallet

1st Normal Form

Table 2.1 Tbl Admin Login

Primary key: id
Id name username password email

Table 2.2 Tbl Category

Primary key: id
Id category order_number status added_on

Table 2.3 Tbl Coupon Code

Primary key: id
Id coupon_code coupon_type coupon_value cart_min_value

expired_on status added_on

Table 2.4 Tbl Delivery Boy

Primary key: id
 Id name mobile password status

added_on

Table 2.5 Tbl Dish management

Primary key: id
Id category_id dish dish_detail image

type status added_on Table 2.6 Tbl Dish Details

Primary key: id
Id dish_id attribute price status

added_on
2nd Normal Form

Table 2.7 User management

Primary key: id
Id name email mobile password

status email_verify rand_str referral_code from_refferal_code

added_on

Table 2.8 Tbl Banner

Primary key: id
Id image heading sub_heading link

link_txt order_number added_on status

Table 2.9 Tbl Contact Us

Primary key: id
Id name email mobile subject

message added_on
Table 2.10 Tbl Dish Cart
Primary Key: id
 Id user_id dish_detail_id qty added_on

Table 2.11 Tbl Order Detail

Id order_id dish_details_id price qty
Primary Key: id

Table 2.12 Tbl Order Master

Id user_id name email mobile
address total_price coupon_code final_price zipcode
delivery_boy_i payment_status payment_type payment_id order_status
d
Primary key: id

Table 2.13 Tbl Order Status

Primary Key: id
id order_status

cancel_by cancel_at added_on delivered_on

Table 2.14 Tbl Rating
Primary Key: id
id user_id order_id dish_detail_id rating

Table 2.15 Tbl Settings

Primary Key: id
id cart_min_price cart_min_price_ms website_close wallet_amt
g
Table 2.16 Tbl Wallet
website_close_msg referral_amt Primary key:
id user_id amt msg type

TABLE 3: DATA DICTIONARY

payment_id added_on
Fieldname Data Type

Table 3.0 Tbl Admin Login

Primary key: id
id Integer
 name varchar

username varchar

password varchar

email varchar

Table 3.1 Tbl Category

Primary Key: id
id Integer

category varchar

order_number Integer

status Integer

added_on datetime

Table 3.2 Tbl Coupon Code

Primary Key: id
id Integer

coupon_code varchar

coupon_type enum(‘P’,’F’)

coupon_value Integer

cart_min_value Integer

expired_on date

status Integer

added_on date_time

Table 3.3 Tbl Delivery Boy

id Integer

name varchar

mobile varchar

password varchar

status Integer
 added_on datetime

Primary key: id

Table 3.4 Tbl Dish Management

Primary key: id
id Integer

category_id Integer

dish varchar

dish_detail text

image varchar

type enum(‘veg’,’non-veg’)

status Integer

added_on datetime

Table 3.5 Tbl Dish Details

Primary Key: id
id Integer

dish_detail Integer

attribute varchar

price integer

status Integer

added_on datetime

Table 3.6 User Management

Primary key: id
id Integer

name varchar

email varchar

mobile varchar

password varchar
 status integer

email_verify integer

rand_str varchar

referral_code varchar

from_referral_code varchar

added_on datetime

Table 3.7 Tbl Banner

Primary key: id
id Integer

image varchar

heading varchar

sub_heading varchar

link varchar

link_txt varchar

order_number integer

added_on datetime

status integer

Table 3.8 Tbl Contact Us

Primary Key: id
id Integer

name varchar

email varchar

mobile varchar

subject varchar

message text

added_on datetime

Table 3.9 Tbl Dish Cart

Primary Key: id
id Integer

user_id integer

dish_detail_id integer

qty integer

added_on datetime

Table 3.10 Tbl Order Detail

id Integer

order_id integer

dish_details_id varchar

price float

Primary Key: id
Table 3.11 Tbl Order Master
Primary Key: id
id Integer

user_id integer

name varchar

email varchar

mobile varchar

address text

total_price float

coupon_code varchar

final_price float

zipcode varchar

delivery_boy_id integer

payment_status varchar

payment_status varchar

payment_id varchar

order_status integer
 cancel_by enum(‘user’,’admin’)

cancel_at datetime

added_on datetime

delivered_on datetime

Table 3.12 Tbl Order Status

Primary key: id
id Integer

order_status vachar

Table 3.13 Tbl Rating

Primary Key: id
id Integer

user_id integer

order_id integer

dish_detail_id integer

rating integer

Table 3.14 Tbl Settings

Primary key: id
id Integer

cart_min_price integer

cart_min_price_msg varchar

website_close integer

wallet_amt integer

wallet_close_msg varchar

referral_amt integer
Table 3.15 Tbl Wallet
Primary Key: id
id Integer

user_id integer

amt integer

msg vachar

type enum(‘in’,’out’)

payment_id varchar

added_on datetime

Based from the outline of chapter 3, it’s more about technical Background that should encompass E-R
and the technical aspect of the project, technologies to be used and how the project will work.

What you have presented are just the context diagram, process flow, data flow diagram and data
dictionary. I think you need to be specific about the technologies to be used.

You may present the following:

1. Software tools/technologies to be used for development.

2. Server/client setup. ( Is it to be hosted locally or in the cloud?)
3. Can it be accessed through mobile devices?
4. Discussion on how the data is processed technically once an order is chosen by the customer up
to the time when the order is to be prepared for delivery.