Abstract

The purpose of this project is to build a food delivery Client mobile application that can be used to replace the traditional ordering system that is currently implemented in the majority of the food and beverage industry. This Application is designed to suit a small to medium single Restaurant. That means, only one Restaurant can host and deliver its products to multiple customers through the Application. This is contrary to the common multiple-restaurant-model used in many other mobile food delivery applications.

For the customer, this application provides a view of food information (category, name, image，price, description), fro m which they can choose to either order immediately or save in their Wish list for later purchase. Users can also update their user information such as name, email, as well as their physical address for receiving their ordered items.  For the backend, the system comes with a web-based panel as well, where the Admin can add, view, update, or delete the products fro m the Application’s database.

The technology used to make develop this application’s front end was Android Studio, which is based on Java language. While for the backend, Parse Server by Back4App.com, a web-based database management system, was used for managing the databases. Also, PayPal’s Payment service called Braintree was used for processing payments made through the Application.

 

Keywords: Android; Food Delivery; Java; Parse Server; Mobile Application

 

目录

摘要

Abstract

1 Introduction-1

1.1 Background of the Project-1

1.2 What is Android OS?-2

1.3 What is a Food Delivery Application-3

2 System Design-5

2.1 Objectives of the Application-5

2.2 System Analysis-5

2.3 Scope of the Application-7

2.4 Admin-User Roles-8

2.5 Overview of Technologies Used-8

2.5.1 Java Programming Language-8

2.5.2 Parse Server-9

2.5.3 Node.js-9

2.5.4 Braintree Payments SDK-10

2.5.5 Adobe XD-10

2.6 System Requirements for HaoChi Application-11

2.6.1 General Requirements-11

2.6.2 Functional Requirements-11

2.6.3 Non Functional Requirements-12

3 Detailed Design-13

3.1 Application Interface-13

3.1.1 Home Screen-14

3.1.2 Product List-15

3.1.3 Product Detail Page-15

3.1.4 Profile Section-17

3.1.5 Cart Section-18

3.1.6 Favorites Section-19

3.1.7 Checkout Page-19

3.2 Payment Process-20

3.3 Database Structure-22

3.3.1 Users table-23

3.3.2 Products Table-23

3.3.3 Cart Table-24

3.3.4 Favorites Table-25

3.3.5 Feedback Table-25

3.3.6 Orders Table-26

4 Application Management-27

4.1Admin Login-27

4.2Admin Panel Dashboard-28

4.3User Management by the Admin-29

5 Application Software Testing-31

5.1 Implementation Issues & Challenges-31

5.1.1 User without background-31

5.1.2 Screen size of different device-31

5.1.3 Server performance-31

5.2 Test Plan-31

5.2.1 Unit Testing-32

5.2.2 Functional Testing-32

5.2.3 System Testing System-32

5.2.4 Acceptance Testing-33

6 Conclusion-34

Acknowledgements-35

References-36