Software Requirement Specification For Yummy Tummy Restaurant Management System

You might also like

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

SRS FOR YUMMY TUMMY DESIGN ENGINEERING

Software Requirement Specification For


YUMMY TUMMY
Restaurant Management System

Prepared by

JHA SHWETA RAVISHANKAR

170280107043

MISTRY AYUSHI

170280107057

MODI DHRUVI

170280107058

2
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

Table of Contents

1 Introduction 3

1.1 Purpose 3

1.2 Scope

1.3 Overview 4

2 The Overall Description 4


2.1 Product Perspective 4
2.1.2 Software Interfaces 4
2.2 Product Functions 4

2.3 User Characteristics 5


2.4 Apportioning of Requirements 5
2.5 Assumptions and Dependencies 5

3 Specific Requirements 6

3.1 External Interfaces 6


3.1.1 User Interfaces 6
3.1.2 Software Interfaces 6
3.1.3 Hardware Interfaces 6
3.1.4 Communication Interfaces 7
3.2 Functional Requirements 7
3.3 Nonfunctional Requirements 9
3.3.1 Performance Requirements 9
3.3.2 Logical Database Requirements 9
3.3.3 Design Constraints 10
3.3.4 Standards Compliance 10
3.3.5 Reliability 10
3.3.6 Availability 10

3
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

3.3.7 Security 10
3.3.8 Maintainability 10
3.3.9 Portability 10

4
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

1 Introduction
The digital era has made the tasks faster, more accurate increased satisfaction and have
brought in robust solutions. The whole world is on internet and if you wish to grow your
business then being online is a necessity. We introduce a new concept of booking your
table instantly through application which will attempt and seek an easier, faster,
accurate and improvised services that satisfies the craving just the way how we like it. It
will also provide flexibility and transparency at the customer end which will ultimately
offer the best options that match your choice and make the important people feel their
significance in your life.

1.1 Purpose
• BOOK TABLES INSTANTLY
• NO MORE STANDING IN LONG QUEUES AND WASTING TIME
• GET INSTANT ADVICE TO ENJOY NEW SPECIALTIES
• MAKE PRIOR PAYMENTS ONLINE
• NO MORE HELTER SKELTER WITH THE BILLS

1.2 Scope
• TABLE BOOKING
• BILL CALCULATOR
• ONLINE PAYMENT
• CHOICE FILTER
• USER ACCOUNT HISTORY

1.3 Overview
The hotel management system basically focuses on prior reservation of tables so
that there is no standing in queues. It allows prior preparation of food so that
there is no waiting for food and to allow online payments. People can choose their
favourite hotels on the basis of cuisine, location, number of people, etc and book
their table and menu from the comfort of their home.

5
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

2 The Overall Description


In 21st century the internet explosion is so tremendous that there exists no such
business you can’t find on internet. It’s very common to find someone special whom you
need to make feel significant in your life. It can be your boss, your family, a stake
holder, your spouse, a business partner, your kids, special guests, etc.

Food is the best way to people’s heart. So here we bring a new online application that
can offer you the perfect environment along with scrumptious and healthy food just the
way you like it served instantly without any hassle of cash payments and bills. We
believe that satisfaction is the key to happiness. People must be satisfied with the
service they seek. This application provides the best options that match your choices to
the point and satisfy the craving for food.

2.1 Product Perspective


The yummy tummy software aims to schedule your booking beforehand and allows the
preparation of food before your arrival to save your precious time and serve their best.

2.1.1 Hardware Interfaces


The yummy tummy software will be placed on PC’s in all restaurants and can be
accessed through mobiles, tabs, laptops and pc’s.

2.1.2 Software Interfaces


Database will be configured in mysql workbench. It stores the following information:

Person details: first name, last name, phone number, number of people

Booking details: assigned table number, chosen dish from menu, total amount

Payment details: credit card number, confirmation number

Time details: automatic cancellation time, arrival time, departure time

Feedback: customer feedback and ratings.

6
SRS FOR YUMMY TUMMY DESIGN ENGINEERING
2.2 Product Function
➢ TABLE BOOKING: helps find tables based on: -
• Location as suggested: customer can choose the location of table like
outdoors, in the garden, on the terrace, in ac rooms, near the window,
near the orchestra, etc.
• No. of people: The number of people invited can help find the perfect
table for you so that all can sit together and enjoy.
• Hotel: this criterion can be chosen by the customers according to their
convenience.
➢ BILL CALCULATOR AND SETTLER :- helps get rid of the helter skelter of the
bills
• Calculates total amount payable
• Finds and avails offers
• Enables online payment
➢ CHOICE FILTERS :- filters choice based on
• Choice of cuisine
• No. of people
• Time and date of booking
• Location or view as suggested
➢ EXCEPTIONAL CASES:- allows treating special cases
• When a customer checks out the amount owed is displayed
• If the internal clock states that customer has exceeded his time to
have checked out then adds an extra amount and provides a report.
• If any extra order is placed then its tracked and amount is added to
the extra amount.
➢ General Management Services and Automated Tasks System
o Reports are automatically generated to provide current occupancy
status online to the application
o Creation of users and assigning passwords

2.3 User Characteristics


Educational level of yummy tummy computer software – Low

Experience of yummy tummy software – None

Technical Expertise – Little

2.4 Apportioning of Requirements


The audio and visual alerts will be deferred because of low importance at this time.

2.5 Assumptions and Dependencies


• The system is not required to save generated reports.
• Assuming user can make only one account with one phone number

7
SRS FOR YUMMY TUMMY DESIGN ENGINEERING
The sequence diagram:

8
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

9
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

The use case diagram:

10
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

11
SRS FOR YUMMY TUMMY DESIGN ENGINEERING

12
SRS FOR YUMMY TUMMY 170280107043

3 Specific Requirements
• MENU- shows a brief content of restaurant services
• BILL CALCULATOR- calculates bills and avails offers
• FILTERS- to classify and specialize the choices of the user
• FEEDBACK, REVIEWS AND RATINGS- to collect feedback
• ONLINE ENABLED PAYMENT- for the ease of proximity
• USER ACCOUNT- for maintaining basic details of user
• MOBILE/LAPTOP/TABLET- device to run the app

3.1 External Interfaces


The Hotel Management System will use the standard input/output
devices for a personal computer. This includes the following:
• Keyboard
• Mouse
• Monitor
• Printer

3.1.1 User Interfaces


The User Interface Screens are described in table 1.
Table 1: Hotel Management User Interface Screens

screen Description

login Login with user credentials

Select cuisine/ hotel or select from To choose a hotel by its name or dish

suggestions

Time page Select entry and exit time and availability

View menu To choose your desired dish

Select number of members To book the seats on table

summary Summarises all your selections and total

payable amount/ also allows to add or remove

items

11
SRS FOR YUMMY TUMMY 170280107043
Payment page Collects card details and password

Otp page Asks use to enter otp and proceed with final

payment

Confirmation page Shows successful payment acknowledgement

and email

Internal clock Saves a reminder for the upcoming booking

3.1.2 Software Interfaces


The system shall interface with an Oracle or Access database.

3.1.3 Hardware Interface


The system shall run on a Microsoft windows based operating system

3.1.4 Communication Interfaces


The system shall be a standalone product that does not require any communication
interfaces.

3.2 Functional Requirements


Functional requirements define the fundamental actions that system must perform.

The functional requirements for the system are divided into two main categories,
Reservation/Booking and Management. For further details, refer to the use cases.

1. Reservation/Booking

1.1. The system shall record bookings.

1.2. The system shall record the customer’s first name.

1.3. The system shall record the customer’s last name.

1.4. The system shall record the number of members.

1.5. The system shall record the table number.

12
SRS FOR YUMMY TUMMY 170280107043

1.6. the system shall record the entry and exit time

1.7. The system shall display the total payable amount.

1.8. The system shall record the customer’s phone number

1.9. The system shall generate a unique confirmation number for each
reservation.

1.10. The system shall check-in customers.

1.11. The system shall allow reservations to be modified without having to reenter all
the customer inforamtion.

1.12. The system shall checkout customers.

1.12.1. The system shall display the amount owed by the customer.

1.12.2. The system shall record the payment.

1.12.3. The system shall record the payment type.

1.13. The system shall charge the customer for an extra time if customer exceeds
the exit time

1.14. The system shall record customer feedback.

2. Management
2.1. The system shall display the table occupancy for a specified period of time
(entry time to exit time).

2.2. The system shall display an exception report, showing where table and food
prices have been overridden.

2.3. The system shall allow for the addition of information, regarding rooms, rates,
menu items, prices, and user profiles.

2.4. The system shall allow for the deletion of information, regarding rooms, rates,
menu items, prices, and user profiles.

2.5. The system shall allow for the modification of information, regarding rooms, rates,
menu items, prices, and user profiles.

2.6. The system shall allow managers to assign user passwords

3.3 Nonfunctional Requirements


NON Functional requirements define the needs in terms of performance, logical
database requirements, design constraints, standards compliance, reliability,
availability, security, maintainability, and portability.

13
SRS FOR YUMMY TUMMY 170280107043
3.3.1 Performance Requirements
Performance requirements define acceptable response times for system functionality.

• The load time for user interface screens shall take no longer than two seconds.

• The log in information shall be verified within five seconds.

• Queries shall return results within five seconds.

3.3.2 Logical Database Requirements


The logical database requirements include the retention of the following data
elements.

Booking/Reservation System

• Customer first name


• Customer last name
• Customer address
• Customer phone number
• Number of members
• Assigned table
• Total amount
• Selected dishes/ menu
• Credit card number
• Confirmation number
• Expected check-in date
• Expected check-in time
• Actual check-in date
• Actual check-in time
• Expected check-out date
• Expected check-out time
• Actual check-out date
• Actual check-out time

14
SRS FOR YUMMY TUMMY 170280107043

• Customer feedback
• Payment received (yes/no)
• Payment type
• Total Bill

3.3.3 Design Constraints


The yummy tummy software shall be a stand-alone system running in a Windows
environment. The system shall be developed using Java and an Access or Oracle
database.

3.3.4 Standards Compliance


There shall be consistency in variable names within the system. The graphical
user interface shall have a consistent look and feel.

3.3.5 Reliability
Uses deadlock algorithms to maintain system consistency, uses mysql db to
maintain data security, uses account logins and passwords for security at user level,
uses 4 level security (i.e the login,the cvv number, the password, the otp) before
payment

3.3.6 Availability
The system shall be available during normal restaurant operating hours.

3.3.7 Security
Customer Service Representatives and Managers will be able to log in to the
restaurant Management System. Customer Service Representatives will have access
to the Reservation/Booking subsystems. Managers will have access to the
Management subsystem as well as the Reservation/Booking. Access to the various
subsystems will be protected by a user log in screen that requires a user name and
password.

15
SRS FOR YUMMY TUMMY 170280107043

3.3.8 Maintainability
The Restaurant Management System is being developed in Java. Java is an
object oriented programming language and shall be easy to maintain.

3.3.9 Portability
The Hotel Management System shall run in any Microsoft Windows environment
that contains Java Runtime and the Microsoft Access database

16
SRS FOR YUMMY TUMMY 170280107043

CONCLUSION
The “ONLINE TABLE BOOKING” brings the best possible service to your table in
fastest and most efficient way. The table booking gets the dishes served just the way
you like it with the most suitable environment to support your mood. The online
payment method is secure and helps you get rid of the unnecessary hassle of bills.
People will be allowed to comment and share reviews about their services which will
provide best recommendations. This application satisfies all cravings of food and
helps your special guests feel their significance in your life.

REFERENCES:
https://play.google.com/store/apps/details?id=com.
dineout.book
https://play.google.com/store/apps/details?id=biz.di
dan.caferestoran
https://play.google.com/store/apps/details?id=de.q
uandoo.android.consumerapp
https://m.coruscatesolution.com/make-restaurant-
table-booking-app/

17
SRS FOR YUMMY TUMMY 170280107043

You might also like