Upload
others
View
9
Download
0
Embed Size (px)
Citation preview
FOOD ORDERING SYSTEM (iORDER)
NUR ANIS FADLIN BINTI GHAZALI
BACHELOR OF COMPUTER SCIENCE
(SOFTWARE DEVELOPMENT) WITH HONOURS
FACULTY OF INFORMATICS AND COMPUTING
UNIVERSITY SULTAN ZAINAL ABIDIN
2020
FOOD ORDERING SYSTEM (iORDER)
NUR ANIS FADLIN BINTI GHAZALI
BACHELOR OF COMPUTER SCIENCE
(SOFTWARE DEVELOPMENT) WITH HONOURS
2020
APPROVAL
This report already submitted to Faculty of Informatics and Computing, Universiti
Sultan Zainal Abidin (UniSZA) and been accepted as fulfil the criteria for Bachelor of
Computer Science (Software Development) with Honours.
Prof.Dr. Mohd Nordin Bin Abdul Rahman
Supervisor,
Faculty of Informatics and Computing,
Universiti Sultan Zainal Abidin.
Date: 23/7/2020
i
DECLARATION
I hereby declare that this report is based on my original work except for quotations and
citations, which have been duly acknowledged. I also declare that it has not been
previously or concurrently submitted for any other degree at Universiti Sultan Zainal
Abidin or other institutions.
Nur Anis Fadlin Binti Ghazali
Bachelor of Computer Science
(Software Development) with Honours.
Date: 10 July 2020
ii
ABSTRACT
Online Food Ordering System is a web-based system for customer and employee to
perform transaction and purchase more smoothly through the online to the internet. The
aim of the system is to ease the customers to place the order as per they like without go
to the cafe. Then the employee will check the order and prepare the food then delivery
food. Users of this system consists of customer, employee and admin. Aim or objectives
of this project are to study the problem and its potential to solve in taking order to the
online system, to design and develop a system for customer to make order employee to
manage the order and to testing the developed system for its usability and functionality.
In addition, the main function of the cafe in this system is to provide food orders that
have made by customers using the Collaborative Filtering method. The outcomes of this
project to help user to make order as soon as possible anytime and anywhere they want.
In conclusion, with the availability of technology, all management will be able to be
managed smoothly, properly and efficiently in the future.
iii
CONTENTS
APPROVAL i
DECLARATION ii
ABSTRACT iii
CONTENTS iv
LISTS OF THE TABLES viii
LIST OG THE FIGURES ix
CHAPTER 1 INTRODUCTION 1
1.1 Background 1
1.2 Problem Statement 2
1.3 Objective 3
1.4 Scope 4
1.4.1 Users 4
1.4.1.1 Admin 4
1.4.1.2 Employee 4
1.4.1.3 Customer 4
CHAPTER 2 LITERATURE REVIEW 5
2.1 Introduction 5
2.2 Existing System 6
2.2.1 Ninja Grill Order and Delivery System 6
iv
2.2.2 Food Ordering Restaurant App 7
2.2.3 Sakae Sushi Delivery 8
2.3 Research in Different Technique 10
2.3.1 Filtering Method Based 10
2.4 Summary 12
CHAPTER 3 METHODOLOGY 13
3.1 Introduction 13
3.2 System Development Methodology 14
3.2.1 Requirement Phase 14
3.2.2 Design Phase 15
3.2.3 Development Phase 15
3.2.4 Testing Phase 15
3.2.5 Deployment Phase 16
3.2.6 Review Phase 16
3.3 Hardware and Software Requirement 17
3.3.1 Hardware Requirement 17
3.3.2 Software Requirement 17
3.4 System Design and Modelling 18
3.4.1 Context Diagram (CD) 18
3.4.2 Data Flow Diagram (DFD) 19
3.4.2.1 Data Flow Diagram Level 1 Process 3.0 21
3.4.3 Entity Relationship Diagram (ERD) 22
v
3.5 Data Dictionary 23
3.6 Summary 26
CHAPTER 4 IMLEMENTATION AND TESTING 27
4.1 Introduction 27
4.2 Interfaces of iORDER System 28
4.2.1 Main Page 28
4.2.2 Login and Sign up 29
4.3 Admin and Employee 30
4.3.1 Main Page 30
4.3.2 Item 31
4.3.3 Order 33
4.3.4 Payment 34
4.3.5 Report 35
4.4 Customer 36
4.4.1 Main Page 36
4.4.2 Profile 37
4.4.3 Item 38
4.4.4 Rating 41
4.4.5 Order 43
4.4.6 Payment 44
4.5 Test Case 45
4.5.1 Sign up 45
vi
4.5.2 Login 46
4.5.3 Add New Item for Admin and Employee 46
4.5.4 Update Item for Admin and Employee 47
4.5.5 Delete Item for Admin and Employee 47
4.5.6 Update Profile for Customer 47
4.5.7 Place Order for Customer 48
4.5.8 Rating Item for Customer 48
4.6 Summary 49
CHAPTER 5 CONCLUSION 50
5.1 Introduction 50
5.2 Project Constraints 51
5.3 Future Work 51
REFERENCES 52
vii
LIST OF THE TABLES
Table Title Page
2.1 Systems comparison 10
2.2 Table of Comparison for Each Technique 12
3.1 Hardware Requirement for iORDER System 18
3.2 Software Requirement for iORDER System 18
3.3 Database iORDER Syatem 23
3.4 Table customer 23
3.5 Table item 24
3.6 Table purchase 24
3.7 Table bayaran 25
3.8 Table rating 25
viii
LIST OF THE FIGURES
Figure Title Page
2.1 Print Screen of Ninja Grill Order and Delivery System 6
2.2 Print Screen of Food Ordering Restaurant App 7
2.3 Print Screen of Sakae Sushi Delivery 8
2.4 Collaborative Filtering (CF) Method 10
3.1 Agile Methodology 14
3.2 Context Diagram iORDER System 18
3.3 Data Flow Diagram iORDER System 19
3.4 Data Flow Diagram Level 1 Process 3.0 21
3.5 Entity Relationship Diagram iORDER System 22
4.1 Home page for iORDER System 29
4.2 Login for Admin, Employee and Customer 30
4.3 Sign up for customer 30
4.4 Home for admin and employee 31
4.5 View Item for admin and employee 32
4.6 Add New Item for admin and employee 32
4.7 Update Item for admin and employee 33
4.8 Delete Item for admin and employee 33
4.9 View Order for admin and employee 34
4.10 View Payment for admin and employee 35
4.11 View Report for admin and employee 36
4.12 View report search by date 37
ix
4.13 Home for customer
4.14 View profile 38
4.15 Update profile and delete account 38
4.16 View Item for customer 39
4.17 Buy Item 39
4.18 Confirmation of buy item 40
4.19 Detail of Order 40
4.20 Average rating and review 41
4.21 Rating item 42
4.21 View order report 42
4.22 View payment report 43
x
CHAPTER 1
INTRODUCTION
1.1 Background
Nowadays, majority people want to make order anywhere, anytime they want. They
don’t have enough time to drive car, walk in to the cafe, make order and spent their time
at there. All of time may need from 30 to 40 minutes for them to spend at the cafe only.
These problems have led to the idea of developing a system which is ‘Food Ordering
System(iORDER)’ that would help the customer in making order. Customer just need
to register themselves and make the order through the system. Then, the staff will take
the order and the order will be stored in the database. Next, after all the order done, the
employee will make delivery of the food to the customer. Lastly, admin can manage
cafe’s information and view the report. The method of this system is using collaborative
filtering technique.
1
1.2 Problem Statement
According to research article written by Amalto blog, Aug 3, 2017, at every
manual touch point in sales order processing, companies lose the transparency that
provides a view of daily activities for effective order management. This lack of visibility
leads to difficulties in budgeting, planning and forecasting, and the inability to identify
and prioritize urgent orders.
Next, since multiple touch points are involved in manually processing orders,
an elevated risk of errors are present. Such errors can include incorrect order entry.
Miscommunication with your production or service delivery lines due to order
processing errors can also result wasted materials, and disgruntled customers.
Last, when manual processes of keying-in orders and physically handling
documents are still in place, the Order to Cash cycle is constantly put on hold. Other
than the human error aspect of sales order processing, there are still other considerations
that can add processing times and costs. There is an inflated cost of processing each
order when documents need to be printed before manually keying into an application.
2
1.3 Objective
➢ To study the problem and its potential to solve the manual system in taking order
to the online system.
➢ To design and develop a system for waiter and kitchen to manage the order and
inventory of food.
➢ To testing the developed system for its usability and functionality.
3
1.4 Scope
Cafe Management System have three user scope which are admin, cashier and
kitchen.
1.4.1 Users
1.4.1.1 Admin
➢ Create, retrieve, update Cafe information.
➢ Create, retrieve, update and delete items.
➢ View all report
1.4.1.2 Employee
➢ Create, retrieve, update and delete items.
➢ Retrieve the order from customer.
➢ Update status for delivery and payment from customer.
1.4.1.3 Customer
➢ Register and login to the system.
➢ Retrieve and update profile
➢ Retrieve the products.
➢ Create and retrieve order.
4
CHAPTER 2
LITERATURE REVIEW
2.1 Introduction
Based on studies that have been done, literature review is important information
of the source. It might give a new interpretation of old material or combine new with
old interpretation. This chapter, review about the system that already be developed.
Literature review is very important to describe the current knowledge that may help in
conducting in this project. This explained the previous study about related project
finding, methodologies solution and some ideas that can be improves in developing this
system.
5
2.2 Existing System
The existing system is to identify the advantages and disadvantages of the
system that already been developed before.
2.2.1 Ninja Grill Order and Delivery System
Ninja Grill is a customer-oriented quick service Japanese Asian restaurant that
purposed to make order and delivery the food. This system was developed by
Joyopos,2012 and this system has been used at United States of America (USA). This
system is used for both booking and delivery. Not only that, this system also has an add
to cart and allows users to order food as much as their wish. The system also has a map
intended to make it easier for users to know the location of the store. The menu for this
system is organized by category and each menu has its own side dish to add.
Figure 2.1 Print Screen of Ninja Grill Order and Delivery System
6
2.2.2 Food Ordering Restaurant App
Food ordering restaurant app belongs to the Abhi Restaurant, India. This app
was developed by AhbiAnroid, 2017. This app also purposed ordering and delivery
food. This restaurant have many kind of main dishes likes salad, chicken, chocolate,
cookies, bread, burger, drinks and also side dishes. First of all, to view the menu, we
need to register and then login. After login, we can see the menu, place order and then
it will add to cart before we proceed to payment. We also can update our profile and
check the order.
Figure 2.2 Print Screen of Food Ordering Restaurant App
7
2.2.3 Sakae Sushi Delivery
Sakae Sushi delivery is a sushi-concept restaurant that has builed by Oddle.me,
2011. this restaurant was based in Singapore but there are several outlets also located
around Selangor, Malaysia. This restaurant has self-pickup or make delivery for their
customers. Through this web-system, customers can view the menu and they also can
add to cart the dish that they want. Then, they need to chooce either pickup at restaurant
or delivery. If customer choose delivery, they need to fill their information to make sure
the confirmation of the order.
Figure 2.3 Print Screen of Sakae Sushi Delivery
8
Table 2.1 Systems comparison
Ninja Grill Food Ordering
Restaurant App
Sakae Sushi
Location USA India Singapore and
Malaysia
Logo
System
overview
- Order and delivery
food.
- Can add to cart.
- Payment by COD
- Order and delivery
food.
- Can add to cart.
- Payment by PayPal
and COD
- Order, self-pickup and
delivery food
- Can add to cart.
- Payment by cash
Method Web-based system App for Android Web-based system
9
2.3 Research in Different Technique
Different technique or method has been analyse through the previous research
and articles. All the article that related to the specific technique will be observe on their
advantage and disadvantages for implementation the suitable technique in this project
system. Two technique were chosen for the literature review.
2.3.1 Filtering Method Based
Collaborative Filtering (CF) is a broad term for the process of recommending
items to users based on similarities in user taste. Their performance will change based
on the dataset that they operate on, and the information they harness to compile a
similarity model. Adaptive Information Filtering using Regression collaborative
recommendation algorithms (User-Based; Item-Based; and Rule-Based CF).
Figure 2.4 Collaborative Filtering (CF) Method
10
Table 2.2 Table of Comparison for Each Technique
Author Title Method Description Advantage Disadvantages
F.O.
Isinkaye,
Y.O.
Folajimi,
B.A.
Ojokoh
(2015)
Recommendation
systems: Principles,
methods and
evaluation
Recommendation
filtering techniques:
Collaborative
filtering
Works by building a
database (user-item
matrix) of preferences for
items by users. It then
matches users with
relevant interest and
preferences by
calculating similarities
between their profiles to
make recommendations
1. Recommendations
that are produced by
CF can be of either
prediction or
recommendation
2. Domain-
independent
prediction technique
1. filtering
techniques compute
predictions using the
similarity between
items and not the
similarity between
users.
John
O'Donovan
and John
Dunnionv
(2014)
A Framework for
Evaluation of
Information Filtering
Techniques in an
Adaptive
Recommender
System
Filtering
Techniques:
Collaborative
Filtering (CF)
This paper focus on two
serious restrictions.
Sparsity Restriction (two
users have co-rated many
of the items in the
system) and Latency
Restriction (This affects
new or unique items).
1.Do not require
items to be machine-
analysable.
2. Require little
knowledge-
engineering
overhead.
1. Cannot handle
fresh items.
2. Hard to include
side features for
query or item.
11
2.4 Summary
This chapter summarized an overview of the concept of the system. Literature
review is one of the important parts to study because it will help to determine the
methodologies used and techniques that can be applied in the proposed system. The system
is developed will use Collaborative Filtering method. This method will add the rating of
the product. So that user can give the rating for the product that they like most. Then, the
system can predict and recommend the most favourite and most purchase products to
another customer.
12
CHAPTER 3
METHODOLOGY
3.1 Introduction
Methodology is method used in develop a system and defined as a set of procedures.
This chapter will cover on methodology that used based on research that have been done.
Project system of iORDER is use Agile methodology. This chapter will fully explain to
achieve the project’s objectives that have been mention earlier in this research report.
Methodology is important part to make sure the system can be accomplished successfully.
13
3.2 System Development Methodology
Figure 3.1 Agile Methodology
3.2.1 Requirement Phase
In this phase, the project title had been selected. The project title for the system was
Food Ordering System (iORDER). This project starting with brainstorming ideas with
supervisor and proposed the title of the project. An abstract and description of the project
module has also been done and attached. Besides, the Gantt chart also needed as a guideline
and references for the project. This phase is to analyse the existing system and the article
of the techniques or method that will be used for this project. In this phase also get all the
requirements that are needed to design and develop the new system. Based on the collection
of information through article, method and technique that is suitable been decided.
14
3.2.2 Design Phase
In the design phase, all the data or requirement obtained during planning and
analysis phase transformed into the design. Diagrams to show the flow of the system will
be develop in this chapter such as Context Diagram (CD), Data Flow Diagram (DFD) Level
0 and 1, Entity Relationship Diagram (ERD). These diagrams are designed as a guideline
to developing the system. After that, will be design the database and system interface.
3.2.3 Development Phase
This phase is where the design will implement into the coding. The system will
develop regarding the user and system requirement. In this project, to develop the system
will be use Xampp server for the database, Visual Studio Code to code and Bootstrap as
framework. This phase is a critical phase because user part needed to fulfil and to make
sure the objectives accomplish.
3.2.4 Testing Phase
When all the module has be done as full system, the system testing has been carried
out. This testing phase will test the system to check the error and ensure the function run
well as a whole system. Any error or bugs will be fixed and repeated testing the system
until all the function can be use.
15
3.2.5 Deployment Phase
This phase is when the system has successfully done and fulfil all the objective. The
system can be deployed and finally the system will publish to the user for use as their need.
3.2.6 Review Phase
This phase got feedback and review form user for the maintenance. In this phase
will follow-up with user to upgrade the system to another version in the future.
16
3.3 Hardware and Software Requirement
This section will show the list all software and hardware that involve in the
development process.
3.3.1 Hardware Requirement
Table 3.1 Hardware Requirement for iORDER
Hardware Explanation
Laptop Lenovo ideapad 330-15ARR Processor: AMD Ryzen 3
RAM: 4 GB
OS: Window 10
GPU: Radeon Vega Graphics 2.50 Hz
Printer HP To print the report for the system.
3.3.2 Software Requirement
Table 3.2 Software Requirement for iORDER
Software Explanation
Edraw Max 7.9 To design CD, DFD and ERD.
PHP Programming language to build the
system.
Xampp server Local server to run and test the system.
MySQL Database Open source relational database
management system that uses structured
Query Language and store the data of the
system.
Visual Studio Code Platform to code the system.
Bootstrap Application Development Framework
17
3.4 System Design and Modelling
3.4.1 Context Diagram (CD)
Figure 2.2 Context Diagram iORDER
Figure 3.2 show the context diagram iORDER. There are three users involve in this
process which are admin, staff and customer. There are seventeen data flows that are
involved in the interaction between the process and entities. For the Admin, there are two
outgoing data (Login and Manage Employee). There is one incoming data (View Report).
For Employee, there are four outgoing data (Login, Item Info, Booking Table Status and
Delivery Status). There are also three incoming data (Item Detail, Order Detail and Booking
Table detail). For the Customer, there three outgoing data (Register and Login, Order
Request and Booking Table Info). There are four incoming data (Item Detail, Order Detail,
Booking Table Status, Delivery Status).
18
3.4.2 Data Flow Diagram (DFD)
Figure 3.3 Data Flow Diagram iORDER
The data flow diagram has three entities which are Admin, Employee and
Customer. There are seven process involves in this data flow diagram (Login, Manage Item,
Order Item, Make Payment, Rating and Report. There are six data stores created for this
system which are, User (Admin and Employee), Customer, Item, and Purchase, Payment
and Rating.
19
1. Admin, Employee and Customer will login in to the system by enter email and
password and the output of the process will verify the id, email and password in the
data store.
2. Employee will Manage Item and will be save in Item data store.
3. Customer can view the Item info and make Order. The data will be store in Purchase
data store. Then, Employee will proceed the order and delivery it to the customer.
Employee also can update the order status and delivery status, so that customer can
get information through the system.
4. Customer can give rating of the item that has been purchased through the system.
Customer also can view the order and payment history as their report.
5. All the data stores, User, Customer, Item, Purchase, Payment and Rating will be
view by Admin from Report process and Customer can view Purchase and Payment
data from Report process.
20
3.4.2.1 Data Flow Diagram Level 1 Process 3.0
Figure 3.4 Data Flow Diagram Level 1 Process 3.0
Customer can view the item and make Order. The data will be store in Order data
store. Next, Order detail will receive to Employee and the Employee can proceed the order
and deliver the item to the customer. Employee also can update the status of delivery.
21
3.4.3 Entity Relationship Diagram (ERD)
Figure 3.5 Entity Relationship Diagram iORDER
The entity relationship diagram is a diagram which illustrates entities information
and entities’ relationship. ERD composed three things such as identifying and defining the
entities, determine entities interaction and the cardinality of the relationship. The database
name for this system is iORDER. The system has six tables (user, customer, item, purchase,
bayaran, rating). Every table have their own attributes and id as primary key.
22
3.5 Data Dictionary
Data dictionary explained the entity, attribute, description, data type and size of all
the tables in database.
Table 3.3 Database iORDER System
Database for this system is dbioder. It has five table which are bayaran, customer,
item, purchase and rating.
Table 3.4 Table customer
23
Table above is for customer. The attributes for customer are idcustomer, nama,
email, password, alamat, poskod, negeri, notel and bangsa. Primary key in this table is
idcustomer and email is unique.
Table 3.5 Table item
Table above is for item. The attributes for item are iditem, kategori, nama and harga
and image. Primary key in this table is iditem.
Table 3.6 Table purchase
24
Table above is for purchase. The attributes for item are invoice, idcustomer, iditem,
Tarikh, masa, kuantiti and status. Primary key in this table is invoice and foreign key are
idcustomer and iditem.
Table 3.7 Table bayaran
Table above is for bayaran. The attributes for table are idbayaran, invoice,
idcustomer, jumlah, carabayar and statusbayar. Primary key for this table is idbayaran and
foreign key in this table are invoice and idcustomer.
Table 3.8 Table rating
Table above is for rating. The attributes for table are idrating, iditem,
idcustomer, ratingNumbar, created and status. Primary key for this table is idrating and
foreign key in this table are iditem and idcustomer.
25
3.6 Summary
This chapter briefly explain methodology used in this project. Agile method used
to develop the proposed system. Every phase in this method was explained deeply and there
are list of hardware and software required to develop this system. The perfect
methodologies preferred may help the development of the project following the Gantt chart.
26
CHAPTER 4
IMPLEMENTATION AND TESTING
4.1 Introduction
In this chapter will be discuss about the implementation of the system which is the
method that apply all the logical design into physical design that can be used by end-user.
This phase will be customized to meet functional requirement. All the process are analysing
problem occurs, software installation and configuration, hardware setup, testing the system
that have been developed and deployment the system.
27
4.2 Interfaces of iORDER System
This section will show all the interfaces in iORDER system for admin, employee
and customer.
4.2.1 Main Page
Figure 4.1 Home page for iORDER System
The Figure 4.1 is the main page for iORDER system. This system has three user
which are Admin, Employee and Customer who can login into this system. For Admin and
Employee, they can login into the system as Staff. For Customer, they need to sign up first
before they can login into the system.
28
4.2.2 Login and Sign up
Figure 4.2 Login for Admin, Employee and Customer
The Figure 4.2 is the login page for Customer and Staff which are Admin and
Employee. They need to insert the email, password and choose the login as Customer or
Admin/Employee. For Customer, they need to choose customer for login as and for Admin
and Employee, they need to choose Admin/Employee for login as. If the customer does not
have account, the need to click ‘Register Now!’ to create new account
Figure 4.3 Sign up for customer
The figure 4.3 is the form for new customer to sign up before they can login into
the iORDER system. After the fill all the form, they need to click save button. If the form
complete, the login page will appear and if they do not fill all the form, the notice will
appear to make sure they are required to fill the form.
29
4.3 Admin and Employee
Admin and employee are the staff that will handle all the orders from customers.
They can create, retrieve, update and delete the item in this system and also update the
delivery and payment status.
4.3.1 Main Page
Figure 4.4 Main pagr for admin and employee
This is the home page for staff after they successful login into the system. Admin
and employee can create, retrieve, update and delete the item of foods, can view the order
and update the delivery status. They also can view the payment that make from the
customers and update the status payment if they receive the payment from customers.
Admin also can view customer’s information. Last, admin and employee can view the
report by search start and end date to view the purchase that make from customers.
30
4.3.2 Item
Figure 4.5 View Item for admin and employee
Staff can view the menu of food that have already added. If the staff want to add
new item of food, they need to click Add New Item.
Figure 4.6 Add New Item for admin and employee
The figure above will be shown if the staff click the Add New Item button. Staff
can fill the form of the new item and save it. The item information will be store in database
and the Item page will be shown.
31
Figure 4.7 Update Item for admin and employee
Staff can update the item information if there any wrong information or they want
to change the new photo of the item.
Figure 4.8 Delete Item for admin and employee
Staff can delete the item and all the data of the item will deleted from database and
on the system.
32
4.3.3 Order
Figure 4.9 View Order for admin and employee
Staff can view all the order and can update the delivery status.
33
4.3.4 Payment
Figure 4.10 View Payment for admin and employee
Staff can view all the payment that make from the customer and can update the
status whether it done or not.
34
4.3.5 Report
Figure 4.11 View all report for admin and employee
Figure 4.11 above show all the report from customer that order the item. Admin
also can view the report by search the date.
figure 4.12 View report search by date
Figure 4.12 above will show after admin choose the start date and end date to view
the certain information. Then, click the search button to view the report result.
35
4.4 Customer
4.4.1 Main Page
Figure 4.13 Home for customer
This is the main page for customer after they successful login the system.
36
4.4.2 Profile
Figure 4.14 View profile
Customer can view their profile by clicking the account and profile. They can
update or delete the account from the system.
Figure 4.15 Update profile and delete account
Customer can update the profile information if the info is incorrect or they want to
change it as their like.
37
4.4.3 Item
Figure 4.16 View Item for customer
Customer can view all the menu of item by clicking the Item page. They also can
choose whether All the menu or they can view in category by click Breakfast, Lunch,
Dinner, Desert or Drink.
Figure 4.17 Buy Item
If customer want to place the order, they need to click buy button and the page
above will be shown. Then, they need to fill the quantity of the food as their want and click
buy.
38
Figure 4.18 Confirmation of buy item
After they click the buy button, the page above will be shown. The customer can
view and check if all the information is correct and they can make the confirmation to buy
the food. In Item Detail, it shown the item information and cannot be edit. For the Shipping
Detail, customer can edit their address and phone number if they want to change it. Last
for Payment Detail, the total will show the price by multiple the price of item with quantity.
Customer can choose the payment option that they want to make like Walk-in, Cash on
Delivery or Bank in.
Figure 4.19 Detail of Order
This page will be shown after customer submit the order. They can print the
information as their evidence.
39
4.4.4 Rating
Figure 4.20 Average rating and reviews
Figure above show all the rating that make from customer of iORDER system. It
also show the average of the rating of thee item. Others customer can view the rating of the
item before they buy it to check the quality of item and read the review from the previous
customers.
40
Figure 4.21 Rating item
Figure 4.21 will be show after customer click the rate the product button. Customer
can rate from one to five star and need to comment the item and click the save review button
after they done.
Figure 4.22 Detail of Order
Figure above show the pop-up of successful rate the item after customer done rated
and reviews the item and the data will be save in database.
41
4.4.5 Order
Figure 4.23 View order report
Customer can view the history of the order that they have make before and see the
status of delivery.
42
4.4.6 Payment
Figure 4.24 View payment report
Customer can view the history of the payment that they have make before and see
the payment status.
43
4.5 Test Case
A test case is a set of condition which is a tester will determine whether a system is
working as it was originally establish for it to do. The process of doing test cases can help
to find out problems input, action or event and an expected response. All of these are used
to determine the system is function properly. The table below show the test cases for the
several of the process of the system.
4.5.1 Sign up
Table 4.1 Test case sign up
Action Expected Response Pass/Fail Comment
Insert all Customer
information (name, email,
password, address,
postcode, state, phone
number, race)
Sign up successful
and Customer will
redirect to Login
page
Pass -
Insert Customer
information without race.
Unable to submit
registration
Fail Customer will be
asked to fill all
the signup form
44
4.5.2 Login
Table 4.2 Test case login
Action Expected Response Pass/Fail Comment
Insert correct email,
password and login as
(customer / staff)
User able to login -
Home page
Pass -
Insert wrong email,
password or login as
(customer / staff)
Unable to login Fail User need to
insert the correct
email, password
and login as
(customer / staff)
4.5.3 Add New Item for Staff (Admin and Employee)
Table 4.3 Test case add new item
Action Expected Response Pass/Fail Comment
Complete the form of add
new item
Successful add new
item
Pass -
Not complete the form of
add new item
Need to refill the
form
Fail -
45
4.5.4 Update Item for Staff (Admin and Employee)
Table 4.4 Test case update item
Action Expected Response Pass/Fail Comment
Edit the information of
item
Successful update
item
Pass Get iditem
Cancel update Item information
remain the same
Pass -
4.5.5 Delete Item for Staff (Admin and Employee)
Table 4.5 Test case delete item
Action Expected Response Pass/Fail Comment
Delete any of item Successful delete
item from database
and on the page
Pass Get iditem
4.5.6 Update Profile for Customer
Table 4.6 Test case update profile
Action Expected Response Pass/Fail Comment
Edit the customer profile Successful edit the
profile
Pass -
46
4.5.7 Place Order for Customer
Table 4.7 Test case place order
Action Expected Response Pass/Fail Comment
Choose any food that
Customer want to order
Food data will be
displayed on order
page to insert the
quantity
Pass User can place
minimum 1
quantity per
order
Fill the quantity they wish
to order
Show the Item
Detail, Shipping
Detail and Payment
Detail
Pass Shipping Detail -
Customer can
edit their address,
phone number
Payment Detail –
Customer can
choose walk-in,
cash on delivery
or bank in to pay
the item they buy
Click submit button Customer has
completed his/her
order
Pass -
47
4.5.8 Rating Item for Customer
Table 4.8 Test case rating item
Action Expected Response Pass/Fail Comment
Choose food that
Customer want to rate
Food data will be
displayed on rate
page
Pass -
Customer need to click
Rating and Reviews
Redirect to the page Pass View all rate and
review from
previous
customer.
Customer need to click
rate this product button
Form to rate the item Pass Rate from one to
five star, fill the
title and
comment.
Click Save Review button Customer completed
his/her rate and
review item
Pass -
48
4.6 Summary
This chapter can conclude that, implementation is the process of converting design
into the real system. This phase allowed to see whether the system has been developed that
can be operating without any problem. Prototype is a model that serves as the end but not
the equipped with full features. But the prototype used to test the process or function of the
basic system works as planned. Then, testing measures will be implemented are assessed.
49
CHAPTER 5
CONCLUSION
5.1 Introduction
In this chapter concludes the overall of this project in the aspects of planning,
design, implementation and testing. This project which is iORDER system is achieving the
objective which is solves the main problem to enable student make accurate and efficiency
purchasing an order process and also this system may reduce human error while taking an
order such as miscalculated price and lost order paper.
50
5.2 Project Constraints
During development of this project, there are several problems, limitation and time
constraint that occur causing a few implementations were left out and was not able to
achieve. The problem and limitation during conducting this study are:
• Alert notification when user has submitted their order into the system was not
present.
• Doesn’t have add to cart function when customer order the item. Customer need to
order the food one by one through the system.
5.3 Future Work
Every developer has aims to improve their system or project for the next project.
For the future work, there are some suggestion that can be add to improve this system to be
more efficient which are:
• Add an alert notification to notify employee that the customer has placed their order.
• The employee also should send the response or information through the customer’s
email to promote the new item of food at the cafe.
• Able to order more food at one time.
51
REFERENCES
[1] Blog: blog.amalto.com/blog/5-key-challenges-with-manual-sales-order-processing,
Title: 5 Key Challenges with Manual Sales Order Processing Aug 3, 2017
[2] F.O. Isinkaye , Y.O. Folajimi , B.A. Ojokoh (2015), ‘Recommendation systems:
Principles, methods and evaluation”, Egyption Information Journal, 20 August 2015, 16,
261-273
[3] John O'Donovan and John Dunnionv (2014), “A Framework for Evaluation of
Information Filtering Techniques in an Adaptive Recommender System”, Conference
Paper in Lecture Notes in Computer Science, August 2004, doi: 10.1007/978-3-540-24630-
5_62
[4] Website https://www.ninjagrillusa.com/, Ninja Grill USA by Joyopos, 2012
[5] Website https://www.sakaesushi.com.my/, Sakae Sushi by Oddle.me, 2011
[6] Website http://abhidemo.com/demo/food/index.php, Abhi Restaurant by AbhiAndroid,
2017
[7] Website https://www.phpzag.com/star-rating-system-with-ajax-php-and-mysql/, Star
Rating System with Ajax, PHP and MySQL by PhpZag Team, 28 January 2019
[8] Website: https://www.infoworld.com/article/3237508/what-is-agile-methodology-
modern-software-development-explained.html, What is agile methodology? Modern
software development explained, Isaac Sacolick, 25 Feb 2020
52
https://www.infoworld.com/article/3237508/what-is-agile-methodology-modern-software-development-explained.htmlhttps://www.infoworld.com/article/3237508/what-is-agile-methodology-modern-software-development-explained.html
[9] Website: https://www.guru99.com/agile-scrum-extreme-testing.html, Agile
Methodology & Model: Guide for Software Development & Testing, Guru99, 2020
[10] Website: https://mybookcave.com/what-do-star-ratings-mean-to-you/, What do star
ratings mean to you?, Catia Shattuck, 18 April 2019
[11] Website: https://www.slideshare.net/armanreza161/food-ordering-system/, Food
Ordering System, Arman Ahmed, Mymensingh weber solution, 21 April 2017
53
https://www.guru99.com/agile-scrum-extreme-testing.htmlhttps://mybookcave.com/what-do-star-ratings-mean-to-you/https://www.slideshare.net/armanreza161/food-ordering-system/,