CONTENTS

1 INTRODUCTION
1.1 PURPOSE
1.2 SCOPE
1.3 DEFINITIONS,ACRONYMS AND ABBREVIATIONS
1.4 REFERNCES
1.5 OVERVIEW

2 OVERALL DESCRIPTION
2.1 PRODUCT PRESCRIPTIVE
2.2 PRODUCT FUNCTIONALITY
2.3 USERS AND CHARACTERISTICS
2.4 OPERATING ENVIRONMENT
2.5 DESIGN AND IMPLEMENTATION
2.6 USER DOCUMENTATION

3 SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE REQUIREMENTS
3.2 FUNCTIONAL REQUIREMENTS
3.3 BEHAVORIAL REQUIREMENTS
3.4 DESIGN CONSTRAINTS
3.4.1 SOFTWARE LANGUAGE USED
3.4.2 DEVELOPMENTAL TOOLS

4 OTHER NON FUNCTIONAL REQUIREMENTS

4.1 PERFORMANCE REQUIREMENTS
4.2 SAFETY AND SECURITY REQUIREMENTS
4.3 SOFTWARE QUALITY ATTRIBUTES

5 INTERFACES
5.1 USER INTERFACE
5.2 SOFTWARE INTERFACE
5.3 HARDWARE INTERFACE
5.4 COMMUNICATION INTERFACE
5.5 LICENSING REQUIREMENTS
5.6 LEGAL,COPYRIGHT ANDOTHER NOTICES
1 Introduction The
introduction of the Software Requirements Specification(SRS) will
provide a detailed description of the requirements for the Restaurant
Booking System. The SRS will provide a complete understanding of what
is to be expected from the newly introduced system is to be constructed.
The clear understanding of the system and its functionalities will allow
for the correct software to be developed for the end-user and will be used
for the development of the future stages of the project.
This SRS will provide the foundation for the project. From the SRS the
restaurant booking can be implemented,designed, constructed, and finally
tested. This SRS documentation of
Restaurant Booking System can minimize the food waste by making food
purchasing decisions based on variety of datas gathered from weeks,
months, or years of reservation history is a lot more accurate than buying
quantities based on a hunch. This
system shows the people are much more likely to leave an online rating or
review(feedback) determining the quantity as well as the quality of food
and also the service of restaurant staffs . We can send a follow-up survey
to get feedback that can help to improve the system. So, the owner of the
restaurant can evaluate any sort of problems in the whole system
1.1 Purpose The prupose of
Software Requirement Specification (SRS) document is to describe the
outline features/objectives of the Restaurant Booking System. This
system promotes the restaurant systemically and manage any kinds of
queries to be answered in online mode rather than depending on the
restaurant staffs or manager. The Owner can also hire less waiters and
create an opportunity to appoint high skilled chefs and better kitchen
workplace to provide food faster as possible as. (All the information about
daily expenses and profit will be saved in the system. Also the required
informations about employees will be stored in the system which can be
accesed only by the database admin). 1.2 Scope
The Software Requirement Specification (SRS)