KWAME NKRUMAH UNIVERSITY OF SCIENCE AND TECHNOLOGY

COLLEGE OF SCIENCE
FACULTY OF PHYSICAL AND COMPUTATIONAL SCIENCE

PROJECT DOCUMENTATION
FOR CONSIDERATION UNDER
BACHELOR OF COMPUTER SCIENCE (BSc) PROGRAMME

PROJECT TITLE
MealTime Food Delivery App

SUBMITTED BY
Renee deGraft-Etsison (8545421)

SUPERVISOR
Dr. Kate Takyi
DECLARATIONS
This document is the original work of Renee, and all rights are reserved. The information contained
herein is accurate to the best of our knowledge, but we make no warranties or representations
regarding its completeness or accuracy

ACKNOWLEDGEMENT
I would like to extend my gratitude to the following individuals who contributed to the success of this
project:
Zainab, who assisted with the documentation and provided invaluable support throughout the project.
ChatGPT, whose expertise and guidance were instrumental in the project's development.
Mimi and Edmund, who generously offered their time and expertise to review the project and
provided constructive feedback that greatly improved its quality.
I would also like to acknowledge that this project was completed independently, with sole
responsibility for its conception, planning, and execution.
Thank you again to these individuals for their support, guidance, and contributions. Their involvement
has been invaluable, and I am grateful for their help in bringing this project to fruition.

DEDICATION
Dedicated to Edmund, whose tireless efforts and dedication to this project have been invaluable?

ABSTRACT
MealTime Food Delivery App aims to revolutionize the way people order and consume food by
providing a user-friendly interface, real-time order tracking, and a wide selection of restaurants. The
app addresses common issues such as inefficiency in tracking orders, limited restaurant options, and
customer dissatisfaction, thereby ensuring a seamless food ordering experience.

Chapter One: Introduction

1.1 Overview
Food delivery apps have revolutionized the way people order and consume food, offering a wide
range of options and flexibility. However, despite the growing popularity of these apps, most are not
user-friendly, orders cannot be tracked efficiently, and there are limited restaurant options and
availability. These issues cause dissatisfaction among customers and decrease restaurant profitability.

1.2 Problem Statement

There is a need to create a food delivery app that is user-friendly and efficient. This app should allow
customers to easily browse and order food from their favourite local restaurants, track their orders in
real-time, and streamline the delivery process to ensure the timely arrival of orders.

1.3 Project Aims

The MealTime Food Delivery App aims to develop a platform that addresses the inefficiencies of
current food delivery services by enhancing user experience, increasing restaurant availability, and
optimizing the delivery process.

1.4 Project Objectives

• Develop an intuitive and easy-to-navigate interface.
• Implement real-time order tracking.
• Increase the number of available restaurants.
• Ensure timely delivery of orders.
• Improve overall customer satisfaction with the food ordering and delivery process.

1.5 Scope of the Project

The project will focus on the development of a mobile application that integrates with local
restaurants, provides real-time order tracking, and enhances user experience through a user-friendly
interface and efficient delivery management.

1.6 Limitations of the Project

• Limited initial restaurant partnerships.
• Potential technical challenges in real-time tracking implementation.
• Scalability concerns during peak usage times.

1.7 Approach to Project

The project will adopt an Agile development methodology to ensure iterative development and
continuous feedback. The development process will include user testing, feedback incorporation, and
phased feature implementation.

Chapter Two: Review of Literature and Tools

2.1 Background Review

Existing food delivery services provide a foundation for understanding the common issues faced by
users and areas for improvement.

2.2 Review of Existing Applications

A review of popular food delivery apps like Uber Eats, Glovo, DoorDash, and Grubhub reveals
common user complaints about interface usability, order tracking inefficiencies, and limited restaurant
options.

2.3 Problem Identification

Current food delivery services often lack user-friendly interfaces, efficient order tracking, and
sufficient restaurant variety, leading to customer dissatisfaction.

2.4 Project Evaluation

The MealTime Food Delivery App aims to address these issues by providing a superior user interface,
real-time order tracking, and an extensive selection of local restaurants.

2.5 Review of Project-Related Methodologies

The project will utilize Agile methodology, Ktor for backend development, Flutter for frontend
development, MySQL for database management, and RESTful APIs for communication between
frontend and backend components.

Chapter Three: Requirements Specifications

3.1 Requirements Gathering

Requirements were gathered through user surveys, competitive analysis, and stakeholder interviews.

3.2 Functional Requirements

• User-Friendly Interface: Simple navigation, search functionality, and personalized
recommendations.
• Order Tracking: Real-time updates, and push notifications.
• Restaurant Availability: Wide selection of restaurants, and filter options.
• Efficient Delivery: Optimized routes, and delivery personnel management.
• Customer Satisfaction: Feedback system, 24/7 customer support.
3.3 Non-Functional Requirements
• Scalability: Ability to handle increasing user load.
• Performance: Quick response times and minimal downtime.
• Security: Protection of user data and transactions.

3.4 Hardware Requirements

• Servers for backend infrastructure.
• Mobile devices for testing the app.

3.5 Requirements Analysis

Detailed analysis of user needs and technical specifications ensures the app meets the defined
requirements.

3.6 Use Case Diagram

Chapter Four: Design Specifications

4.1 System Design and Methodology

The system architecture includes a backend developed using Ktor, a mobile frontend developed using
Flutter, a MySQL database, and RESTful APIs for communication. Real-time features are
implemented using Socket.io.

4.2 System Interfaces

The app interfaces include user registration and login, restaurant browsing, order placement, and real-
time order tracking.

4.3 Requirement Model (Use Case Descriptions)

Actors:
1. Customer
2. Restaurant
3. Delivery Person
4. Admin

Customer Use Cases:

 Register/Login: Create or access an account.

 Browse/Search Restaurants: Find restaurants.
 View Menu: See a restaurant's menu.
 Place Order: Order food.
 Make Payment: Pay for the order.
 Track Order: Monitor order status.
 Rate/Review Order: Provide feedback.
 View Order History: Look at past orders.

Restaurant Use Cases:

 Register/Login: Create or access an account.

 Manage Menu: Add/update/delete menu items.
 View Orders: See incoming orders.
 Update Order Status: Change order status.
 Manage Restaurant Profile: Update profile info.
 View Feedback: Read customer reviews.

Delivery Person Use Cases:

 Register/Login: Create or access an account.

 View Delivery Requests: See available deliveries.
 Update Delivery Status: Change delivery status.
 View Delivery History: Look at past deliveries.
 Manage Profile: Update profile info.
Admin Use Cases:

 Manage Users: Manage customer and restaurant accounts.

 Manage Restaurants: Approve/suspend/delete restaurant profiles.
 View System Reports: See analytics and reports.
 Manage Payments: Oversee transactions.
 Resolve Issues/Complaints: Handle user issues.

Relationships:
1. Customer: Interacts with the system for registration, ordering, tracking, and reviewing.
2. Restaurant: Manages menu and orders, interacts with customers via the system.
3. Delivery Person: Handles deliveries, updates statuses.
4. Admin: Manages overall operations, user accounts, payments, and issues.

Chapter Five: Implementation and Testing

5.1 Development Tools and Platform Consideration

• Backend: Ktor
• Database: MySQL
• Frontend: Flutter
• APIs: RESTful
• Real-Time: Socket.io
• Version Control: Git
• CI/CD: Continuous Integration and Continuous Deployment Pipelines

5.2 Testing
Testing will include unit, integration, and user acceptance testing to ensure all features work as
intended.

5.3 Unit Testing

Individual components will be tested in isolation to ensure they function correctly.

5.4 Integration Testing

Combined components will be tested to ensure they work together seamlessly.
5.5 Deployment
The app will use CI/CD pipelines to ensure smooth and efficient releases.

Reference
CHATGPT 4o