CHAPTER I

INTRODUCTION

In today’s world, pens and paper have been used by many fast food and restaurants
throughout the world. This food ordering method is primarily the widely used and most
popular type of food ordering method, because of its low cost and easy to use approach.
This type of method is as simple as writing down the order of the customer, in order for
the chef or the cashier to know what food the customer wants.

But this type of method has its own flaws and disadvantages. First is, sometimes waiters
or the staff of the establishment misreads the order, which can lead to customer
dissatisfaction, another one are unorganized orders. Sometimes customers’ orders huge
amounts of foods and with this can still lead to customer dissatisfaction and inefficiency
in the establishment. Lastly the disadvantage of this method is only the cashier are able to
see what the student’s order. When customers are in a hurry, especially for the students,
when ordering food sometimes it take too much time to process the bill of the customer,
which again is a major flaw in the approach.

With the proposed food ordering system, it will be a big step up to the default food
ordering method of the establishment. This system will not only serve as an easier way
for the staff to take orders from customers but will be of help with the organization of
order, calculations of the bill and printing of the receipt. This major function can not only
help the staff and owner of the establishment but can also help the customers a way to
order food with ease and without worries.

1
Purpose and Descriptions

The main purpose of this study is to upgrade and enhance the current food ordering
method, as an improvement to their establishment, since pen and paper still can be used
but is not efficient and no longer applicable in today’s modern world, the system to be
developed will allow the staff and the owner of the fast food to take orders from the
customers, calculate the bill and view all of the food ordered with its detail. This system
will be of a big help to the establishment.

Objectives

This study aims to develop a functional and user-friendly food ordering system
intended for the staff and owner of School Canteen,

The study has the following specific objectives.

 To design a system able to accommodate huge amounts of orders.
 To improve the communication between the cashier and customer and minimize
the time of ordering.
 To automatically compute the bill.
 To automatically display the final bill so that it will be ready to print without any
error

Scope and Limitations

This study is only focused on the development of a system that will be usable to
the staff and owner of School Canteen. The developed system aims to eliminate the
manual transaction process. By using Canteen food ordering system, the operation of
ordering and computing inventories is convenient. The Administrator login can access the
systems database and all of the functions. The Cashier can access the menu and the
punching of orders and other development function of this system but it doesn’t have an

2
access on database. The developed system also has its limitation, this system can only be
used offline, and only limited in ordering food in the restaurant or canteen, it can only be
done by service cash and cannot receive amounts on a credit card basis.

Definition of Terminologies
-
AMD
- They combine the processor with Radeon graphics on the same chip. Used in the
requirements of this system

Intel
- The world’s largest manufacturer of PC microprocessors and the holder of the x86
processor architecture patent. Used in the requirements of this system

Database
- Database is a collection of information that is organized so that it can be easily
accessed, managed and updated. Data is organized into rows, columns and tables, and it
is indexed to make it easier to find relevant information. Database is used to store the
data of orders.

Operating System
- Is system software that manages computer hardware and software resources and
provides common services for computer programs.

3
 CHAPTER II

REVIEW OF RELATED SYSTEM

Technical Background

This review is to make other researchers known to be relevant to the project topic,
many researchers have made lots of solution and even made it better to achieve the
objective of the problem, and many fast food and restaurants today uses automated
ordering system in taking orders from customers instead of writing it on a paper. The
advantages of this system is not only that it will be relevant in today’s generation and not
only will it help the everyday work of staffs of the establishment easier but to also help
the customer’s order food with ease.

Related Studies

For the developers to further understand the study. The developers made use of
reading materials related to the food ordering system. Browsing the internet for these
samples and web articles that are similar to the study. These sample thesis and web article
played a critical role in broadening the idea and knowledge of the developers. These also
helped the developers to have an answer to the objectives these also helped the
developers to have an answer to the objectives by getting ideas on other related systems
and sample thesis to make improvements possible

The information gathered by the researchers focuses on the development of a food

ordering system and the advantages to the business and the consumers. Background of
the study for the related system

In the Philippines, eating is done at least three times a day with Filipino favorite meals;
Filipinos considered food highly important as it represents an integral part of our local art
and culture. In an ordinary day, some Filipinos consume five small and tasty meals,
starting with breakfast, followed by morning, merienda, lunch, afternoon snacks, dinner
and sometimes even late night snacks. The significance of the related system

The project is designed to provide easy access of orders, similar to the proposed system.

4
 Chapter III

Design and Methodology

This chapter presents the design and methodologies used by the developer in
developing the system. Different diagrams that can be applied in developing the system
are also included. This chapter also explains the type of research utilized in the study and
how it is related in the development in the system.

Project Concept

The developer conducted the project system by simply identifying the problem in
the situation of the fast food establishment in their day to day work. On a daily basis
many customers order food from the cashier. The pen and paper method is sometimes
inaccurate which can result to food orders being misread also when calculating the total
amount of orders, sometimes customers will order huge amounts of food, with this
method calculating the charge will take some time, and with that using the proposed
system will help in the problem.

The developer have started to gather the data needed in the development of the
system for Batangas State University- Malvar Campus Canteen to achieve its objectives.
The developer concluded that to eliminate the problems that might be encountered in the
current process, and to save time for the personnel, they developed a Canteen food
ordering system.

Development Approach

This section discusses the steps of development which can support business
needs. Designing the system, Building it and delivering it to the users. The SDLC is
compose can be possibly arranged a process study. The developer decided to use method
of System Development Life Cycle (SDLC). This can help organize the development
steps effectively. SDLC is the process of how Information Systems (IS) can support
business needs. Designing the system. Building it and delivering it to the users. The
SDLC is composed of four phases. Planning, Analysis, Design and Implementation.

5
 In this stage, the graphical layout was optimized to be integrated with Visual
Basic and development tools were used to make the graphics. In general, testing is done
in all stages of the project. Pre and post launch test are both critical in maintaining a good
web site. The testing of the software is essential as it forms an integral part to detect the
defects and faults in the software involve the software.
The content and system maintenance are constantly performed and monitored to ensure
that the system runs smoothly and the client is able to carry out the task effectively.

Figure 1. Ordering System Development Life Cycle Development Approach

Figure 2 shows the Top–Down approach that emphasizes planning and a complete
understanding of the system. It inherits that no coding can be begin until a sufficient level
of detail has been reached in the design of at least some part of the system.

6
 In gathering phase, the proponents conducted a research for other information to
help improve the system. In analysis phase, the developers gave the main flow and
conduct studies on how the system will work. In design phase, this includes the prototype
of the system. This shows how the system looks like and also includes the functionality
and other features. In developing the process of the application, the developers used
approach to deal with the need of the users. In implementation phase, the production
system was installed, initial user training was completed, user documentation was
delivered, and the post implementation review meeting was held. They used the top-down
approach which started with the system and breaks down into smaller segments to
progress its composition sub-systems.

Figure 2. Top – Down Development Approach

7
Planning

The first step in developing a new system is the planning phase. To identify the needs for
a Food Ordering System. In order for us to plan an effective system is to identify the
problems associated with the business. Planning what functions are necessary for
development, how will it be used and how will it help in supporting the business.

Analysis

The second step in developing a new system is the analysis phase. As we finished the
planning phase, we then analyzed the problems with the current system and how will we
make it better.

Design

The third step is the design phase. After the necessary specifications for the hardware,
software, people and data resources and the information of the products have been
determined that will satisfy the functional requirements of the proposed system. The
design will serve as the blueprint of the system and will help detect any problems or bugs
that are built in the final system. We will create the system design by reviewing the work
of the scope to ensure the design meets the objectives of the food ordering system.

Implementation

The final step in the (SDLC) is the implementation phase. The implementation phase is
described as those activities that begin when the system design are finalized. The required
documentation should be referred to throughout the rest of the system development
process, to ensure the developing project aligns with the needs and requirements or
scope. The system also is tested to evaluate its actual functionality is relation to expected
or intended functionality in the establishment.

Hardware Requirements

For the hardware requirements, personal computers are required to run the system.

8
Table 1 shows the hardware specifications needed and the tools together with its
functions to meet the proper standard needed by the developed system for architecture
equipment the minimum hardware specification requires is any version of Intel/AMD,
while for the processor speed a 1.2 GHz and above is required for the system to function

properly meanwhile a minimum single core is needed for CPU together with the RAM of
2gb on the other hand the minimum hardware requirements for the hard drive is at least
4gb free space memory there is no required specification for graphic cards this means that
the users may use any version of graphic cards an optical mouse and lastly a keyboard.

EQUIPMENT SPECIFICATIONS

Architecture Intel/AMD any version of processor

Processor Speed 1.2 GHz and beyond

RAM Minimum of single core

CPU 500mb

Hard Drive At least 2gb free space

Graphics Card Any

9
Peripheral’s Optical Mouse/ Touch Pad

Table 1. Minimum Hardware Specification for The Computer

EQUIPMENT SPECIFICATIONS

Architecture Intel/AMD any version of processor

Processor Speed 1.2 GHz and beyond

RAM 4gb

CPU Dual Cores

Hard Drive At least 10gb free space

Graphics Card At least 512mb of video card

Peripheral’s Optical Mouse/Keyboard

10
 Table 2.Recommended Hardware Specification for the Computer

Software Requirements

Table 2 illustrates the software specification of the developed system these are the
requirements for the system so that it will run properly these are the requirements.
Windows 10 is the operating system used to create this project because many developers
nowadays use windows 10, as their operating system’s this system is tested on a volume.

SOFTWARE TYPES/SPECIFICATION

Operating System for Windows Windows 7,10

Programming Language Visual Basic 2010

Database Back-End
Microsoft Access 2010

Table 3.Minimum Software Specification

Software Development Tool

11
 The system would not be as effective without the use of the software development
tools. In developing a system the developer used Visual Basic 2010. Since this is a
freeware it became easier for the developer to use this software, it is also easy to connect
to a database in addition, it is much easier to code in visual basic since each functions can
be coded separately unlike other programming languages.

Database used for this system is Microsoft Access 2010, this software is much easier to
use and connect to Visual Basic 2010.

Testing and Evaluation

To have higher quality system, software that will satisfy the user, effective
software is a must.

The developer tested this system thoroughly and let other users use the system to
give their thoughts about the program, there were a lot of missing features but it is
functional as an ordering system.

Table 4 illustrates the Likert Scale Table that was used by the developers to gather
the Weighted Average Mean of the questions regarding the Functionality of the
developed project. Likert Scale Table shows the Numeric Scoring and Verbal
Interpretation of the score for the project evaluation.

Table 4
Likert Scale

SCALE VERBAL INTERPRETATION

5 Strongly Agree
4 Agree
3 Moderately Agree
2 Disagree
1 Strongly Disagree

12
 Table 5 illustrates the range of the verbal interpretation of the scoring of the
functionality assessment of the project. It served as the basis on how to determine the
proper and accurate verbal interpretation of the results of the survey.

Table 5
Range of Verbal Interpretation

SCALE VERBAL INTERPRETATION

4.50-5.00 Strongly Agree
3.50-4.49 Agree
2.50-3.49 Moderately Agree
1.50-2.49 Disagree
1.00-1.49 Strongly Disagree

Chapter IV

RESULTS AND DISCUSSION

This chapter is the analysis of the development of the program. The results of
evaluation are presented in a tabular form. Screen shots are also presented in this chapter.
It includes the actual testing of the software and observations of the developer based on
the objectives of the study. The developer created the website to aid the needs of the
users of BSU – Malvar School Canteen. The user is someone who has an ability to access
a computer and their available products. The users will have their own username and
password in order to make a transaction.

13
LOG IN FORM
Figure 3 shows the log-in form for the system. It contains fields such as Username
(1), Password (2), Register button (3) and Login button (4). Text box is used in inputting
username and password. Register buttons will lead the user to another form. Log in
button will enables the system to search through its food order list if the account or data
existed.

Figure 3. Log in Form

REGISTER
Figure 4 shows the Register form for the system. It contains fields such as First
Name, Last Name, Username , Password , and Register button . Text box is used in
inputting first name, last name, username, password, and re-type password while the
Command register button. If the user Registered , it will go back to the Log in form and
then the admin can access the menu list.

14
 Figure 4. Log in as Admin Form

MENU FORM

Figure 5 shows the environment interface . The users can access all the buttons in the
menu list except the Admins’ button. Numeric keys is a button for how many food orders
are customer wants (1). Canteen Menu is a button that the user can access all the menu
list (2). Void Line is a button for the wrong order of the customer so the user can change
the order (3). Admin’s Menu is a button for the database of the system that the admin can

15
have an access on that data (4). After the customer is done with the items Total button is
click so that the total amount of items is calculated (5). Recipient is where all the items
click by the user will show the total and change of the customers(6).

Figure 5. Menu Board

TOTAL FORM

Figure 6 shows the environment interface on how the user will manage the payment
of the customer. The users are required to enter the amount of the bills of the
customers.Button for the bills is for the customers that paying an higher or exact of the
bills shown on the interface (1). The Exact Amount is a button where if the customers
pay an exact amount (2).Cash amount tender is a button for higher amount of bills than

16
the total amount of customer’s bills (3). Numeric keys for the typing of amount of the
customer’s pay after the Cash amount tender (4).

.
Figure 6. Total Form

PASSWORD FOR ADMIN

Figure 7 shows the environment interface of the ADMIN who will need to put the
Admin’s password. The password need in this form is the password in Log in form. This
form will have an access in the database of the system. Only admin have an access for it.
This interface shows the action button of Okay which is directly go to the database and
Back button if they don’t want to have show the database.

17
 Figure 7. Guest Log in Form

Evaluation Result
The developers used black-box testing, a method of acceptance testing that
examines the functionality of an application without peering into its internal structures or
workings. This method of test can be applied virtually to every level of software testing:
unit, integration, system and acceptance. It typically comprises most if not all higher level
testing, but can also embody unit testing.
The researchers conducted a survey that consisted of three categories. Each
category has a corresponding question. The survey was given to the users for the
researchers to determine the functionality, usability, reliability and maintainability of the
system. They tested the ability of the system to perform the task required and the user
tested all buttons to determine if all working based on their specified tasks and user
friendliness of the system created by the developers. It was participated by the
management of the system to assess their responses. The evaluation focused on the
functionality, usability, reliability and maintainability of the system.

18
 Table 6 shows the results of evaluation in terms of functionality of the system.
Based on the result, the users agreed on the ability of the software to perform the task
required with a mean of 4.23. They also agreed that the system’s buttons are all working
based on their specified tasks with a mean of 4.20. In addition, the users agreed on the
ability of the system to provide reliable information with a mean of 4.21. The users also
agreed on the capability of the system to respond on time with a mean of 4.20. As the
result of, 4.21 is the total composite mean with verbal interpretation of “Agree”.

Table 6

Summary of the result of Evaluation in terms of Functionality

Functionality Mean Verbal

Interpretation

1 The system can perform the task required. 4.23 Agree

2 System’s buttons are all working based on its 4.20 Agree

specified task.
3 The system can provide reliable information. 4.21 Agree

4 The capability of the system to respond on time. 4.20 Agree

Composite Mean 4.21 Moderately Agree

In terms of usability the table 7 shows result, the users agreed on the ability of the
system to be easily understood by users with a mean of 4.21. They also agreed that the
system’s overall design is appealing to the user’s eye with a mean of 4.33. As the result
of, 4.27 is the total composite mean with verbal interpretation of “Agree”.

Table 7
Summary of the result of Evaluation in terms of Usability

19
 Usability Mean Verbal
Interpretation

1 The ability of the system to be easily understood 4.21 Agree

by users.
2 The system’s overall design is appealing to the 4.33 Agree
user’s eye.
Composite Mean 4.27 Moderately Agree

Table 8 shows the results of evaluation in terms of reliability of the system. Based
on the result, the users agreed on the reliability of the system that the system can respond
on time with a mean of 4.19. They also agreed on the fast transaction ability of the
system for reservation with a mean of 4.19. As the result of, 4.19 is the total composite
mean with verbal interpretation of “Agree”.
Table 8
Summary of the result of Evaluation in terms of Reliability

Reliability Mean Verbal

Interpretation

1 The system can respond on time. 4.19 Agree

2 The fast transaction ability of the system for 4.19 Agree

reservation.

Composite Mean 4.19 Moderately Agree

Lastly, table 9 shows the results of evaluation in terms of functionality of the

system. Based on the result of maintainability, the composite mean of 4.50 the
respondents strongly agreed that the software functions are easy to test. The respondents
strongly agreed that the software can continue functioning if the changes are made as
seen by the composite mean of 4.70. The software tested that the user provides a

20
continuing and easily tested of the software. As the result of, 4.6 is the total composite
mean with verbal interpretation of “Agree”.

Table 9
Summary of the result of Evaluation in terms of Maintainability

Maintainability Mean Verbal

Interpretation

1 The system can be tested easily. 4.50 Strongly Agree

2 The system can continue functioning if changes 4.70 Strongly Agree

are made.

Composite Mean 4.6 Moderately Agree

Through the survey performed by the developers, the result lead to a satisfactory
evaluation which allowed the developers to continue the development of the application.
The developers also asked some of the respondents some suggestions for further
improvement of the software.

Implementation Plan of the Developed System

The Implementation Plan for Canteen food order system. The automation of the
manual system has been planned before the deployment of the system. Training or
orientation of the developed system is needed. The developers ensure that the
administrator will easily familiarize with the developed Food Ordering System.
Developer provide a step by step plan to successfully implement their developed system
to their clients.

Chapter V

SUMMARY OF FINDINGS, CONCLUSIONS AND RECOMMENDATIONS

21
 This chapter presents the summary of findings that the developer gathered in the
study. Out of these results, the developer provided conclusions along with the
recommendations for further modification of the present system.

Summary of Findings
The study is conducted for BSU-Malvar School Canteen. The study focused on
the development of a system that can help the administrator of the canteen render
efficient services to their customers.
The main purpose of the system is to create a food ordering system. The study
aims to have an easier to make an order through the use of system.
The developers came up with the following findings:

1. The researcher found out that many of the customers are having a wasteful
time to fall in line to have their meals because of manually taking their order
and computing their bills. The researcher provides a system where the
customers will find the easiest way to get there order fast and hassle free
paying.
2. The developer provided a module for the users where they can view the menu
of the products.

3. The developer provided reports of the products and monthly sales salary to be
monitored by the administrator.

4. The developer provided a functional and easy to manipulate system to aid the
transaction to their customers, it also can updates all the products to provide
accurate information to the customers.
5. The developer provided an implementation plan of the developed system to
help the customers look for available products and provide the necessary
information.

Conclusions

22
 The developer conducted a test run to find out the capabilities of the project. In
light of the results, the developer obtained the following conclusions:

1. The developed system made it easier for the users to make an order easily.
2. The users secure their tour by viewing the information needed for their travel
online.
3. The developed system provides the administrator an easier way to have an
access and monitor the products of the system and monthly sales through
report generation.
4. The developer tested the system and found out that the system is working
easily and possess an understandable user interface that allows the customer to
choose and make their orders.
5. The developer applies the plan to implement the system. The developer
conducts an orientation to the administrators to manage the system. And
lastly, the system is advertised to the user to give them the information they
need to use the system.

Recommendations
Based on the results of the findings and conclusions gathered, the developer
would like to recommend the following:

1. The proponents recommend that the system can be used as a fastest way to
the automatic process since it provides a better service for the customers.
2. To the future researchers, this will serve as a reference for them if they
will conduct similar study.
3. Future developers should also improve the system by using a touch pad
devices so the customers can access their orders easily.
4. To the future developers, the developer recommends to enhance the
system by creating an android version of the system.

23