NIT6150: Online Food Ordering & Delivery Service Application Project

Desklib provides past papers and solved assignments for students. This project details the design of an online food ordering system.

NIT6150
ONLINE FOOD ORDERING &
DELIVERY SERVICE APPLICATION
Student Name:
Student ID:

Contents
1. Introduction..................................................................................................................................3
1.1 Overview & Background Information...................................................................................3
1.2 System Objectives.................................................................................................................3
2. Development Methodology and Approach..................................................................................4
2.1 Methodology Selected...........................................................................................................4
3. Functional Requirements.............................................................................................................4
3.1 UML – Class Diagram...........................................................................................................5
3.2 Database Specifications.........................................................................................................6
3.3 Sequence Diagram.................................................................................................................8
4. System Use Cases........................................................................................................................9
4.1 Use Case Diagram (Complete)..............................................................................................9
5. Non-Functional System Requirements......................................................................................12
6. System Navigation & Interface Design.....................................................................................12
7. Cost Analysis of the Complete Project......................................................................................14
8. Project Schedule and Work Breakdown Structure....................................................................14
9. System Issues & Limitations.....................................................................................................15
10. Work Distribution Between the Members...............................................................................16
11. Conclusion...............................................................................................................................16
References......................................................................................................................................17

List of Figures
Figure 1: Food-Ordering System's Class Diagram..........................................................................6
Figure 2: Sequence Diagram for Food Ordering Process................................................................9
Figure 3: Use case of Manager......................................................................................................10
Figure 4: Restaurant Staff activities..............................................................................................11
Figure 5: Kitchen Staff..................................................................................................................11
Figure 6: Customer Use Case........................................................................................................11
Figure 7: Use Case diagram for Online Food Ordering System....................................................12
Figure 8: Home & Menu Screen....................................................................................................14
Figure 9: Cart & Payment Screens................................................................................................14
Figure 10: Work Breakdown Structure & Schedule (as Gantt Chart)...........................................16

1. Introduction
1.1 Overview & Background Information
Due to rapid growth in the IT industries and the movement of consumers towards online
services, all the businesses need to provide online services in one way or another to cope up with
the rapidly growing business and competitions in the market. System analysis and designing help
new businesses to grow faster and compete in the market by providing an online platform to
deliver their services.
The case scenario for the “System Analysis & Design” report is of a small restaurant, “Happy
Tummy”, which is facing loss in the market due to emerging competitors with their latest
services. On the basis of the proposal designed in Assessment 1, this report will include steps and
methodologies used while designing a system for online food ordering and delivery service.
1.2 System Objectives
The Happy Tummy is affected by huge market competition and its customer strength is slowly
decreasing as the company does not provide its services online. Therefore, a new system is to be
designed for the restaurant to help them gain more customers through online sources. The system
to be designed should be able to provide online food ordering and payment functionalities to the
customers. The users should be able to make different selections from the menu available online
and pay for the order online. In order to address these conditions, the system will have the
following functions:
1. A “Home Page” that can provide all the necessary information and links to the customers
regarding the food and services made available by Happy Tummy.
2. Categorization of different services and food items for the users to choose from.
3. A system component that will help the restaurant effectively interact with the customers
and vice versa. This should make the system more efficient.
4. A solution using which the customers can make requests or submit issues and the
restaurant can provide feedback quickly.
5. It will also provide order management and retrieval functionalities.

2. Development Methodology and Approach
The methodologies that can be selected for the system development have multiple research
dimensions to be studied. The method to be selected for the development may not necessarily
fulfill the scope of the proposed system. These system development methods are a set of
principles and guidelines to direct a system towards the project goal. A model that can fulfill the
main system requirement will be chosen as a development framework.
2.1 Methodology Selected
The “waterfall model” provided in the SDLC is used as a preferred methodology in this project.
The waterfall methodology for the online food-order service system is used to design the
corresponding software as this method creates different segments for different processes in the
development. After completion of each stage, the model will move forward to the next stage.
This methodology will provide a framework for tasks and process the information to generate an
efficient system for the restaurant (Bagla and Khan, 2017).
3. Functional Requirements
The functional requirements to be fulfilled by the target system should cover the following
functionalities:
a. Management of Food Orders – The order management functionality should include placing
a single or multiple food orders, order verification, additional customization of the order, and
order cancellation features. This also includes managing the order queue and segregating
different food items to be prepared.
b. Documentation & Reporting – This function will help in efficient report generation based on
different time-stamps which can be customized by the users. This reporting is mainly performed
to provide a report about some information requested by the customers.
c. Management of Restaurant Menu – The menu management function should be able to allow
the restraint officials to update and edit the menu contents and not the customers. This will
require a separate authorization for the restaurant officials. The updated menu card must be
stored in the database.

d. Billing, Tax and Payment Management – The system should be able to structure particular
information retrieved from the database and should include several payments for the users to
choose from. The functionality will also guide the restaurant about the tax and dues to be paid to
the government (R. et al., 2017).
3.1 UML – Class Diagram
Figure 1: Food-Ordering System's Class Diagram
The class diagram designed above is used to display different components of the system
designed in this project. This diagram provides a static and stable view of the application
processes and components. The main purpose of the class diagram is to help the reader in
visualizing the working and methods used in the system application. The diagram also helps in
developing the code that is executable in the system.

3.2 Database Specifications
The system used to design the database works on major tables for different entities. The structure
of tables used in the database including the datatypes and size of these data types is given below:
a. Manager
Field Type Key Size
Mgr_Name Char PRI 20
Login_Id Int 4
Password Varchar 8
Mgr_Address Varchar 30
Mgr_Email Varchar 20
b. Customer
Field Type Key Size
Cust_Name Char PRI 20
Login_Id Int 4
Password Varchar 8
Cust_Address Varchar 30
Cust_Email Varchar 20
c. Food Product
Field Type Key Size
Category Char 20
Food_Item Char PRI 20
Type Char 20

d. Payment
Field Type Key Size
Payment_ID Int PRI 8
Cust_Name Char 20
Reciept_ID Int FRN 8
Order_Amount Int 4
e. Restaurant
Field Type Key Size
Rest_ID Int PRI 8
Rest_Name Char 20
Rest_Address Varchar 8
Status Char 10
f. Order
Field Type Key Size
Order_ID Int PRI 8
Order_Time Int 8
Cust_Name Char 8
Order_Amount Int 4

3.3 Sequence Diagram
Figure 2: Sequence Diagram for Food Ordering Process
A sequence diagram is used to show and demonstrate the interaction between different entities
and systems involved in any process. It is an activity distribution diagram which divides different
activities based on the time period of activation of those activities. The sequence diagram given
above is a diagrammatical representation of different processes that combine together to
complete the online ordering of food by the customers. The diagram shows how the customer
places the order, receives confirmation from the restaurant, makes a payment, receive an
acknowledgment from the bank, and finally receives food delivered by the restaurant.

4. System Use Cases
4.1 Use Case Diagram (Complete)
The different use cases based on different actors in the system are defined as follows:
1. Manager –
 The manager handles the menu of the Happy Tummy including any editing and deletion
operations in the menu.
 Generates a report for all the activities, payment, revenue, and staff information.
 The manager can appoint new staff members in the restaurant and also manages staff
activities.
Figure 3: Use case of Manager
2. Restaurant Staff –
 The staff manages the food orders including the confirmation, placement, and deletion of
a particular order.
 Payment activities are also managed by the staff members including the receipt
generation and sometimes handles the refunds.

Figure 4: Restaurant Staff activities
3. Kitchen Staff – The kitchen staff handles the order queue and frequently updates the food
status on the system.
Figure 5: Kitchen Staff
4. Customer – The customer places an order online using the system application designed to
order food. The submit the order request which is then confirmed by the staff.
Figure 6: Customer Use Case

5. Final Use-Case Diagram
Figure 7: Use Case diagram for Online Food Ordering System
The use-case diagram given above is used to design and represent the system functionalities and
their behavior. The above diagram represents the system activities and actors involved in that
system. The use-cases are based on individual actors and their activities involved in the food
ordering process through online sources. This diagram will help in understanding the roles
played by different actors and their responsibilities in handling the system efficiently.