Pizza Ordering App: The Mumbai University, Mumbai

PIZZA ORDERING SYSTEM 2019-2020
A
Project Report On
PIZZA ORDERING APP

Submitted To
The Mumbai University, Mumbai

IN
In the partial fulfillment of the degree of
Bachelor of Information Technology
By
Mr. Adnan Rafiq Bukhari
Under Guidance Of
Prof. Pooja Butala
Through
I.C.S. College(Science , Commerce & Arts)
Khonde - Khed
2019-2020
CERTIFICATE
This is to certify that the project entitled “Pizza Ordering App ” submitted by Mr.
Adnan Rafiq Bukhari Exam Seat No. in partial fulfillment of the requirement of the award
of degree Bachelor of Science ( I T ) to Mumbai University has been carried out by him under my
guidance satisfactory during the academic year 2019-2020.
Date:
Signature Of Signature Of Signature Of Signature Of

Internal Guide External Examiner Head Of Department Principal
Organization Certificate
This is to certify that the Project entitled “Pizza Ordering App ” undertaken at the “I.C.S.
College.” Khed , by Mr. Adnan R Bukhari. Exam No .has successfully completed his
as a part of his curriculum for Degree in T.Y.B.Sc. ( I T) Year 2019-2020 of Mumbai
University.His work was satisfactory during the project period.
Principal,
I.C.S. College,
khed
ACKNOWLEDGEMENT
I wish to place on record our profound gratitude to Principal of I.C.S. College of
Arts, Commerce & Science, Khed Dr. G. B. Sarang. I wish to place our special thanks to Prof.
Sachin S. Bhosale (Head of Dept. of Information Technology), for having provided us with the
laboratory facilities and wish enables us to complete by project in time.
I place our sincere thanks towards our guide Prof. pooja Butala , who supported us
whole heartedly and gave us a valuable guidance. Constructive criticism and timely suggestions
helped us a lot in the completion of project with base possible manner.
I am also thankful to other teaching and non-teaching staff of the college who helps
us to complete this project.It would be grateful to mention about the valuable suggestions and
encouragement from our family and friends and who helped directly and indirectly to make
this project a success.
Yours sincerely,
Mr. Adnan Rafiq Bukhari
B.Sc.( I T)
Year 2019-2020
Index
Sr. No. TOPIC NAME PAGE NO.
1. INTRODUCTION
2. SURVEY OF TECHNOLOGIES
SYSTEM DESIGN
3.1 TECNICAL FEASIBILITY
3. 3.2 ECONOMICAL FEASIBILITY

INTRODUCTION
Introduction to Project
The Application “Pizza Ordering” is designed for people. In this project administrators set
product, product prize, employee information, employee salary, transaction, purchase, sell all of
these data. Administrator can register the user id and their password, which is necessary for user.
Administrator gives order to supplier for raw materials.
Customer easily handles the Application & gets their product. In administrator side the work
of administrator is easy than manual work. All data are saved in digital format. Administrator
can store number of more data in system. She/he can easily find out employee details, their
salary, and customer information. As compare to manual work, my project can save time &
energy. Administrator can easily generate reports that are used in audit. So as compare to manual
work this Application perform better & fast work.
SYSTEM
ANALYSIS
Existing System
The present system is totally depending on manual data management for different activities
such as maintaining details of customer, supplier, Students etc.
They maintain Different registers for various activities such as storing and searching data which
is tedious and time consuming task.
In present system all transactions are done manually with pen and paper so the frequent updating
is not possible. Also generating reports, bills accurately is not possible with current system.
There are various other problems for instance, if customer comes for the inquiry of particular
Parcel and if that Parcel is not available then it is difficult to remember about it.
In short system is lacking facilities such as searching, deleting, and adding data efficiently
and effectively.
Limitations of present system:

There are certain limitations in system, which areas follow:-
1. To maintain records of every task like record of Employee, bill, payment, Stock, etc. manually
is unaffordable.
2. To Search the records of Employee, payment, customer, customer- order, bill, salary from
registers is critical process.
3. Retrieval of information and searching any old record is critical process.
4. In the current system, time is wasted for searching any old records of student, staff.
Most chances of losing information in the manual files and it requires lot of manpower.
Advantages of proposed system

1. It utilizes a large amount of space for customer and supplier transaction information in paper
files.
2. Our Application saves time.
3. A large amount of data can be a save.
4. No reminder for customer and Purchaser.
5. Calculation has to be done directly & accurate.
6. Updating is not performed that efficiently and may lead complications.
7. No security as data can be misplaced or damaged.
8. A Application provide user friendly work environment.

Hardware Requirements
Hardware and Software Requirements:
RAM
Minimum 2 GB RAM required to run the system.

Hard Disk
Minimum 20 GB HDD is necessary to deploy the system.

Processor
Pentium IV and above.

Operating System
Software Requirements
Operating System
Window’s 8, Window’s 10.
Platform
Android Studio
Backend
JDK 1.8
Feasibility study
The feasibility study proposes one or more conceptual solutions to the problem set for
project. The conceptual solution gives an idea of how the system looks like. The following three
things should be done to establish feasibility:-
1] Technical feasibility: - Technical feasibility study determines whether the organization has
the technology & the skills necessary to carry out the project. If not then it determines how they
should be obtained. In this proposed system, the existing technology satisfies the need for the
system that is available. Therefore, the system is feasible.
2] Operational Feasibility: - Operational feasibility study determines if the proposed system

satisfies the user’s objectives & can be fitted into the current system operation. Our proposed
system will certainly satisfy the user’s objective & it will enhance their capability. The proposed
system can be best fitted instead of the current system operation. Therefore, the system is
operationally feasible.
3] Economic Feasibility:-
Economic feasibility study determines whether the project goals can be achieved within the
limits allocated to it. It must also determine that the benefits obtained from the new system are
not worth the cost.
GANTT CHART
Name Of The Phase Expected Actual Date Signature

Date Of Of Of Guide
Completion Completion
Project Search
Finalization & Allocation
Investigating Of System
Requirements
Data & Process Modeling
System Design
Program Design
Program Coding & Unit

Testing
System Integration
Project Review By Guide
System Implementation
Acceptance Testing
Feedback For Improving,

Correcting& Modifying the
Project
Fact-Finding Techniques
Fact-finding technique is one of the parts of the system analysis. At the time of analysis of the
system or before starting actual work, system analysts collect the information. For gathering
information system analyst prefers any fact-finding technique such as:
1] Interview.
2] Questionnaire.
3] Record review.
4] Observation.
While developing this system we have done this part by using interview & record-review
techniques.
1] Interview: -
The whole system investigation part has done by taking interview of the concerned people, user
& staff. By asking them manual process of each work, by pointing hints regarding the work, by
discussing their problems deeply, by asking them their requirements, by taking their valuable
suggestion guidance regarding system study.
After taking their interviews regarding the systems study noting down the points regarding the
system. This work of taking interview-asking difficulties to concern person till all the points of
the system understood. This interview technique proved beneficial outcome for system analysis.
2] Questionnaire:-
In this method we actually provide a list of questions to the user. According to the list the user
answers the questions, taking his own time without stress to answer quickly. In this method the
results Obtained are rather accurate and thoughtfully given. Questionnaires can be an effective
method for gathering facts. E.g. how your system actually works?
3] Record review:-
Review of record is good but a tedious way to retrieve information from an organization. This
refers to a personal viewing of records.
4] Observation: -
This technique proves useful in finding the facts of the system. In this technique has done by
observing ledger, registers, document, files that are prepared manually. By observing such record
a view of the database file, reports, screen designing, required input output of the system,
database designing of the system, and logical designing of the system.
Thus by doing their techniques of the fact finding method different facts of the system gathered.
Event Table
EVENT TRIGGER SOURCE ACTIVITY RESPONS DESTINATIO

E N
Add New Adding New customer

customer
Customer Arrival of customer Details Master
Record customer Record
Update Change in Updating Customer

customer customer
Customer Customer Details Master
Record Record
detail
Delete Delete Delete Customer Customer
Customer Customer Record Details Master

Customer
Record Record
Add New Arrival of Employee Adding New Employee

new Employee
Employee Details Master
Employee Record
Record
Update Change in Updating Employee
Employee Employee Employee Employee Details Master
Record detail Record
Delete Delete Employee Delete Employee Master

Employee Employee Details
Employee
Record
Add New Arrival of new Manager Adding New Manager Master

Manager Manager Manager Details
Record Record
Use case diagram:

1. Use case for Pizza Ordering App System
Manage
Customer
record
Manage Employee
record
Manage Supplier
record
Manage Items
record
Manage Purchase
Record
Administrator
Manage Sales
Record
Manage Report
2. Use Case for Customer:-
Enquiry about
Product
Selecting the
Product
Login Account
Ordering the
Product
CUSTOMER Fill up information

about delivery
Get Bill
Pay Bill
3Use case for Employee
Provide
Information
Provide Information
about the Product
EMPLOYEE Delivery of
Product
4)Use case for Supplier:
Get Order
Supply Product
Get Payment
Supplier
Prepare Bill
Entity Relationship Diagram

Quality
type price
Product
1
Address
Id
Nam Manage
Addres
e Name s
1 Contac
Contac
M 1 t
t Manager Admit Customer
1 M M
E-mail Gende
r
ID
Work Handles
for
Product
E-mail 1 M 1
Employee Type ID
Post
Name
Salary
Name Price
Company
Contact
Addres ID Product_ name
s
Bill_no
Cust_name Product_ID
Cust_ID Quantity
Address Purchase Product

Customer Price
phone_No
Sale
Demand
/provide Supplier _Name
Emp_ID
Supplier
Employee Orders Supplier _ID
Emp_Pos Produ
t ct
Supplier_ Name
Phone_No
Emp_email_id Date of joining
Salary
Activity Diagram
1) Create Customer Record :

Collect Fill Save
Customer Info Customer Info Record
2) Update/Delete Customer Record:
Search Update/Delete Save

Record Record Changes
1) Create Employee Record :
Collect Fill Save

Employee Info. Employee Info. Record
1) Update/Delete Employee Record:
Search Update/Delete Save

Record Record Changes
Class Diagram:
Customer Master Supplier Master

Customer Id Supplier Id
Customer Name Supplier Name
Customer Address Supplier Address
Contact No Email-Id
Product buyed Contact No
add()
add () update()
update () delete()
delete () display()
display () search()
search()
Employee Master Product Master
Employee Id Product Id
Employee Name Product Name
Employee Address Quantity
Email-Id Price
Contact No
add()
add() update()
update() delete()
delete() display()
display() search()
search()
view()
Customer Bill Order
Bill Id Order Id
Bill Date Order Date
Supplier Id
Customer Name
Supplier Name
Customer Address Product Id
Product Name Product Name
Price Quantity
Quantity Total amount
Total Amount
add()
add() update()
delete() delete()
search() display()
search()
Employee Salary
Employee Id
Salary Date
Employee Name
Employee Gender
Employee Address
Employee Salary
add()
delete()
update()
search()
Class Association Diagram:-
1 Gives *
Customer Supplier Products
Take *
*
Gives has
Include
*
1 1
*
Bill Order Report
1has 1
OBJECT DIAGRAM:
 Object Diagram Customer places many order:-
C:Customer
Cust_Id : 1
Cust_Name : Suraj
Cust_Address:Khed
O1:order O2:order
Order_Date : 1-08-2019 Order_Date : 1-08-2019
Product Type: Veg Pizza Product Type: Non-Veg
Item Name: Peppy Paneer Pizza
Item Name: Chicken
Dominator
 Object Diagram for Order has Bill:-
O1:Order B1:Bill
Product_Type : Veg Pizza
Product Type: Veg Pizza Company Name: Peppy
Item Name: Peppy Paneer Paneer Price: 90
Comp_Name:Lux
 Object Diagram for Order includes many

products:-
O1:Order
Cust_Id : 12
Cust_Name :Suraj
Cust_ Order_Id : 14
Order_Date : 1-08-2019
P1:Product P2:Product
Product_Id : 1 Product_Id : 2
Product_Type :Veg Pizza Product_Name : Non-Veg
Item Name: Peppy Paneer Pizza
Item Name: Chicken
Dominator
Sequence Diagram
:Customer Employee :Stock :Dealer
1.ProductEnquiry()
LookUpProduct()
2.Available()
3.ProductNotAvailable
PlaceOrder()
4.FullFillOrder()
5.ArrangeOrder()
COLLABORATION DIAGRAM
New Customer Entry:
1.1 Collect Information ()
1. New Record 1.2 Save Record ()

GE: User : Customer
Interface
Update Customer Entry:
Update Member 1.1 Search Record

Record 1.2 Update Record
GE: User : Customer
Interface
Delete Customer Entry:
Delete Member 1.1 Search Record

Record 1.2 Delete Record
GE: User : Customer
Interface
Customer Bill Entry:
: Paid bill
1.2 Receive Bill ()
1.3 Paid Bill ()
1.4 Save Bill ()

GE: User : Customer
Interface
System
Design
COMPONENT DIAGRAM
Manage DB
Access DB Customer
Database
Manage DB
Access DB Employee
Database
Manage DB
Product
Administrator
Type
Access DB
Database
Manage DB
Customer
Bill
Report Access DB
Database
Manage DB
Employee
Salary
Access DB
Database
Manage DB
Remaining
Bill
Access DB
Database
Package Diagram
User Report
Interface
Master Customer Bill
Information Employee Report
Transactions Product Type Structure
Reports Add Customer Form
Database
Customer
Employee
Product Type
Bill
Product Information
Deployment Diagram:
Database
DB: Database
Server
Printer Printer
System Admin
(Executable)
App. Common App.
Server (Executable)
Manage Res. Manage Project

Desktop Desktop
(Executable) (Executable)
Client Client
(Owner) (Clerk)
SYSTEM FLOWCHART:
Customer
Database
Create Customer
Create New
Customer Entry Record
Customer
Customer Report
Information
Member Lookup
Customer Bill
Database
Create Customer
Create New Bill
bill Record
Entry
Customer bill
Customer bill Report
Information
Employee Info
Database
Create Employee
Create New
Record
Employee Entry
Employee
Employee Report
Information
Employee Info
Database
Create Employee
Create New
Record
Employee Entry
Employee
Employee Report
Information
Employee Salary
Database
Create New Create New

Employee Salary Employee Salary
Entry Record
Employee
Employee Salary
Report Salary Information
Product Database
Create New Product

Create New Record
Product Entry
Product Report Product

Information
STRUCTURE FLOW CHART:
Online Pizza Ordering App
Customer Customer Bill Employee Product

Registration Information Information
Customer Registration
C_Id
C_Name
Address Registration Registration

Details Object
Contact
Registration Object
Product
Create New Registration Update/Delete

Registration
Customer
Bill
Customer_Id
Customer Name
Member
Product Details
Bill
Customer Object
Date
Customer Object
ADD Customer Update/Delete
Employee Info
Address
Employee
Schedule
Details
Salary
Joining Date Employee Object
Employee info
object
ADD New Employee Update/Delete Employee

Purchase Order Bill
Total Amt
Credit
Bill_Date
Company
BillId
Bill Detail
ADD New Purchase Order Bill


Pizza Ordering App: The Mumbai University, Mumbai

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pizza Ordering App: The Mumbai University, Mumbai

Uploaded by

Copyright:

Available Formats

PIZZA ORDERING SYSTEM 2019-2020

PIZZA ORDERING APP

The Mumbai University, Mumbai

Signature Of Signature Of Signature Of Signature Of

as a part of his curriculum for Degree in T.Y.B.Sc. ( I T) Year 2019-2020 of Mumbai

University.His work was satisfactory during the project period.

3.1 TECNICAL FEASIBILITY

3. 3.2 ECONOMICAL FEASIBILITY

Limitations of present system:

3. Retrieval of information and searching any old record is critical process.

Advantages of proposed system

2. Our Application saves time.

3. A large amount of data can be a save.

4. No reminder for customer and Purchaser.

5. Calculation has to be done directly & accurate.

6. Updating is not performed that efficiently and may lead complications.

7. No security as data can be misplaced or damaged.

8. A Application provide user friendly work environment.

Minimum 2 GB RAM required to run the system.

Minimum 20 GB HDD is necessary to deploy the system.

Pentium IV and above.

2] Operational Feasibility: - Operational feasibility study determines if the proposed system

Name Of The Phase Expected Actual Date Signature

Finalization & Allocation

Data & Process Modeling

Program Coding & Unit

Project Review By Guide

Feedback For Improving,

EVENT TRIGGER SOURCE ACTIVITY RESPONS DESTINATIO

Add New Adding New customer

Update Change in Updating Customer

Delete Delete Delete Customer Customer

Customer Customer Record Details Master

Add New Arrival of Employee Adding New Employee

Update Change in Updating Employee

Employee Employee Employee Employee Details Master

Record detail Record

Delete Delete Employee Delete Employee Master

Add New Arrival of new Manager Adding New Manager Master

Use case diagram:

2. Use Case for Customer:-

CUSTOMER Fill up information

3Use case for Employee

4)Use case for Supplier:

Entity Relationship Diagram

Address Purchase Product

1) Create Customer Record :

2) Update/Delete Customer Record:

Search Update/Delete Save

1) Create Employee Record :

Collect Fill Save

1) Update/Delete Employee Record:

Search Update/Delete Save

Customer Master Supplier Master

Employee Master Product Master

Customer Bill Order

Class Association Diagram:-

 Object Diagram Customer places many order:-

 Object Diagram for Order has Bill:-

 Object Diagram for Order includes many

:Customer Employee :Stock :Dealer

New Customer Entry: