0% found this document useful (0 votes)
179 views13 pages

Srs Template-Ieee

The document provides a software requirements specification for a restaurant management system. The system aims to help managers and workers manage restaurant operations and provide customer services. Key functions include allowing customers to order food and view menus, processing food orders in the kitchen, and managing finances. The system must be secure, fast, and able to handle any food order at any time to efficiently manage the restaurant's operations.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
179 views13 pages

Srs Template-Ieee

The document provides a software requirements specification for a restaurant management system. The system aims to help managers and workers manage restaurant operations and provide customer services. Key functions include allowing customers to order food and view menus, processing food orders in the kitchen, and managing finances. The system must be secure, fast, and able to handle any food order at any time to efficiently manage the restaurant's operations.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Software Requirements Specification

For

Restaurant
Version 1.0 approved

Prepared by Team

FCAI-H

2019/2020

ID Name
20170024 ‫احمد راضي عبدالاله‬
20170021 ‫احمد حسين‬
20170034 ‫احمد صابر‬
20160340 ‫محمد جمال‬
20170640 ‫يارا يحيي محمد‬
20170600 ‫نهي عبدالسالم حمدى‬
20120514 ‫ندى جمال سيد‬
Software Requirements Specification for Restaurant Page ii

Table of Contents

1. Introduction ......................................................................................................................... 1
1.1 Purpose ....................................................................................................................................... 1
1.2 Product Scope ............................................................................................................................. 1
1.3 Definitions , acronyms, abbreviations .......................................................................................... 2
1.4 References................................................................................................................................... 2
1.5 Overview .................................................................................................................................... 3
2. General description ............................................................................................................. 4
2.1 Product Perspective ..................................................................................................................... 4
2.2 Product Functions ....................................................................................................................... 4
2.3 User Characteristics .................................................................................................................... 5
2.4 General constraints ...................................................................................................................... 5
2.5 Assumptions and dependencies .................................................................................................... 6
3. Specific requirements .......................................................................................................... 7
3.1 Functional ................................................................................................................................... 7
3.2 Non-Functional ........................................................................................................................... 9
4. Results ................................................................................................................................ 10
4.1 Evaluation of the current System ............................................................................................... 10
4.2 problems of the current System .................................................................................................. 10
4.3 problems of the current System and its solutions ........................................................................ 10
Software Requirements Specification for Restaurant Page 1

1. Introduction

This SRS document is about Restaurant system So it’s our main reference for the
project as a whole. In general, The Restaurant management system is based on
computer technology that gives service for users, managed by the Restaurant who give
implementation of function relatively in effective times as well as will design for
removing time wasting, saving resources, easy data access of security on data input
and data access by removing almost manual based system

1.1 Purpose
The purpose of this project is to help manager for Restaurant systems in order
to manage restaurant , Help workers work and provide services to customers.
It will also describe how the system will perform and under which it must
operate.

1.2 Product Scope


The customer can order food and tell the restaurant’s menu and
can close the order. The cashier can make the request to the
customer, add the meals in the kitchen, and delete the meals that
are not available from the menu, and when sending a report, both
the kitchen and the manager can tell it. When the report is received,
the kitchen sends the food; the cashier can add the food to the food
list and adjust the existing amount. When a new customer arrives,
the cashier can add it to the system, because in the future, offers
will be added to the old customers and add offers. The cashier can
amend the customer information on the system.
Software Requirements Specification for Restaurant Page 2

1.3 Definitions, acronyms, abbreviations

Term Definition

System User A person who is using or operating the system but with a
limited privilege.

Database Collection of all the information monitored by this system.

Software Requirements A document that completely describes all of the functions


Specification (SRS) of a proposed system and the constraints under which it
must operate. For example, this document.

Manager Any person who is involved in the development process of


the software.

RMS Restaurant Management System.

Acronyms and abbreviations


PMS- Restaurant management system.
JDK- java development kit
IDE- integrated development environment

1.4 References
www.google.com-the world's information.
www.wikipedia.com-free online encyclopedia.
Software Requirements Specification for Restaurant Page 3

1.5 Overview
The following sections of this document will cover the functionalities of the Restaurant system and
its development, the second section is covering the general description of the system, the system
functional and non-functional requirements are covered in the third section, then the fourth section
is covering the evaluation of the system and the suggested solutions for the current system, the last
section will cover the appendices of the document and the index.
Software Requirements Specification for Restaurant Page 4

2. General description

2.1 Product perspective

system is used in the restaurant in ordering to facilitate the


interaction between customers and the kitchen ,It works to manage
customer orders and organize them consistently in order to
manage the kitchen and deliver the order to the customer in a
timely manner, In addition, it manages the store and finances in
terms of the daily income of the restaurant and invoices.

2.2 Product functions:

Customer:
2.2.1 Customer order
2.2.2 customer details
2.2.3 sent reports

Cashier:
2.2.4 Transfer food order
2.2.5 Print Bill
2.2.7 Update sold goods

Goods:
2.2.8 Modifying system
Software Requirements Specification for Restaurant Page 5

2.3 User characteristics

Users of this system are (customer , kitchen and manager)

customer: He can access in system to order foods and receive bill.

kitchen : That cook the food and receive it to system to receive it to


the customer.

Manager: He has access to all high-level permissions and funcations


in the system.

2.4 General constraints

o The system must be very secure and accurate.

o The System should be interactive and fast for every action-


response.

o The program can be modified to change requirements if


required.

o The System software can be easily repaired if a fault occurs


to manage any order foods at any time.

2.5 Assumptions and dependencies


Software Requirements Specification for Restaurant Page 6

The system should provide fast access to database. If this system have IOS and
Windows app then customers who use such kind of smartphone (windows and IOS)
will be more benefited. If there are more Tablets for each tables the whole system
performance will be better.
Software Requirements Specification for Restaurant Page 7

3. Specific requirements

3.1 Functional:

3.1.1 Place Order:


The system will give customers the ability to place their orders using our product. It
will display a list of dishes in the menu. Customer will be able to select multiple dishes
and their quantity for a particular order.

3.1.2 Transfer Order:


Whenever a new order is placed by the Customer, the dishes in the orders are
classified into categories. The system will assign each dish to the kitchen and place it
in the order queue.

3.1.3 Request Bill:


After ordering, the customer will pay for his/her order cash or by
credit card and the system will save the money in data store.

3.1.4 Save Customer Details:


When the customer place the order if he/she is a new customer, then the manger will
save the customer details (Name/ID) in the customer data store.
Software Requirements Specification for Restaurant Page 8

3.1.5 Update Sold Goods:


After placing the order, the system will add the order details (Name of order/Quantity)
to the sold goods data store.

3.1.6 Modify The System:


The manager only can control the system and he/she can add or delete items from the
inventory data store according to the reports received.

3.1.7 Generate Report:


The system will retrieve the data from sold goods data store, money data store and
inventory data store to make delay report, store this reports in delay report data store
and send this report to the manager of the restaurant.
Software Requirements Specification for Restaurant Page 9

3.2 Non-Functional:

3.2.1 Performance:
The System should be interactive and fast for every action-response, The system shall
support at least 2 transactions per second

3.2.2 Reliability:
No matter the num of orders are pleased, The system must return the correct result

3.2.3 Usability:
The software of the system should be easy to use and it doesn't be complex to user
have a view ,So it should be simple

3.2.4 Portability:
The software can be easily installed on devices and run according to the requirements

3.2.5 Flexibility:
If need arises in the future ,software can be modified to change the requirements

3.2.6 Maintainability:
The System software can be easily repaired if a fault occurs
Software Requirements Specification for Restaurant Page 10

4. Result

4.1 Evaluation of the current System:


The current system is manual so Every process is in slow progress and
there is many problems

4.2 problems of the current System and its solutions:


4.2.1 Sales are few
4.2.2 System slow

4.3 problems of the current System and its solutions:


4.3.1 Solve Problem (4.2.1): We have made offers for all old
and new customers.
4.3.2 Solve Problem (4.2.2): Improving user algorithms and
continuous system development.
Software Requirements Specification for Restaurant Page 11

You might also like