Table of ContentsDocument PurposeTarget ScopeIntended Audience and Document OverviewDefinitions, Acronyms, and AbbreviationsGeneral Descriptions:Product PerspectiveProduct CapabilitiesUsers and FeaturesOperating EnvironmentDesign and Implementation ConstraintsUser DocumentationAssumptions and DependenciesUser InterfacesHardware InterfacesSoftware InterfacesCommunication InterfacesFunctional RequirementsOrder of food via ApplicationTake orderServe foodPaymentVoucher availableGoods requiredCustomer informationCustomer reviewPerformance requirements.Safety and security requirements.Purpose of the documentThis document presents an in-depth description of the purposes, features, user interface and application of the restaurant management system in real life . It will also describe how the system will run and the conditions under which it will need to operate. The user interface will also be shown in this article. Both stakeholders and system developers can benefit from this document. Say no to plagiarism. Get a tailor-made essay on "Why Violent Video Games Shouldn't Be Banned"? Get Original EssayScopeThis software system will be designed to efficiently and systematically manage the restaurant business. In this system, we will provide an application that can be used by customers to order food items. Consumers can also provide their opinions through the application, so that the restaurant management can evaluate the entire system. This will ultimately guide the restaurant management to efficiently manage their resources, such as employing fewer waiters and appointing more cooks who will help deliver orders faster. Customers (end users) will also be able to pay bills via debit or credit cards using the POS which will be integrated with the management software. Customers will be shown the calorie table of a food which will help them in choosing food based on their health. Employee information will be saved in the system which can only be accessed by the system administrator. Audience and document overview This document is aimed at different types of readers such as restaurant managers, system designers, system developers and testers. By understanding this document a reader can understand the purpose for which the project was implemented and how it will present its basic ideas. This article has a linear overview of the entire product, so if a reader reads the article from top to bottom; will have a perfect picture of the product. Definitions, Acronyms and Abbreviations We will use some acronyms throughout the article. Below are some of the abbreviations and definitions we will use: Definition of TermsSystem Administrator The system administrator is a person who is legally responsible for managing the entire software and who has complete access to the entire system. System User A person who works on or runs the system but has limited privileges. Database Storage group of all information supervised by the system. Field A cell within a form. Software Requirements Specification (SRS) A document that thoroughly defines all the tasks of a proposed system and the restrictions under which it must operate. For example, this document. Stakeholder Every single individual involved in the software development process. Point of Sale (POS) A point of sale system is a self-contained machine or network of input and output devices used by restaurant employees to carry out their daily tasks, including ordering food and beverage products, transmitting tasks to the kitchen, and other areas remote, balanceof guest checks, credit card transaction processing, and charge record sheets. General Descriptions: Product Perspective RMS guides the restaurant manager to manage the restaurant more efficiently by automating meal ordering, billing and inventory control. The software executes the transaction and saves the resulting data. The system will produce reports from the data that will guide the manager to make appropriate business decisions for the restaurant. For example, by estimating the number of customers for a certain time interval, the manager can decide whether more waiters and cooks are needed. Plus, easily calculate your daily expenses and profits. The entire management system will be developed to automate and digitalize a restaurant, so that any restaurant management can acquire it and start an automated process for the restaurant. Product Features All operations will be performed through this direction. Customers can order food via the app. The IT operators of a restaurant take the order and pass it to the chefs. Waiters serve orders and collect bills from customers. Furthermore, the management can check the available and requested goods. Customers can provide feedback via the application. Users and Features The RMS has five roles and a cooperating system. The customer can interact with the system via Wi-Fi connection and place the food order. The cook will be able to see the order and after cooking the food he will tell the system that the food is ready. The waiter can get the food confirmation from the cook through the system and deliver it to the right table. The cashier can log in to the software and receive the invoice from the customer. The admin can manipulate the price, count the total income and expenses. Operating Environment Operating System: Minimum Windows XP or Windows Vista. Healthier environment Windows 7, 8, 8. 1 and 10. Language: Java To use this application, you will need a smartphone to place your order, which will run on the Android operating system. (We will deliver the Android application to place the order to the system). An excellent Wi-Fi connection will be needed for a restaurant and a display for cooking in the kitchen. To maintain your system, you can follow these instructions for the best environment (not required): Three computers are required. (One for the owner, one for the cashier, one for the manager) 2 to 3 tablets with Android OS are required. (These are for customers who do not have an Android smartphone) Design and Implementation Constraints There are few restrictions that cause overhead to the system. If such restrictions can be overcome, the entire system will function at its best. They are: IOS application and Windows application. The information flow or data flow can be controlled and more effective. Faster server system. Use C# for added security. User documentation It will provide precise instructions to a user for use for RMS. Furthermore; A video will be delivered that will illustrate the functionality of the entire system and its operation. Assumptions and Dependencies If the system has IOS and Windows applications, consumers using this type of smartphone (Windows and IOS) will be more advantaged. The performance of the entire system will improve if there are additional tablets for each table. Using CC camera is preferable for more secure system. External Interface Requirements: There are many types of interfaces supported by this software system, namely: User Interface Software Interface Hardware Interface User Interfaces The user interface will be done using any navigator Android smartphone application. This interface will be designed to be easy to use, in.