Chapter 3
RESEARCH METHODOLOGY
In this chapter the research methodology is described in terms of
design, method, population, instruments and procedures used for data
collection. The research design chosen enabled the researcher to achieve the
purpose and objectives of the study.
The Research Design
The proponents chose to use Research and Development or most
commonly known as R&D, as the Research Design. Research and
Development is a phrase used to describe the activities associated with the
creation or discovery of new processes, methods, products and services and
using the newly discovered knowledge to fulfill a market need or demand.
Techniques that involve science, technology and mathematics are used in
research and development (Harmon, 2007). R&D is the most appropriate
design for the project since it involves techniques such as science,
technology and mathematics. All these techniques were applied in the
project.
The proponents have researched the problems and the needs of
Quattro Grill and Viewdeck. The proponents then developed a system that
will fulfill the need of the company through technological innovation.
Software Development Methodology
The proponents carefully chose the development methodology base on
the nature of the project to obtain the objectives of the research.
The proponents chose to use Rapid Application Development as the
development methodology. Rapid Application Development (RAD) is a
methodology for compressing the analysis, design, build and test phase into
a series of short, iterative development cycles.
The proponents have chosen this kind of methodology because
Waterfall Model is inflexible and linear. Once you have completed one phase
there is no back tracking. The researchers do not expect that after one phase
all is perfect. The researchers decided to use this methodology for the reason
that the structure of RAD lifecycle was designed to ensure that developers
build the system the uers really need.
Figure 3.1: Modified Waterfall Model with Feedback at every stage
2
RAD consists of the following phase: (1) analysis and quick design, (2)
construction, (3) testing and (4) implementation
Phase 1 – Analysis and Quick Design
In this phase, the process is divided into two, analysis and quick
design. The first phase of the development is to gather and identify the
requirements of the system. The problems were specified regarding
restaurant management along with the desired objective of solving the
problems. The requirement specification is then produced from the detailed
definitions that clearly define the system functions.
The next phase involved in the analysis was Quick Design. Quick
design is a phase that emphasize on how the system should perform in order
to fulfill the requirements identified in the analysis phase. The purpose of this
phase is to create a blueprint for the new system that will satisfy all
document requirements. This is the phase where all necessary output, input,
interfaces and processes were identified.
3
In this phase the researchers used a Data Flow Diagram to show the
step by step process of the existing and proposed system which served as a
guide in the development of the system. A prototype of the interface of the
proposed systm is included in this chapter as well as the entity relationship
diagram of the database in the system.
Figure 3.2
Customer Order WAITER
Context Diagram of Existing System
Received Food
CUSTOMER Payment Order
Receipt
Food Order COOK
Sales Report
Received Order
Bill
Existing
0
Manual Payment
Details
System
Daily Sales
Report
Receipt Details
RESTAURANT
CASHIER
MANAGER
4
This diagram illustrates the existing manual system Of Quattro Grill
and Viewdeck. The waiter gets customer order then delivers it to the kitchen.
The waiter then gives a copy of customer order to the cashier. The cashiers’
compute bills and make receipt manually. At the end of the day the cashier
makes a daily sales report. The restaurant manager is the one who receives
the daily sales report.
Figure 3.3
Context Diagram of Proposed System
WAITER
Customer Order
CUSTOMER Received
Payment Food Order
5
Receipt
Received Order Food Order
COOK
Computerized
Order, Billing
0
and Sales
Customer Received
Tracking Payment Details
order Order
System 1.0
CUSTOMER WAITER
Get
Order
Daily Sales
Received
Report
Food Order
Receip
Receipt Details
t 2.0
RESTAURANT CASHIERCASHIER
MANAGER 5.0 Forward
Receipt Customer
Details Food
Create Goods Sold Order
This diagram illustrates the proposed system for Quattro Grill
Receipt
and Viewdeck. The waiter gets customer order3.0 then gives it to the cashier.
Paymen
Payment 6.0 Create
The cashier inputs the order in tthe computer then
Details prints the food order to the
Process Sales
COOK
kitchen. Once the orders
Paymen have been input Record
the system can automatically
t
generate bills and receipt. The database for sales, inventory and order are
Goods Sold
also automatically updated. The cashier needs not toData
make a manual sales
report because the system will do the task. 4.0
D
Sales Record
1
Folder Release
Figure 3.4
Food
Order
Sales Record
Diagram 0 of the Existing System
Details
Daily Sales 5.0
Report Produce
Sales
RESTAURANT Report
MANAGER
6
Received Customer Order
Food Order
Processed
Food Order
7
Figure 3.5
Diagram 0 of the Proposed System
Customer order 1.0 Received Order
CUSTOMER WAITER
Get
Order
Received Food
Order
Payment
7.0
Payment Details
Receipt
Process 2.0
Payment
Submit
Order
10.0 Receipt
Details
Generate Received Food Food Order
4.0
Bill Order Details Details
Process Food
Order
Details CASHIER
5.0 Received Food
Goods Products 6.0
Order Details
Update Good Sold Sold
Sales Update
Database
Inventory
Database
3.0
8
COOK
Goods Sold Forward
Inventory data Customer
Data
Food Order
Inventory
D2 Sales Journal D3 Processed
Food Order
Daily Goods Daily Sales
Sold 8.0 Report
RESTAURANT
Food
Produce MANAGER
Order
Management
Reports3.
9.0
Received Order Release
Food Order
9
Figure 3.6
Entity Relationship Diagram of the Proposed System
CUSTOMER
NAME TABLE WAITER
NUMBER NAME
1 Orders 1
CUSTOMER
food WAITER
1 M
Is given Print
to Bills
Gives
Order
CASHIER
NAME
M 1
ORDER Inputs
CASHIER
PRICE
ITEM
NUMBER
TABLE
NUMBER
ITEM
NAME
10
Figure 3.6 shows the entity relationship of the proposed system. It
shows the relationship between entities. One customer orders food to one
waiter. Then waiters give all customer orders to one cashier. The cashier
inputs many order to the computer then these orders after they are cooked
are given to the customer. Cashier also prints bills to be given to the
customer.
Figure 3.7
User Interface
11
Figure 3.7 shows the login interface of the proposed system. The users
have to enter correct username and password in order to access the main
window.
Figure 3.8
Main Window
12
Figure 3.8 shows the restaurant window of the proposed system once
the restaurant button is clicked. This is where the cashier selects customer
order, generate bill and sales report with just a click.
Phase 2 – Construction
During the construction phase the researchers developed the
application in iterative cycles of development, testing requirements, and
development again. This is synonymous t build, demonstrate and refine. In
this phase, the researchers converted the Data Model that was developed
during the design stage into a functional database. Coding was also done in
this phase.
Phase 3 – Testing
13
The phase where the proposed system was given to a panel of critics
and end-users for testing. In this way, the developers have determined the
response of the user whether or not the proposed system met the criteria in
the objectives.
Phase 4 – Implementation
In this phase the software has already been written, tested,
documented and system is installed. The objective of the implementation
phase is to deliver a completely functioning and documented system.
Data Gathering Tools
Observation
The researchers visited the locale several times in order to understand
further the existing procedures and processes that take place in restaurant
management. This tool enabled the researchers to obtain additional
knowledge.
Interview
An informal interview was conducted to know the process of the
existing restaurant management system as well as the problems
encountered.
Survey Questionnaire
The researchers used the questionnaire to evaluate and validate the
developed system.
14
Library Research and Internet Research
Different case studies, thesis and books in the library served as
reference in making the system.
The use of search engine such as Google has proven to result in vital
information which could not be found in books.
15
