Building an Efficient and Reliable System for

Pizza Ordering System

Pizza Ordering System

Semester Project 2020-2024

Submitted by :-

Ammar Khawar (20-UON-

0576)
Usama Aziz (20-UON-0564)
 2

TABLE OF CONTENTS
1. Problem Statement
2. Design Approach
3. User Journey Map
4. Project Scope
a. Included in the Scope
b. Excluded from the Scope
5. Project Characteristics and Requirements
6. Project Management Deliverables
7. Project-related Deliverables and Requirements
8. Project Success Criteria
9. Scope of Work
10.User Flow Diagram
11.Location of Work
12.Period of Performance:
13.Acceptance Criteria
14.Additional Requirements
15.Introduction
16.Purpose
17.Intended Audience
18.Constraints
19.System Overview
a. Architectural Design for Mobile Pizza Ordering System
b. Architectural Styles
c. Architectural Views
d. Architectural Patterns
e. Documentation
20.Functional Requirements
21.Non-Functional Requirements
 3

Problem Statement

The Problem Statement is a clear, concise description of the challenges or issues the project is
addressing. It provides a context for why the project is essential and establishes the purpose and
direction.
With the rise in smartphone usage, consumers expect quick, convenient solutions for everyday
tasks, including ordering food. Pizza, being one of the world's most popular foods, often requires
restaurants to manage a high volume of orders, especially during peak hours. The current
methods used by many pizza houses involve phone orders or website-based systems that may not
be optimized for mobile use. This can lead to:

1. Inefficiency in Order Processing: Manual phone orders can cause errors, missed details,
or miscommunications.
2. Limited Customer Reach: Not catering to a mobile-optimized platform can alienate a
significant portion of potential customers.
3. Delayed Services: The lack of real-time updates and notifications means customers are
not informed about the status of their orders.
4. Inconsistencies in User Experience: Using a website on mobile that is not optimized
can be frustrating for users, leading to abandoned carts and loss of potential sales.

The primary problem here is the gap between the existing ordering methods of pizza houses and
the rising demand for a more efficient, mobile-optimized ordering experience.
 4

Design Approach

The process of designing the application focuses 100% on looking through the user's eyes and
their experience while using it. This will allow us to identify any issues and improve them. The
process consists of five factors that will answer the question of whether the application is
efficient and user-friendly.
The first step is to empathize with the user. Then, we must define their needs and expectations of
the application. The third step is to create several thoughtful designs and select the ideal one. The
chosen design requires prototyping, and at the end, We will conduct compatibility testing to
ensure that the application is functional.

User Journey Map

We created a user journey map to identify pain points and emotions that the customer may
experience while placing an order in the traditional way. We also asked for solutions to problems
that our application would solve.
 5

Project Scope

The Project Scope defines the boundaries of the project, detailing what will be delivered by the
project and what won't. It helps ensure that all stakeholders have a shared understanding of these
boundaries.

Included in the Scope:

 Mobile Application Development: Design and deploy an application that's compatible

with both Android and iOS platforms.
 User Interface & Experience (UI/UX): An intuitive, easy-to-navigate layout for users,
ensuring a seamless ordering process. This includes the main menu, pizza customization
options, order summary, and payment page.
 Payment Gateway Integration: Incorporate various payment methods such as
credit/debit card payments, mobile wallets, and cash on delivery option.
 Real-time Order Tracking: Once an order is placed, users should be able to track its
status – from preparation to delivery.
 Push Notifications: Alert users about promotions, order status updates, and other
relevant notifications.
 Customer Data Storage: Implement a secure system to store customer details like name,
address, phone number, and order history. This facilitates quicker future orders and
 6

personalized experiences.
 Feedback System: A feature where users can leave reviews and rate their ordering
experience.

Excluded from the Scope:

 Inventory Management: The app won't manage the inventory of ingredients or other
items in the pizza house.
 Loyalty Programs: While this can be an additional feature in future versions, the initial
version won't have loyalty program integrations.
 Employee Management: The app won't have features related to managing staff
schedules or duties.
 Augmented Reality Features: Some apps may have features where users can "see" their
pizza through AR before ordering. Such high-end features are not included in the current
scope.

Project Characteristics and Requirements:

This section defines the distinct features, functionalities, and essential conditions that the project
should embody or adhere to. It's essentially the heart of the project, determining its nature and
guiding its direction.

 Mobile-Friendly Interface:
1. Feature: An interface tailored for mobile devices.
2. Requirement: The application should resize and adapt seamlessly to various
screen sizes, from smartphones to tablets, ensuring optimal user experience.

 Flexible Payment Methods:

1. Feature: Multiple modes of payment.
2. Requirement: Integration of diverse payment gateways, ensuring smooth
transactions, and offering payment options like debit, credit card, mobile wallets,
and cash on delivery.

 Data Validation:
1. Feature: Accurate order and payment data.
2. Requirement: The app should validate all data inputs from users, such as
ensuring valid credit card numbers or phone numbers, to avoid errors or
fraudulent activities.
 7

 Push Notifications:
1. Feature: Real-time updates to users.
2. Requirement: Users should receive timely alerts for order confirmations, status
updates, and promotional offers.

 Automatic Calculations:
1. Feature: Calculation of total bill and dues.
2. Requirement: Upon adding items to the cart and applying discounts or charges,
the app should auto-calculate the final amount.

 Data Storage:
1. Feature: Safe storage of user data.
2. Requirement: User data, such as order history and payment methods, should be
securely stored, ensuring data protection and faster future transactions.

 Security Measures:
1. Feature: Protection against potential threats.
2. Requirement: The application should employ encryption methods, secure APIs,
and other best practices to safeguard against data breaches or hacks.

Project Management Deliverables

This segment defines the various outputs or products that team members are responsible for
throughout the project's life cycle. It's about managing tasks, roles, and ensuring that everyone
contributes effectively.

Detailed Project Management Deliverables for the Mobile Pizza Ordering System:

1. Usama - Mobile Architecture:

 Deliverable: A robust mobile architecture blueprint.
 Details: Usama was tasked with ensuring that the app's backbone could handle
multiple user interactions, integrate various modules seamlessly, and remain
scalable for future enhancements.

2. Ammar - Mobile UI/UX Design:

 Deliverable: Intuitive design templates for the application.
 Details: Ammar's role was pivotal in shaping how users interacted with the app.
 8

This involved creating responsive designs, wireframes, and mockups, ensuring a

pleasant user journey.

3. Zunaira - Data Validation and Storage:

 Deliverable: A reliable database and data validation system.
 Details: Zain ensured that all data entered by users was valid and stored securely.
This involved creating algorithms for data checks and setting up a robust database
system.

4. Hiba - Payment Gateway Integration:

 Deliverable: Seamless payment methods within the app.
 Details: Hbo was in charge of integrating various payment methods, ensuring
smooth transactions, and maintaining payment security.

5. Alisha - Mobile Platform Security:

 Deliverable: A comprehensive security framework.
 Details: In today's digital age, security is paramount. Lish ensured that the app
was protected from threats and vulnerabilities, overseeing encryption methods,
and monitoring potential security breaches.

Project-related Deliverables and Requirements:

These refer to the tangible outputs or products and the necessary conditions associated with the
project. While "Project Management Deliverables" focus on the management aspect, "Project-
related Deliverables" pertain to the concrete results that the project aims to produce.

For the Mobile Pizza Ordering System:

1. Application Codebase:
 Deliverable: Fully functional and clean code for the mobile application.
 Requirement: The code should follow industry best practices, be free of critical
bugs, and be well-documented for future updates.

2. User Manual:
 Deliverable: Comprehensive guide for end-users.
 Requirement: The manual should be clear, concise, and provide step-by-step
instructions on using every feature of the app.
 9

3. Testing Reports:
 Deliverable: Reports from various stages of application testing.
 Requirement: These reports should cover all testing phases, from unit to
acceptance testing, documenting any bugs found and how they were addressed.

Project Success Criteria:

This establishes the conditions under which the project is considered successful or complete.
For the Mobile Pizza Ordering System:

 Functionality: The application should perform all the tasks as outlined in the
requirements, such as order placement, payment processing, and real-time order tracking.

 User Satisfaction: High positive feedback and low error reports from end-users after the
first month of launch.

 Adherence to Timeline: The project should be completed and the application launched
within the specified timeframe.

 Budget Adherence: The entire development and launch process should remain within
the allocated budget.

Scope of Work:

This section defines the entirety of work and responsibilities required to complete the project.

For the Mobile Pizza Ordering System:

 Develop a mobile-optimized user interface.
 Integrate multiple payment gateways.
 Implement real-time order tracking.
 Ensure security protocols for user data.
 Conduct comprehensive testing before launch.

User Flow Diagram:

 10

Location of Work:

This refers to where the work or tasks will be performed.

 Development: Virtual team setup, with members working remotely from various
locations.
 Testing: In a dedicated testing environment with the necessary tools and software.
 Deployment: In the app store environments (e.g., Google Play Store, Apple App Store).

Period of Performance:

This defines the duration over which the project tasks will be performed.
 Start Date: [Specify the date]
 End Date: [Specify the date, generally after considering all phases of development,
testing, and deployment]

Acceptance Criteria
These are conditions that must be met for the product to be accepted by stakeholders.
 11

 Successful execution of all functionalities without critical errors.

 Positive user feedback after beta testing.
 No major security vulnerabilities identified post-launch.

Additional Requirements
Any other requirements not covered above.
 Maintenance: A post-launch support period of six months to address any immediate
bugs or user concerns.
 Training: Two training sessions for the client team to understand the application
management.

Introduction:

In today's digital age, the traditional methods of food ordering have been overtaken by the rising
demand for online food delivery platforms. Smartphones have become the epicenter of this
revolution, acting as gateways to a world of culinary delights delivered straight to the doorstep.
Amidst this surge, pizza, a global favorite, holds a distinct place. From a casual meal with friends
to weekend indulgences, pizzas are ordered frequently and in large volumes. However, despite
its popularity, there exists a noticeable gap in the market. Many pizza houses still rely on
outdated ordering methods, such as phone calls or non-mobile optimized websites, leading to
inefficiencies, inaccuracies, and a less-than-ideal user experience.

Purpose:

The primary objective of the "Mobile Pizza Ordering System" project is to bridge this gap. This
application aims to provide pizza enthusiasts with an optimized, user-friendly mobile platform,
offering a seamless ordering experience from pizza customization to doorstep delivery. Users
can choose their preferred pizza size, crust, toppings, accompaniments, and drinks. They can also
view their order summary, make secure payments using multiple payment methods, and track
their order in real time.

Furthermore, the system endeavors to simplify and streamline the order processing system for
pizza houses. With features like data validation, real-time updates, and secure data storage, the
platform minimizes errors, ensures prompt service, and fosters customer loyalty. The inclusion
of various payment gateways and the automated calculation of the final billing amount offers
both convenience and accuracy.

In essence, the Mobile Pizza Ordering System project is not just about building an app but
 12

revolutionizing the way people order pizzas. It’s about enhancing the user experience, fostering
efficiency for businesses, and ensuring that the next time someone craves a slice, it's just a few
taps away.

Scope:

The scope defines the boundaries of the project, what it will achieve, and the functionalities it
will encompass.

For the Mobile Pizza Ordering System:

 Design and develop a mobile-optimized interface for ordering pizzas.
 Allow customization of pizzas by size, crust, toppings, and drinks.
 Integrate multiple secure payment gateways, with real-time confirmation and invoice
generation.
 Feature real-time order tracking for users.
 Data validation for user information and payment details.
 Storage of user data and order history in a secure database.
 The system will cater only to pizzas and related items from the menu; any other cuisine
or dish outside of this is beyond the project's scope.

Intended Audience
This section identifies the primary users or beneficiaries of the system.
 End-users (Customers): Individuals who will use the app to order pizzas and related
items.
 Restaurant Staff: This includes managers to track and manage orders, chefs to view and
prepare the ordered items, and delivery personnel to view order details and delivery
locations.
 System Administrators: Technical staff responsible for app maintenance, updates, and
troubleshooting.

Constraints:
These are the limitations or restrictions the project might face.
 Limited to mobile platforms: iOS and Android.
 The app requires an active internet connection for functionality.
 Dependency on third-party payment gateways for transaction processes.
 Potential limitations in handling extremely high simultaneous user loads, depending on
the server infrastructure.
 Limited to the menu items and pricing structure provided by the restaurant at the onset of
the project.
 13

Definitions, Acronyms, and Abbreviations:

This section clarifies terms, short forms, and phrases pertinent to the restaurant domain and this
project.
 POS (Point Of Sale): A system where the customer executes the payment for goods or
services.
 UI (User Interface): The space where user interactions with the software occur.
 UX (User Experience): Refers to the overall experience a user has with the software or
system.
 API (Application Programming Interface): A set of rules and tools for building
software applications.
 CRM (Customer Relationship Management): Software that manages a company's
interactions with its customers.

System Overview:
This section offers a bird's-eye view of the entire system, its components, and its interactions.
The Mobile Pizza Ordering System is a digital platform aimed at revolutionizing the pizza
ordering experience. At its core, the system consists of:
 User Module: Allows registration, profile management, pizza customization, order
placement, and payment.
 Restaurant Management Module: Enables order management, real-time updates, menu
management, and user data analysis.
 Payment Module: Integrates various payment gateways, processes transactions, and
generates digital invoices.
 Notification Module: Sends real-time updates to users on order status, promotional
offers, and other relevant information.
 Admin Module: Facilitates overall system monitoring, updates, troubleshooting, and
user support.
Each module is interlinked, ensuring a seamless flow of data and operations across the system.
The front-end, designed with the latest UI/UX standards, ensures optimal user experience, while
the back-end, anchored by a robust database, guarantees data security, efficient data retrieval,
and system stability.

Architectural Design for Mobile Pizza Ordering System:

1. Importance of Architectural Design for the Project

 Scalability: Given the potential popularity of a pizza ordering application, scalability is
 14

essential to handle growing numbers of users and orders.

 Security: As the app deals with user information and financial transactions, a robust
architecture ensures data integrity and protection.
 Usability: A proper architectural design ensures smooth user experience and intuitive
interactions.

2. Key Concepts
 Components: Specific modules like User Registration, Order Processing, Payment
Handling, and Notification Module.
 Connectors: APIs that connect the mobile application to the back-end server, and
further, the server to the database or external services like payment gateways.

3. Architectural Styles
 Layered (or Tiered) Architecture: Given the diverse functionalities required, a three-
tier architecture would be apt:
1. Presentation Layer: The mobile app interface where users interact.
2. Business Logic Layer: Server-side logic for order processing, payment handling,
etc.
3. Data Access Layer: Interacts with the database to fetch menu items, store user
details, and manage orders.
 Microservices: Given the different functionalities (ordering, payments, user
management), it may be beneficial to split these into separate microservices. This way,
each service can be developed, scaled, and maintained independently.

4. Architectural Views
 Logical View: Encompasses the functionality presented to users, including browsing the
menu, customizing pizzas, and making payments.
 Development View: Details the software components. This will cover the various
modules of the system and their interfaces.
 Process View: Emphasizes the flow of the application. For instance, from user
registration to pizza customization, ordering, payment, and finally, notifications.
 Physical (Deployment) View: Indicates how the system is distributed across servers.
This might include a mobile app deployed to app stores, server-side components on a
cloud platform, and databases in secure data centers.

5. Architectural Patterns
 MVC (Model-View-Controller): Given its separation of concerns, MVC can be used for
both the mobile app and the server side.
 15

 Model: Represents data structures (e.g., pizza objects, user profiles).

 View: UI of the mobile app.
 Controller: Handles user interactions, directing requests and updating the view.
 Repository Pattern: This can be used to abstract the database interactions, making data
access more organized and maintainable.

6. Documentation
 Introduction: Overview of the Mobile Pizza Ordering System, emphasizing its purpose
and major functionalities.
 Architectural Decisions: Elaborate on the decision to use a layered architecture,
microservices, and the MVC pattern.
 Component Descriptions: Breakdown of each module, from user registration to
notifications, detailing their functionalities, dependencies, and interfaces.
 Connectivity: Details on how the mobile app communicates with the back-end, how
different services interact, and how data is fetched or stored in the database.
 Constraints: Restrictions like platform dependency (iOS/Android), reliance on external
payment gateways, and potential limitations regarding high simultaneous user loads.

System Features:
System features define the main functions or capabilities of a system. For the Pizza Ordering
System, the features might include:
 User Account Management: Allows users to register, log in, and manage their profiles.
 Menu Browsing: Users can view the range of pizzas, drinks, and other items on offer.
 Order Customization: Users can select pizza sizes, crusts, toppings, and other items.
 16

 Shopping Cart: Users can review their order before checkout.

 Payment Integration: A feature to handle payments, including multiple payment

methods like credit, debit, and cash-on-delivery.
 17

 Order Tracking: Post-order, users can track the progress of their pizza in real-time.
 Notifications: Users receive updates about their order status via push notifications.
 Feedback/Rating System: Post-delivery, users can rate their experience and provide
feedback.

Functional Requirements:
Functional requirements specify what the system should do. They detail the functionalities the
system must support to meet user needs. For our Pizza Ordering System:
 Registration & Authentication: Users should be able to register with an email or phone
number and create a password-protected account.
 Data Retrieval: The system should fetch and display the latest menu items from the
database.
 Order Placement: Users should be able to place an order by adding items to their cart
and checking out.
 Payment Processing: The system should securely process payments, provide a payment
confirmation, and handle payment failures.
 Order Update: Users should receive real-time updates on their order status, from
preparation to out-for-delivery.
 Feedback Collection: Post-delivery, the system should prompt users to rate and review
their order.
 18

Non-Functional Requirements:
Non-functional requirements specify how the system performs a function rather than what
functions it should perform. They often reflect the quality of the system:
 Performance: The system should load menu items quickly and process orders within a
specific time frame.
 Scalability: The system should handle spikes in user traffic, especially during peak
hours.
 Security: User data, especially payment information, should be protected. Encryption
and secure protocols should be implemented. Regular vulnerability assessments are
crucial.
 Reliability: The system should have a high uptime, with minimal downtimes or
disruptions.
 Usability: The user interface should be intuitive and user-friendly, minimizing the steps
required to place an order.
 Maintainability: The code should be modular and well-documented, allowing for easy
updates and bug fixes.
 Portability: The mobile app should work seamlessly across different devices and OS
versions.
 Responsiveness: The app should adjust to various screen sizes and orientations to ensure
a consistent user experience.
Together, system features, functional requirements, and non-functional requirements provide a
comprehensive overview of what the system does, how it should perform its functions, and the
quality standards it must meet.