PIZZA ORDERING SYSTEM

Table of Contents
Background ................................................................................................................................................... 2
Feasibility Study ............................................................................................................................................ 2
Requirements: .............................................................................................................................................. 6
Logical Design ............................................................................................................................................... 9
Trace-ability Matrix .................................................................................................................................... 14
Background
Computers have become part of the life for accessing almost any kind of information. Life in the 21 st
century is full of technological advancement and in this technological age it is very difficult for any
organization to survive without utilizing technology. The World Wide Web contributes greatly to the
creation of an ever-increasing global information database. It could also be used as a mechanism to
share information within an enterprise.

In today’s age of fast food and take out, many restaurants have chosen to focus on quick preparation
and speedy delivery of orders rather than offering a rich dining experience. Until very recently, all of
these delivery orders were placed over the phone, but there are many disadvantages to this system,
including the inconvenience of the customer needing to have a physical copy of the menu, lack of a
visual confirmation that the order was placed correctly, and the necessity for the restaurant to have an
employee answering the phone and taking orders. What I propose is an online pizza ordering system,
which is a technique of ordering pizza online applicable in any pizza shops. The main advantage of my
system is that it greatly simplifies the ordering process for both the customer and the restaurant. When
the customer visits the ordering webpage, they are presented with an interactive and up-to-date menu,
complete with all available options and dynamically adjusting prices based on the selected options. After
making a selection, the item is then added to their order, which the customer can review the details of
at any time before checking out. This provides instant visual confirmation of what was selected and
ensures that items in the order are, in fact, what was intended.

This system also greatly lightens the load on the restaurant’s end, as the entire process of taking orders
is automated. Once an order is placed on the webpage, it is entered into the database and then
retrieved, in pretty much real-time, by a desktop application on the restaurant ‘send. Within this
application, all items in the order are displayed, along with their corresponding options and delivery
details, in a concise and easy to read manner. This allows restaurant employees to quickly go through
the orders as they are placed and produce the necessary items with minimal delays and confusion

Feasibility Study
General Requirements Feasibility Report

 The new system will be cost effective

 The new system will improve productivity and service and service.
 The new system will enhance user interface.
 The new system will improve information presentation and durability.
 The new system will upgrade systems reliability, availability and flexibility.
 The new system will address human factors for better and uses acceptance

Website Goal

The website is going to be designed for a Pizza restaurant. The customer will expect that this website is
able to find a reactive and dynamic website for Pizza shops that include images of types of pizza with
descriptions of what the food consists of. In addition to this, a basket where the customers will be able
to put items that can be updated and added to it or remove items from the basket, a about us page, and
links for the pizza shop. The website aims to sell pizza products through the website of the pizza shop
where customers can place an order from PC and phones. In addition to this another goal is to make the
website User friendly and Responsive.

Statement of the Problem

How to develop an online pizza ordering system to enable customers place orders online from the comfort
of their location with just a click. The challenges encountered by the existing system serve as a major
drawback to the realization of efficiency and customer satisfaction. The experience of ordering in food
restaurants is not pleasant for the customers. Customers will have to make long queues before placing
their orders especially during peak hours and then the ordering staff will record customer orders. Having
placed their order, the customer must then wait near the counter until their order is ready for collection.
The other problem in the food service industry is that restaurants are not realizing the efficiencies that
would result from better application of technology in their daily operations. Fast food business in a very
competitive business and one way to stand out from competitors is through improving the business
process where business process automation can assist business improvement. The other problem with
the current system is that the customers are not able to see the ingredients of the meals before they place
their order and also they only have to pay for their order online

Objectives of the study

Main Objective

The general objective of the study is to help customers in ordering custom pizzas. So the customer will
pick exactly the things which he/she wants in their pizza. This will surely enhance the image of the
pizzeria and customer satisfaction will be more.

Our website will be available to view 24/7 but you can only order from it from 10 AM to 12 PM. The
website can be viewed anywhere in the world, but the customers can only order from the website if
they are living in the following cities in Jordan: Amman, Aqaba, and Zarqa.

Specific Objectives

The study has the following specific objectives:

Better Knowledge:

This system will provide a customer with all the details of his order before making an order. This
confirmation will help customers to check the items ordered with their prices.

Know Delivery Time

This system will show the time by which the order will be delivered to the customer. For pick-ups
customers can fix the time by which they will pick their order.

Reduce Paper Work

As most of the things will be performed online, it will reduce the usage of paper for the pizzeria.

Improves Efficiency
This system will make things easier for staff as the whole ordering process will be done by customers
only.

Project/Product Scope:

Pizza ordering system will be a web based application whose main language of programming will be
PHP. Its main aim is to simplify and improve the efficiency of the ordering process for both customer and
pizza shop owners, minimize manual data entry and ensure data accuracy and security during order
placement process. Customers will also be able to view product menus and their ingredients and be able
to have a visual confirmation that the order was place correctly.

Project/Product Costing

A metric is some measurement we can make of a product or process in the overall development
process. Metrics are split into two broad categories:

 Knowledge oriented metrics: these are oriented to tracking the process to evaluate, predict or
monitor some part of the process.

 Achievement oriented metrics: these are often oriented to measuring some product aspect, often
related to some overall measure of quality of the product. Most of the work in the cost estimation field
has focused on algorithmic cost modeling. In this process costs are analyzed using mathematical
formulas linking costs or inputs with metrics to produce an estimated output. The formulae used in a
formal model arise from the analysis of historical data. The accuracy of the model can be improved by
calibrating the model to your specific development environment, which basically involves adjusting the
weightings of the metrics. Total Cost of our project is estimated by using COCOMO’81, therefore we did
not use project cost estimation by functional Point Analysis and Activity Based Costing.

Risk List:

 If any team member cannot continue with this project there is no substitute of it, because it take more
development time to start from beginning.

 Development time if less then pressure would be high.

 Low motivation and moral support.

 Detail reporting would take more development time.

 Adding extra functionalities increase cost of project.

 Team members needs extra time to learn unfamiliar tools or technique.

 Development of extra functionalities that are not required will expand the schedule.

 Development team may deliver components of low quality and more time will require to improve
quality.

 Lack of experiences in project management, especially in testing, risk management and changes
management in existing team.
  All team member need time for preparation of midterm, final and other work.

 Resources are not enough.

Gantt chart:

Modules of online pizza ordering system:

There are 3 modules in this system. These modules are:
 Ordering.
 Order Processing.
 Administration.
 Requirements:
Introduction:

Requirements engineering process provides the appropriate mechanism for understanding what the
customer wants, analyzing need, assessing feasibility, negotiating a reasonable solution, specifying the
solution unambiguously, validating the specification and managing the requirements as they are
transformed into an operational system. The task of capturing, structuring, and accurately representing
the user's requirements so that they can be correctly embodied in systems which meet those
requirements (i.e. are of good quality).

Requirements management
REQUIREMENT ANALYSIS

Comprises of the user, functional and non-functional requirements.

User requirements

 The users require a system that has the following features.

 A user friendly graphical user interface.
 An informative and intuitive website.

Functional requirements:

This is how the system shall look like and do when successfully completed. The system shall meet the
following functional requirements:

When a customer will visit the online pizza ordering system of any pizzeria, he will be asked to login or
sign up with them for better experience. The customer will have to create a unique username and a
password. Then he /she will need to enter details like Name, phone number, address. After these steps
account of that customer will be created.

The system will provide the customer a menu in which all the pizzas and non-pizza items will be shown
with their prices. The pizzas in the menu are created by the professional chefs of the pizzeria. The
ingredients in this pizza will be changed according to the customer interests. The customer will select
any pizza from the menu or build custom pizza.

Each pizza will be shown with their image and price. The ingredients used in the making of that pizza will
also be seen. Each of these ingredients will be removed or other new ingredients will be added in the
order. After each selection or de-selection, the grand total of the order will be updated. One of the most
amazing feature of online pizza ordering system is that you can build your pizzas from the scratch. This
system will provide the options to create your custom pizzas with everything of your choice.

Requirement

 The website requirements will have the following including an account for the user to sign in and
log in.
 To be able to edit the shopping basket by adding more items removing and deleting item.
 The website will be available 24/7 for the customers to view
 The website will be able to handle many customers without slowing down.
 The website will be able to check out your items.
 Menu that people could see the name of an item and its picture.
 The website should be mobile optimized meaning the website should work on mobile phone to.

Let me tell you more about making custom pizzas.

 The customer will get an option to select pizza’s crust size which can be small, medium or large.
 Then customer will to choose the sauce to be used on his pizza crust. These can marinara,
cheese, ranch and others.
  Then the system will ask the customer whether to add cheese or not. He will also have an option
to select for extra cheese.
 At last the system will show the customer different types of toppings. Firstly, the customer will
choose between veg. and non veg. toppings. Suppose he/she selected veg., then different
options like pineapple, mushrooms, olives etc. are shown.

Non-functional Requirements:

A non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors. Some of the non-functional requirements include:

 There should be sufficient network bandwidth

 Backup- provision for data backup
 Maintainability- easy to maintain
 Performance/ response time- fast response
 Usability by target user community- easy to use
 Expandability- needs to be future proof or upgradable
 Safety- should be safe to use.

System user:

Modules of online pizza ordering system:

There are 3 modules in this system. These modules are:
 Ordering.
 Order Processing.
 Administration.

Menu:

 The system will provide customers a menu in which all the pizzas and non-pizza items will be
shown with their prices. The pizzas on the menu are created by the professional chefs of the
pizzeria.
 The ingredients in this pizza can be changed according to the customer’s interests. The customer
can select any pizza from the menu or build a custom pizza.
 Each pizza will be shown with its image and price. The ingredients used in the making of that
pizza can also be seen.
 Each of these ingredients can be removed or other new ingredients can be added in the order.
 After each selection or de-selection, the grand total of the order will be updated.
Logical Design
High Level Use case Diagram: A use case scenario is a visual description, typically written in structured
English or point form, of a potential business situation that a system may or may not be able to handle.
A use case defines a goal-oriented set of interactions between external actors and the system under
consideration. A use case is initiated by a user with a particular goal in mind, and completes successfully
when that goal is satisfied. It describes the sequence of interactions between actors and the system
necessary to deliver the service that satisfies the goal.

Use case diagram:

 ER Diagram:

ER Diagram of Pizza Ordering System describes entities of system, their attributes and relationship
between them.

E_ID Date Time

Sheet
Total

ID
Name House Status
City

Customer 1 *
Place Order
1

Finaliz
e
Have

* *

Employee
1
Manage Food
1

ID

Price ID
Password
U_Name
Name
Amount
Data flow diagram

Data flow Diagram of Pizza Ordering System describes entities of system, their attributes and
relationship between them.

It is a two-dimensional diagram that explains how data is processed and transferred in a system. The
graphical depiction identifies each source of data and how it interacts with other data sources to reach
common output.
Class Diagram:

The class diagram depicts a static view of an application. It represents the types of objects
residing in the system and the relationships between them. A class consists of its objects, and
also it may inherit from other classes.
ER diagram pizza odering system:
Trace-ability Matrix

Following columns are involved in the trace-ability matrix

ID Initial requirements Category Use case name Bulld

1 The customer will Business UC_login B1
get an option to
select pizza’s crust
size which can be
small, medium or
large.
2 Then customer will Business Uc_check menu B2
to choose the sauce
to be used on his
pizza crust. These
can marinara,
cheese, ranch and
others.
3 Then the system will Business UC_make B3
ask the customer payment
whether to add
cheese or not. He
will also have an
option to select for
extra cheese.
4 Each pizza will be Business UC_pay bil B4
shown with its
image and price.
The ingredients
used in the making
of that pizza can
also be seen.
5 Each of these Business UC_Add and dell B5
ingredients can be menu
removed or other
new ingredients can
be added in the
order.
6 Customer edit the Business UC_view and edit B6
shopping basket customer
7 Make sure the Business UC_Edit shopping B7
adress basket
8 At last the system Business Uc_deliver order B8
will show the
customer different
types of toppings.
Firstly, the customer
will choose between
veg. and non veg.
toppings. Suppose
he/she selected
veg., then different
options like
pineapple,
mushrooms, olives
etc. are shown.