Cover

[Online Food Ordering and Delivery

System For Sunflower Fast Food
Restaurants]

Student ID: 00186578

Student Name: Mg Oak Gar Oo

Section: L5DC-70

1|Page
Table of Contents

2|Page
Abstract

3|Page
Acknowledgement

4|Page
Project Proposal

5|Page
1. Project Proposal

1.1 Overview (200 to 400) words

Sunflower restaurant is a well-known fast food restaurant in Yangon. Food served in
Sunflower restaurant is offered from a popular menu, cooked in bulk in advance and kept hot,
is finished and packaged for order and is usually available ready for pickup or to be delivered
though seating may also be provided. Customers are usually waiting seats, selecting their
meals and paying .And sunflower restaurant don’t have online service system. Nowadays
,every system based on Digital marketing. So restaurant manager have clear strategic goal for
what he want to achieve online in terms of gaining new customers with deeper relationships
and want to know customer feedback. Some customers claim that they want to order with
online service system. Now, Sunflower restaurant set up and start up their online ordering and
delivery system. After that customer demand on online service is very grow and their software
is not comfortable for customers. So, they want more comfortable ordering and delivery
system for users.

1.2 Current Business History

Sunflower restaurants prepare and serve various kinds of food and drinks for customers.
Meals are served and eaten in the restaurant and also offer takeout and food delivery
services. Sunflower restaurant serve like a family restaurant for customers. Sunflower
restaurant is not a small business. There are many restaurant branches in Yangon. The
primary factors of the Sunflower restaurants are usually the food itself (example. vegetarian,
steak),the cuisine(Thailand and Chinese). Sunflower Restaurant range from inexpensive and
informal lunching or dinning place catering to people working nearby, with modest food served
in simple settings at low prices. The food ordering and delivery system is for restaurant and
food cooperative with other cooperator websites and applications for the customers to provide
more interactive feelings so that ordering process could be carried out.

1.3 Current Business Process

1.3.1 Food Ordering Process
In restaurant-controlled ordering, Sunflower restaurants created their own website and
application. So, a customer can choose to have the food delivered or pick-up. In this process
customers can scanning the menu items, choosing the items and finally choosing to delivery
or pick-up the app or website.

6|Page
1.3.2 Food Delivery Process
1. Food Cooperatives
Food cooperatives like food panda co-op and allow members to place orders of locally
produced food online and pick up and deliver for their orders to customers.

2. Food delivery riders and drivers

Food riders and drivers are depending restaurant delivery app service when they work.
Sunflower restaurant consider them as employees because they work full time hours
and required to wear uniforms.

7|Page
1.4 Current Business Issues
1.4.1 The problem statement of current system
The problem in current system is not realizing the efficiencies that would result from
better application of technology in daily operations. Fast food business is a very
competitive business and one way to stand out from competitors is through improving
the business process where business process automation can assist business
improvement. The system can’t truck customer past history and lack of data security.
1.4.2 Payment issue
The customers are not able to see the ingredients of the meals before they place their
order and also they only have to pay for an order online.
1.4.3 Customer Feedback problem
In this current system , customer cannot send customer feedback in the website and
also staff can’t see the customer feedback because of the some bugs error in website.
So, restaurant employees cannot serve more better service and don’t keep in touch
with customers sometimes.
1.4.4 Application and design problem
When hungry customers want to order online, they don’t want to spend their time
navigating a complicated menu that doesn’t allow them to easily modify to their food
selection. In this current system, the web design is not satisfying for customers .
Ingredients of menus and price are cannot update easily in web because of server
delay. If, customers try to order in online, find that the menus list is confusing or
complicated they will be disappointed. Online ordering system that isn’t mobile-friendly
with customers could cause a problem in their overall sales.

1.5 Proposed System Scope

The system will be a bunch of benefits from the various point of views and bring many
efficiency for customers.

1.5.1 Web Ordering System

The purpose of this system is to make the process of placing order as simple as possible
for the customers. Customers can manage order, select items , make payment on online or
cash in hand when delivery man arrive.

8|Page
1.5.2 Delivery System for restaurant employees

This system will be available only to restaurant employees and allow them to manage
the orders that are displayed to users of the web ordering system. The online website enables
the end user to register to the system online and placed into the database and then retrieved.
In application , all food items and orders are displayed , along with their corresponding options
and easy to read delivery details. This features allow restaurant employees to quickly go
through the orders. After that they can placed and produce the necessary items without delay
and confusion.

1.5.3 User Interface Specifications for system

The design patterns for the online food ordering and delivery system is more standard
them existing system and it is pretty much standard web application. The system will be a
web based application and its mains is to simplify and improve the efficiency of ordering
process for both customer and restaurant, minimize manual data entry and to make more
stronger security when order placement process. Moreover , customers can view product,
menus, and many ingredients with more flexibility .

9|Page
1.6 Aims and Objectives
1.5.1 Aims

This system is aimed at developing a complete online ordering system for use in the
foodservice industry which will allow Sunflower restaurant to quickly and easily manage an
online menu which customer can browse and use to place orders with just a few clicks.

1.5.1 Objectives(Analysis, Design, Coding, Deployment, Evaluation)

Research

1.Project Proposal

1.1Overview

1.2Current business history, process ,issues

1.3Proposed system scope

2.Introduction

3.Similar product Comparison(Investigation)

3.1Funcational Comparison

3.2Non- funcational comparison

4.Feasibility Study

4.1Technical Feasibility

4.2Operational Feasibility

4.3Economic Feasibility

5.Foundations

6.Exploration and Engineering

7.Deployment

8.Conclusion and Evaluation

10 | P a g e
Estimate Cost and Duration

1.6.1 Hardware Cost

No Item Description Unit Price Quantity Sub-Total

1 Desktop Computer Cpu: Core i 7 583,200MMK 3 1,749,600MMK
Ram:8 GB 65,000MMK 3 195,000MMK
SSD:2TB 442,000MMK 3 1,326,000MMK
Graphic:Nvidia 200,000MMK 3 600,000MMK
2 Ups GT730
Router Ups(2000) 225,000MMK 3 675,000MMK
Cisco 69,000MMK 4 276,000MMK
Printer EA2700
Canon 330,000MMK 2 660,000MMK
MF235
FingerprintDevice 75,000MMK 4 300,000MMK
Barcode Reader 55,000MMK 3 165,000MMK
CCTV 47,900MMK 5 239,500MMK
Automatic Voltage 120,000MMK 1 120,000MMK
Stabilizer

Total 6,306,100MMK

1.6.2 Software Cost

No Item Description Unit Price Quantity Sub-Total

1. Operating System Window10 license 15,000MMK 3 45,000MMK

2. Office software Office 365 license 10,000MMK 3 30,000MMK

3. Xampp Open source 0 0 0
4. IDE Sublime Text(free) 0 0 0
5. Antivirus Avast(1 year) 10,000MMK 3 30,000MMK
Total 105,000MMK

11 | P a g e
1.6.3 Development Cost

No Item Description Unit Price Quantity Sub-Total

1 Website Language: PHP 200,000MM 1 200,000MMK
Development Cost Database: Mysqli K
Data Entry: Free
Training: FOC
Total Pages:20 pages

2 Hosting Shwe web hosting(2 1 39,100MMK

service years) 39,100MMK

3 Domain name Domain.com(premium) 1 14,985MMK

registration 14,985MMK

Total 254,085MMK

1.6.4 Summary Cost

Category Cost
Software 105,000MMK
Hardware 6,306,100MMK
Development 254,085MMK
Total 6,665,185MMK

12 | P a g e
1.7 Project Plan (Gantt chart)

Fig (1) Project Proposal

13 | P a g e
Chapter-1
Introduction

14 | P a g e
1. Chapter – 1 Introduction

1.1 Background of the Current System

1.2 Current Business History

Sunflower restaurants prepare and serve various kinds of food and drinks for customers.
Meals are served and eaten in the restaurant and also offer takeout and food delivery
services. Sunflower restaurant serve like a family restaurant for customers. Sunflower
restaurant is not a small business. There are many restaurant branches in Yangon. The
primary factors of the Sunflower restaurants are usually the food itself (eg. vegetarian,
steak),the cuisine(Thailand and Chinese). Sunflower Restaurant range from inexpensive and
informal lunching or dinning place catering to people working nearby, with modest food served
in simple settings at low prices. The food ordering and delivery system is for restaurant and
food cooperative with other cooperator websites and applications for the customers to provide
more interactive feelings so that ordering process could be carried out.

1.3 Current Business Process

1.4 Food Ordering Process
In restaurant-controlled ordering, Sunflower restaurants created their own website and
application. So, a customer can choose to have the food delivered or pick-up. In this process
customers can scanning the menu items, choosing the items and finally choosing to delivery
or pick-up the app or website.

1.5 Food Delivery Process

1.5.1 Food Cooperatives

Food cooperatives like food panda co-op and allow members to place orders of locally
produced food online and pick up and deliver for their orders to customers.

1.5.2 Food delivery riders and drivers

Food riders and drivers are depending restaurant delivery app service when they work.
Sunflower restaurant consider them as employees because they work full time hours
and required to wear uniforms.

15 | P a g e
1.6 Current Business Issues

1..6.1 The problem statement of current system

The problem in current system is not realizing the efficiencies that would result from
better application of technology in daily operations. Fast food business is a very
competitive business and one way to stand out from competitors is through improving
the business process where business process automation can assist business
improvement. The system can’t truck customer past history and lack of data security.
1.5.3 Payment issue
The customers are not able to see the ingredients of the meals before they place their
order and also they only have to pay for an order online.
1.5.4 Customer Feedback problem
In this current system , customer cannot send customer feedback in the website and
also staff can’t see the customer feedback because of the some bugs error in website.
So, restaurant employees cannot serve more better service and don’t keep in touch
with customers sometimes.
1.5.5 Application and design problem
When hungry customers want to order online, they don’t want to spend their time
navigating a complicated menu that doesn’t allow them to easily modify to their food
selection. In this current system, the web design is not satisfying for customers .
Ingredients of menus and price are cannot update easily in web because of server
delay. If, customers try to order in online, find that the menus list is confusing or
complicated they will be disappointed. Online ordering system that isn’t mobile-friendly
with customers could cause a problem in their overall sales.

1.2 SWOT Analysis (Current System)

16 | P a g e
1.3 Proposed System Scope (Details Explain)

17 | P a g e
1.4 Aims & Objectives of the Project

18 | P a g e
1.5 Short overview of the remaining chapters

19 | P a g e
 Chapter-2
Similar Product Comparison
(Investigation)

20 | P a g e
2. Chapter-2 Similar Product Comparison

2.1 Similar Product Introduction

Intro & explain & Screenshot

21 | P a g e
2.2 Functional Comparison
(1) Customer Registration

Shop.com

Fig (1) Customer Signup Form from Shop.com

???

City Mall

Fig (2) Customer Signup Form from City Mall

???

22 | P a g e
2.3 Non-Functional Comparison
10 Usability Heuristics

1. Visibility of System Status

Explain??????????????????

Shop.com

Fig (1) ??? Explain………………

CityMall

Fig (2) ??? Explain………………

23 | P a g e
Chapter-3
Feasibility Study

24 | P a g e
3. Chapter-3 Feasibility Study

3.1 Technical Feasibility

3.1.1 Methodologies

A. Definition

B. Strength and Weakness of each Methodology

C. Comparison of Methodology
Criteria

D. Recommendation for Methodology

25 | P a g e
3.1.2 Programming Languages

A. Definition

B. Strength and Weakness of each Programming Languages

C. Comparison of Programming Languages

Criteria

D. Recommendation for Programming Language

26 | P a g e
3.1.3 Databases

A. Definition

B. Strength and Weakness of each Databases

C. Comparison of Databases

Criteria

D. Recommendation for Programming Language

27 | P a g e
3.2 DSDM Feasibility (DSDM Nine Principles)

28 | P a g e
3.3 Possible LESP (Legal, Ethical, Social and Professional) Issues

29 | P a g e
Chapter-4
Foundations

30 | P a g e
4.1 Target User
The target…

Type of User Age Computer skill / IT Language skill

Literacy (especially English
skill)

31 | P a g e
4.2 Functional Requirement
1 Manage Purchase Process
1.1 Manage Staff (HL)
 Register Staff (ML)
Email already exist check (LL)
Password Length check (LL)
 Update Staff
 Delete Staff
 Search Staff
 Staff Login
1.2 Manage Supplier
 Register Supplier
 Update Supplier
 Delete Supplier
 Search Supplier
1.3 Manage Brand
 Register Brand
 Update Brand
 Delete Brand
 Search Brand
1.4 Manage Category
 Register Category
 Update Category
 Delete Category
 Search Category
1.5 Manage Product
 Register Product
 Update Product
 Delete Product
 Search Product
1.6 Manage Purchase
 Record Purchase
 Confirm Purchase
 Search & Report Purchase

32 | P a g e
4.3 MOSCOW Prioritization
Must

Must Justification
Record table
Record Room
Record Booking

33 | P a g e
4.4 Non-Functional Requirements

1. Usability

2. Security

3. Performance

4. Interface

5. Operational

6. Resource

7. Portability

8. Reliability

9. Maintainability

10. Safety

11. Recovery

34 | P a g e
4.5 Time box Plan

Time box 1: Manage Purchase Process Time box

Time box Name Manage Purchase Process Time-box

Start Date July 31, 2019
End Date XXX
Task Duration Start Date End Date
Functional Requirement 1 day July 20, 2018 July 20, 2018
Use Case Diagram 1 day July 20, 2018 July 20, 2018
Class Design 1 days July 23, 2018 July 23, 2018
Sequence Diagram 1 days July 23, 2018 July 23, 2018
High Level & Low Level 2 ?? ??
Prototype
Coding 6 days July 24, 2018 July 31, 2018
Functional Testing 1 days August 1, 2018 August 1, 2018
Usability Testing 1 days August 2, 2018 August 2, 2018
Time Box Summary 1 day August 3, 2018 August 3, 2018
Key Deliverables (Output)
Design
 Use Case Diagram for Purchase Process

Coding

Testing
 Unit Test Document
 Usability Test Document
 Test Cases

35 | P a g e
Time box 2: XXX

Time box 3: XXX

36 | P a g e
4.6 Risk Management
4.6.1 Identification of Possible Risks

The

37 | P a g e
4.6.2 Risk Matrix

Risk Probability Impact Proactive Reactive Risk

Action Action Owner
Not enough Medium Medium Learn about Discuss with
experience business supervisor about
process and project
discussion with
the user

38 | P a g e
4.6.3 Critical Success Factors for current project

The

39 | P a g e
The Whole System UseCase & Class

40 | P a g e
 Chapter-5
Exploration & Engineering

41 | P a g e
5.1 Time-box 1: Manage Purchase Time-box Development
Project Plan for Time Box 1

5.1.1 Functional Requirements List

Manage Purchase

1.1 Manage Staff (HL)

 Register Staff (ML)
Email already exist check (LL)
Password Length check (LL)
 Update Staff
 Delete Staff
 Search Staff
 Staff Login
1.2 Manage Supplier
 Register Supplier
 Update Supplier
 Delete Supplier
 Search Supplier
1.3 Manage Brand
 Register Brand
 Update Brand
 Delete Brand
 Search Brand
1.4 Manage Category
 Register Category
 Update Category
 Delete Category
 Search Category
1.5 Manage Product
 Register Product
 Update Product
 Delete Product

42 | P a g e
  Search Product
1.6 Manage Purchase
 Record Purchase
 Confirm Purchase
 Search & Report Purchase

5.1.2 Use Case Diagram

Use Case Diagram for Room and Table

Booking Timebox

Record Customer

Record Room

Receptionist
Record Table
Restaurant Manager

Record Booking

Use Case Description

Use Case Name Record Customer

Actor Receptionist

Flow of Event Fill the customer details in the customer form. Register button is
clicked.

For remaining, see Appendix.

43 | P a g e
5.1.3 Screen Design

1) Customer Register Form

Fig (1) Low Level Prototype for Customer Registration

Fig (2) High Level Prototype for Customer Registration

44 | P a g e
5.1.4 Iteration for Screen Design

Iteration 1

Users tell that table form and room form design are needed to change. So, table style
combo box is added in table entry form and room size combo box and Facility text box is also
added in room form.

(Iteration 1) Screen Design for Customer Register Form

45 | P a g e
5.1.5 Class Diagram

Initial Class Diagram

46 | P a g e
Detailed Class Diagram

Detail Class Definitions

Class Name Customer

Attributes Customer ID, Customer Name, Phone No, Address, Email, Member Type

Operation Register (),Cancel (), AutoID(), Checkdata()

Description << The Customer class is used to do register for customers who booked.>>

For remaining, see Appendix.

47 | P a g e
5.1.6 Sequence Diagram for Booking Process

Customer: c Room r Table: t Booking: b

Receptionist

Check Existing()

Return Customer

if room, choose room add to booking

Ask Room or Table

Add to Booking

if Table, Choose Table

Booking List
Check

Booking Confirmed

Sequence Diagram Description

48 | P a g e
5.1.7 Functional Testing

Test Plan
Module 1: Customer Entry
Test Script Description Date Tester
1.1 Test customer Name text box 7- August- 2018 Kyal Sin Linn
1.2 Test Customer Phone no text 7- August- 2018 Kyal Sin Linn
box
1.3 Test Customer Address text 7- August- 2018 Kyal Sin Linn
box
1.4 Test the ‘@’ in the E mail 7- August- 2018 Kyal Sin Linn
1.5 Test Customer Email text box 7- August- 2018 Kyal Sin Linn
1.6 Test Register Button 7- August- 2018 Kyal Sin Linn

49 | P a g e
Test Script (1)

Unit Test 1 Test Case: Register by data entry Designed by: Mg Mg

customers
Data Source: Customer Objective: To test the Register of data Tester: Mg Mg
Table entry customers
Test Case Description Test Procedure Expected Actual
Result Results
1.1 Test 'Register' button is clicked. Customer Show See
customer Name is blanked. ‘Please fill Fig.1.2
Name text out this
field’
box
message.
Before Testing

Fig.1.1

After Testing

Fig.1.2

Test Case Description Test Procedure Expected Actual

Result Results

50 | P a g e
1.2 Test 'Register' button is clicked. Customer Show See
Customer Name is blanked. ‘Please fill Fig.1.2
Phone no out this
field’
text box
message.

Before Testing

Fig.1.1

51 | P a g e
After Testing

Fig.1.2

For remaining test cases, please see Appendix.

52 | P a g e
5.1.8 Usability Testing

Visibility of System Status

Can see text box

with different color

Explain

Match between System and Real World

FASDF

Aesthetic and Minimalist Design

ASDF

Consistency and standard

ASDF

Error Prevention

SDFDFS

User Control and Freedom

ASDF

53 | P a g e
5.1.9 Iteration for Usability Testing

Iteration 2

Users tell that table form and room form design are needed to change. So, table style
combo box is added in table entry form and room size combo box and Facility text box is also
added in room form.

(Iteration 2) Iteration For Visibility of System Status

Click to the
help link

5.1.8 Time box Summary

Wok Done

Problems (Issues)

Solutions

Remaining Time-boxes

54 | P a g e
CHAPTER – 6
Deployment

55 | P a g e
 6.1 Deployment
6.1.1 Deployment Diagram

<<Web Server>>
<<Apache>>
 admin_profile.php
 adminheader.php
 adminfooter.php
 adminstaff_home.php
Router  appointment.php
Internet  appointment_detail.php
 appointment_list.php
 appointment_report.php
 appointment2.php
<<Laptop>>  appointment3.php
 AutoID_Functions.php <<Database Server>>
 confirmappointment.php
Firefox
 connect.php
familyhospital_db
 contactus.php
 department.php
Chrome  department_list.php <<MYSQL>>
Firewall  doctor_entry.php
 doctor_home.php
 doctor_list.php
Adobe Acrobat  doctor_logout.php
 doctor_profile.php
 footer.php
 forgot_password.php
Avast Antivirus  functions.php
 header.php
 help.php
 index.php
 log_list.php
 login.php
TCP/IP

 patient_entry.php
 patient_home.php
 patient_list.php
 patient_logout.php
 patient_profile.php
 payment.php
 payment_report.php
 payment_voucher.php
 schedule.php
<<Printer>>  schedule_detail.php
 schedule_functions.php
 schedule_list.php
 schedule_report.php
 setup.php
 specialty_list.php
 staff_entry.php
 staff_home.php
 staff_list.php
 staff_logout.php
 staff_profile.php
 suggestion.php
 suggestion_email.php
 suggestion_report.php
 TokenEmail.php
 treatment.php
 treatment_report.php

6.1.2 Explanation for diagram

ASDFASDFDF

56 | P a g e
 6.2 Data Migration
6.2.1 Data to Migrate

Explain

Time Box Master Data Transaction Data

Time Box 1: Table and Customer, Staff, Room, Booking
Room Booking Time Box Table

6.2.2 Plan

TimeBox Data To Migrate Duration Start End Date Responsible

Date person
Time Box 1: - Customer 4 days 9 August 14 August
Room and - Staff 2018 2018 Receptionist,
Table Booking - Room Restaurant
Time Box - Table Manger
- Booking
-
-
-

57 | P a g e
 6.3 Training
6.3.1 Training plan

No Contact Trainee Start End Date Venue Time

Date
1 Time Box 1 Receptionist, 15 17 Jame 5 pm – 7
- Customer Restaurant August August Restaurant pm
- Room Manager, 2018 2018
- Table
- Booking
- Staff
-
-
-

6.3.2 User Manual

Firstly, set the booking date

And set the booking time

After choosing the booking

type click to the Find
button
And Choose the booking
type

58 | P a g e
CHA
PTE
R–
7
CON
CLU
SIO
N
& 59 | P a g e
 7.1 Evaluation against Aim & Objectives
Aim

Objective 1

Analysis –

Objective 2

Design –

Objective 3

Coding –

Objective 4

Testing –

Objective 5

Training –

60 | P a g e
 7.2 Evaluation Against Similar System

No My System Incy POS

1 Visibility of System Status Visibility of System Status

The system status the selected text box in the

specific color so the status of the system is said
to be visible.

The system status the selected tab in the

specific style so the status of the system is
said to be visible.

61 | P a g e
 7.3 Evaluation against Justification Made
Method

Language

Database

62 | P a g e
 7.4 Evaluation against Time Box Plan
Time Box 1: Room and Table Booking Time Box
When making the time box plan, the end date for time box 1 is ‘August 9, 2018’. And
time box 1 was finished with all the needed iteration within this date. Therefore, end date was
matched with time box plan.

7.5 Personal Evaluation

7.6 Strength & Weakness

Strength

Weakness

63 | P a g e
7.7 Future Amendment

64 | P a g e
APP
END
IX

65 | P a g e
 Section A: Use Case Descriptions
Timebox 1: Room and Table Booking Timebox

Section B: Detailed Class Definitions

Timebox 1: Room and Table Booking Timebox

Section C: Coding

Form Function Purpose

Ingredient Entry, Table Entry, Save ()
Room Entry, Food Entry,
To save the data from the forms into the
database. When SAVE button is clicked
the input data are loaded into variables
and then using sql statements, inserting is
made.

66 | P a g e
 Section D: Test Scripts

Section F: Interview Scripts

When interview with manager

67 | P a g e
References

68 | P a g e
References List

69 | P a g e