Online Restaurant Management System

Submitted by

Tariq Qasim

BS-IT-20-13

2020-2024

Supervised by
Ma’am Sarah Bukhari

DEPARTMENT OF INFORMATION TECHNOLOGY

BAHAUDDIN ZAKARIYA UNIVERSITY MULTAN

PAKISTAN

1
 FINAL APPROVAL

This is to certify that we have read this report submitted by Tariq Qasim and it is our judgment that this
report is of sufficient standard to warrant its acceptance by Bahauddin Zakariya University, Multan for
the degree of BS-IT (Bachelor of Information Technology).

Committee:

1. External Examiner ______________________

2. Supervisor ________________
Ma’am Sarah
Department of Information Technology
Bahauddin Zakariya University, Multan

3. Head of Department ________________

Dr. Marouf Pasha
Department of Information Technology
Bahauddin Zakariya University, Multan

2
 DEDICATION

To my Loving Parents,
Teachers and Friends

3
 ACKNOWLEDGMENT

First of all, thanks to Allah Almighty for his utmost blessings upon me and granting me courage
and capability to complete the degree and especially this task. My sincere gratitude to my parents, family
members and friends; they prayed for me and helped me whenever I needed. I wish to express thanks to
my project supervisor for his constant motivation and valuable help during the project work. I also extend
my thanks to other faculty members of the Department of Computer Science for their cooperation
throughout my degree program.
Tariq Qasim

4
 PROJECT BRIEF
PROJECT NAME: Online Property Management System

UNDERTAKEN NAME: Anas Aslam

SUPERVISED BY: Dr. Sarah Bukhari

STARTING DATE: Sep 22, 2023

COMPLETION DATE: June 10, 2024

COMPUTER USED: Intel(R) Core (TM) i3-4010U CPU@ 1.70GHz

OPERATING SYSTEM: Microsoft Window 10

SOURCE LANGUAGE: Html, CSS, Bootstrap, PHP, JS

DBMS USED: MY SQL

TOOTS/PACKAGES: XAMPP SERVER / Sublime Text Editor /

Google Chrome (Browser) / MS Word 2019

5
Table of Content
Chapter No. 1
Introduction

1. INTRODUCTION.................................................................................................................................10
1.1. MAIN THEME..................................................................................................................................10
1.2. SCOPE OF THE PROJECT..................................................................................................................10
1.2.1 Improving Operational Efficiency:.............................................................................................10
1.2.2 Increasing Revenue Generation:...............................................................................................11
1.2.3 Providing a Seamless User Experience for Clients and Staff:....................................................11
1.2.4 Ensuring Compliance with Legal Requirements:.......................................................................11
1.3. OBJECTIVES OF THE PROJECT..........................................................................................................12
1.4. DEFINITION, ACRONYMS................................................................................................................12
1.5. CONTEXT LEVEL DIAGRAM..............................................................................................................13
1.6. SPECIFIC REQUIREMENTS...............................................................................................................14
1.6.1. ADMIN ASPECTS......................................................................................................................14
1.6.2. CLIENT ASPECTS.......................................................................................................................14
1.6.3. BROKER ASPECTS.....................................................................................................................15
1.6.4. LEGAL ADVISOR ASPECTS.........................................................................................................15
1.7. PORTABILITY...................................................................................................................................16
1.7.1. CROSS-PLATFORM COMPATIBILITY..........................................................................................16
1.7.2. MOBILE-FRIENDLY INTERFACE.................................................................................................16
1.7.3. OPERATING SYSTEM INDEPENDENCE......................................................................................16
1.8. PERFORMANCE...............................................................................................................................17
1.8.1. FAST RESPONSE TIMES............................................................................................................17
1.8.2. SCALABILITY AND LOAD BALANCING.......................................................................................17

Chapter No. 2
System Analysis

2. SYSTEM ANALYSIS..............................................................................................................................19
2.1. OVERVIEW OF EXISTING SYSTEM....................................................................................................19
2.2. CHALLENGES WITH EXISTING SYSTEM............................................................................................19
2.3. DATA GATHERING & ANALYSIS.......................................................................................................20
2.4. REQUIREMENT ANALYSIS:...............................................................................................................20

6
 2.4.1 Functional Requirements (FRs):................................................................................................20
2.4.2 Non-Functional Requirements (NFRs):......................................................................................21
2.4.3 Drawbacks of Existing System:..................................................................................................22
2.4.4 REQUIREMENTS DIAGRAM.......................................................................................................22
2.5. GANTT CHART.................................................................................................................................23
2.6. PIE DIAGRAM OF REMS...................................................................................................................24
2.7. FLOW CHARTS.................................................................................................................................24
2.7.1. BACKEND FLOW CHART...........................................................................................................24
2.7.2. FRONT-END FLOW CHART........................................................................................................25
2.8. DATA FLOW DIAGRAM (DFD):.....................................................................................................26
2.8.1. ZERO-LEVEL DATA FLOW DIAGRAM (0 LEVEL DFD)..................................................................27

Chapter No. 3
System Design

3. SYSTEM DESIGN.................................................................................................................................29
3.1. PROPOSED SYSTEM.........................................................................................................................29
3.2. OBJECTIVES OF THE PROPOSED SYSTEM........................................................................................29
3.3 SYSTEM DESIGN AND UML..............................................................................................................29
3.3.1. USE CASE DIAGRAM.................................................................................................................30
3.3.2 SEQUENCE DIAGRAM................................................................................................................31
3.3.3 CLASS DIAGRAM.......................................................................................................................33
3.4 DATABASE DESIGN...........................................................................................................................36
3.5 ENTITY RELATIONSHIP DIAGRAM (ERD)...........................................................................................37
3.6 DATABASE NORMALIZATION...........................................................................................................37
3.7 DATABASE TABLES...........................................................................................................................38

Chapter No. 4
System Development, Testing & Implementation

4. SYSTEM DEVELOPMENT, TESTING & IMPLEMENTATION...................................................................42

4.1. INTRODUCTION TO SYSTEM DEVELOPMENT..............................................................................42
4.2. TEST CASES.....................................................................................................................................43
4.2.1. ADMIN MODULE......................................................................................................................43
4.2.2. CLIENT MODULE......................................................................................................................43
4.2.3. PROPERTY MODULE.................................................................................................................44

7
 4.2.4. BOOKING MODULE..................................................................................................................44
4.2.5. PAYMENT MODULE.................................................................................................................44
4.2.6. LANDLORD MODULE................................................................................................................44
4.2.7. EMPLOYEES / BUSINESS ASSOCIATES MODULE.......................................................................44
4.2.8. PROJECT MODULE...................................................................................................................45
4.2.9. ENGINEER MODULE.................................................................................................................45
4.2.10. LEGAL ADVISOR MODULE......................................................................................................45
4.3. STATIC TESTING..............................................................................................................................46
Code Reviews:...................................................................................................................................46
Walkthroughs:...................................................................................................................................46
Inspections:.......................................................................................................................................46
4.4. IMPLEMENTATION..........................................................................................................................47
Installation and Configuration:..........................................................................................................47
Data Migration:..................................................................................................................................47
User Training:....................................................................................................................................47
Rollout and Deployment:...................................................................................................................47
Conclusion.............................................................................................................................................48
Reference..............................................................................................................................................49

8
 Chapter 01
INTRODUCTION

9
1. INTRODUCTION
ORMS is a comprehensive web-based platform designed to centralize and streamline every
aspect of restaurant management. From order processing and inventory management to customer
relationship management, ORMS encompasses a wide range of functionalities aimed at
improving operational efficiency and enhancing customer satisfaction. One of the primary goals
of ORMS is to provide restaurant managers with the tools and insights they need to effectively
oversee their operations.

1.1. MAIN THEME

The main theme of the Online Restaurant Management System (ORMS) is to leverage
technology for streamlining restaurant operations, enhancing customer experiences, and
optimizing administrative tasks. ORMS digitizes and automates processes, prioritizes customer
satisfaction through intuitive interfaces, empowers managers to focus on strategic decisions, and
provides a comprehensive digital platform adaptable to restaurants of all sizes. Overall, ORMS
aims to set new standards for excellence in the food service industry by revolutionizing how
restaurants operate and interact with their customers.

1.2. SCOPE OF THE PROJECT

This project aims to develop a comprehensive ORMS tailored to meet the needs of modern
restaurants. The scope encompasses the creation of a user-friendly interface for staff and
customers, a robust backend for managing logistics and supplies, and data analytics capabilities
to track restaurant performance. The system will be designed to support both small local bistros
and large chain restaurants, providing scalability and flexibility in its features.

1.2.1 Improving Operational Efficiency:

 Streamline processes: ORMS aims to automate and digitize various tasks such as order
processing, inventory management, and staff scheduling, reducing manual errors and
saving time.

10
  Optimize resource utilization: By providing real-time insights and analytics, ORMS
enables managers to allocate resources effectively, minimizing wastage and maximizing
productivity.

1.2.2 Increasing Revenue Generation:

 Enhanced customer experience: By providing intuitive interfaces and personalized
service options, ORMS enhances the overall dining experience for customers, leading to
increased customer satisfaction and loyalty.
 Upselling opportunities: ORMS can suggest complementary items or promotions to
customers during the ordering process, potentially increasing the average order value and
overall revenue.

1.2.3 Providing a Seamless User Experience for Clients and Staff:

 User-friendly interfaces: ORMS is designed with intuitive interfaces that are easy to
navigate for both clients placing orders and staff managing operations.
 Efficient staff management: For staff members, ORMS simplifies tasks such as order
processing, inventory management, and customer communication, reducing their
workload and improving job satisfaction.

1.2.4 Ensuring Compliance with Legal Requirements:

 Regulatory adherence: ORMS incorporates features to ensure compliance with local
regulations and industry standards regarding food safety, data privacy, and financial
transactions.
 Secure transactions: ORMS implements robust security measures to protect sensitive
information, such as customer payment details, ensuring compliance with data protection
laws and regulations.

11
1.3. OBJECTIVES OF THE PROJECT
The primary objectives of the Online Restaurant Management System include:

 Enhancing Customer Experience: Streamlining the process of reservations, ordering,

and payments to ensure a smooth and pleasant dining experience.

 Operational Efficiency: Automating routine tasks such as inventory management and

order tracking to reduce human error and operational costs.

 Data-Driven Decisions: Utilizing collected data to generate insights on customer

preferences, peak times, and menu performance, aiding in strategic decision-making.

 Scalability: Developing a system that can easily adapt to the growing needs of a
restaurant, accommodating more features and functionalities as required.

1.4. DEFINITION, ACRONYMS

The sub-section defines all terms, acronyms, and abbreviations used in this document.

Sr. Role Description

Manages the entire system, including user accounts, restaurant data,

1 Admin / Owner
menus, orders, and staff.

Represents the end-users who browse the system, view restaurant

2 Client / User
menus, place orders, and make payments.

Owners of restaurants registered in the system. They manage their

3 Restaurant Owner
restaurant's profile, menu, orders, and staff.

Employees working for restaurant owners. They manage orders, handle

4 Staff
customer queries, and assist in restaurant operations.

 ORMS (Online Restaurant Management System): A digital platform that manages all
aspects of restaurant operations, from customer interactions to backend processes.

12
  UI (User Interface): The part of the system through which users interact with the
ORMS.

 Backend: The server-side components of the ORMS that process data and perform core
functionalities.

1.5. CONTEXT LEVEL DIAGRAM

The context level diagram provides a visual representation of the ORMS, illustrating its
interfaces with external entities such as customers, staff, and suppliers. The diagram depicts the
system's primary processes, data flows, and storage elements, offering a clear overview of how
different components interact within the system. It serves as a foundational tool for
understanding the architecture and scope of the project.

Figure 1. 1 Context Diagram of OREM

13
1.6. SPECIFIC REQUIREMENTS
The successful implementation of an ORMS requires addressing specific needs across different
user roles, each with unique functions and requirements.

1.6.1. ADMIN ASPECTS

System Administration and Control:

Administrators require robust control panels for overseeing all facets of the restaurant
operations. This includes the ability to:

 Manage User Roles and Access: Admins must be able to assign roles, set permissions,
and manage access to sensitive data, ensuring that staff can only access information
pertinent to their duties.

 Update Menu Items: Admins should be able to update the menu in real-time, reflecting
changes in availability and seasonality.

 Reporting and Analytics: An integrated analytics tool that provides insights on sales
trends, customer behavior, and inventory levels is essential. For instance, a system might
track that 70% of orders are placed online during peak hours, indicating the need for a
streamlined online ordering system.

1.6.2. CLIENT ASPECTS

Customer Interaction and Engagement:

For clients, or restaurant customers, the system should offer:

 User-Friendly Interface: An intuitive online ordering interface that reduces the average
order placement time, which is crucial during busy hours.

 Customization Options: Features that allow customers to customize their meals, such as
adding or removing ingredients, which increases customer satisfaction and can
potentially increase the average order value by 20%.
14
  Feedback and Support: Easy access to leave feedback about their dining experience,
and a quick response feature for resolving any issues experienced during the order
process.

1.6.3. BROKER ASPECTS

Supply Chain Management:

Brokers, or suppliers, need a streamlined process for inventory management and order
fulfillment, which includes:

 Automated Inventory Updates: Automatic updates when stock levels are low, which
helps in maintaining a 30% reduction in wasted ingredients.

 Order Forecasting Tools: Advanced forecasting to predict restaurant needs based on

historical data, improving order accuracy and reducing excess inventory costs by up to
25%.

 Real-Time Communication: Facilities for real-time communication with the restaurant

to update delivery statuses and manage supply chain disruptions efficiently.

1.6.4. LEGAL ADVISOR ASPECTS

Compliance and Regulation:

Legal advisors focus on ensuring that the system complies with all relevant laws and
regulations, such as:

 Data Privacy Laws: Ensuring the system adheres to data protection regulations like
GDPR or CCPA, which mandate the safeguarding of customer information.

 Employment Laws: Integration of features that help manage staff hours and payroll in
compliance with local labor laws, such as overtime calculations and minimum wage
compliance.

15
  Health and Safety Standards: Features that support the tracking of health and safety
compliance in food storage and handling, critical for avoiding legal issues and
maintaining public trust.

1.7. PORTABILITY
Portability is crucial for the widespread adoption and efficient functionality of an Online
Restaurant Management System (ORMS). Ensuring that the system is accessible across different
platforms and devices enhances user experience and operational flexibility.

1.7.1. CROSS-PLATFORM COMPATIBILITY

The ORMS must function seamlessly across various platforms such as Windows, macOS, and
Linux. This ensures that every stakeholder, from restaurant staff to management, can access the
system regardless of their preferred technology. Statistics show that approximately 75% of
businesses prioritize cross-platform capability to reach a broader audience and ensure uniform
service delivery.

1.7.2. MOBILE-FRIENDLY INTERFACE

With over 50% of global website traffic coming from mobile devices, a mobile-friendly interface
is essential. The ORMS should feature a responsive design that adjusts to different screen sizes
and resolutions, providing an optimal user experience on both smartphones and tablets. This not
only enhances customer interaction by allowing easy menu access and order placement on the go
but also enables staff to manage operations directly from mobile devices, increasing efficiency
and response times.

1.7.3. OPERATING SYSTEM INDEPENDENCE

Operating system independence ensures that the ORMS can run effectively regardless of the
underlying OS. This is achieved through the use of web-based technologies such as HTML5,

16
CSS3, and JavaScript, which are universally supported by modern web browsers. This approach
also simplifies updates and maintenance, as changes can be rolled out simultaneously across all
platforms without compatibility issues. Additionally, utilizing cloud-based servers for data
handling and storage can further enhance the system’s independence and scalability, reducing
operational costs by up to 40% and improving data recovery times by 50%.

1.8. PERFORMANCE
Performance is a critical component of an Online Restaurant Management System (ORMS),
impacting both user satisfaction and operational efficiency. High performance in terms of
response times and scalability ensures that the system can handle peak loads effectively while
providing a seamless experience for users.

1.8.1. FAST RESPONSE TIMES

Fast response times are essential for maintaining a high level of user satisfaction. In the context
of an ORMS, this means ensuring that web pages load within 2 seconds, as studies show that
53% of mobile users abandon sites that take longer than 3 seconds to load. Achieving this
requires optimizing server responses and streamlining database queries to minimize delays.
Effective caching strategies can reduce load times by storing frequently requested data, thus
improving overall speed by up to 60%. Moreover, using a Content Delivery Network (CDN) can
decrease load times by distributing content closer to where users access it, enhancing
responsiveness across diverse geographic locations.

1.8.2. SCALABILITY AND LOAD BALANCING

Scalability is crucial for an ORMS to accommodate growth in user numbers and data volume
without degradation in performance. Implementing a scalable architecture involves using elastic
cloud services that can dynamically adjust resources based on real-time demand. This flexibility
allows the system to handle sudden spikes in traffic, such as those experienced during special
promotions or peak dining hours, without affecting user experience.

17
Load balancing is another key aspect, distributing client requests efficiently across multiple
servers. This not only maximizes resource use but also ensures redundancy, reducing the risk of
downtime. For instance, load balancing can help handle up to 1,000 simultaneous user requests
without performance loss, critical during peak restaurant hours. Moreover, modern load
balancers can direct traffic to servers based on the current load, optimizing response times and
resource usage.

18
 Chapter 02

SYSTEM ANALYSIS

19
2. SYSTEM ANALYSIS
In the modern era, where technology is reshaping various industries, including the food service
sector, the need for efficient and streamlined management systems in restaurants has become
more pronounced. This section aims to delve into a comprehensive analysis of an Online
Restaurant Management System (ORMS). We will explore the existing landscape, identify
challenges inherent in conventional systems, discuss techniques for data gathering and analysis,
and meticulously outline both functional and non-functional requirements. Additionally, we'll
touch upon various visualization tools like Gantt charts, pie diagrams, flowcharts, and data flow
diagrams that aid in understanding and planning.

2.1. OVERVIEW OF EXISTING SYSTEM

Traditional restaurant management systems predominantly rely on manual processes for order
taking, inventory management, and customer relationship management. These systems are often
characterized by their labor-intensive nature, susceptibility to errors, and limited accessibility to
real-time data. The absence of integration among various functions further compounds
operational challenges, potentially hindering both efficiency and customer satisfaction.

2.2. CHALLENGES WITH EXISTING SYSTEM

The challenges inherent in traditional restaurant management systems include:
 Manual Processes: Order taking, inventory tracking, and employee scheduling are
primarily performed manually, leading to inefficiencies and errors.
 Limited Accessibility: Data is typically stored locally, restricting accessibility and real-
time insights for management.
 Lack of Integration: Functions like inventory management, order processing, and
customer relationship management often operate in silos, resulting in disjointed
operations and inefficiencies.

20
2.3. DATA GATHERING & ANALYSIS
Understanding the limitations of the existing system and gathering requirements effectively
necessitates the use of various data gathering techniques, such as interviews, surveys, and
observation. Through meticulous analysis of gathered data, stakeholders can identify pain points,
user preferences, and system requirements crucial for designing a robust solution.

2.4. REQUIREMENT ANALYSIS:

There are two major types of requirements for the proposed system

1. Functional Requirements (FRs)

2. Non-Functional Requirements (NFRs)

These requirements should be the following

2.4.1 Functional Requirements (FRs):

1. User Authentication and Authorization:
 Users should be able to register and log in to the system securely.
 Different user roles (admin, client, landlord, etc.) should have different levels of
access to system functionalities.
2. Menu Management:
 Admins should be able to add, update, and delete menu items.
 Menu items should be categorized by type (appetizers, main courses, desserts,
etc.).
 Clients should be able to browse the menu, view item details, and add items to
their order.
3. Order Management:
 Clients should be able to place orders for food items.
 Clients should be able to specify customization options (e.g., toppings, cooking
preferences) for each item.
 Admins should be able to view and manage incoming orders, including order
status updates and order history.
4. Inventory Management:
21
  Admins should be able to track inventory levels for each menu item.
 Inventory levels should be automatically updated when orders are placed.
 Admins should receive notifications for low-stock items and be able to replenish
inventory as needed.
5. Booking Management:
 Clients should be able to search for available properties for booking (e.g., tables,
event spaces).
 Clients should be able to book properties for specific dates and times.
 Landlords should be able to manage property listings, availability, and booking
requests.
6. Payment Processing:
 Clients should be able to make secure payments for their orders.
 Multiple payment methods (credit/debit cards, mobile wallets, etc.) should be
supported.
 Payment processing should be seamless and integrated with the ordering system.

2.4.2 Non-Functional Requirements (NFRs):

1. Performance:
 The system should be able to handle a large number of concurrent users during
peak hours without significant performance degradation.
 Response times for key functionalities (e.g., order placement, inventory updates)
should be minimal.
2. Reliability:
 The system should be highly reliable, with minimal downtime and data loss.
 Backup and recovery mechanisms should be in place to ensure data integrity in
case of system failures.
3. Security:
 User authentication and data transmission should be encrypted to prevent
unauthorized access and data breaches.
 Payment processing should comply with industry security standards (e.g., PCI
DSS) to protect financial transactions.

22
 4. Scalability:
 The system should be able to scale horizontally and vertically to accommodate
growth in user traffic and data volume.
 Scalability should be achieved through load balancing, database sharding, and
other techniques.
5. Usability:
 The user interface should be intuitive and easy to navigate for both clients and
admins.
 Help documentation and tooltips should be provided to assist users in using the
system effectively.
6. Compatibility:
 The system should be compatible with a wide range of devices and web browsers
to ensure accessibility for users.
 Compatibility testing should be conducted to verify the system's performance
across different platforms.

2.4.3 Drawbacks of Existing System:

Drawbacks are problem or weakness of the existing system. These are the following drawback
which are exit in examination system

1. Time Consuming and Tedious: Since exam are conduct by human resources so it is
very slow and tedious.
2. Huge Investment in Human Resources: As paper conduct manually so a lot of human
resources is required for conducting exam.
3. Less Reliable: Manual Exam system is less reliable as Exam may not performed with
precision each time because of human errors.

2.4.4 REQUIREMENTS DIAGRAM

A requirements diagram serves as a visual representation of the relationships between different
requirements, ensuring comprehensive coverage of system functionalities and constraints,
thereby guiding the development process effectively.

23
2.5. GANTT CHART
A Gantt chart is a valuable project management tool that provides a visual representation of a
project schedule. By depicting tasks, their start and end dates, and dependencies, Gantt charts aid
in project planning, resource allocation, and progress monitoring, thereby ensuring timely
completion of the project.

24
2.6. PIE DIAGRAM OF REMS
A pie diagram, or pie chart, can be used to visually represent various aspects of the Online
Restaurant Management System, such as the distribution of orders by category, revenue sources,
or customer demographics. This graphical representation helps stakeholders gain insights into
key metrics and trends, facilitating informed decision-making.

2.7. FLOW CHARTS

Flowcharts are invaluable tools for visualizing and understanding the flow of processes within
the system. They help stakeholders comprehend the sequence of actions, decision points, and
data flows involved in various operations.

2.7.1. BACKEND FLOW CHART

A backend flow chart delineates the processes and data flow within the system's backend
infrastructure. It illustrates server-side operations such as order processing, inventory
management, and database interactions, providing stakeholders with a clear understanding of the
system's architecture and functionality.

25
2.7.2. FRONT-END FLOW CHART
A front-end flow chart illustrates the user interaction flow, detailing the steps from order
placement to payment processing on the customer-facing interface. By visualizing the user
journey, stakeholders can identify potential bottlenecks and areas for improvement in the user
experience, thereby enhancing customer satisfaction.

26
2.8. DATA FLOW DIAGRAM (DFD):
Data Flow Diagrams provide a graphical representation of the flow of data within the system,
illustrating processes, data stores, and data movement. They help stakeholders understand the
interactions between various components of the system and identify opportunities for
optimization and refinement.

27
2.8.1. ZERO-LEVEL DATA FLOW DIAGRAM (0 LEVEL DFD)
The zero-level DFD provides a high-level overview of the system, depicting major processes and
data sources without delving into finer details. It serves as a foundation for developing more
detailed DFDs for individual system components, thereby ensuring a structured and systematic
approach to system design and development.

28
 Chapter 03

SYSTEM DESIGN

29
3. SYSTEM DESIGN
System design is a critical phase in the development of any software system, including an Online
Restaurant Management System (ORMS). This section outlines the proposed system
architecture, objectives, and design using Unified Modeling Language (UML). It further delves
into database design, including entity-relationship diagrams (ERD), normalization, and database
tables.

3.1. PROPOSED SYSTEM

The proposed system aims to revolutionize restaurant management by providing an online
platform that streamlines operations, enhances customer experience, and facilitates efficient
management of resources. Leveraging technology, the system integrates order management,
inventory control, payment processing, and customer relationship management into a cohesive
and user-friendly interface.

3.2. OBJECTIVES OF THE PROPOSED SYSTEM

The objectives of the proposed system include:
 Automating order processing and inventory management to improve operational
efficiency.
 Enhancing customer satisfaction through seamless online ordering and payment
processing.
 Providing real-time insights through comprehensive reporting and analytics.
 Streamlining administrative tasks such as staff management and menu updates.
 Ensuring data security and compliance with regulatory requirements.

3.3 SYSTEM DESIGN AND UML

Unified Modeling Language (UML) is a standardized modeling language used to visualize,
specify, construct, and document software-intensive systems. It provides a set of diagrams to

30
represent various aspects of system design, including use case diagrams, sequence diagrams, and
class diagrams.

3.3.1. USE CASE DIAGRAM

A use case diagram illustrates the interactions between users and the system, depicting various
use cases and actors involved.

31
3.3.2 SEQUENCE DIAGRAM
Sequence diagrams depict the interactions between objects or components within the system over
time, showcasing the flow of messages and responses.

3.3.2.1. Sequence diagrams for REMS

Sequence diagrams for the Online Restaurant Management System depict the flow of
interactions between different system components, such as users, orders, inventory, and payment
processing.

32
3.3.2.2. Sequence diagrams for Admin-User Interaction in REMS
These diagrams detail the interactions between administrators and users, including tasks such as
user management, menu updates, and reporting.

3.3.2.3. Sequence diagrams for Food search by client/user in REMS

These diagrams illustrate the steps involved in property search by clients or users, including
search criteria, filtering options, and result presentation.

33
3.3.2.4. Sequence diagrams for Ordering Food by client/user in REMS
These diagrams outline the process of ordering food by clients or users, including reservation
requests, availability checks, and confirmation.

3.3.3 CLASS DIAGRAM

Class diagrams provide a structural view of the system, illustrating classes, attributes, methods,
and relationships between objects.

34
3.3.3.1. Class Diagram for REMS
This diagram outlines the main classes and their relationships within the Online Restaurant
Management System, including users, orders, inventory items, and payment transactions.

35
3.3.3.2. Class Diagram for client-restaurant relation
This diagram illustrates the relationship between clients and properties, detailing attributes such
as property type, location, and availability.

36
3.3.3.3. Class Diagram for restaurant and menu
This diagram showcases the relationships between users, properties, booking reservations, and
landlords, defining attributes and associations between them.

3.4 DATABASE DESIGN

Database design plays a pivotal role in the development of any software system, including an
Online Restaurant Management System (ORMS). It involves structuring the database to
efficiently store, retrieve, and manage data, ensuring data integrity, security, and performance.
This section outlines the database design process, including entity-relationship diagrams (ERD),
normalization, and database tables.

3.5 ENTITY RELATIONSHIP DIAGRAM (ERD)

An Entity-Relationship Diagram (ERD) visually represents the entities, attributes, and
relationships within the database. It provides a clear depiction of the data model, facilitating
37
understanding and communication among stakeholders. In the context of an ORMS, the ERD
would include entities such as users, orders, inventory items, payment transactions, and their
respective attributes and relationships.

3.6 DATABASE NORMALIZATION

Database normalization is the process of organizing data in a relational database to reduce
redundancy and dependency, thereby improving data integrity and efficiency. The normalization
process involves decomposing large tables into smaller, related tables and applying
normalization rules to ensure each table serves a single purpose and avoids data anomalies such
as insertion, update, and deletion anomalies.

3.7 DATABASE TABLES

Database tables represent entities and their attributes within the relational database management
system. Each table corresponds to an entity in the ERD, with columns representing attributes and

38
rows representing individual instances of the entity. For an ORMS, typical database tables would
include tables for users (e.g., customers, staff, administrators), orders, inventory items, payments,
menus, and so on.
In the context of an ORMS, the database tables would be designed to efficiently store and
manage various aspects of restaurant operations, such as customer information, order details,
inventory levels, menu items, pricing, and transaction history. Each table would be appropriately
normalized to minimize redundancy and dependency, ensuring data integrity and facilitating
efficient data retrieval and manipulation.

Admin Registration Table:

Column Name Data Type Constraint

id INT PRIMARY KEY

name VARCHAR(250) NOT NULL

email VARCHAR(50) NOT NULL

password VARCHAR(250) NOT NULL

created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP

Admin Table:

Column Name Data Type Constraint

id INT PRIMARY KEY

name VARCHAR(250) NOT NULL

email VARCHAR(50) NOT NULL

password VARCHAR(250) NOT NULL

39
User Table:

Column Name Data Type Constraint

id INT PRIMARY KEY

name VARCHAR(50) NOT NULL

email VARCHAR(50) NOT NULL

password VARCHAR(100) NOT NULL

timestamp VARCHAR(100) NOT NULL

Categories Table:

Column Name Data Type Constraint

id int(11) NOT NULL, AUTO_INCREMENT, PRIMARY KEY

name varchar(250) NOT NULL

short_desc varchar(250) NOT NULL

long_desc varchar(500) NOT NULL

Food Table:

Column Name Data Type Constraint

id int(11) NOT NULL, AUTO_INCREMENT, PRIMARY KEY

cat_id int(10) NOT NULL

fname varchar(50) NOT NULL

40
description varchar(250) NOT NULL

Orders Table:

Column Name Data Type Constraint

id int(11) NOT NULL, AUTO_INCREMENT, PRIMARY KEY

order_id varchar(20) NOT NULL

user_id varchar(10) NOT NULL

food_id varchar(10) NOT NULL

user_name varchar(100) NOT NULL

timestamp varchar(50) NOT NULL

41
 Chapter 04

SYSTEM DEVELOPMENT, TESTING &

IMPLEMENTATION

42
4. SYSTEM DEVELOPMENT, TESTING & IMPLEMENTATION
In the journey of developing an Online Restaurant Management System (ORMS), understanding
the system development process, meticulous testing, and smooth implementation are paramount.
This section navigates through the introduction to system development, tool and language
selection, and highlights the importance of HTML5, CSS, JavaScript, PHP, MySQL, and
XAMPP Server in building a robust ORMS.

4.1. INTRODUCTION TO SYSTEM DEVELOPMENT

System development is a structured process that involves designing, coding, testing, and
deploying software systems. It ensures that the developed system meets user requirements and
functions effectively.
4.1.1. TOOL AND LANGUAGE SELECTION
Selecting the right tools and programming languages is crucial for the success of any software
project. The following tools and languages are commonly used in web development:
4.1.1.1. HTML5 (Hypertext Markup Language 5)
HTML5 is the latest version of the HTML standard. It provides semantic markup tags for
structuring web content, making it easier for search engines to index and for developers to create
modern web applications.
4.1.1.2. CSS (Cascading Style Sheets)

CSS is used to style HTML elements, controlling the layout, colors, fonts, and other visual
aspects of a web page. It enhances the user experience by making web pages visually appealing
and responsive.
4.1.1.3. JavaScript
JavaScript is a versatile programming language that adds interactivity and dynamic behavior to
web pages. It enables developers to create interactive forms, manipulate DOM elements, and
handle user events, enhancing the functionality of web applications.
4.1.1.4. PHP

43
PHP is a server-side scripting language widely used for web development. It allows developers
to create dynamic web pages, interact with databases, handle form data, and perform various
server-side tasks.
4.1.1.5. MySQL

MySQL is a popular open-source relational database management system (RDBMS). It provides

a robust and scalable platform for storing and managing structured data, making it ideal for web
applications that require data persistence.
4.1.1.6. XAMPP Server
XAMPP is a free and open-source cross-platform web server solution stack package developed
by Apache Friends. It includes Apache HTTP Server, MariaDB (MySQL), PHP, and Perl
interpreters, making it easy to set up a local development environment for PHP-based web
applications like ORMS.

4.2. TEST CASES

Testing is a critical aspect of software development, ensuring that the system functions as
expected and meets the requirements of its users. Test cases are designed to validate different
aspects of the system's functionality and behavior. Below are test cases categorized based on
different modules of the Online Restaurant Management System (ORMS):

4.2.1. ADMIN MODULE

1. Test Case: Verify that the admin can log in to the system with valid credentials.
2. Test Case: Verify that the admin can add new menu items with all required details.
3. Test Case: Verify that the admin can update existing menu items with new information.
4. Test Case: Verify that the admin can delete menu items that are no longer available.
5. Test Case: Verify that the admin can generate sales reports for a specified period.

4.2.2. CLIENT MODULE

1. Test Case: Verify that the client can register for an account with valid details.
2. Test Case: Verify that the client can log in to the system with valid credentials.
3. Test Case: Verify that the client can browse the menu and add items to the cart.
4. Test Case: Verify that the client can place an order with the selected items in the cart.

44
 5. Test Case: Verify that the client can track the status of their orders.

4.2.3. PROPERTY MODULE

1. Test Case: Verify that properties are displayed accurately with all relevant details.
2. Test Case: Verify that users can search for properties based on specific criteria.
3. Test Case: Verify that users can filter search results by various parameters.
4. Test Case: Verify that users can view detailed information about a specific property.
5. Test Case: Verify that users can book a property for a specified date range.

4.2.4. BOOKING MODULE

1. Test Case: Verify that users can view their booking history.
2. Test Case: Verify that users receive confirmation emails after making a booking.
3. Test Case: Verify that users can cancel bookings within the allowed time frame.
4. Test Case: Verify that users receive refunds for canceled bookings.
5. Test Case: Verify that the system updates property availability after a booking is made.

4.2.5. PAYMENT MODULE

1. Test Case: Verify that users can choose from multiple payment methods.
2. Test Case: Verify that the payment gateway securely processes transactions.
3. Test Case: Verify that users receive payment confirmation emails after successful
transactions.
4. Test Case: Verify that failed transactions are handled appropriately, with clear error
messages.
5. Test Case: Verify that users can view their payment history.

4.2.6. LANDLORD MODULE

1. Test Case: Verify that landlords can register for an account with valid details.
2. Test Case: Verify that landlords can log in to the system with valid credentials.
3. Test Case: Verify that landlords can add properties to the system with all required details.
4. Test Case: Verify that landlords can update property information as needed.
5. Test Case: Verify that landlords can view booking requests and confirm or reject them.

45
4.2.7. EMPLOYEES / BUSINESS ASSOCIATES MODULE
1. Test Case: Verify that employees can log in to the system with valid credentials.
2. Test Case: Verify that employees can view their assigned tasks and deadlines.
3. Test Case: Verify that employees can update task statuses and provide progress updates.
4. Test Case: Verify that business associates can register for an account with valid details.
5. Test Case: Verify that business associates can log in to the system with valid credentials.

4.2.8. PROJECT MODULE

1. Test Case: Verify that project managers can create new projects with all required details.
2. Test Case: Verify that project managers can assign tasks to team members and set
deadlines.
3. Test Case: Verify that project managers can track project progress and milestones.
4. Test Case: Verify that team members receive notifications for new tasks and updates.
5. Test Case: Verify that project managers can generate project reports for stakeholders.

4.2.9. ENGINEER MODULE

1. Test Case: Verify that engineers can log in to the system with valid credentials.
2. Test Case: Verify that engineers can view their assigned tasks and project details.
3. Test Case: Verify that engineers can update task statuses and provide progress updates.
4. Test Case: Verify that engineers can communicate with team members through the
system.
5. Test Case: Verify that engineers can access project documentation and resources.

4.2.10. LEGAL ADVISOR MODULE

1. Test Case: Verify that legal advisors can log in to the system with valid credentials.
2. Test Case: Verify that legal advisors can access legal documents and templates.
3. Test Case: Verify that legal advisors can provide legal advice and recommendations.
4. Test Case: Verify that legal advisors can communicate with clients and other team
members.
5. Test Case: Verify that legal advisors can generate legal reports and documents as needed.

46
4.3. STATIC TESTING
Static testing involves reviewing and analyzing software artifacts without executing the code. It
aims to identify defects, errors, and inconsistencies early in the development process, thereby
reducing the cost and effort of fixing them later. Common techniques used in static testing
include code reviews, walkthroughs, and inspections.

Code Reviews:
 Objective: To identify code defects, ensure adherence to coding standards, and promote
code quality.
 Process: Peer developers review the code line by line, looking for errors, inefficiencies,
and opportunities for improvement.
 Benefits: Early detection of defects, knowledge sharing among team members, and
improved code quality and maintainability.

Walkthroughs:
 Objective: To gain an understanding of the software requirements, design, and code
implementation.
 Process: The development team walks through the software artifacts, such as
requirements documents, design diagrams, and code files, discussing their features,
functionality, and potential issues.
 Benefits: Improved clarity and understanding of the system, identification of ambiguities
and inconsistencies, and alignment of stakeholders' expectations.

Inspections:
 Objective: To systematically examine software artifacts for defects, deviations from
standards, and opportunities for improvement.
 Process: A formal inspection meeting is conducted with a defined agenda and roles,
where team members thoroughly examine the artifacts, document defects, and propose
corrective actions.
 Benefits: Rigorous defect detection, adherence to quality standards, and continuous
process improvement.

47
4.4. IMPLEMENTATION
Implementation is the process of deploying the developed system into the production
environment, making it accessible to users. It involves several steps, including installation,
configuration, data migration, and user training. A well-planned implementation strategy ensures
a smooth transition from development to production and minimizes disruptions to business
operations.

Installation and Configuration:

 Objective: To set up the necessary hardware and software components required to run the
system.
 Process: Install the ORMS software on the production servers, configure settings
according to the deployment environment, and ensure compatibility with existing
infrastructure.
 Considerations: Hardware requirements, software dependencies, security configurations,
and scalability options.

Data Migration:
 Objective: To transfer existing data from legacy systems or previous versions of the
software to the new system.
 Process: Extract data from the source systems, transform it as needed, and load it into the
target database of the ORMS.
 Considerations: Data integrity, accuracy, completeness, data mapping, and data
validation.

User Training:
 Objective: To familiarize users with the features, functionality, and usage of the ORMS.
 Process: Conduct training sessions for administrators, staff members, and end-users,
covering topics such as system navigation, order processing, inventory management, and
reporting.
 Considerations: Tailored training materials, hands-on exercises, ongoing support, and
feedback mechanisms.

48
Rollout and Deployment:
 Objective: To make the ORMS available to users and ensure a seamless transition from
the old system to the new one.
 Process: Gradually deploy the ORMS to different user groups or locations, monitor
system performance and user feedback, and address any issues or concerns promptly.
 Considerations: Phased rollout, contingency plans, communication strategies, and user
acceptance testing.

Conclusion

In conclusion, the Online Restaurant Management System (ORMS) presented in this

project stands as a testament to the convergence of technological innovation and culinary
excellence. Through an exhaustive exploration of contemporary advancements in information
technology and the intricacies of the hospitality industry, this endeavor has successfully
amalgamated these realms to redefine the operational landscape of restaurants in the digital age.

The primary objective of this project was to design and implement a comprehensive system that
streamlines the myriad functions of a restaurant, encompassing aspects ranging from inventory
management to customer engagement, in a seamless online platform. Leveraging cutting-edge
technologies such as cloud computing, data analytics, and user-centric design principles, the
ORMS has demonstrated unparalleled efficiency and effectiveness in addressing the multifaceted
challenges faced by restaurant owners and managers.

One of the most significant contributions of this project lies in its emphasis on enhancing
operational efficiency and optimizing resource utilization. By automating routine tasks,
optimizing inventory levels, and providing real-time insights into key performance indicators,
the ORMS empowers restaurant personnel to focus their efforts on delivering exceptional dining
experiences to patrons, thereby fostering customer satisfaction and loyalty.

Furthermore, the integration of customer relationship management (CRM) functionalities within

the ORMS represents a paradigm shift in the way restaurants interact with their clientele.
Through personalized recommendations, targeted promotions, and seamless communication

49
channels, the system facilitates deeper engagement with customers, fostering lasting
relationships that extend beyond individual transactions.

Moreover, the scalability and flexibility inherent in the design of the ORMS ensure its
adaptability to the evolving needs and dynamics of the restaurant industry. Whether it be a small-
scale bistro or a large-scale franchise, the modular architecture of the system enables seamless
customization and expansion, thereby accommodating the diverse requirements of
establishments across the culinary spectrum.

Nevertheless, it is important to acknowledge that the success of the ORMS is contingent upon
the collaborative efforts of stakeholders at various levels, including restaurant owners, managers,
staff, and customers. As such, ongoing support, feedback, and iteration are essential to the
continued evolution and refinement of the system, ensuring its relevance and efficacy in an ever-
changing landscape.

In essence, the Online Restaurant Management System encapsulates the fusion of tradition and
innovation, craftsmanship and technology, to usher in a new era of culinary excellence and
operational excellence. As restaurants continue to adapt to the digital paradigm, the ORMS
serves as a beacon of inspiration and a blueprint for the transformative potential of technology in
redefining the gastronomic experience.

Reference

50