CHAPTER III

METHODOLOGY

This Chapter presents the purpose to discuss the Requirement Analysis,

Data Gathering Procedures, Data Gathering Instruments, Population and Sample,
Design of Software, Systems, Product, and/or Processes which is followed by
researcher for this research study. This chapter will describe the tools and
equipment used to e-Menu System of Northern Light Kaffe. Data gathering is one
primary task that involved in researching, in order of that, this researching must
have to gather the data analysis. There are many procedures for gather the data
such as make an interview with the owner or manager of the shop to gather
information about the manual process of giving receipt, old inventory system and
testing the system that had design.

REQUIREMENT ANALYSIS

Methods of Research
The proponents used the quantitative method in gathering data and other
related information about the system. This study focused on describing the
problems encountered by people who are employees and as well as who are
customers in the Northern Light Kaffe, for us to be able to help them in giving an
easier way whenever they are making an order, processing an order, and serving
an order. Quantitative Method are surveys, interviews, and review of records or
documents for numeric information. The proponents conducted an interview with
the employees of the cafe shop regarding their problems in making and processing
an order. Survey forms are also given as an evaluation about the current system
that they have.
 Figure: Rapid Application Development Model of Software Development Life Cycle

Rapid Application Development or RAD model is one of the approaches for

writing software. RAD model distributes the analysis, design, build and test phases
into a series of short, iterative development cycles. There is less long-term
planning involved in the process and more focus is paid to the adaptability of the
development workflow. The RAD model takes information gathered during
workshops and other focus groups created to identify what customers want from
the product. The initial product is also tested, which helps in the creation of the
final product and a continued use of the parts of the product that have been proven
to be effective. RAD model should be used where the requirements change during
the project and working prototypes are to be presented to customer in small
iterations of 2-3 months.

Requirements Planning

This phase is equivalent to a project scoping meeting. Although the planning

phase is condensed compared to other project management methodologies, this
is a critical step for the ultimate success of the project. During this stage,
developers, clients (software users), and team members communicate to
determine the goals and expectations for the project as well as current and
potential issues that would need to be addressed during the build.
A basic breakdown of this stage involves:

 Researching the current problem

 Defining the requirements for the project
 Finalizing the requirements with each stakeholder’s approval

It is important that everyone can evaluate the goals and expectations for the
project and weigh in. By getting approval from each key stakeholder and
developer, teams can avoid miscommunications and costly change orders down
the road.

User design

Once the project is scoped out, it’s time to jump right into development,
building out the user design through various prototype iterations. This is the meat
and potatoes of the RAD methodology—and what sets it apart from other project
management strategies. During this phase, clients work hand in hand with
developers to ensure their needs are being met at every step in the design process.
It’s almost like customizable software development where the users can test each
prototype of the product, at each stage, to ensure it meets their expectations. All
the bugs and kinks are worked out in an iterative process. The developer designs
a prototype, the client (user) tests it, and then they come together to communicate
on what worked and what didn’t.

This method gives developers the opportunity to tweak the model as they
go until they reach a satisfactory design. Both the software developers and the
clients learn from the experience to make sure there is no potential for something
to slip through the cracks.

Development

Development takes the prototypes and beta systems from the design phase
and converts them into the working model. Because most of the problems and
changes were addressed during the thorough iterative design phase, developers
can construct the final working model more quickly than they could by following a
traditional project management approach. The phase breaks down into several
smaller steps:

 Preparation for rapid construction

 Program and application development
 Coding
 Unit, integration, and system testing

The software development team of programmers, coders, testers, and

developers work together during this stage to make sure everything is working
smoothly, and the result satisfies the client’s expectations and objectives. This
phase is important because the client still gets to give input throughout the process.
They can suggest alterations, changes, or even new ideas that can solve problems
as they arise.

Testing Phase

This is the implementation phase where the finished product goes to testing
phase. It includes data conversion, testing, and changeover to the new system, as
well as user training. All final changes are made while the coders and clients
continue to look for bugs in the system.
Data Gathering Procedures

Figure: Flow Chart of Data Gathering Procedure

The figure above shows the process of data gathering to develop a

proposed system. In this stage, the proponents chose their target client and
analyze their problem to overcome the proposed system. The proponents
formulate a system proposal and waited for approval on both client side which
consists of the owner of the business establishment and on the panel side which
consist of professors and dean of the school. When the proposal was approved,
the proponents gathered and analyze the requirements needed to the proposed
system. After that, the next stage will be the system development wherein the
proponents will create the system. When the system is built, the next step will be
the system testing to know if there will be some major or minor adjustments on the
system especially on how it is work. If the system testing fails, the proponents will
go back on gathering of requirements, debugging and adjusting the system. If the
system testing work well, the proponents will go on the implementation of the
system
 The researchers used the surveys and interview in the data gathering
through the process of questionnaires and personal interview. Personal interview
was the one of main tools in data gathering because the researchers will ask some
questions to gather the needed information.

Questions were asked to know the status of the manual system. These
questions helped the researchers in conceptualization of the study especially of
designing of the system. Their responses guided the researchers in the
construction and completion of the system.

Figure: Initial Use Case Diagram for Point-of-Sale System

In this figure, the Customer places the order, which is read by the internal
order system, and the order is then sent to the food preparation person for
execution. In the meantime, the customer makes the payment. The payment is
made in cash there is a cash collector actor who is processing and keeping the
balance cash amount.
 Figure: Context Diagram of Point-of-Sale System

The context diagram of the overall function of the system. From the diagram
we can see the major entities are the staff and the system. Admin can register the
staff through the system by entering individual’s username and password. Admin
can access the customer service panel. After successful completion, Admin need
to send the customer service receipt to the customers.

Figure: Level 0 Diagram of Inventory System

 Beside hat staff need to log in with their respective username and password
to access the system. Then they can proceed to new product sales and service
accordingly. After successful completion they will send a copy of sales receipt as
well as service receipt (if any) to the customers. Again, staffs can also update the
customer service records on demand. We will discuss more about system (POS)
functionality on below diagram

The researchers used the surveys and interview in the data gathering
through the process of questionnaires and personal interview. Personal interview
was the one of main tools in data gathering because the researchers will ask some
questions to gather the needed information.

Questions were asked to know the status of the manual system. These
questions helped the researchers in conceptualization of the study especially of
designing of the system. Their responses guided the researchers in the
construction and completion of the system.

Data Gathering Instruments

The proponents conducted a personal interview to the customer as well

as to the owner in preparation of the information and the processes being done in
the cafe shop. The proponents also gathered information through the reference
materials such as books and other studies for additional information which are
related to the study. In accumulation, the proponents collected applicable data
from thesis completed by graduated students, browse the internet for some studies
also related to the system

Description of Respondents

The proposed system e-Menu and Inventory System will be used by both
the employees and customers of Northern Light Kaffe. This system will be an
improvement for the customers and the owners to be able to give them an easier
and simpler process when they are ordering foods and/or coffee. The system could
be also be an advantage for the customers as well as record keeper because of
the owner inventories.
Functional Requirement

There are several functions that are included in the system to satisfy the
need of the shop. Some of these are as follows:

The proposed system is intended for point-of-sale and inventory purposes.

Thus, it can perform different processes included in the system. The system
supports customers purchased receipt. System can search the product from the
stock according to customer’s demand. System can add, update and/or delete
stock. System can show the stock report and sales report. System can register
new staff. System can add and/or update customer service. System can view all
the service records according to product specific ID. System can update password
(Admin & Staff).

Non-functional Requirement

The system would require the hardware and software specification stated
below to maximize its performance. If the specified requirements are not provided
by the shop, the system will not satisfy the customer expectation of the system.
The system can save stock into the database safely, can support all the PC
(Personal Computer), can create a backup database file after every transaction
(sales, stock, service, update of authentication details). Stock should be added
after end of sales per day. For security issues only admin can change the password
on behalf of staffs. Staffs can only access this system for sales, service and
checking reports. Aside from the hardware and software specification, the system
also requires a user that can navigate the system well. And it's not necessary that
the user types very fast, even if it is just the average speed if it can manage the
system well.
SYSTEM DIAGRAM, PRODUCT, AND/OR PROCESSES

Food Ordering
System
From the benefit of World Wide Web, a lot of fast food industry applies a
system known as Online Ordering System to assist their business processes.
Online Ordering System is a technique that allow customer to order their favorite
food online via the internet by using a web browser that installed in their respective
computer or smart phone.

Implementing this system can help restaurant industry to solve the

problem that they face while using the traditional food ordering processes. The
system greatly simplifies the food ordering process for both customer and
restaurant compare to the past. The customer can place an order everywhere and
anywhere whenever wireless (internet) connection is available for them.
Customers access to the website and choose the food that they prefer from the
online menu display then customers have to choose whether the food is delivered
to them or it will be packaged for pick up and the payment method will be upon
delivered or pick up and lastly it will show all the order details to the customer for
double checking and confirmation.

On the other hand, the system also greatly lightens the work load on the
restaurant’s end. Once customers have placed an order via the internet, the data
will send to the restaurant database and place in a queue in real-time. In addition,
the data will be display on the computer screen along with the corresponding
option. It allows restaurant employee easily to manage the orders sequentially,
produce the necessary item with a minimal delay and help reduce human error.
 Figure: Context Level Data Flow Diagram of Food Ordering System

Strength
The system is very suitable for cafe and restaurant industry due to it
provides ability for customer to place order anywhere and everywhere and
minimized the time require during the order processes. Customers do not need to
physically go to the cashier for food ordering instead of just using their mobile
device to place an order via the wireless connection and when the customer made
an order, they can directly have their meal while waiting for the queue. Meanwhile,
it helps the cafe and restaurant to have a better customer services because the
most important factor that cafe and restaurant concern about is quickness
therefore the restaurant should serve their customer without any delay.

Weaknesses and Limitations

The system is not effective enough to target all the customers on the
market. Because have a lot of senior citizen are without computer literate, so they
do not really understand how to utilize the web service. Thus, if they want to place
an order by using the system it will be a very troublesome incident for them.
 Table: Comparison of System’s Functionality Between Two Existing Systems with The
Proposed System

As a conclusion, the proposed system had pointed out the strength,

weakness and limitation for each existing system that have been reviewed. The
strength of the proposed solution will be combining the strength of each reviewed
existing system. Proposed solution is provided to solve the limitation and
weaknesses of the existing system; thus, it can be applied in small-medium
restaurant enterprise.
Activity Diagram for Generate Report

Figure: Activity Diagram for Generate Report

Activity Diagram for Place Order

Figure: Activity Diagram for Place Order

Activity Diagram for Update Menu Info

Figure: Activity Diagram for Update Menu Info

Activity Diagram for Validate Order

Figure: Activity Diagram for Validate Order

Activity Diagram for Void Order

Figure: Activity Diagram for Void Order

Activity Diagram for Add Menu Info

Figure: Activity Diagram for Add Menu Info

Activity Diagram for Delete Menu Info

Figure: Activity Diagram for Delete Menu Info

Activity Diagram for Make Payment

Figure: Activity Diagram for Make Payment

Activity Diagram for Add New Staff

Figure: Activity Diagram for Add New Staff

Class Diagram (Input Type)

Figure: Class Diagram (Input Type)

Class Diagram (Sample Input)

Figure: Class Diagram (Sample Input)

USER DESIGN
User interface is one of the most important parts of any system. It shows
how the users will interact with the system smoothly. Below are the details of user
interface. It will go from Admin Panel, User Panel to Staff Panel accordingly.

On this section, the log-in screen will pop-up to enter their credentials
(username and password) to access as Admin or Staff. It will show the user panel
(admin or staff) following their roles from the database.

Illustration: Login Interface (Admin)

 Illustration: Login Interface (Staff)

Illustration: Main Dashboard (Staff)

In this section, staff see Main Dashboard wherein the staff can pick the
transaction that will process. Its either the staff can process sales via purchase,
can add stock-ins to inventory, can manage the customer list, can edit and update
the product list
 Illustration: Create New Order (Staff)

Illustration: Sales Transaction (Staff)

Customer and/or staff can make an order which contains the category,
product name and price. Staff can choose the order of its choice by finding the
menu on the dropdown list and can put the number of items of its order.
 Illustration: E-Receipt (Staff)
The e-receipt will pop-up when you press "complete sales" after making
an order. It contains the overall summary of the customer's order and total price
that the customer will pay. The confirmed order with a sales invoice number are
also included on the receipt

Illustration: E-Receipt – Printing Option (Staff)

 Illustration: Stock-in Interface (Staff)

Illustration: Category Interface (Staff)

Admin can add and update the category of menu items like drinks,
desserts, Kids meal, fries, sandwiches and etc…
 Illustration: Product Interface (Staff)
In this section, staff can add products list with the details of product
picture, category, product name, product price, they can show its status availability
too.

Illustration: Add New Product – Modal (Staff)

Illustration: Update Product – Modal (Staff)

Illustration: Supplier Interface (Staff)

Illustration: Product Inventory (Staff)

Illustration: Activity Log (Staff)

Illustration: Sales Report – Select Date (Staff)

Illustration: Sales Report – Overview (Staff)

 Illustration: Income Report – Overview (Staff)

Illustration: Sales and Inventory Interface (Admin)

Illustration: Product Inventory (Admin)

Illustration: Overall Reports (Admin)

 Illustration: Add New Staff (Admin)
Admin can register new staff with their specific USERNAME and
PASSWORD. Admin can also edit and delete staff.

Illustration: Activity Log (Admin)

SOFTWARE TOOL SPECIFICATION

XAMPP
XAMPP is an easy to install Apache distribution containing MySQL, PHP
and Perl. XAMPP is really very easy to install and to use - just download, extract
and start.

The distribution for Windows 7, 8, 8.1 and 10. This version contains: Apache,
MySQL, PHP + PEAR, Perl, mod_php, mod_perl, mod_ssl, OpenSSL
phpMyAdmin, Webalizer, Mercury Mail Transport System for Win32 and NetWare
Systems v3.32, Ming, FileZilla FTP Server, mcrypt, eAccelerator, SQLite, and
WEB-DAV + mod_auth_mysql.

MySQL Workbench
MySQL Workbench is a unified visual tool for database architects,
developers, and DBAs. MySQL Workbench provides data modeling, SQL
development, and comprehensive administration tools for server configuration,
user administration, and much more. MySQL Workbench is available on Windows,
Linux and Mac OS.

MySQL Workbench enables a DBA, developer, or data architect to visually

design, model, generate, and manage databases. It includes everything a data
modeler needs for creating complex ER models, forward and reverse engineering,
and delivers key features for performing difficult change management and
documentation tasks that normally require much time and effort.

MySQL Workbench delivers visual tools for creating, executing, and

optimizing SQL queries. The SQL Editor provides color syntax highlighting, reuse
of SQL snippets, and execution history of SQL. The Database Connections Panel
enables developers to easily manage database connections. The Object Browser
provides instant access to database schema and objects. MySQL Workbench
provides a visual console to easily administer MySQL environments and gain
better visibility into databases. Developers and DBAs can use the visual tools for
configuring servers, administering users, and viewing database health.
Hardware Requirement

Processor: 800MHz Intel Pentium III or equivalent or new

Disk Space: 50 MB or more 2.7

Software Requirement

Operating System: No particular Operating System required because PHP is

platform independent.

Software: XAMPP, MySQL

Programming Language:

 HTML
 CSS
 Jquery
 Bootstrap
 Raw PHP
 MYSQL