Chapter 3
Transcript of Chapter 3
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.
RAD consists of the following phase: (1) analysis and quick design, (2)
construction, (3) testing and (4) implementation
2
Figure 3.1: Modified Waterfall Model with Feedback at every stage
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.
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
Context Diagram of Existing System
3
Receipt Details
Receipt
Sales Report
Bill
PaymentDetails
Daily Sales Report
Payment
CASHIER
Received Order
RESTAURANT MANAGER
Customer Order
CUSTOMER Received FoodOrder
WAITER
0
Existing Manual System
COOKFood Order
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
4
WAITERCustomer Order
CUSTOMER Received Food Order
This diagram illustrates the proposed system for Quattro Grill
and Viewdeck. The waiter gets customer order then gives it to the cashier.
The cashier inputs the order in the computer then prints the food order to the
kitchen. Once the orders have been input the system can automatically
generate bills and receipt. The database for sales, inventory and order are
also automatically updated. The cashier needs not to make a manual sales
report because the system will do the task.
Figure 3.4
Diagram 0 of the Existing System
5
0
Receipt Details
Receipt
Payment Details
Daily Sales Report
Payment
CASHIER
Computerized Order, Billing
and Sales Tracking System
Received Order
RESTAURANT MANAGER
Food OrderCOOK
CUSTOMER
Customer order Received Order
WAITER
CASHIER
COOK
GetOrder
Forward Customer
Food Order
Received Food Order
Goods Sold
Create Sales
Record
Sales Record Folder
ProduceSales
ReportRESTAURANT
MANAGER
Sales RecordDetails
Daily Sales Report
Goods Sold Data
Receipt Details
Receipt
Create Receipt
1.0
3.0
2.0
4.0
5.0
5.0
ReleaseFood Order
Received Customer Order
6.0
Process
Payment
Payment
D1
Payment Details
Figure 3.5
Diagram 0 of the Proposed System
6
Food Order
CUSTOMER
Customer order Received Order
WAITERGet
Order
1.0
ProcessedFood Order
Received Food Order
7.0Payment
Payment Details
3.
7
CASHIER
Submit Order
2.0
4.0Process
Food Order Details
Received Order
3.0
Food Order Details
Forward Customer Food Order
Update Good SalesDatabase
COOK
ProcessedFood Order
Received Food Order Details
Received Food Order Details
Update Inventory Database
Sales Journal
Goods Sold Data
Produce Management Reports
D2
Daily Goods Sold
Inventory D3
Inventory data
8.0
RESTAURANT MANAGER
Daily Sales Report
5.06.0Goods
Sold Products Sold
9.0
ReleaseFood Order
10.0
Generate Bill
Receipt
Receipt Details
Process
Payment
Food Order
Figure 3.6
8
WAITER
WAITER NAME
CASHIER NAME
CASHIERORDER
GivesOrder
Inputs
CUSTOMER
CUSTOMER NAME TABLE
NUMBER
ITEM NAME
PRICE
ITEMNUMBER
Is givento
TABLE NUMBER
PrintBills
Ordersfood
1 1
M
1M
1
Entity Relationship Diagram of the Proposed System
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
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
9
Main Window
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
10
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
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.
11
Survey Questionnaire
The researchers used the questionnaire to evaluate and validate the
developed system.
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.
12