ONLINE RESTAURANT TABLE RESERVATION

Purpose
In proposed ordering system we provide facility customers to reserve tables for dining, and can
also get details of hall availability for reservation of party and celebrations. At the same time
this online reservation system will provide the restaurant owner to manage their services
including food.
This documents includes detailed information about requirements of project. It reflects
identified constraints and purposed software functionalities, also specify functional and
nonfunctional requirements.

Scope
The scope of this application include reserve table for dining online, also get details of hall
availability for reservation of party and celebrations. At the same time this online reservation
system will provide the restaurant owner to manage their services including food. Currently
proposed system will be fast and easy to use and involves the application of five modules which
are the reservation, the order takeaway, your order gallery and contact us. This system will
managed by two main android applications, first one would be available for general customers
for viewing and booking of table and halls. Second would be used by the admin to manage the
services with in the restaurant premise.

Requirements specification:
 Functional Requirements
 Non Functional Requirements
Functional Requirements:
The main function of this application is online table reservation.
A. Table Reservation:
The main function of this application is online table reservation user can reserve any table
through this application anytime and from anywhere.
B. Hall Booking: The second main function is user can book hall using this app also cancel
booking when they need.
C. Food Ordering: User also can order their favorite food using this application by just filling the
form.
D. Contact Us: User can contact with hotel admin any time using this application.

Use Cases
  Log in
 Manage Order
 Mange Customer
 Mange Table
 Manage food
 Manage Bookings
 View Bookings
 Reserve Table
 View Food
 Book Hall
 Place Order
 User class 1-Customers, User class2-Admin

Functional requirement 1.1

ID: UC1
Title: Login
Primary Actor: Admin, Customer
Stakeholders:
1-Customers: can logs into the system for booking and also view booking details.

2-Admin: logs into the system to manage the classes time table.

Precondition: User must be registered.

Post condition: User successfully logs into the system.
Success Scenario:
1-User wants to login into the system.

2-System Prompts to the user to enter his/her username and password.

3-User enter his/her username and password.

4-User successfully log into the system.

Alternative Flow:
*a. At any time, System fails:
1. user restarts System, logs in, and requests recovery of prior state.
2. System reconstructs prior state.
2a. System detects anomalies preventing recovery:
1. System signals error to the user, records the error, and enters a clean
state.

3a- user enters the wrong password or username.

1. System shall prompts the user again enter the username and password until it is correct.

Special Requirement:
1- System response to the user within 30 seconds.
2- Language internationalization text displayed.

Technology and Data Variations:

1-Technology and data variation is not applicable.

Frequency of Use:
Could be used frequently.

Open Issues:
Person has not the internet access.

Functional requirement 1.2

ID: UC2
Title: Manage Order
Primary Actor: Admin
Stakeholders:
1-Admin: Manages all the bookings and food order reserve for the reserve table.

Precondition: User must be authenticated.

Post condition: All orders manages successfully.

Success Scenario:
 1-User wants to manage all the orders.

2-System Prompts to the user either he want to manage booking details or food orders details.

3-User select the option and manage the details.

4-User successfully manages all the orders.
Alternative Flow:
*a. At any time, System fails:
3a- There are no orders there to manage.

Special Requirement:
1- System response to the user within 30 seconds.
2- Language internationalization text displayed.

Technology and Data Variations:

1-Technology and data variation is not applicable.

Frequency of Use:
Could be used frequently.

Functional requirement 1.3

ID: UC3
Title: Reserve table
Primary Actor: customer
Stakeholders:
1-Customer: Customer reserve table online without making any effort.

Precondition: User should be register.

Post condition: Request for reservation of table successfully sent.

Success Scenario:
1-User wants to reserve table.

2-user should have an account on the app.

3-system then search the register restaurant.
4-User select the desire restaurant.

5- User select the table of type 2-sitter, 3- sitter etc.

6- User the send the request for reservation of table.

7- Request for reservation of table successfully sent.

Alternative Flow:
*a. At any time, System fails:

2a-User don’t have account

1:User should have to create an account first

4a-no restaurant is register to app.

Special Requirement:
1- System response to the user within 30 seconds.
2- Language internationalization text displayed.

Technology and Data Variations:

1-Technology and data variation is not applicable.

Frequency of Use:
Could be used frequently.

Open Issues:
Person has not the intranet access.

Use Case Diagram:

Non-Functional Requirements:
A. Performance Requirements: In order to assess the performance of a system the following
must be clearly specified.
B. Response Time: 10 seconds are about the limit for keeping the user’s attention focused on
the dialogue. For longer delays, users will want to perform other tasks while waiting for the
computer to finish, so they should be given feedback indicating when the computer expects to
be done.
C. Workload: The system should be capable of supporting 1,000 customers” or “the system
should be able to support 4 pages/sec”. These statements are often good metrics at a high level
management level but do not define the work that the system must support.
D. Scalability: In one respect scalability is simply specified as the increase in the system’s
workload that the system should be able to process.
E. Platform: A platform is defined as the underlying hardware and software (operating system
and software utilities) which will house the system. Our product support Android platform with
and later lollipop version.
F. Safety Requirements
We are used safety techniques for the following error
1) Software logic errors
2) Software support errors
3) Hardware failures
G. Security Requirements: Before you can determine if a program is secure, you need to
determine exactly what its security requirements are. So there is just one security requirement
for our product.
H. Database Security: For this security we are using firebase Database because without
authentication Firebase is not allowing to anonymous to read and write data in database.
I. Software Quality Attributes
1) Adaptability: This App can be installed on devices having android operating system.
2) Economic feasible: The developing app must be justified by cost and benefit.
3) Usability: This app is very useful and friendly for user, easy to use.

Date:26-03-2019