Overview of The Restaurant Management System

Document Purpose

This paper presents a thorough description of the purposes, features, user interface and application of Restaurant Management System in real life. It will also describe how the system will execute and under which it must operate. In this paper it will be also shown user interface. Both the stakeholders and the developers of the system can acquire advantage from this paper.

Scope

This software system will design to efficiently manage restaurant business systematically. In this system, we will deliver application that can be consumed by customers to order foodstuff. Consumers can also provide his views through the application, so that management of the restaurant can assess the whole system. This will ultimately guide the management of the restaurant to efficiently manage its resources i. e. to employ fewer waiters and to appoint more cooks which will help in deliver of order quicker. Customers (end-user) can also pay bills through debit or credit cards using POS which will be integrated with the management software. Calorie chart of a food will be shown to the customers that will help in the selection of food according to their health. Information about employees will be saved in the system which can be only accessed by the system admin.

Intended Audience and Document Overview

This paper is subjected to different types of readers such as restaurant management, system designer, system developer and tester. By understanding this paper a reader can comprehend about what the project is implemented for and how it will present its basic ideas. This paper has a linear overview of the whole product so if a reader reads the paper from top to bottom; he will have a perfect picture about the product.

Definitions, Acronyms and Abbreviations

We will use some acronyms through the paper. Some of the abbreviations and definition we will use are given below:Terms DefinitionSystem Administrator System administrator is a person who is legally responsible for handling the whole software and who has complete access to the whole system. System User A person who is working or executing the system but with a restricted privilege. Database Storage group of all the information supervised by the system. Field A cell within a form. Software Requirements Specification (SRS) A paper that thoroughly defines all of the jobs of a proposed system and the restrictions under which it must work. For example, this paper. Stakeholder Every single individual who is involved in the development procedure of the software. Point of Sale(POS) A point of sale system is either a stand-alone machine or a network of input and output devices used by restaurant employees to accomplish their daily basis activates including foodstuff and drink orders, transmission of tasks to the kitchen and other remote areas, guest-check settlement, credit card transaction processing and charge posting folios.

Overall descriptions:

Product Perspective

The RMS guides the restaurant manager to manage the restaurant more efficiently by automating meal ordering, billing and inventory control. The software performs transaction and saves the resultant data. The system will produce reports from the data which guide the manager to make suitable business decisions for the restaurant. For example, estimating the number of customers for a certain time interval, the manager can decide whether more waiters and cooks are required. Furthermore, calculate daily expenditure and profit easily. The whole management system will develop to automate and digitalized a Restaurant, so that any restaurant management can acquire it and can start automated process to restaurant.

Product Functionality

Whole operations will be executed through this direction. Customers can order food via application. The computer operators of a restaurant take order and pass it the cooks. The waiters serve the order and collect bills to customers. Also, management can check the available and required goods. Customers can give feedback through the application.

Users and Characteristics

The RMS has five roles and one cooperating system. The customer can interact with the system through Wi-Fi connection and place food order. The cook can see the order and after cooking the food he will tell to the system that the food is prepared. The waiter can get the confirmation of food from the cook through the system and deliver it to the right table. The cashier can access the software and receive the bill from the customer. The Administrator can manipulate the price, count total earning and expenditure.

Operating Environment

Operating system: Minimum Windows XP or Windows Vista. Healthier environment Windows 7, 8, 8. 1 and 10. Language: JavaIn order to use this application, Smart phone will be needed to place order, which will run on Android Operating System. (We will deliver the android application to place order to the system). Excellent Wi-Fi connection will be required for a restaurant and a display for cook in kitchen. To retain system, these instructions can be followed for finest environment (Not obligatory):Three computers are required. (One for owner, one for cashier, one for manager) 2 to 3 Tablets with android operating system are required. (These are for those customers who have not android smartphone)

Design and Implementation Constraints

There are few restrictions which overheads for the system, If those restrictions can overcome then this whole system will execute finest.

They are:

1. IOS Application and Windows Application.
2. Information flow or data flow can be controlled and more effective.
3. Speedier server system.
4. Use C# for more safety.

User Documentation

It will deliver precise instructions to a user for using for the RMS. Additionally; a Video will be delivered which will illustrate the whole system functionalities and its working.

Assumptions and Dependencies

If the system has IOS and Windows application then consumers who use such kind of smartphone (windows and IOS) will be more benefited. The whole system performance will be improved if there are extra Tablets for each table. It is favorable to use of CC TV camera for more secure system.

External Interface Requirements: There are many types of interfaces as such supported by this software system namely;User Interface Software Interface Hardware Interface

User Interfaces

The user interface will be executed using any android smartphone application browser. This interface will be designed to user friendly, so that all type of customer can place order easily. Customers can also provide views through it easily with some sample comments or if they are intend to write their review by own they can do it.

Hardware Interfaces

The logical address of the system will be in IPv6 format.

Software Interfaces

The system shall connect with the Configurator to identify all the available components to configure the product. The system shall connect with the content manager to get the product specifications.

Communication Interfaces

Communication operation required the Internet protocol version 6 and it will follow HTTPS. It will use FTP for whole system with local server.

Functional Requirements

Food Order via Application

Customer can place order food through the application but it requires specific Wi-Fi connection.

Take Order

The cook will take the order and if it is feasible to make the food, he will approve the order and start to cook food.

Serve Food

When the foodstuff is prepared to be served then the cook will alert the waiter. Afterwards, the waiter will assure the order is served.

Payment

The cashier will collect the payment if the customer is a member he/she will get discount.

Available Good

The cook will add the details of available goods and the administrator can see that records.

Required Goods

The cook will also add what goods are required.

Customer Information

The customer will be recorded and be the member of special customer.

Customer Review

Customer can provide his opinion about the foodstuff and services.

Performance Requirements.

The product will be established on local server. The product will take initial time for loading. The performance will also dependent on hardware components. Cash system will be entirely protected through POS system. Different database for employees.

Safely and Security Requirements.

The source code will develop for the system shall be upheld in configuration management tool. The whole system is protected. Only Administrator have right to access all the records. The system will use HTTPS; because of this protocol the system security will enhanced. The system will use protected POS system.