Wings X Pasta’s Web-Based Ordering, Seat And

Event Reservation System

A Project Study Presented to the

College of Informatics and Computing Sciences
Batangas State University
Batangas City

In Partial Fulfillment of the Requirements for the Courses:

IT311: Systems Administration and Maintenance
IT312: System Integration and Architecture
IT313: System Analysis and Design
IT314: Web Systems and Technologies

By:

ESTERON, REYNALYN MARIZ M.

FALCULAN, OWEN PATRICK F.
MALABANAN, KYLA S.
MANALO, ARRA GRACE E.
MARASIGAN, JOHN ERIC M.

IT-BA-3104

December 2020
 Table of Contents

I Introduction 1
I.1. Project Context 1
I.2. Purpose and Description 2
I.3. Objectives 3
I.4. Scope and Limitations 3

II System Analysis 5
II.1. Development Model 5
II.2. Development Approach 6
II.3. Schedule and Timeline 6
II.4. Project Teams and Responsibilities 7
II.4.1. Responsibilities 7
II.4.2. Activities and Tasks 8

III System Design 10

III.1. System Analysis and Design 10
III.1.1. Functional Requirements 10
III.1.2. Non-Functional Requirements 11
III.2. Data Flow Diagram 12
III.3. Graphical User Interface 15

IV System Integration 25
IV.1. Integration Support 25
IV.1.1. Resources and their Allocation 25
IV.1.2. Training 28
IV.1.3. Testing 30
IV.1.4. Change procedures and history 35

V System Administration and Maintenance 39

V.1. Risk Management Process 39
V.2. Financial Impact 44
V.3 Timeline Impact 44
V.4 Risk Monitoring 45
V.5.Risk Categories 46
V.6. Risk Assessment Matrix 47
V.7. Mitigation Grading Matrix 48
V.8. Stakeholder Tolerances 49
 CHAPTER I

INTRODUCTION

Project Context

Running a food business is a huge task that comes with a never-ending to-do-list.

Most operators probably do not like the idea of adding another assignment but there is one

that is very important, which is a website. The proposed project is to create a web-based

system that will modify or make minor changes to the past traditional transactions or

methods in WingsxPastaHQ and Tea-Tol milk tea shop. The WingsxPastaHQ restaurant

and Tea-Tol milk tea shop had a significant increase in the past few months. The restaurant

is often full well before the dining hours and on the other hand, the milk tea shop is having

a lot of orders any time of the day. Often parties of high revenue potential are declined

upon arrival because the seating capacity has been occupied by earlier arriving customers

in WingsxPastaHQ. However, on Tea-tol, it is quite time consuming for the customers to

receive their orders since they do not have much manpower considering that the milk tea

shop is just starting to pop up. Therefore, the project team have decided to make a web-

based system for handling deliveries, dine-in orders, seat and event reservations to provide

flexible accommodations. Managing the increased demand, pricing, and table utilization is

critical to the restaurant business profitability. The seat and table reservation on the

restaurant and the lack of having enough manpower on the milk tea shop are a well-defined

problem. It is also important for business owners to monitor their sales and visualize the

1
direction of their business hence the system that will be developed will offer various

visualizations prior to business status.

There are a number of fixed time periods of a certain interval, thirty minutes in this

study, in each of which there are a number of requests for reservations in WingsxPastaHQ.

The size of a reservation is represented by the number of seats requested. Tables and seats

are allowed to combine when it comes to a large number of people to satisfy their needs.

On the other hand, Tea-tol needs a web-based application which handles deliveries since

they are receiving a lot of good feedback and deliveries from time to time despite how

small and simple their shop is.

Purpose and Description

WingsxPastaHQ and Tea-Tol website is designed to be user friendly that provides

flexible accommodation for a wide range of requirements. The proposed project will be

beneficial to the user since the transaction would require lesser minutes or hour in terms of

providing the output to the user. The purpose of the project is to have a web-based ordering

system for both restaurant and milk tea shop and also the seat reservation/dine-in order for

WingsxPastaHQ. Since all the orders would come from the website, it would be beneficial

for the business owner since they can analyze the data and see the status of their business.

The website will have an admin panel, managed by business owner/staff, which will

include a dashboard that displays today’s data such as number of orders and customers and

total sales for the day. The admin side also manages received deliveries, seat reservations,

event reservations and dine-in orders. There is also an analytics tab wherein visualizations

2
display customer analytics, current month sales, all-time sales and stars received through

customer feedbacks.

Objectives

The main objective of the project is to create a web-based system for

WingsxPastaHQ restaurant and Tea-Tol milk tea shop. Specifically, the system aims to

achieved the following objectives:

1. To develop a system that will manage delivery requests, dine-in orders, seat and event

reservations.

2. To develop a system that will improve current business process and establish smooth

transactions among business owners, staff and customers.

3. To provide sales and customer analytics to business owners.

Scope and Limitations

The proposed system provides a lot of features such as receiving delivery requests,

seat and event reservations in real time, providing the means for customers to send

feedbacks, and also providing business owners with analytics reports that can be used to

set directions and goals for the business. It also offers processing of dine-in orders that

completes the system by means of data needed for analytics.

In terms of online placing of orders, reservation of seats and for any kind of events

the system is expected to accept basic information from clients like name, contact number,

reservation type (meetings, birthdays, themed parties, intimate gatherings and others) time

3
of arrival, number of seats, advance orders and any other request of the customer. Also, the

online advertisement located in the home page of the site helps the customers know what

WingsxPastaHQ and Tea-tol offers. The advertisement in the website is a big help in the

business by means of reaching the customers easily. From posting any updates like:

promos, events, new products and all that will satisfy the customers cravings. The system

also does not require logging in or creating accounts for the customers which means that

customers will initially send their order or requests and the expected confirmation will be

sent via text or call from the restaurant.

The system also has its limitations. The information inputted by the customers will

not be saved when their devices were refreshed or disconnected from the system. In short,

if these circumstances happened, they will need to input their orders or information once

again. When customers send requests such as for delivery or seat reservations, some details

in the admin panel were updated asynchronously except in the analytics tab wherein the

business owner or staff needs to refresh the page first when displaying the latest data.

4
 CHAPTER II

SYSTEM ANALYSIS

Development Model

Figure 2.1 shows the development model that will serve as the framework on the

development model of the project.

Figure 2.1 Agile Development Methodology (Onion Advisor Technology, 2019)

Agile is an iterative approach to project management and software development that

helps teams deliver value to their customers faster and with fewer headaches. Instead of

betting everything on a "big bang" launch, an agile team delivers work in small, but

consumable, increments. Requirements, plans, and results are evaluated continuously so

5
teams have a natural mechanism for responding to change quickly. The required software

starts with a simple design, then to code small functions and modules. The work on these

functions and modules is done in weeks for each life cycle which is called increment or

sprint. In these sprints, errors to be recognized, and customer feedback to be incorporated

into the design of the next increment (Ben-Zahia and Jaluta, 2014).

Development Approach

The project team used top-down development approach. The top-down approach is

an approach to program development in which progress is made by defining required

elements in terms of more basic elements, beginning with the required program and ending

when the implementation language is reached. At every stage during top-down

development, each of the undefined elements from the previous stage is defined. Until at

some stage, the elements can be defined directly in the implementation language.

Schedule and Timeline

Figure 2.2 shows the schedule for the development of the project. Gantt chart was

used to represent the tasks involved in systems development. In Gantt chart, project

management timelines and tasks are converted into a horizontal bar chart, showing start

and end dates, as well as dependencies, scheduling and deadlines, including how much of

the task is completed per stage and who is the task owner.

6
 Figure 2.2 Gantt Chart

Project Teams and Responsibilities

This section contains the assignments of modules and activities to be done by each

team member.

Responsibilities

Table 2.1 shows the roles or responsibilities of each team member together

with their address and contact information.

7
 Roles /
Name Address Contact Number
Responsibilities

Esteron, Reynalyn San Pascual,

System Analyst 09102216131
Mariz M. Batangas

Falculan, Owen
Lead Developer Lipa City 09202966963
Patrick F.

Malabanan, Kyla UI Designer / San Luis,

09752012880
S. Contractor Batangas

Manalo, Arra
Software Tester Ibaan, Batangas 09550956698
Grace E.

Marasigan, John
Programmer Batangas City 09155907413
Eric M.

Table 2.1 Project Team Responsibilities

Activities and Tasks

Table 2.2 provides a brief description of each major task performed by each

member of the project team for the development of the system.

Major Task Performed Task owner Start and End of Task

Determine the overall

project scope, identify Reynalyn Mariz M.
Day 1 - Day 4
key personnel and Esteron
develop timelines
Define system Reynalyn Mariz M.
Day 5 – Day 6
requirements Esteron

8
 Define safety and Reynalyn Mariz M.
Day 7 – Day 8
security requirements Esteron
Cost and schedule
Reynalyn Mariz M.
estimates and staffing Day 9 – Day 13
Esteron
plans
Establish development
Kyla S. Malabanan Day 12 – Day 14
framework and approach

Develop web design Kyla S. Malabanan Day 15 – Day 19

John Eric M. Marasigan

Specify software
and Owen Patrick F. Day 20
requirements
Falculan

Write code for client side John Eric M. Marasigan Day 20 – Day 32

Write code for admin

Owen Patrick F. Falculan Day 27 – Day 36
side

Integration of system
Owen Patrick F. Falculan Day 37 - Day 41
modules

Establish test procedures Arra Grace E. Manalo Day 41 – Day 42

Conduct unit testing Arra Grace E. Manalo Day 43 – Day 46

Conduct qualification
Arra Grace E. Manalo Day 47 - Day 48
testing

System deployment Owen Patrick F. Falculan Day 49

Table 2.2 Activities and Tasks

9
 CHAPTER III

SYSTEM DESIGN

System Analysis and Design

System analysis focuses on system requirement description; defines the system

functional requirements, and requirement specification of the proposed system. System

design provides the technical specification and construction of the solution for the

requirements identified during the system analysis phase of the research/project.

Functional Requirements

Functional requirements are product features or functions that developers

must implement to enable users to accomplish their tasks. Table 3.1 and Table 3.2

shows the hardware and software requirements which are needed in order to develop

the proposed system.

Hardware Recommended specifications

Hard disk drive at least 50 GB free space

Processor Dual core

Memory At least 8 GB

Table 3.1 Hardware Requirements

10
 Software Recommended versions

Visual Studio Code version 1.36 +

PgAdmin 4 version 4.0.0 +

Docker Desktop version 2.4.0 +

Git version 2.20 +

Python version 3.8

Table 3.2 Software Requirements

Non-functional Requirements

1. Performance

1.1 The system is expected to be mobile responsive.

1.2 Data sent from the customers are expected to be received in less than 1

second.

2. Accessibility

The system shall be accessible for business owners and customers at any

given point in time.

3. Maintainability

The system shall be easy to maintain when an error or bug arises.

4. Usability

11
 The system must be clear and user-friendly. The interface and features

provided must be easily adapted by customers and business owners.

5. Portability

The system is expected to run with most of the browsers including mobile

browsers.

6. Data Integrity

Any issues concerning data will be handled properly.

7. Scalability

The system is expected to handle multiple customers asynchronously.

8. Security

The system shall have an authentication module for accessing admin panel.

Any users who directly access the admin panel through the URL will be blocked.

Data Flow Diagram

Figure 3.1 shows the whole process of the system modelled through context

diagram. Context diagrams define how the business process or computer system interacts

with its environment. Context diagrams are used early in a project to describe the entities

of the system. It shows the external entities and data flows into and out of the systems. As

shown in the figure, three external entities were defined. Customer who requests for

deliveries, seat and event reservations. Staff who manages deliveries, seat reservations and

also processes dine-in orders. Lastly, the business owner, which accommodates event

reservations and monitor sales and customer data through analytics report.

12
 CUSTOMER

DELIVERY
REQUEST
SEAT
RESERVATION
REQUEST EVENT
RESERVATION
REQUEST

0 VALID
EVENT
WINGS X PASTA’S WEB- RESERVATION
BASED ORDERING, SEAT AND REQUEST BUSINESS OWNER
EVENT RESERVATION ANALYTICS
SYSTEM REPORT

VALID
SEAT PENDING
DELIVERY
RESERVATION DINE-IN
QUEUE
REQUEST ORDERS

SEAT
DELIVERY DINE-IN
RESERVATION
DETAILS ORDERS
STATUS

STAFF

Figure 3.1 Context Diagram of the Proposed System

13
 1
EVENT
VALIDATE EVENT RESERVATION BUSINESS OWNER
RESERVATION REQUEST LIST

VALID EVENT
EVENT ANALYTICS REPORT
RESERVATION REQUEST
RESERVATION LIST
EVENT
RESERVATION EVENT RESERVATION 6
REQUEST

GENERATE
ANALYTICS REPORT

DELIVERY

DELIVERY
DELIVERY
QUEUE LOG DATA
REQUEST

CUSTOMER DELIVERY DELIVERY

PROCESS DELIVERY LOGS
REQUEST DETAILS
REQUESTS

SEAT RESERVATION REQUEST

DELIVERY
DELIVERY
QUEUE
DETAILS
3
SEAT
VALIDATE SEAT RESERVATION STAFF
RESERVATION REQUEST LIST
SEAT SEAT
RESERVATION RESERVATION
STATUS DETAILS
VALID SEAT SEAT
RESERVATION RESERVATION
REQUEST LIST

4
SEAT RESERVATION PENDING
DINE-IN DINE-IN
CHECK SEAT RESERVATION
ORDERS ORDERS
STATUS

DINE-IN
ORDERS

PENDING
DINE-IN 5
ORDERS
PROCESS
DINE-IN DINE-IN
DINE-IN ORDERS
DETAILS
DINE-IN
ORDERS

Figure 3.2 Level-0 Diagram

14
 Figure 3.2 shows the more comprehensive flow of the system as presented in the

Level-0 Diagram. Process 0 was break down into six different processes and data stores

can now be seen in the diagram. As shown in the diagram, requests from customers are

first validated and stored in the data stores. Then, data stores return all the data to staff and

the business owner. Paid and cancelled deliveries are stored in logs as well as cancelled

seat reservations. The information from the customers who reserved for a seat and arrived

at the site are then transferred into dine-in orders. Staff can also process dine-in orders and

all of these information will be stored to logs. Since all the transactions are stored in logs,

the data stored can be used to generate analytics report for the business owner.

Graphical User Interface

The figures below are sample interfaces of the web-based system. Client-side page

can be accessed in https://wingsxpastahq.herokuapp.com/. Login for admin in

https://wingsxpastahq.herokuapp.com/adminsite/ with username admin and password

wingspasta.

Figure 3.3 Home Page in Mobile and Desktop

15
 Figure 3.3 shows the home page of the system in mobile and desktop view. Short

narrative on what is Wings and Pasta, advertisements and images on what the restaurant

offers are present in the home page.

Figure 3.4 Seat Reservation in Mobile and Desktop

Figure 3.5 Delivery in Mobile and Desktop

16
 Figures 3.4 and 3.5 shows the process of seat reservation and requesting for delivery

in mobile and desktop view. In requesting for seat reservation, customers are expected to

input their information such as their name, contact number, number of persons dining date

and time of arrival. Customers also have the option to add pre-orders. As the customers

add their pre-orders, the total price of all the meals they added are displayed.

In requesting for deliveries, customers need to add orders and their information in

checkout form otherwise their request will not come through. Confirmation from both seat

reservation request and delivery request will not come from the system but from the text

message or call from the restaurant.

Figure 3.6 Event Reservation

17
 Figure 3.6 shows the form in requesting for event reservation. Like in requesting for

seat reservation and delivery, the customers are required to fill up all the inputs in the form

otherwise the system will reject the request. The confirmation for event reservation will

come from text message or call from the restaurant.

Figure 3.7 Footer

Figure 3.7 shows the footer of the page wherein users can send feedbacks. Links to

seat reservation, delivery and event reservation are also displayed in the footer.

18
 Figure 3.8 Dashboard

Figure 3.8 shows the dashboard that is located in admin side. In dashboard,

operational data were displayed such as delivered and pending orders, sales comparison

between yesterday and today and also total number of customers today in terms of dine-in

and deliveries. Two charts are also displayed in dashboard which is sales in the last 30 days

19
and top 3 meals of the week. Latest feedbacks and upcoming events are also displayed at

the bottom of the page.

Figure 3.9 Dine-in Tab

Figure 3.9 shows the dine-in tab which processes dine-in orders on site. Staffs are

the one who will add orders as per requested by the customers. As the staff adds order, all

the meals added will be displayed in Added orders pane. If the staff is now finished adding

orders, the system is expecting for the table number and number of customers. After the

staff filling all the required inputs. All the information including table number, number of

customers and dine-in orders will be displayed in order status pane. The order status pane

20
provides some functionalities for the staff such as viewing, editing and deleting the orders.

Deleting and marking as paid will both be stored in logs.

Figure 3.10 Delivery Tab

Figure 3.11 Seat Reservation Tab

Figures 3.10 and 3.11 shows the delivery and seat reservations tab. Both of these

tabs are responsible for displaying delivery and seat reservation requests. In delivery,

21
requests can be mark as paid and cancelled. The staff can also indicate the status of delivery

whether it is a new order, preparing or on delivery. In seat reservation tab, requests include

the information sent by the customers such their basic information and added orders. These

requests can also be marked as dine-in and cancelled. If dine-in button was clicked, all the

information on the request will be transferred in dine-in tab. Both transactions made will

be stored in logs.

Figure 3.12 Analytics Tab

22
 Figure 3.12 shows the analytics tab wherein various visualizations are displayed

such as customer analytics, all time sales and sales proportion in dine-in and delivery.

Figure 3.13 Feedbacks Tab

Figure 3.14 Events Tab

23
 Figures 3.13 and 3.14 shows feedbacks tab and events tab. Feedbacks received and

event reservation requests are displayed in these tabs.

Figure 3.15 Logs Tab

Figure 3.15 shows the logs tab where all transactions made were stored. In case of

misclick where the staff mistakenly deleted a request like dine-in order, delivery or

reservations, the staff can restore all the information. In logs, each of transactions’

information can also be viewed. The staff also have the option to permanently delete a

transaction.

24
 CHAPTER IV

SYSTEM INTEGRATION

INTEGRATION SUPPORT

This section describes the support software, materials, equipment, and facilities

required for the integration, as well as the personnel requirements and training necessary

for the integration.

Resources and their Allocation

In this section, the tables below show the facility, equipment, and support

software required for the project development and system integration. It also

indicates the personnel needed and their estimated cost and wages.

Facility Address Monthly Rent Total Rent

2nd Floor, WxP

Php 12,000.00
WxP Tech Bldg.., Lemery, Php 6,000.00
(2 months)
Batangas

Table 4.1 Rented facility

Table 4.1 shows the facility rented by the project team. The rented facility is

located at Lemery, Batangas with monthly rent that costs Php 6,000. The

development of the whole project lasts for only two months which totals the rent to

Php 12,000.

25
 Number of Cost per
Equipment Description of use Total Cost
units unit
Project designing,
Desktop
development and 3 Php 25,000 Php75,000
Computers
testing
Computer table, ad
Tables 3 Php 1,500 Php 4,500
hoc use

Chairs Ad hoc use 5 Php 800 Php 4,000

LAN and Internet

Router 1 Php 1,500 Php 1,500
connection

Printer Printing Documents 1 Php 3,500 Php 3,500

Bond paper Documentation 1 Php 150 Php 150

Table 4.2 Equipment used in project development

Table 4.2 shows all the equipment used for system development and

integration. The equipment used in facility are desktop computers for designing,

development and testing of the system, tables and chairs, router for LAN and

Internet connection, printer and bond paper for printing documents.

Number of Cost per

Software Description of use Total Cost
units unit

Visual
Text Editor 2 Free ---
Studio Code

26
 PostgreSQL
PgAdmin 4 2 Free ---
Database Server

Docker Running Redis in

2 Free ---
Desktop Docker Container

Version control and

Git 2 Free ---
collaboration

Microsoft Php 350 /

Documents 1 Php 700
Office month

Heroku Website hosting 1 Free ---

Redis Labs Redis Server hosting 1 Free ---

Table 4.3 Software used in project development

Table 4.3 shows all the software used for system development and

integration. For the development phase, the team used visual studio code as text

editor, PgAdmin 4 for the database server and Docker Desktop to run Redis instance

in a docker container since Redis is not supported in Windows operating system.

The team also used Git, a version control system, for code cooperation and

collaboration. Most of the software used costs free except for the Microsoft office

which costs Php350 per month. Heroku and Redis Labs were used for hosting the

system on the Internet.

27
 Personnel Designation Monthly Wage Total Wage

Esteron, Reynalyn
System Analyst Php 22,000 Php 44,000
Mariz M.

Falculan, Owen
Lead Developer Php 30,000 Php 60,000
Patrick F.

Malabanan, Kyla
UI Designer Php 22,000 Php 44,000
S.

Manalo, Arra
Software Tester Php 22,000 Php 44,000
Grace

Marasigan, John
Programmer Php 25,000 Php 50,000
Eric

Table 4.4 Project team

Table 4.4 shows persons involved in project development and integration

their corresponding monthly and total wages. The project team consists of lead

developer, system analyst, UI designer, software tester and computer programmer.

Training

Table 4.5 shows the table of contents of the sample training manual for the

client. The training manual provides instruction on how to use the various features

of the system such as sending feedbacks, locating URL for admin and logging into

it, receiving delivery and seat reservation requests, and also some instructions on

processing dine-in orders.

28
 Wings X Pasta Training Manual

How to use this manual? 1

I Getting Started 1
System Walkthrough 2
System Components 2
Navigation 3
Client Side 5
Admin Side 7

II Client Side 8
Home Page 8
Clock 9
Links 9
Footer 10
Sending Feedbacks 10
Seat Reservation 11
Seat Reservation Form 11
Form validation 12
Pre-orders 13
Removing orders 13
Confirmation 14
Delivery 15
Adding orders 16
Viewing orders 17
Removing orders 17
Checkout form 18
Delivery Confirmation 19
Event Reservation 20
Filling up the form 21
Form validation 22
Sending event reservation request 22

III Admin 23
Admin URL 23
Logging in 24
Sessions 24
Dashboard 25
Dine-in Tab 26
Adding dine-in orders 26
Viewing dine-in orders 27
Editing dine-in orders 27
Delivery Tab 28
Seat Reservation Tab 29
Analytics Tab 30
Feedbacks Tab 31
Events Tab 32
Logs 33

Table 4.5 Table of Contents of the Sample Training Manual

29
Testing

This section includes all the tests conducted after the system has been

developed. The tables below include the following attributes: test case ID, test case

description, test execution steps, inputs and outputs, test results and also the one

who is responsible for the testing.

Test
1 Description Evaluating page URLs
ID
Test Execution Steps
S. Expected Test
Tester Action Inputs Actual Output
No. Output Result
Arra Launch https://wingsxpastahq.
1 Home Page Home Page Pass
Manalo Home Page herokuapp.com/
Click link Seat Seat
Arra https://wingsxpastahq.
2 for Seat Reservation Reservation Pass
Manalo herokuapp.com/reserve/
Reservation Page Page
Click link
Arra https://wingsxpastahq.
3 for Delivery Page Delivery Page Pass
Manalo herokuapp.com/order/
Delivery
Click link Event Event
Arra https://wingsxpastahq.
4 for Event Reservation Reservation Pass
Manalo herokuapp.com/event/
Reservation Page Page
Launch
Arra https://wingsxpastahq.
5 Login Page Login Page Login Page Pass
Manalo herokuapp.com/adminsite/
for Admin

Table 4.6 Evaluating page URLs

Table 4.6 shows the test results on evaluating page URLs. The system is

expected to display correct templates on different endpoints. The inputs for this

particular test are different endpoints. The system passed all the test conducted by

Arra Manalo.

30
 Test
2 Description Evaluating seat reservation functionalities
ID
Test Execution Steps
S. Expected Test
Tester Action Inputs Actual Output
No. Output Result

Fill up the Representative name: Test

Arra form with Contact number: No input “Please fill out “Please fill out
1 Pass
Manalo missing Date: No input all inputs.” all inputs.”
data Time of Arrival: No input

“Your “Your
Representative name: Test reservation reservation
Fill up the
Contact number: request has request has
Arra form with
2 09202966963 been sent. We been sent. We Pass
Manalo complete
Date: 12/7/2020 will call you will call you
data
Time of Arrival: 12:00PM within 5 within 5
minutes.” minutes.”
Representative name: Test
Reserve Contact number: “We are “We are
Arra
3 seat in 09202966963 closed at that closed at that Pass
Manalo
closed time Date: 12/7/2020 time.” time.”
Time of Arrival: 9:00AM

Table 4.7 Evaluating seat reservation functionalities

Table 4.7 shows the test results on evaluating seat reservation functionalities.

In this test, the system should validate and display correct message in different

inputs of the customer. This test of functionality is to ensure that the data which

flows into the system is correct.

Test Evaluating calculation of total order prices in delivery and seat

3 Description
ID reservation’s pre-order
Test Execution Steps
S. Expected Test
Tester Action Inputs Actual Output
No. Output Result
Click on
3 x Unli Wings + Unli
seat
Arra Rice, Total price: Total price:
1 reservation Pass
Manalo 2 x Nachos Overload, Php 1401 Php 1401
and add
4 x Pinoy Spaghetti (Solo)
pre-orders

31
 3 x Unli Wings + Unli
Arra Remove Total price: Total price:
2 Rice, Pass
Manalo one meal Php 1005 Php 1005
2 x Nachos Overload
Click on 2 x Bacon Carbonara
Arra delivery (Party Size), Total price: Total price:
3 Pass
Manalo and add 1 x Small Bilao, Php 2722 Php 2722
orders 1 x Fries Platter
Arra Remove 1 x Small Bilao, Total price: Total price:
4 Pass
Manalo one meal 1 x Fries Platter Php 724 Php 724

Table 4.8 Evaluating total price calculation

Table 4.8 shows the test results on evaluating total price calculation. The

system is expected to calculate the correct total price for all the meals added by the

customer. Customers are also allowed to remove orders in which the system is

expected to recalculate the total price. The system passed all the test conducted by

Arra Manalo.

Test
4 Description Admin login test
ID
Test Execution Steps
S. Expected Test
Tester Action Inputs Actual Output
No. Output Result
Go to the
admin https://wingsxpastahq.
“Access “Access
Arra dashboard herokuapp.com/
1 denied! Login denied! Login Pass
Manalo directly adminsite/
in here.” in here.”
without dashboard/
logging in
Enter
correct
Arra Username: admin Admin Admin
2 username Pass
Manalo Password: wingspasta Dashboard Dashboard
and
password
Enter
incorrect
Arra username Username: test “Access “Access
3 Pass
Manalo and Password: wingspasta denied.” denied.”
correct
password

32
 Enter
correct
Arra username Username: admin “Access “Access
4 Pass
Manalo and Password: test denied.” denied.”
incorrect
password

Table 4.9 Admin login test

Table 4.9 shows the test results on admin login. As shown in the first test

case, the system is expected to block all the users who directly enter the URL for

dashboard without logging in. The system was able to block those users since there

is no session variable set and this session variable can only be set when the user logs

in. The rest of the test cases are all about validating credentials. The system is

expected to validate user’s input and only allow users with correct credentials to

login.

Test
5 Description Evaluating dine-in functionalities
ID
Test Execution Steps
S. Expected Test
Tester Action Inputs Actual Output
No. Output Result
Meals added
Meals
will be
Arra 2 x Fries Platter, displayed in
1 Add orders displayed in Pass
Manalo 2 x Pinoy Spaghetti added orders
added orders
pane
pane

Arra 2 x Fries Platter, Total Price: Total Price:

2 Add orders Pass
Manalo 2 x Pinoy Spaghetti Php 396 Php 396

Arra Remove Total Price: Total Price:

3 2 x Fries Platter Pass
Manalo order Php 198 Php 198

33
 Added dine-in
dine-in order
Confirm Added orders, order will be
Arra displayed in
4 dine-in Table number, displayed in Pass
Manalo order status
order Number of customers order status
pane
pane
Added orders
Arra View Added orders
5 Click view button will be Pass
Manalo orders displayed
displayed
Added orders
Added orders
will be
displayed in
displayed in
orders pane,
orders pane,
Arra table number
6 Edit orders Click edit button table number Pass
Manalo and number of
and number of
customers
customers will
displayed into
be displayed
input box
into input box
Dine-in order
Dine-in order
Delete will be
Arra was removed
7 dine-in Click delete button removed and Pass
Manalo and stored to
order will be stored
logs
to logs
Dine-in order
Dine-in order
Mark dine- will be
Arra was removed
8 in order as Click paid button removed and Pass
Manalo and stored to
paid will be stored
logs
to logs

Table 4.10 Evaluating dine-in functionalities

Table 4.10 shows the test results on evaluating dine-in functionalities. Dine-

in is located in Admin and the staff are the ones who adds requested order from the

customers on site. As the staff adds order, the system is expected to calculate the

total price. The system is also expected to recalculate the total price whenever the

staff remove orders. After confirmation of order, the order information should be

displayed in order status pane where the system provides various functionalities

such as viewing, editing, deleting and marking the orders as paid. The system is

expected to respond to these different events.

34
Change Procedures and History

This section includes all changes made during the unit testing. The tables

below contain the following attributes: date of request, the name of the initiator of

request, details of change, approval status and the name of the person who approved.

Change Request

Date: 11/28/2020 Team Leader: Owen Falculan

Design change request from: Kyla Malabanan

Details of Previous Procedure: In home page, the displayed text was “Wings x Pasta is a
business ran by the Malabanan family, managed by Tetol Malabanan.”
Details of Change Required: Change Tetol Malabanan to K-Anne Malabanan.

New Design Verification: 11/28/2020 – John Eric Marasigan

New Design Validation: 11/28/2020 – John Eric Marasigan

Remarks:

Approve changes: Yes

Date approved: 11/28/2020

Person approved: Owen Falculan

Designation: Lead Developer

Screenshots
Before After

Table 4.11 Change request for term error

35
 Table 4.11 shows the change request for term error in home page. The request

came from Kyla Malabanan, verified and validated by John Eric Marasigan and was

approved by Owen Falculan.

Change Request

Date: 11/29/2020 Team Leader: Owen Falculan

Design change request from: Reynalyn Esteron

Details of Previous Procedure: The section headers used Times New Roman as font family.

Details of Change Required: Change font-family to bold Helvetica.

New Design Verification: 11/29/2020 – John Eric Marasigan

New Design Validation: 11/29/2020 – John Eric Marasigan

Remarks:

Approve changes: Yes

Date approved: 11/29/2020

Person approved: Owen Falculan

Designation: Lead Developer

Screenshots
Before After

Table 4.12 Change request for font family

Table 4.12 shows the change request from Reynalyn Esteron. The request

was all about changing the font-family from Times New Roman to Helvetica Bold.

36
 Change Request

Date: 11/30/2020 Team Leader: Owen Falculan

Design change request from: Arra Manalo

Details of Previous Procedure: In home page slideshow, pictures are not related to Wings X
Pasta.
Details of Change Required: Change slideshow pictures with Wings X Pasta related pictures.

New Design Verification: 11/30/2020 – John Eric Marasigan

New Design Validation: 11/30/2020 – John Eric Marasigan

Remarks:

Approve changes: Yes

Date approved: 11/30/2020

Person approved: Owen Falculan

Designation: Lead Developer

Screenshots
Before After

Table 4.13 Change request for home page slideshow

Table 4.13 shows the change request from Arra Manalo. The request was

changing the initial homepage slideshow pictures with images related to the client’s

restaurant. This was approved by Owen Falculan.

37
 Change Request

Date: 12/1/2020 Team Leader: Owen Falculan

Design change request from: Kyla Malabanan

Details of Previous Procedure: In seat reservation form, there is no input for date.

Details of Change Required: Add input for date.

New Design Verification: 12/1/2020– John Eric Marasigan

New Design Validation: 12/1/2020– John Eric Marasigan

Remarks:

Approve changes: Yes

Date approved: 12/1/2020

Person approved: Owen Falculan

Designation: Lead Developer

Screenshots
Before After

Table 4.14 Change request for seat reservation form

Table 4.14 shows the change request for seat reservation form. Initially the

reservation form does not have the input for date. The request came from Kyla

Malabanan, verified and validated by John Eric Marasigan and was approved by

Owen Falculan.

38
 CHAPTER V

SYSTEM ADMINISTRATION AND MAINTENANCE

Risk Management Process

This section explains the process of assessing and treating the risks which can cause

great damage to project development and especially to the institution. Figure 5.1 shows the

five steps of risk management process.

Figure 5.1 Risk Management Process (Invensis Learning, 2020)

The first step in risk management process is identifying potential risks. With

identified risks, members of organization need to analyze and evaluate the risk based on

39
the scope and the amount of severity it can cause. Risks that are not identified and analyzed

have the potential to harm the institution but with early risk evaluation and assessment, the

impact can be reduced and possibly eliminated. Treating the risk is also a vital step in risk

management process since it will reduce the possibility of the risk from recurring and also

the procedure used to treat the risk can be reused. The process also includes the monitoring

and reviewing the risk which makes sure that the risks are continuously monitored to make

the mitigation process more effective.

1. Identify potential risks

The first step in an effective risk management process is to identify the risks

that the institution is currently dealing with or may deal in the future. Table 5.1

shows the identified risks and their corresponding severity, likelihood and level.

Risk
ID Risk Risk Severity Risk Level
Likelihood
Project purpose and need is not
1 Undesirable Improbable Medium
well-defined
2 Scheduling errors Tolerable Improbable Medium

3 Delayed project task Undesirable Possible High

4 Hardware failure Tolerable Possible Medium

5 Security threats Undesirable Possible High

Theft of materials, intellectual
6 Undesirable Improbable Medium
property or equipment
7 Deployment problems Tolerable Possible Medium
Extreme weather which leads to
8 Undesirable Improbable Medium
loss of resources

Table 5.1 Identified risks

40
2. Analyzing the Risk

After identifying the risks, analysis of risks is a must. During the risk

management process, members of the institution estimates the probability of each

risk occurring and defining the amount of severity of each risk. Tables 5.2 and 5.3

shows the likelihood and severity of risks along with their descriptions.

Severity Description

Acceptable Little to no effect on event

Effects are felt, but not critical to
Tolerable
outcome
Serious impact to course of action and
Undesirable
outcome
Intolerable Could result in disaster

Table 5.2 Risk Severity

Severity Description

Improbable Risk is unlikely to Occur

Possible Risk will likely occur

Probable Risk will occur

Table 5.3 Risk Likelihood

3. Evaluating the Risk

After completing a thorough analysis of risks, they need to be ranked in order

of severity and then prioritized. A risk causing minor inconvenience to the

41
organization gets a low rating, whereas risks that can have a big impact on

operations is considered to be high risk. Table 5.4 shows the risk levels and their

corresponding descriptions and actions.

Risk Level Description Action

Low Acceptable Ok to proceed

As low as reasonably
Medium Take mitigation efforts
practicable
High Generally unacceptable Seek support

Extreme Intolerable Place event on hold

Table 5.4 Risk Levels

4. Treating the Risk

Once the risks have been analyzed and prioritized, it is time to take action.

Every risk to the organization or the project needs to either be eliminated or

contained. Table 5.5 shows the mitigating actions on each of identified risks.

ID Risk Mitigating Action

Project purpose and need is not Complete a business case if not already
1
well-defined provided and ensure purpose is well defined.
Track schedules daily and include schedule
2 Scheduling errors review as an agenda item in every project
team meeting.
Track task completion and measure project
3 Delayed project task
progress

42
 Identify any alternate piece of equipment that
4 Hardware failure
may be used as a substitute to the equipment.
Make backups of all software including
5 Security threats
operating systems.
Follow security procedures, ensure non-
Theft of materials, intellectual
6 disclosure agreements, and compliance
property or equipment
certificates are in place.
Ensure all requirements are met before
7 Deployment problems
deployment.
Extreme weather which leads to
8 Establish disaster recovery plan.
loss of resources

Table 5.5 Treating the risks

Table 5.6 shows mitigating action in order to reduce risk impact in budget

and timeline.

Risk Mitigating Action

Budget Monitor and assess correct estimations for costs

Track schedules daily and include schedule

Timeline review as an agenda item in every project team
meeting.

Table 5.6 Risk assessment in Budget and Timeline

5. Monitoring and Reviewing the Risk

Monitoring and reviewing risk is the last part of the risk management process

and involve regular checking or surveillance. The results should be recorded and
43
 reported externally and internally. The results should also be an input to the review

and continuous improvement of the institution's risk management framework.

Financial Impact

Table 5.7 shows the estimated funds required and budgetary impact wherein initial

fees, recurring fees and estimated assumptions are defined. Pricing methodology is also

identified in which the project team used demand-based pricing.

Estimate Description

Initial fees Php 88,650 Includes equipment used for project operation

Includes rent, software subscriptions and

Recurring fees Php 254,700
salary payments. (2 months)
Estimated overall project cost plus indirect
Assumptions Php 360,000
and operational costs.
Demand-based pricing in which the price of a product is finalized
Pricing Methodology
according to its demand.
With risks that could possibly occur during project development,
Budget Impact
correct estimation of budget and costs is a must.

Table 5.7 Estimated Funds Required and Budgetary Impact

Timeline Impact

Table 5.8 shows the incidents occurred during project development that might have

caused delay. The table is consisting of the following attributes: incident, major task at

hand, task owner and the start and end of the affected task.

44
 Major task at Start and End of
Incident Task owner
hand Task
Cost and schedule
Reynalyn Mariz M.
Task owner got sick estimates and Day 9 – Day 13
Esteron
staffing plans
Write code for John Eric M.
Hardware failure Day 20 – Day 32
client side Marasigan
Typhoon hit the
Write code for Owen Patrick F.
country and caused Day 27 – Day 36
admin side Falculan
power outage.

Table 5.8 Incidents occurred during project development

Risk Monitoring

Table 5.9 shows the risk monitoring activities performed during project

development. It is essential to perform these activities to check for possible issues that may

escalate and to ensure that these issues will be properly handled.

Parties Responsible for

Activity Review Frequency
Reviewing
Reviews of Risks and Reynalyn Mariz Esteron
3 times a week
Issues and John Eric Marasigan

Monitoring 2 times a week Owen Patrick Falculan

Kyla Malabanan and Arra

Reporting 3 times a week
Grace Manalo

Table 5.9 Risk Monitoring

45
Risk Categories

Risk management is an essential activity of project management. It is important to

classify risks into appropriate categories. Table 5.10 shows the different categories of risk

with their corresponding descriptions.

Risk Category Description

Risks of loss due to improper process
Operational Risk implementation, failed system or some
external events risks.
Occurs when project tasks and schedule
Schedule Risk
release are not addressed properly.
Wrong budget estimation or project scope
Budget Risk
expansion leads to this kind of risk.
Non-availability of contracts or purchase
order at the start of the project or delay in
Business Risk
receiving proper inputs from the customer
or business analyst.
Risks related to the environment under
Technical Environment Risk which both the client and the customer
work.
The risks related to the security of
information like confidentiality or
Information Security Risk
integrity of customer’s personal / business
data.
The external risks beyond the operational
Programmatic Risks
limits.
Improper planning of infrastructure /
resources may lead to risks related to slow
Infrastructure Risk network connectivity or complete failure
of connectivity at both the client and the
customer sites.
This risk occurs due to incorrect
Quality and Process Risk application of process tailoring and
deviation guidelines.
This risk depends on factors like schedule,
staff, budget and facilities. Improper
Resource Risk
management of any of these factors leads
to resource risk.

46
 This risk occurs due to the uncertain or
Supplier Risk
inadequate capability of supplier.
It is related to the complete change in
Technology Risk technology or introduction of a new
technology

Table 5.10 Risk Categories

Risk Assessment Matrix

LOW MEDIUM HIGH EXTREME

1
RISK 0 ALARP as low as
2
3
RATING Generally
Acceptable reasonably Intolerable
KEY Unacceptable
practicable
Ok to Proceed Take Mitigation Seek Support
Place Event
Efforts
On Hold

SEVERITY

ACCEPTABLE TOLERABLE UNDESIRABLE INTOLERABLE

Effects are felt, Serious impact to

Little to no effect Could result in
but not critical to course of action
on event disaster
outcome and outcome

IMPROBABLE LOW MEDIUM MEDIUM HIGH

Risk is Unlikely
–1– –4– –6– – 10 –
to Occur
LIKELIHOOD

POSSIBLE LOW MEDIUM HIGH EXTREME

risk will likely

–2– –5– –8– – 11 –
occur

PROBABLE MEDIUM HIGH HIGH EXTREME

risk will occur –3– –7– –9– – 12 –

Table 5.11 Risk Assessment Matrix

47
 Table 5.11 shows the risk assessment matrix used in evaluating risks during project

development. A risk matrix is a matrix that is used during risk assessment to define the

level of risk by considering the category of probability or likelihood against the category

of consequence severity. This is a simple mechanism to increase visibility of risks and

assist management decision making (Wikipedia).

Mitigation Grading Matrix

Table 5.12 shows the mitigation grading matrix which helps in developing

mitigation strategy.

RISK MATRIX
SECTIONS IMPACTED
LOW MEDIUM HIGH EXTREME
LOW N D C A
LIKELIHOOD MEDIUM D C B A
HIGH C B A A
RISK MITIGATION BASED UPON GRADE

GRADE POSSIBLE ACTION

As a priority, mitigation actions reducing both likelihood and seriousness
A
are to be identified and implemented at start of project.
Mitigation actions reducing both likelihood and seriousness are to be
B
identified and implemented throughout course of project.
Mitigation actions reducing both likelihood and seriousness are to be
C
identified and costed for possible action should funds permit execution.
Risk to be noted: No action is required unless grading increases over
D
time.
Risk to be noted: No action is required unless grading increases over
N
time.

Table 5.12 Mitigation Grading Matrix

48
Stakeholder Tolerances

Figure 5.2 shows the contingency plan which allows the institution to return to its

daily operations as quickly as possible after an unforeseen event. The contingency plan

protects resources, minimizes customer inconvenience and identifies key staff, assigning

specific responsibilities in the context of the recovery.

Emergency
Situation

Security Hardware
threats failure

Anti-virus
Repairable?
installed?

Yes No Yes No

Install anti-
Buy and
Back-up files virus and then Repair replace
back-up files

Figure 5.2 Contingency Plan

49