Scribd
Upload
451 views8 pages

Pizza Ordering Management System

The document describes the requirements for a Pizza Ordering Management System. It includes 4 sections that cover: 1) an introduction describing the purpose and scope of the project, 2) an overall description of product functions and user characteristics, 3) specific requirements around interfaces, functionality, performance, security, and capacity, and 4) data flow diagrams at multiple levels to depict system processes and data flows. The system will allow customers to order pizza online, check availability and prices, and pay for orders, while also providing manager access to booking details and reports.

Uploaded by

atik pal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
451 views8 pages

Pizza Ordering Management System

The document describes the requirements for a Pizza Ordering Management System. It includes 4 sections that cover: 1) an introduction describing the purpose and scope of the project, 2) an overall description of product functions and user characteristics, 3) specific requirements around interfaces, functionality, performance, security, and capacity, and 4) data flow diagrams at multiple levels to depict system processes and data flows. The system will allow customers to order pizza online, check availability and prices, and pay for orders, while also providing manager access to booking details and reports.

Uploaded by

atik pal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

PIZZA ORDERING MANAGEMENT

SYSTEM
Software Requirement Specification
Table of Contents:

1. INTRODUCTION:

Purpose
Scope of the Project
System Overview
References

2. OVERALL DESCRIPTION:

Product Functions
User Characteristics
Design & Implementation Constraints

3. SPECIFIC REQUIREMENTS:

External Interface Requirements


Functional Requirements
Performance Requirements
Security & Safety Requirements
Capacity & Availability Requirements

4. DATA FLOW DIAGRAM:

0-level DFD
1-level DFD
2-level DFD
1) INTRODUCTION:

The Pizza Ordering Management System is a tool for ordering pizza through online by the
customer. It provides the proper management tools and easy access to the pizza menu
information.

Purpose:

This Pizza Ordering Management System Software Requirement Specification (SRS) main
objective is to provide a base for the foundation of the project. It gives a comprehensive view of
how the system is supposed to work and what is to be expected by the end users.

Scope of the Project:

The Pizza Ordering Management System’s SRS document is intended for ordering pizza
through online. Pizza Ordering Management System will consists of Booking Management
System, DBMS Server, and Receipt Generator. Customers will be able to check for pizza’s
availability, select the pizzas, and pay for the pizzas. Manager will have access to update or
modify booking details. HOD will able to view the book status report and able to update book
information such as author and category.

System Overview:

The remaining sections of this documentations describes the overall descriptions which
includes product perspective and functions, characteristics of users. It also consists of
Assumptions, and Constraints.

References:

[1] Software Engineering 9th Edition, Ian Sommerville


[2] Fundamentals of Database System, 6th Edition, Ramez Elmasri, Shamkant B. Navathe
[3] Requirement Engineering: https://dipeshagrawal.files.wordpress.com/2018/07/srs-
Library- management-system-ok.pdf
[4] Data Flow Diagram: https://www.geeksforgeeks.org/what-is-dfddata-flow-diagram/
2) OVERALL DESCRIPTION:
Product Functions:

Our Product General functions are:


 Customer Registration
 Check for Availability Of Pizzas
 Display the Variety and Prices
 Confirmation Of Granting
 Email Notification
 Free Delivery(If Late)
 Set Pizza Details
 Manage Pizza Details
 Generate Receipt
 Customer Service

User Characteristics:

There are 5 user Levels in our Pizza Management System:


A. Customer
B. Cook
C. Staff
D. Manager
E. Delivery Partner

 Manager:
Manager have every access to the Pizza system. Manager is solely responsible for managing Pizza
resources and staffs. Manager can view any report such as pizza status report, customer information,
granting information , analyze them and take the decision accordingly.

 Cook:
Cook’s sole purpose is to provide the quality customer service. He/She have lesser access than Manager.
He/She can cook the ordered pizza. He/She can search for availability of pizza’s resources, add the
customer, confirm the granting, and update the requesting details.

 Staff:
Staff’s sole purpose is to provide the quality customer in the shops and to help the cook with their
necessary errands. Staff cleans the kitchen and the food making utensils in a hygienic manner.

 Delivery Partner:
Delivery partner is also an essential part in this system. After making of customer’s order the delivery
partners then deliver this pizza within 30 mins. If they cant deliver within the time limit then the
company will give a free pizza to the customers. The amount or the price of the extra pizza will be
deducted from the delivery partner’s salary.

 Customer:
Customers are vital part of the system. customer have access to view the menu information and price
range. They should be able to request the book and cancel it if necessary. Customers have access to
Customer service desk portal to forward their inquiry. Customer should at least be capable to use the
web UI interface.
Constraints

 Memory: System will have only 10GB space of data server.


 Language Requirement: Software must be only in English.
 Budget Constraint: Due to limited budget, POMS is intended to very simple and just for
basic functionalities. UI is going to be very simple.
 Implementation Constraint: Application should be based on Java only.
3) SPECIFIC REQUIREMENTS:

External Interface Requirements :

The user interface for system shall be compatible to any type of web browser such as
Mozilla Firefox, Google Chrome, and Internet Explorer.

Functional Requirements:

 Registration
 Logging in
 Requesting Pizzas
 Manager Access
 Fine Management System

Performance Requirements:

 Data in database should be updated within 2 seconds.


 Query results must return results within 5 seconds
 Load time of UI Should not take more than 2 seconds
 Login Validation should be done within 3 seconds
 Response to customer inquiry must be done within 5 minutes.

Security & Safety Requirements:

 All external communications between the date's server and client must be encrypted
 All data must be stored, protected or protectively marked.
 Payment Process should use HTTP over Secure protocol to secure the
payment transactions
 Database should be backed up every hour.
 Under failure, system should be able to come back at normal operation under an hour.

Capacity & Availability Requirements:

 Not more than 10,000 members to be registered.


 System need to handle at least 20 transactions during peak hours.
 Report should be generated automatically every day for manager and anytime
upon request
4) DATA FLOW DIAGRAM:

0-level DFD

1-level DFD
2-level DFD

You might also like