Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Srs On Dominos

Download as pdf or txt
Download as pdf or txt
You are on page 1of 15

lOMoARcPSD|39584935

SRS on Dominos

Software Engineering (Lovely Professional University)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university


Downloaded by prudhvi danda (prudhvid77@gmail.com)
lOMoARcPSD|39584935

Software Requirement Specification


on

Domino’s Pizza Delivery System

Submitted by: Submitted to:

Austin Jacob Anil Anurag Sigh


Reg no: 12209074 Asst. Professor
Section: K22CG Lovely Professional University
Roll no: 54

Page 1

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

Table of contents:

1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1 Functional requirements . . . . . . . . . . . . . . . . . . . . . 4
3.2 Non functional requirements . . . . . . . . . . . . . . . . . 5
3.3 Interface requirements . . . . . . . . . . . . . . . . . . . . . . 6

4. System design . . . . . . . . . . . . . . . . . . . . . . . . . .7
4.1 Presentation layer . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Application layer . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Data management layer . . . . . . . . . . . . . . . . . . . . . 7

5. Use case diagram . . . . . . . . . . . . . . . . . . . . . . . 8


6. Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . .9
6.1 Zero level DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.2 Level one DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

7. Test cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11


8. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Page 2

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

1. Abstract:
As per the current scenario, pizza has became a favourite dish to all people in
this world irrespective of their age. So nowadays the need of an online pizza
delivery system is very important. It will helps us to order pizza in a very
efficient way within a small time period. This system replaces old pizza stores
where lots of crowd of people is there by online pizza booking system.
Moreover conventional pizza shops requires more manpower when compared
to online booking system.

2.Introduction:
Domino’s Pizza delivery system is a web-based application which enables
customers to order their pizza online for home delivery or pick up from the
pizza shop. It is a dedicated solution that helps us to manage deliveries and
takeaways. The software operates similarly to an online system where the
customer can order, complete payment and then get their pizza on their
doorstep. The customer can browse the menu from their own device. The
project will be based on Web Publishing System.

2.1 Purpose:
The purpose of this document is to present a detailed description of the
Web Publishing System of Domino’s online delivery system. It will
explain the purpose and features of the system, the interfaces of the
system, what the system will do, the constraints under which it must
operate and how the system will react to external stimuli.

2.2 Scope:
The Online booking system is an online web application that enables
users to place their orders online. Also the outlets agent had done the
same job when a user calls to them to place an order. The users also
able to track and edit their order. This web application makes the pizza
delivery faster and more efficient.

Page 3

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

3. Requirements:
3.1 Functional requirements:
Functional requirements are classified into three modules based on users. They
are:
Customer module
Employee module
Admin module

3.1.1 Customer module:


3.1.1.1: Sign up function
This module enables the new users to sign up by creating new
account. It takes input from the user and validate. As it got
information as per the requirements it will displays to the user
and stores the data in database.

3.1.1.2: Login
This function enables the existing user to login to their own
account by verifying their email and password. It takes input from
user and matches the data given by the user and existing data in
the database.

3.1.1.3 Search function


The module need to search the item given by the user as input.
The input will be containing the keywords of the product and as
an output function should return the product related to the
keyword.

3.1.1.4 Create new order


User must be able create new order by selecting their favourite
dishes.

3.1.1.5 Order status

Page 4

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

Customer must be able to edit, cancel and track their order and
update the edited order.

3.1.1.6 Change password


Customer must be able to change their password and login
credentials. And this change should also be made to database.

3.1.1.7 Cart function


The user selects the products and quantity of the product. These
items will be added to cart and final product price should be
displayed to user.

3.1.1.8 Payment
This module should display the sum of price of all products that
are added to the cart and the total amount should reflect through
the payment gateway. After payment it should reflect on the
account and save on the database.

3.1.2 Employee module:


3.1.2.1 Employee must be able log in and out by verifying their id.
3.1.2.2 Employee must be able to view the orders.
3.1.2.3 Employee must be able to update order status.

3.1.3 Admin module


3.1.3.1 Admin must be able to log in and out.
Admin can add users, employee and outlet into the system & can
edit their information & locations plus delete them from the
system as well.

3.1.3.2 Admin must be able to add/edit/delete orders


3.1.3.3 Admin must be able to view an order status
Admin can view orders of any outlet in form of report.

3.2 Non functional requirements:

Page 5

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

3.2.1 Performance
The system shall provide appropriate messages to the user as user
submits any inputs.
The speed of the application is one the main factor which determines
the performance. So that the acceptable time should be less than 10
seconds.

3.2.2 Security and Control


The main purpose of security is to protect from unauthorised access.
Access to the system and information must be controlled. Privacy
requirements i.e. password should be view in encrypted form. Criticality
of data necessitates the need for special handling (backup).

3.2.3 Usability
The users should be able to use the software in a convenient manner. So
that the software should be user friendly. User can easily navigate
through the interface and can easily determine the features of the
application.

3.2.4 Portability
The system should effectively work in all environments. The developer
should take care of this while designing. The application should function
properly on multiple devices to improve the portability. It should
consider the different media frames.

3.2.5 Maintainability
The system should be maintainable in such a manner that if any new
requirement occurs then it should be easily incorporated in an individual
module.

3.3 Interface requirements:


3.3.1 User interface
The user interface must be highly interactive so that all users may be
able to operate the system as easily and fluently. Graphical User

Page 6

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

Interface (GUI) can be used for creating home page with navigation bar
and other pages for respective categories.

3.3.2 Software interface:


Any browser with internet connection needed. PHP and MYSQL should
be installed.

4. System design
The system will use a multi-tier architecture, with separate layers for the
presentation, application, and data management.

4.1 Presentation Layer


The presentation layer will consist of a web-based user interface that
customers and restaurant employees can access using a compatible web
browser. The user interface will be designed to be user-friendly and easy
to navigate.

4.2 Application Layer


The application layer will contain the business logic and processing logic
of the system. This layer will be responsible for processing customer
orders, managing inventory, assigning delivery drivers, and updating the
status of orders and deliveries in real-time.

4.3 Data Management Layer


The data management layer will be responsible for managing the
system's data. This layer will include a database that will store customer
data, order data, delivery data, and inventory data. The data
management layer will also include APIs that will allow the application
layer to retrieve and manipulate data from the database.

Page 7

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

5. Use case diagram

Customer login
Admin

View menu

Customer Select an item

View total bill

Pick up or Delivery

Confirm order

Finish order

Customer pickup

Delivery order Delivery, Employee

Log out

Page 8

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

6. Data Flow Diagram


6.1 Zero level DFD:

Login

Customer order Dominos pizza delivery Admin


Payment system
Conformation

Zero level DFD

Page 9

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

6.2 Level one DFD:

Billing notice
User billing information
Billing
User Order
Cash
User data inflow
Return order Invoice
Receive User info
order Payment
Users
Users

Ship
Product
product
Order information
Product
Product info
Orders Distribution information

Product storage

Level One DFD

Page 10

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

7. Test cases
7.1 Test case 1

Test case ID: TS_1 Test designed by: Austin Jacob Anil
Test Priority(Low/Med/High) : Med Test designed date: 31/3/2023
Module name: Dominos login screen Test executed by: Austin Jacob Anil
Test title: Verify login with valid Test execution date: 1/4/2024
username and password
Description: Test the dominos login page
Pre conditions: User has valid username and password.

Slno. Test steps Expected output Actual output Status


(Pass/Fail)
1 Navigate to User navigated User navigated Pass
login page to login page to login page
2 Enter valid email Pass
3 Enter valid Pass
password
4 Click on login Logged in User redirected Pass
button successfully. to the
User should dashboard.
redirect to
dashboard.

Post conditions: User is validated with database and successfully login to account. The account
session details are logged in database.

Page 11

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

7.2 Test case 2

Test case ID: TS_2 Test designed by: Austin Jacob Anil
Test Priority(Low/Med/High) : Med Test designed date: 31/3/2023
Module name: Dominos signup screen Test executed by: Austin Jacob Anil
Test title: Creating a new account by Test execution date: 1/4/2024
using sign up page.
Description: Test the dominos signup page
Pre conditions: User should have a valid email and phone number.

Slno. Test steps Expected output Actual output Status


(Pass/Fail)
1 Navigate to sign User navigated to User navigated Pass
up page signup page to signup page
2 Enter valid email Pass
3 Enter valid Pass
phone number
4 Enter new Pass
password
5 Click on signup User successfully User Pass
button signed up. New successfully
account created. signed up. New
account
created.

Post conditions: User is able use all features that are available on his/her ’s
dashboard. Newly registered user can order pizza through this application.

Page 12

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

7.3 Test case 3

Test case ID: TS_3 Test designed by: Austin Jacob Anil
Test Priority(Low/Med/High) : Med Test designed date: 31/3/2023
Module name: Pizza booking screen Test executed by: Austin Jacob Anil
Test title: Ordering a pizza through Test execution date: 1/4/2024
Dominos pizza delivery system.
Description: Test the dominos pizza ordering page
Pre conditions: User should have a valid account and completed his/her profile
by giving address and contact details.
Slno. Test steps Expected output Actual output Status
(Pass/Fail)
1 Go to menu Should display all Items Pass
items from database displayed
2 Select Items Items should add to Items are Pass
and add to cart added to the
cart cart
3 Open cart Display cart with total Displayed cart Pass
amount to be paid with total
amount
4 Pay online Should return tracking Returned Pass
id tracking id
5 Track It should show the Location Pass
tracking id location of the order displayed

Post conditions: Pizza order successfully placed and user got a tracking id.

Page 13

Downloaded by prudhvi danda (prudhvid77@gmail.com)


lOMoARcPSD|39584935

8. Conclusion
Dominos online booking system will make a great impact on our conventional
stores with lots of new features and comfort. As it is an online platform,
customer is going to love it because it will save our lots of time in this busy
world. It is very easy to use and user friendly. It is going to be a new revolution
in this industry. Also it is going to be a solution for lot of existing problems.

Page 14

Downloaded by prudhvi danda (prudhvid77@gmail.com)

You might also like