SRS Restaurant Management System
Running a restaurant is hectic enough as it is, so why not make the day-to-day processes easier by having a system that will help ease the workload for you? Restaurant management System is specially designed for the purpose of keeping record of all transaction carried out in the restaurant on daily bases. In current marketplace, there is a great value for food, restaurants and its management. There is a day by day increase in the number of restaurants and food places that are emerging today. The Restaurant Management System helps the restaurant management to keep adequate record of all transactions carried out and does that will still be carried out by the restaurant and maintain the database of the restaurant. . It will be a windows-based application that has been developed to make all the operations fast and easy. The design of the Restaurant Management system is easy to use for every type of user because a lot of restaurants have salespersons which are not well qualified. The main objective of developing this system is to help every restaurant, whether small, medium-sized, or large, will benefit greatly by switching from manual restaurant management processes to automated or software-based ones.
Scope of Project Restaurant Management System:
Project scope is the part of project planning that involves determining and documenting a list of specific project goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target
Functional and Non Functional Requirements of Restaurant Management System:
Functional Requirements :
A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs
Functional Requirements of Restaurant Management System:
The administrator can create a new user (Workers at Restaurant). New user can login and logout. User & Role Management:
o The administrator can create different Roles with permission as per your need. o Predefined roles – Admin & Cashier
o Create unlimited users with different roles. Contacts (Customer & Suppliers):
o Mark contact as customer or supplier or both. o View details of transactions with a contact. o View total of Credit/Debit balance amount. Products:
o Manage products. o Classify products according to Brands, Category, Sub-Category. o Add products having different units
o Add SKU number or auto-generate SKU number with prefixes. Purchases:
o Easily add purchases. o Manage Paid/Due purchases.
o Simplified interface for selling products
o Add new customer from POS screen. o Mark an invoice for draft or final
o Different options for payments
o Customize invoice layout and invoice scheme. Manage Expenses:
o Easily add business expenses
o Categorize expenses
o Purchase & Sale report
o Tax Report
o Contact Reports
o Stock Reports
o Expense Report
NON-FUNCTIONAL REQUIREMENTS Restaurant Management System:
- Application is user friendly.
- Application Perform fast manipulation and calculations.
- Application is adaptable.
- Application will be able to work on all types of operating systems.
- Application will be capable to handle multi user activities simultaneously.
- There will be back up system to face any problem in system
- All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
- Response Time is very awesome.
Some others are:
- Fault Tolerance.
Use Case Diagram of Diagnosis of Restaurant Management System
a use case diagram can summarize the details of your system’s users and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve
Usage Scenarios Diagnosis of Restaurant Management System:
A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a User.
ADOPTED METHODOLOGY for Restaurant Management System:
The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.
Work Plan of Diagnosis of Restaurant Management System:
for complete srs contact us