A

Project Reporton

Pizza Shop App

in partial fulfillment of the requirement for the degree

of Bachelor of
Technology In
COMPUTER SCIENCE AND ENGINEERING
Submitted by

Mini Tomar (1901330100151)

Mansi Singh (1901330100148)
Prabha Singh (1901330100193)
Pranjwal Gupta (2001330109018)

Under the supervisionof

Mr. Rahul Kumar Sharma
(Assistant Professor)

NOIDA INSTITUTE OF ENGINEERING AND

TECHNOLOGY GREATER NOIDA
 DECLARATION

This is to certify that the project report entitled “Pizza shop” is done by me and all my group

member is an authentic work carried out for the partial fulfillment of the requirements for the

award of the B.Tech in “Computer Science and Engineering” under the guidance of Mr. Rahul

Kumar Sharma The matter embodied in this project work has not been submitted earlier forward

of any degree or B.Tech to the best of my knowledge and belief.

Pranjwal Gupta
Mini Tomar
Prabha singh
Manshi Singh
 ACKNOWLEDGEMENT

We would like to place on record my deep sense of gratitude to MrRahul Kumar Sharma Assistant
Professor, Department of Computer Science and Engineering, Noida Institute of Engineering &
Technology, Greater Noida, Gautam Buddha Nagar, Uttar Pradesh, India for his generous guidance,
help and useful suggestions.
We express our sincere gratitude to Mrs. Kumud Saxena, HOD(CSE), Noida Institute of Engineering
& Technology, Greater Noida for her stimulating guidance, continuous encouragement and
supervision throughout the course of present work.

Date: Student Names:

Pranjwal Gupta ( 2001330109018 )

MiniTomar (1901330100151)
Mansi Singh (1901330100148)
Prabha Singh (1901330100193)
 10/11/2022…..……...

COMPLETION CERTIFICATE

This is to certify that the Project report entitled “Pizza Ordering System” is a record of the work done
by the following students:

Student name Roll No.

MiniTomar (1901330100151)

Pranjwal Gupta ( 2001330109018 )

Mansi Singh ( 1901330100148)

Prabha Singh (1901330100193)

This work is done under my/our supervision and guidance during the academic year of 2021-22. This report is
submitted to the Noida Institute of Engineering & Technology, Greater Noida for partial fulfillment for the
degree of B.TECH. (Computer Science and Engineering) of Dr A. P. J. Abdul Kalam Technical University,
Lucknow, Uttar Pradesh, India.
I wish them all the best for all the endeavors.

Signature of Guide-
Mr. Rahul Kumar Sharma
(Assistant Professor)
 Index
1. Declaration
2. Acknowledgement
3. Certificate
4. Introduction
6. Objectives
7. Existing System Description
8. Proposed System
9. Tools Used
10. System
11. Analysis
12. Objective
13. SDLC Phases

Feasibility Study
Report Approval
System Analysis
System Design
Coding
Testing
Implementatio
n Maintenance

14. Process Description

15. Project Model Used
16. ER-Diagram
17. Data Flow Diagram
18. Software Requirement

19. Specification……….

Hardware
Requirement Software
Requirement Support
Maintenance
20. System Design……………
22. Low Level Design
22.1 Description of Classes and Methods
23. Data Modeling

24. List of Tables

25. Structure of Tables
26. Testing
27. Input-Output
28. Forms………

Modularization
Details User
Screenshots Admin
Screenshots
29. Future Scope………….
30. Conclusion……………..
 INTRODUCTION

➢ Problem Definition

Online pizza ordering services is a website that feature interactive menus

allowing customers to place orders with local Pizza Restaurants of same
franchisee across the globe name Mamma’s Crust. Much like ordering consumer
goods online, it allows customers to keep accounts with them in order to make
frequent ordering convenient.

➢ Objectives

In the current marketplace of food and restaurant services, different types of food dishes
are available and each country has its own kind of dishes to offer. But if we pick a food
item which is loved by everyone, then pizza will be a clear winner in it. The whole world
is crazy with Pizzas. The love of pizzas has approved the rise of large pizza companies
like Pizza Hut, Domino’s, and many others.
Nowadays people prefer online Pizza ordering services because it provides the flexible
ordering services and people get it on their doorsteps. In the traditional delivery system,
people get the home delivery services by giving orders through the phone calls. But there is
no visual menu shown during a phone call and employees have to repeat a lot of things again
and again to the customers. The phone call system is a time-consuming process which at
times irritates customers. Also, it takes a lot of time of the pizzeria staff. The online Pizza
ordering system is the perfect solution to many questions that are created in the traditional
Pizza ordering services. In the online services, people can see the menu list of the Pizza and
give the online order. So, no any question related to misunderstanding and not take more
times. In just a few minutes, customers can check the Pizza menu and give the order and get
it at their doorsteps.
 PROBLEM DEFINITION

In this section we shall discuss the limitation and drawback of the existing system that forced us to

take up this project. Really that work was very typical to manage the daily errors free records and adding

or removing any node from server. This problem produces a need to change the existing system. Some of

these shortcomings are being discussed below: -

• Low Functionality

With the existing system, the biggest problem was the low functionality. The problem

faced hampered the work. For small task like adding any new node to server or deleting a

node or keeping daily record we have to appoint minimum two or three employee.

• Erroneous Input and Output

In the existing system, humans performed all the tasks. As in the human tendency,

error is also a possibility. Therefore, the inputs entered by the person who is working in

the
 Company, in the registers may not be absolutely foolproof and may be erroneous. As a

result of wrong input, the output reports etc.will also be wrong which would in turn affect

the performance.

• Portability Problem

System that existed previously was manual. As a result, the system was less portable. One

has to carry the loads of many registers to take the data from one place to another. A big

problem was that the system was less flexible and if we wanted to calculate yearly or

monthly maintenance report or efficiency report, then it was a big headache.

• Security-

Security concerns were also one of the motives of the Company for the need of software.

In the registers, the data is not secure as anybody can tamper with the data written in the

registers. While in this software, just a password makes it absolutely secure from the

reach of unauthorized persons.

• Data Redundancy

In the case of manual system, the registers are maintained in which, a lot of data

is written.

• Processing Speed

In manual system maintaining a register and performing the necessary calculation has

proved to be a troublesome job, which takes a lot of time and may affect the performance

of the Company. But with this software we can have all the tasks performed in a fraction

of second by a single click thus making the troublesome job much easier.
• Manual Errors

When a number of tough tasks are prepared by the humans like preparation of reports,

performing long calculation then some human error are obvious due to a number of

factors like mental strain, tiredness etc. But as we all know that computer never get tired

irrespective of the amount of work it has to do. So this software can nullify the

probability of manual error that improve the performance.

• Complexity in Work

In manual system whenever a record is to be updated or to be deleted a lot of cutting and

overwriting needs to be done on the registers that are concerned that are deleted or

updated record, which makes the work very complex.

 SYSTEM ANALYSIS

Phases:

System Development Life Cycle (SDLC) mainly consists of the following7

phaseswhich can be detailed

Preliminary Investigation: -

This is the first phase of the system development life cycle. In this phase we tend to find
out the needs of the client ―what exactly does the client want? Before the development
of any system the important point is to know the needs, objectives and scope of the
system.
 Feasibility Study: -

Feasibility study is these conducted step of the system development life cycle. Things are always
easy at the beginning in any software process. In fact nothing is infeasible with unlimited time
and resources. But it is not the fact. So, practically we have to do in limited resources in a
restricted time margin. So for the system to be feasible, following points we have to consider.
The feasibility study is conducted to check whether the candidate system is feasible. The
system which is selected to be the best against the criteria is thereafter designed and developed.
The feasibility study takes in to consideration, the risks involved in the project development
beforehand. Therefore in this phase we have to do feasibility study which is the test of the
website according to its workability, impact on the organization, ability to meet user need and
effective use of resources. We do the feasibility study for website to analyze the risks, costs and
benefits relating to economics, technology and user organization. There are several types of
feasibility depending on the aspect they cover. Import of these includes:

➢ Technical Feasibility:

This is an important outcome of preliminary investigation. It comprise of

following questions:-
• Can the work of project be done with the current equipment, existing
software and available man power resource?
• If Technology is required what are the possibilities that it can be developed?
➢ Economic Feasibility:

It deals with question related to the economy. It comprise of the following questions:-
• Are there sufficient benefits in creating the system to make the cost acceptable?
• Are the costs of not creating the system so great that the project must
be undertaken?
 ➢ Legal Feasibility:

It deals with the question related to the legal issues. It comprise of the following questions:-
• Contract Signing
• Software License agreement
• Issues related to cyber laws.
• Legal issues relating to the man power contract.

➢ Operational Feasibility:

The operational feasibility consists of the following activity:-

• Will the system be useful if it is developed &implemented?

• Will the reb resistance from employee?

Social &Behavioral Feasibility:

It deals with the various issues related to the human behavior like:-
• Whether the user be able to adapt a new change or not?
• Whether the ambiance we are providing suits the user or not?

Request Approval:-

Request approval is the third phase of system development lifecycle. Request approval is the
phase in which all the requirements which would be provide in the system are stated. The
request approval is a sort of agreement between the client and the company which is building
his software. Both the parties should be mutually agreed on the stated requirements.

System Analysis:-
System analysis is the phase following the phase of the quest approval. In this phase wet
end to analyze the overall system which we have to build. System analysis is the crucial
part in SDLC.

System Design:-

System design means the designing of the system. The System can be done in either of the
following two ways:-

• Logical System Design

• Physical System Design

Coding:-

Coding is the phase in which a developer codes using any programming languages. Coding
constitutes only20 %of the whole project and which is easier to write. The coding work is
also done in the teams; development of the system is usually done under the modular
programming style, which can be either top-down approachor bottom-up approach.

Testing:-

Testing is the phase in which the system that has been developed is tested. Testing comprises
of the 60%ofthe overall development of the system. Testing of the system is important
because testing aims to uncover the different errors in the system. There are various different
testing techniques that can be used for the testing of the system.
Implementation:-

Implementation process involved the installation of software on user’s side. Implementation

process actually depends on type of a system &various. Opting for suitable conversion
approach is a step implementation. The conversion processes are as follows:-

• Parallel Conversion
• Direct Conversion Approach
• Pilot Conversion Approach
• Phase In Conversion Approach

Maintenance: -

Merelydevel oping the system is not important but also maintenance is important. The company
that has built the system provides for some time free of cost maintenance to the client and after
that period it is usually a paid service.
 PROJECT MODEL USED

Iterative Enhancement Model

➢
This model has the same phases as the waterfall model, but with fewer restrictions.
Generally the phases occur in the same order as in the waterfall model, but they may be
conducted in several cycles.
➢
Useable product is released at the end of the each cycle, with each release providing
additional functionality. Customers and developers specify as many requirements as
possible and prepare a SRS document. Developers and customers then prioritize these
requirements. Developers implement the specified requirements in one or more cycles of
design, implementation and test based on the defined priorities.

The procedure itself consists of the initialization step, the iteration step, and the Project
Control List. The initialization step creates a base version of the system. The goal for this initial
implementation is to create a product to which the user can react. It should offer a sampling of
the key aspects of the problem and provide a solution that is simple enough to understand and
implement easily. To guide the iteration process, a project control list is created that contains a
record of all tasks that need to be performed. It includes such items as new features to be
implemented and areas of redesign of the existing solution. The control list is constantly being
revised as a result of the analysis phase.

The iteration involves the redesign and implementation of iteration is to be simple,

straightforward, and modular, supporting redesign at that stage or as a task added to the project
control list. The level of design detail is not dictated by the iterative approach. In a light-weight
iterative project the code may represent the major source of documentation of the system;
however, in a critical iterative project a formal Software Design Document may be used. The
analysis of an iteration is based upon user feedback, and the program analysis facilities available.
It involves analysis of the structure, modularity, usability, reliability, efficiency, & achievement of
goals. The project control list is modified in light of the analysis results.
PHASES:

Incremental development slices the system functionality into increments (portions). In

each increment, a slice of functionality is delivered through cross-discipline work, from the
requirements to the deployment. The unified process groups increments/iterations into phases:
inception, elaboration, construction, and transition.
• Inception identifies project scope, requirements (functional and non-functional) and risks at
a high level but in enough detail that work can be estimated.
• Elaboration delivers a working architecture that mitigates the top risks and fulfills the
non- functional requirements.
• Construction incrementally fills-in the architecture with production-ready code
produced from analysis, design, implementation, and testing of the functional
requirements.
• Transition delivers the system into the production operating environment.
 SOFTWAREREQUIREMENT SPECIFICATION

A requirements specification for a software system is a complete description of the behavior of a

system to be developed and it includes a set of use cases that describe all the interactions the
users will have with the software. In addition to use cases, the SRS also contains non-functional
requirements.

Non-functional requirements are requirements which impose constraints on the design or

implementation (such as performance engineering requirements, quality standards, or design
constraints).Requirements are a sub-field of software engineering that deals with the elicitation,
analysis, specification, and validation of requirements for software.

The software requirement specification document enlists all necessary requirements for project
development. To derive the requirements we need to have clear and thorough understanding of
the products to be developed. This is prepared after detailed communications with project team
and the customer.

Hardware Requirements

(A) For Client Side –

Internet explorer 8, Chrome or any supported browser

Pentium 4
256 MB RAM
1 GB HDD

(B) For Server Side –

Xeon based or higher end Server
4 GB RAM
200 GB disk space
Software Requirements-

React (front end)

HTML
JavaScript
MS Word 2007 or later
Web Browser: Microsoft Internet Explorer, Mozilla, Google Chrome or later
Mongo DB (back-end)
Operating System: Windows XP / Windows7/ Windows 10 Node JS
Express
NPM

SUPPORTANDMAINTENANCE

One year free support for rectifying system bugs including front end and beck end will be
provided. During warranty period Software Engineers will be responsible for removing bugs and
improving it. After one year support can be extended @ 20% of the total product deployment
cost

SYSTEM DESIGN APPROACH

Top – Down designing:

The top - down designing approach started with major components of the system. It is a stepwise
refinement which starts from an abstract design, in each steps the design is refined two or more
concrete levels until we reach a level where no – more refinement is possible or not needed.
Bottom – Up designing:

In bottom – up designing the most basic and primitive components are designed first, and we
proceed to higher level components. We work with layers of abstractions and abstraction are
implemented until the stage is reached where the operations supported by the layer is complete.

Approach we are following:

In this project we are following Mixed Approach i.e. A combination of top – down and bottom
– up. We are developing some of the components using top – down designing approach (e.g. the
WebPages) and the some components in bottom – up designing approach (e.g. the middle tier
classes).
Low Level Design

Description: Low Level Design creation is one of the most important activities in the
development of any software product. The low level design document gives the design of
the actual software application. Low level design document is based on High Level
Design document . It defines internal logic of every sub module. A good low level design
document will make the application very easy to develop by the developer. An effective
design document results in very low efforts in developing a Software product.

Each project's low level design document should provide a complete and
detailed specification of the design for the software that will be developed in the project,
including the classes, member and non-member functions, and associations between classes that
are involved.

The low level design document should contain a listing of the declarations of all the
classes, non-member-functions, and class member functions that will be defined during the
subsequent implementation stage, along with the associations between those classes and any
other details of those classes (such as member variables) that are firmly determined by the low
level design stage. The low level design document should also describe the classes, function
signatures, associations, and any other appropriate details, which will be involved in testing and
evaluating the project according to the evaluation plan defined in the project's requirements
document.
 LITERATURE SURVEY

That exploration of the buyer's acceptance of online pizza applicant or different subjects
with in Indian context is restricted as online pizza requesting administration has entered the
Indian market a few years ago. The paper surveyed identifies with the experiments
performed out beyond India, where even the web pizza request has become a success. As
has been the case, online food applicants have recently started its Business in Indian
Market and are still on track to be a success. Client Perspective and Comfort for Ordering
Pizza on the Internet, there was a case on Foodzoned.com website, in the city Manipal
(2016)-The investigation revealed that there was a high growth in internet food requesting
administration. That understudy clients of all these administrations were trained all over
with the data available on such pages as well as feel a lot more comfortable with the help
of the web-based administration.
His studies clarifies the recognition of online purchasing as well as the target of online
shopping is not only affected with its propensity to simplicity of value, satisfaction, but also
by exogenous components such as buyer characteristics, situational factors, past web- based
shopping encounters and item quality and web-based shopping confidence. Foremost
Important Aspects for Web Pizza Purchase Services: Empirical Research Suggests the web
pizza ordering organizations need to consider the nature of the data, Android & ios apps and
web architecture, protection or safety of installment frameworks to give their clients full
experience. Customerpurchase option period using the web pizza application stage in
Bangkok investigation reveals that now the internet stage has fundamentally changed the
management of the pizza conveyance industry. The latter has helped to increase the client's
participation in conventional pizza conveyance management organizations, such as the
significant drive- through food chains, thereby influencing the purchaser's observation of the
pizza conveyance industry in general.
 PROPOSED METHODOLOGY

The analysis is as exploratory as the contrast of the natural world. This plans
for investigate the buyer's acceptance of the online pizza application. Each
information about the investigation has been accumulated across organized 2
arrangements with survey. The web study is being used to collect information
for that kind of analysis. Research was generally performed on the sub-studies
of Mumbai. The variables have been interpreted by writing upon this web
pizza application. This initial section of this study covered enquiries
concerning certain components made by shoppers to order pizza on the internet

Differentiate certain elements that have an effect on the purchaser in

organizing pizza on the network.

a-Timing as well as conveyance

Timing seems to be the important point on every form of company and
administration, when timing and transport are linked to the hip. On-Time
Delivery is a much of the time KPI (Key Performance Index) assess
provider's dependent on conveyance execution responsibility. With less
squander, the rise in conveyance that impact everybody unique in world
where nobody spends on inefficient things. Time and conveyance are
significantly portrayed by the getting pizza inside couple of moments.
Administration has impacts, as the consumer is not bound with a fixed
timing period.
b-Accommodation
Accommodation seems to be biggest driver factor on web pizza asking,
followed by reasonableness, for further analysis by the critical exploration
firm that the Chrome Data Analytics said. Buyers don't fly to discover but get
pizza on the internet or lose their families. As this aspect additionally
assumes the vital role of impacting the purchaser on the use of the web pizza
administration, as the ill-advised accommodation transforms into a big chaos
that prevents the purchaser from actually continuing with the purchasing of
pizza. Comfort gives consumer a degree of stability, power on what’s to
buy, and its following also assists in the choice of products from the large
web assortment. In addition, it is as safe even considerably as many as the
normal methods, while raising costs also has an effect on internet the pizza
buyer. c- Simple Accessibility An individual allude and accepts that utilizes
the framework that would liberate from exertion. What's more, this is the
significance of the online pizza request because, because of its simple
transparency of nature, in just a few taps users receive whatever they need on
the entryway stage, that's one thing that the purchaser wants so much,
launching application on your mobile phone or browsing that software in the
PC's, asking with less than few seconds. Many individuals do the same in
view towards availability, since the need to be somewhat kind of a concern
since they may become.
Few zones dont actually contribute to online pizza
requesting because of which certain may incorporate accessible in country
region might be result of less progression in the span entirely snags figuring
everything so significantly individuals appreciate administrations.
c-Adaptability
Everybody appreciates great deal of advantages and requesting very
illustration of it. Regardless of where you are, time you need you can
arrange, this is the thing buyers wants things being worked out as indicated
by their requirements and needs. All apps & web servers are planned
including adjustments as per needs of the purchaser thus make everyone
interaction very well adaptable although it could reasonably be anticipated.
Different presentation highlights for the ideas of online pizza requests like
money down, entryway conveyances, alerted pizza requests and many other
with the lines adding pizza requests. Customer characterize the internet
buying as purchaser made as positive or negative assessment for purchasing
pizza and encourages slanting on the positive role.
d-Simplicity of payments
Hassel's optional installments that's off great importance because that's a
thing a shopper wants in great majority, usually, individuals trying not to use
online administration is basically due to the preference of not getting stuck
for the installments. Presents a new installment approach has contributed to
the confidence of individuals and, as a result, to the advancement of a vast
number of organizations. Strategies, for example, Money for conveyance,
Transaction via merchant accounts, Master cards, and so on, to help eradicate
the problem of installments and to make it easy for the purchaser.
e-Advancement
Deals Advancement involves Shopper Advancement Devices that are
discounts, money savings incentives cost off, fees, prizes, and so on. Deals &
limitations were those that really attracts each Shopper so that they may
enjoy
on-line pizza ordering consistently. Cost has served the major sole measure
for the purchaser's decision Lower Evaluation seen during web pizza
administration just like users to do shoping in web pizza administration.
Since everyone prefers to set aside cash & capitalize on what they are
paying for, so these outstanding sales and other special exercises will earn
the customer's principal premium
f- To what amount users prefer to buy pizza online? As indicated in
the report, outside from one-hundred twenty participants, most individuals
having 42.6 percent participants prefer To arrange week after week,
although a similar level of respondents chose 16.3% on a day-to- day basis
and 16.3% on a month-to-month basis last, 12.7 percent respondents chose a
biweekly basis.
g- By and large, how do people prefer ordering Pizza? Within that
sense, We interrogate individuals what approach people find most
appropriate when applying on the web, off from 130 participants,58.7
percent participants picked up across these Application(mobile/tablet), 16.4
per cent preferred over the website(desktop/laptop) and 11.6 per cent picked
up across these Phone (Direct contact).
h- Which food people usually order pizza online? This review
reveals that total 110 participants, 36.4 per percent participants picked
snack, 26 per cent picked supper and 15.6 per cent of them picked
dinner.
 FUNCTIONAL & NON-FUNCTIONAL REQUIREMENTS

Functional Requirements:

1. Registration
If customer wants to order the food then he/she must be registered, unregistered user can’t go for
ordering.

2. Login
The customer login to the system by entering valid user id and password for ordering.

3. Display the menu

In the system all the items are displayed with their rates.

4. Modify menu
System can make changings in menu like adding or removing food items which are not avaiable.

5. Select food item/s

ltems are selected customer feel free to order.

6. Changes to order
Changes to order means the customer can make changings in order like he/she can delete or
add food item in order.

7. Review the order before submitting

Before submitting the complete order is reviewed to the customer. Customer name, phone
number, location (address) and placed order, hen finally order is submitted.

8. Payment
For customer there are many type of secure billing will be prepaid as debit or credit card,
postpaid as afer delivering, check or bank draft.

9. Provide delivery and payment details

Here bill is generated, order no, and payment is given and confirmation of delivery is done.

10. Logout
After the payment or surf the product the customer will log out.
 Non-Functional Requirements:

1. Portability
System running on one phtiorm can easily be converted to run on another platform

2. Reliability
The ability of the system to behave consistently in a user-acceptable manner when operating
within the environment for which the system was intended.

3. Availability
The term should be available at all times, meaning the user can access it using a web browser,
only restricted by the down time of the server on which the system runs.

4. Maintainability
A commercial database is used for maintaining the database and the application server takes care
of the site.

5. Security
Secure access of confidential data (customer information).

6. User friendly
System should be easily used by the customer.

7. Performance
Performance should be fast.

8. Efficient
System should be efficient that it won’t get hang if heavy traffic of order is placed.

9. Safety
Data in the database of system should not loss or damage.

10. Privacy
Personal data of the system should not disclose to anyone.
 MAJOR MODULES AND THEIR FUNTIONALITIES

Let us now understand the working of this system Firstly the Customer Login or Signup. The
menu will be visible to the customer with the pizzas and other non-pizza products on offer. All
the ingredients will be shown at their prices.

Now the customer will customize his pizza and make changes in the ingredients if he wishes and
select the quantity for it. After selecting the items to be ordered, the customer has to select the
type of order whether it will be home delivery or pick up.
After that, the customer has to provide his/her details like name, phone number, address, email id.

Now payment option is shown to the customer. He has to choose from the various online
payment methods or cash-on-delivery options. After this process, the order is made and the
customer is notified about the time by which the pizza will be delivered to them.
Modules of online pizza ordering system: There are 3 modules in this
system.
These modules are:
▪ Ordering.

▪ Order Processing.

▪ Administration.

Let us now get into the details of these modules:

 Ordering
This module will provide the interface for customers to order their pizzas:

Login/Sign-Up:
When a customer visits the online pizza ordering system of any Shop, he will be asked to log
in or sign up for them for a better experience. The customer has to create a unique username
and a password. Then he /she need to enter details like Name, phone number, address. After
these steps account of that customer will be created.
 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 shop.
▪ 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.
 Build Your Pizza:

One of the most amazing features of an online pizza ordering system is that you can build your
pizzas from the scratch. This system provides the options to create your custom pizzas with
everything of your choice. Let me tell you more about making custom pizzas.

▪ The customer will get an option to select the pizza’s crust size which can be small,
medium, or large.
▪ Then the customer has to choose the sauce to be used on his pizza crust. These can
marinara, cheese, ranch, and others.
▪ Then the system asks the customer whether to add cheese or not. He also has an
option to select extra cheese.
▪ At last, the system shows the customers different types of toppings. Firstly, the
customer has to choose between veg. and non-veg. toppings. Suppose you selected
veg., then different options like pineapple, mushrooms, olives, etc. are shown.
One important point to be noticed here is after each step, the updated price of your
custom-built pizza is shown to the customers. Each item’s price is also reflected below its
image.
 Add To Cart:

This feature is useful in a situation where you have to order more than one pizza or other
non-pizza items.
Suppose you have selected a Margherita pizza and now you want to select another pizza as well.
Then you just have to add that pizza to the cart using the Add to cart option. Items added to the
cart will be saved so that you can choose other pizzas as well.

Finally, when you are ready to order you can check out from the cart to make payment.
Payment There will be basically 2 payment options i.e. online payment using Credit/Debit
cards and Internet banking or Cash on delivery. Before making payment, your order details
are shown and confirmed. This system makes transactions easier as the need to pay with cash
is not there.

Home Delivery or Pick up. This feature asks the customer if he/she intends to pick up his/her
order from the shop or it is needed to be delivered to their address.
 Track your Order:

This is another interesting feature which helps customers to keep a track of his order. The
customer is notified at every step of their order completion. After making payment the
customer is shown the time by which his order will be delivered to his doorstep.
 Order Processing
In the previous section, I told you all about pizza ordering by customers. But what happens after
this. How our shop manages the order made by the customer and delivers it on time. The online
pizza ordering system comes to their rescue again. It provides all the features and functionalities
for processing orders without any fuss for the staff of the shop.

This module will be used by the employees of the for preparing orders and delivering them to
their destination. Each employee of the shop will have an account in this ordering system. They
will have a username and password provided to them by the system admin. Mainly there are
three types of employees using the online pizza ordering system.

They are Kitchen staff, delivery staff, and other employees like the counter staff.

Let me tell you about each user’s rights and responsibilities:

 Kitchen Staff:

They have an interface that shows them the list of orders to be prepared. Each order shows its
details like ingredients to be used and the quantity of each item. The current status of each order
is pending. After a particular order is prepared and ready to be delivered, the kitchen staff
updates the status to ‘Prepared’.

The customer is notified at this stage that their order is prepared and soon will be delivered.
 Delivery Staff:

After the order is prepared the available delivery staff is handed over the orders with their
address. When the delivery staff leaves for delivery the status of the order is updated again to
‘Out for Delivery’ and the customer is notified. When the delivery staff delivers the order
successfully, he updates the order status to ’Delivered’.

If he fails to deliver the order due to any reason, the status is updated to ‘Delivery Failure’.
 Counter Staff:

In case of pick up, the counter staff updates the status of the orders. When the kitchen staff has
prepared the order, the counter staff updates the status to ‘Ready to be picked’ and the customer
is notified that he can pick up his order now. After the customer picks up his order, the counter
staff updates the order status to ‘Received by customer’.

Each kind of employee has its own rights and permissions. The kitchen staff has a right to
only check pending orders and update status to ‘Prepared’. He cannot update the order status
to ‘Delivered’ as he doesn’t have the right to do so.
 Administration:

Till now, I told you about the two most important modules of the online pizza ordering system.
Let us move our discussion towards the last (but not the least) module of this system i.e.
Administration. The administration module is equally important in the functioning of this
system. The user is of this module is known as Admin or superuser.

He is the master of this online system. Admin has all the rights and power to use this system.

The tasks which can be performed by the admin are:

1. He can add/edit/delete different ingredients into the system. He can add/edit/delete new
pizzas, their images, prices, and other details. The same functions can be performed for
non-pizza items.
2. He can add/edit/delete users in this system. It’s the admin who adds new
employees’ accounts to the system.
3. Admin has rights to add/edit/delete orders for customers.
 Login Sequence Diagram Of Pizza Ordering System:

This is the Login Sequence Diagram of Pizza Ordering System, where admin will be
able to login in their account using their credentials. After loginuser can manage all the
operations on Order, Payments, Customer, Coupans, Pizza. All the pages such as
Customer, Coupans, Pizza are secure and user can access these page after login. The
diagram below helps demonstrate how the login page works in a Pizza Ordering System.
The various objects in the Coupans, Order, Payments, Customer, and Pizza.
This is the UML sequence diagram of Pizza Ordering System which shows the
interaction between the objects of Payments, Customer, Order, Pizza, Coupans. The
instance of class objects involved in this UML Sequence Diagram of Pizza Ordering
System are as follows:
- Payments Object
- Customer Object
- Order Object
- Pizza Object
- Coupans Object
Pizza Ordering System Class Diagram (/Uml/Pizza-Ordering-System-Class- Diagram)
Pizza Ordering System Class Diagram describes the structure of a Pizza Ordering
System classes, their attributes, operations (or methods), and the relationships among
objects. The main classes of the Pizza Ordering System are Pizza, Order, Customer,
Order Status, Coupans, Payments.
Classes of Pizza Ordering System Class Diagram:
Pizza Class : Manage all the operations of Pizza
Order Class : Manage all the operations of Order
Customer Class : Manage all the operations of Customer Order Status
Class : Manage all the operations of Order Status Coupans Class :
Manage all the operations of Coupans Payments Class : Manage all the
operations of Payments
Classes and their attributes of Pizza Ordering System Class Diagram: Pizza
Attributes : pizza_id, pizza_name, pizza_type, pizza_description Order Attributes :
order_id, order_customer_id order_type, order_number, order_description
Customer Attributes : customer_id, customer_name, customer_mobile,
customer_email, customer_username, customer_password customer_address.
Payments Attributes : payment_id, payment_customer_id, payment_date, payment_amount,
payment_description
Classes and their methods of Pizza Ordering System Class Diagram: Pizza
Methods : addPizza(), editPizza(), deletePizza(), updatePizza(), savePizza(),
searchPizza()
Order Methods : addOrder(), editOrder(), deleteOrder(), updateOrder(),
saveOrder(), searchOrder()
Customer Methods : addCustomer(), editCustomer(), deleteCustomer(),
updateCustomer(), saveCustomer(), searchCustomer()
Order Status Methods : addOrder Status(), editOrder Status(), deleteOrder Status(),
updateOrder Status(), saveOrder Status(), searchOrder
Status()
Coupans Methods : addCoupans(), editCoupans(), deleteCoupans(),
updateCoupans(), saveCoupans(), searchCoupans()
Payments Methods : addPayments(), editPayments(), deletePayments(),
updatePayments(), savePayments(), searchPayments()
 Class Diagram of Pizza Ordering System

Class Diagram Image:

Process Description

Gantt charts-

Gantt charts mainly used to allocate resources to activities. The resources allocated to activities include
staff, hardware, and software. Gantt charts (named after its developer Henry Gantt) are useful for resource
planning. A Gantt chart is special type of bar chart where each bar represents an activity. The bars are
drawn along a timeline. The length of each bar is proportional to the duration of the time planned for the
corresponding activity.
Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt chart, by
coloring each milestone when completed. The project will start in the month of August and end after 4
months at the beginning of November.

Aug Sep Oct Nov

 ER-Diagram

Introduction:-

In software engineering, an entity-relationship model(ERM) is an abstract and conceptual representation of

data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual
schema or semantic data model of a system, often a relational database, and its requirements in a top-down
fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs.
ER Diagrams depicts relationship between data objects. The attribute of each data objects noted in the
entity-relationship diagram can be described using a data object description. Entity relationship diagram is
very basic, conceptual model of data and it is fundamental to the physical database design. This analysis is
then used to organize data as relations, normalizing relations, and obtaining a Relational database.
The entity-relationship model for data uses three features to describe data. These are:
1. Entities which specify distinct real-world items in an application.

2. Relationship, which connect entities and represent meaningfuldependencies between

them.

3. Attributes which specify properties of entities & relationships.

 Data Flow Diagram

Introduction:-

DFD is an acronym for the word Data Flow Diagram. DFD is pictorial representation of the system. DFD
is a graphical representation of the ―flow of data through the information system. DFD are also used forth
visualization of data processing (structured design). ADFD provides no information about the timings of
the process, or about whether process will operate in parallel or sequence. DFD is an important technique
for modeling a system’s high-level detail by showing how input data is transformed too input results
through as sequence of functional transformations. DFD reveal relationships among between the various
components in a program or system. of DFD lies in the fact that using few symbols we are able to express
program design in an easier manner . ADFD can be used to represent the following:-

External Entity sending and receiving data.

Process that change the data. Flow of
data within the system. Data Storage
locations.

Uses of DFD:-

The main uses of data flow diagrams are as follows:-

DFD is a method of choice for representation of showing of information through a system because of the
following reasons:-

DFDs are easier to understand by technical and non-technical audiences.

DFDs can provide a high level system overview, complete withboundaries and
connections to other system.
DFDs can provided tailed representation of system components.
0 Level DFD:-

1 Level DFD:-
2. Level DFD:-
 DATA MODELING

LIST OF TABLES:

1. Tbl_Registration
2. Tbl_Login

1. Tbl_Registration:-

Field Name Data Type Status

FirstName Varchar(100) Not null
LastName Varchar(7) Not null
Gender Varchar(100) Not null(Primary key)
DOB Varchar(20) Not null
Address Varchar(Max) Not null
Contact Varchar(Max) Not null
Email Id Varchar(20) Not null
Password Varchar(30) Not null
Profile Varchar(70) Not null
Reg Date dateTime Null

2. Tbl_Login

Field Name Data Type Status

ID Int Not null(primary key)
EmailId Varchar(100) Not null
Password Varchar(60) Not null
 TESTING

Testing is the integral part of any System Development Life Cycle insufficient and interested
application tends to crash and result in loss of economic and manpower investment besides user’s
dissatisfaction and downfall of reputation.

“Software Testing can be looked upon as one among much process, an organization performs,
and that provides the last opportunity to correct any flaws in the developed system. Software
Testing includes selecting test data that have more probability of giving errors.” The first step in
System testing is to develop the plan that all aspect of system .Complements, Correctness,
Reliability and Maintainability.

Software is to be tested for the best quality assurance, an assurance that system meets the
specification and requirement for its intended use and performance.
System Testing is the most useful practical process of executing the program with the
implicit intention of finding errors that makes the program fail.

Types of Testing

Black Box (Functional) Testing:

Testing against specification of system or component. Study it by examining its inputs and related
outputs. Key is to devise inputs that have a higher likelihood of causing outputs that reveal the
presence of defects. Use experience and knowledge of domain to identify such test cases. Failing
this a systematic approach may be necessary. Equivalence partitioning is where theinput to a
program falls into a number of classes, e.g. positive numbers vs. negative numbers. Programs
normally behave the same way for each member of a class. Partitions exist for both input and
output. Partitions may be discrete or overlap. Invalid data (i.e. outside the normal partitions) is
one or more partitions that should be tested.
Internal System design is not considered in this type of testing. Tests are based on requirements
and functionality.
This type of test case design method focuses on the functional requirements of the software,
ignoring the control structure of the program. Black box testing attempts to find errors in the
following categories:
➢
Incorrect or missing functions.
➢ Interface errors.
➢ Errors in data structures or external database access.
➢ Performance errors.
➢ Initialization and termination errors.

White Box (Structural) Testing

Testing based on knowledge of structure of component (e.g. by looking at source code).

Advantage is that structure of code can be used to find out how many test case need to be
performed. Knowledge of the algorithm (examination of the code) can be used to identify the
equivalence partitions. Path testing is where the tester aims to exercise every independent
execution path through the component. All conditional statements tested for both true and false
cases. If a unit has n control statements, there will be up to 2n possible paths through it. This
demonstrates that it is much easier to test small program units than large ones. Flow graphs are a
pictorial representation of the paths of control through a program (ignoring assignments,
procedure calls and I/O statements). Use flow graph to design test cases that execute each path.
Static tools may be used to make this easier in programs that have a complex branching structure.
Tools support. Dynamic program analysers instrument a program with additional code.Typically
this will count how many times each statement is executed. At end print out report showing
which statements have and have not been executed. Problems with flow graph derived testing:
This testing is based on knowledge of the internal logic of an application’s code. Also known as a
Glass Box Testing .Internal software and code working should be known for this type of testing.
Tests are based on coverage of code statements, branches, paths, conditions.

Unit Testing:

Unit testing concentrates on each unit of the software as implemented in the code. This is done to
check syntax and logical errors in programs. At this stage, the test focuses on each module
individually, assuring that it functions properly as a unit. In our case, we used extensive white-
box testing at the unit testing stage.
A developer and his team typically do the unit testing do the unit testing is done in parallel with
coding; it includes testing each function and procedure.

Incremental Integration Testing:

Bottom up approach for testing i.e. continuous testing of an application as new functionality is
added; Application functionality and modules should be independent enough to test separately
done by programmers or by testers.

Integration Testing:

Testing of integration modules to verify combined functionality after integration .Modules are
typically code modules, individual applications, client and server and distributed systems.
Functional Testing:

This type of testing ignores the internal parts and focus on the output is as per requirement or
not .Black box type testing geared to functionality requirements of an application.

System Testing:

Entire system is tested as per the requirements. Black box type test that is based on overall
requirement specifications covers all combined parts of a system.

End-to-End Testing:

Similar to system testing ,involves testing of a complete application environment in a situation

that mimics real-world use, such as interacting with a database ,using network communications,
or interacting with hardware, applications, or system if appropriate.

Regression Testing:

Testing the application as a whole for the modification in any module or functionality .Difficult to
cover all the system in regression testing so typically automation tools are used for these testing
types.

Acceptance Testing:

Normally this type of testing is done to verify if system meets the customer specified
requirements. User or customers do this testing to determine whether to accept application.

Performance Testing:

Term often used interchangeably with “stress” and “load” testing, To check whether system
meets performance requirements, Used different performance and load tools to do this.
Alpha Testing:

In house virtual user environment can be created for this type of testing. Testing is done at the
end of development .Still minor design changes may be made as a result of such testing.

Beta Testing:

Testing typically done by end-users or others. This is final testing before releasing application
for commercial purpose.
User Screenshots:

HomePage
Registration Page
Login Page
Add to Cart and Payment Info-
Admin Login-

Admin Dashboard-