Fast Food Billing System

INTRODUCTION:
This system is named as Restaurant billing system source code. This is designed
especially for a restaurant which wants to attend their customers in a very well
manner.This system has the capability to take the orders from the customers.

It generates unique transaction id for that according to the selection of the mode
of payment.

He can opt for his choice of payment. This system has the capability of
calculating the bill according to the total number of the item ordered and taxes
are also added accordingly then shown to the customer in a proper bill.

REQUIREMENT ANALYSIS:
1. Functional Requirements:
A) Customer:
 A customer shall be able to engage their menu by double tapping
the activated surface computer in their table.
 A customer shall be able to dismiss their menu by double tapping
its dismiss option.
 A customer shall be able to navigate through the available items in
their engaged menu.
 A customer shall be able to cancel an order through their engaged
menu if it is pending and not yet placed.
 A customer shall be able to engage bill mode to finalise payment
through their engaged menu.
B) Waiter:
 A waiter shall be able to log into a tablet using their assigned
username and password.
 A waiter shall be able to activate a surface computer and
consequently open its associated account through a tablet.
 A tablet shall allow a waiter to accept an order placed by a
customer through a surface computer.
  A tablet shall allow a waiter to process a payment using
cash/bankcard.
C) Chef:
 A chef shall be able to accept a customer’s order item through a
display.
 A chef shall be able to reject a customer’s order item through a
display.
 A chef shall be able to indicate that a customer’s order item is
ready to be served through a display.
D) Supervisor:
 A supervisor shall be able to do everything a waiter can.
 A supervisor shall be able to do everything a chef can.
 A supervisor shall be able to abort/purge a customer’s meal from
the active system with no expectation of payment.
 A supervisor shall be able to abort/purge a table's account/meals
from the active system with no expectation of payment.
 A supervisor shall be able to issue a refund for one or more items
to a customer
2. Non-Functional Requirements:
A) Safety:

 The system shall log every state and state change of every surface
computer, tablet and display to provision recovery from system
failure.
 The system shall be capable of restoring itself to its previous state
in the event of failure (e.g. a system crash or power loss).
 The system shall be able to display a menu at all times to facilitate
manual order taking should the need arise.
 The system shall utilise periodic 30-second keep-alive messages
between tablets and the server to monitor tablet operational status.
 The system shall flag tablets that fail to send timely keep-alive
messages as non-operational and disassociate the assigned waiter
from the tablet.

B) Security:
  Wireless communication throughout the system will be encrypted
using SSLv3 at the application layer and WPA2-PSK at the data
link layer.
 The WPA2-PSK password used for wireless communication must
be changed every three months.
 A waiter password used for tablet login must be changed every
three months.
 A waiter shall only be able to log into one tablet at any given
instance of time.
 A surface computer shall not require a user to log in.

C) Performance requirements:

 The server shall be capable of supporting no less than 200

concurrent connections from any combination of surface
computers, tablets and displays.
 The server shall be capable of supporting an arbitrary number of
surface computers, tablets and displays, that is, it shall provide no
limit on how many devices are in the system.
 The server shall be capable of supporting an arbitrary number of
active meals/orders, that is, no meals/orders shall be lost under any
circumstances.
 The server shall be capable of supporting an arbitrary number of
active customer payments, that is, no payments shall be lost under
any circumstances.

3. Modules of fast food billing system:

There are several modules required to complete this system. Here we are
discussing the main modules or core modules of the system.
A) Registration:
User’s data need to be registered in the system so as to identify each of them
uniquely and do the-the needed transaction as easy possible .like on the name of
the bill will be issued. Beyond this, a lot of things are there where we can
reference him.

B) Login:
After registration one can log in the system as the operator of the system either
on the behalf of user. After this, he has the other user interfaces available for
further actions.
C) Select Item:
Here we have the option to select the items we needed to get eat. On demand,
we have options to search according to the various filters like the taste of food
on the basis of rating, feedbacks, beverages, fast food, continental, state wise,
healthy food, compliments etc.

Here onward one can select on the basis of filters according to price, newly
added, special dish and much more us here. Further, he can select as much as he
can and added to his account in a very pleasant user interface.

D) Place Order:
After the successful selection of the item now he has the option to place the
order. Here customer confirmation is required on the basis of the order will be
placed.

E) Bill:
Now bill of the order will be prepared according to the items selected and
further needs to shown to the user. Here tax calculation is also considered and
then this is passed to total calculation and then bill according to the all is shown
to the user and then payment part comes.

F) Payment:
Payment is selected by the customer either it is cash mode or by debit card or
credit card as he demands the bill of the payment and order is collected by the
customer after the successful payment and fed into the system.

USE CASE DIAGRAM:

DATA FLOW DIAGRAM(DFD):