Traditional Culture Encyclopedia - Hotel franchise - Catering Management System Design Paper

Catering Management System Design Paper

In the daily management and operation of the catering industry, a large number of companies still adopt a purely manual management model, and the overall scientific and technological content of management is low. Below is a catering management system design paper that I compiled for your reference. Catering management system design paper Part 1

Physical store catering management system design and implementation

Catering management system design paper abstract

Abstract: With the development of my country's market economy With rapid development, people's living standards have improved, and the catering industry is booming rapidly. The traditional manual work methods can no longer meet the needs of catering operators. Managing physical stores through the catering management system has advantages that manual management cannot match. It can greatly improve the efficiency of catering management and enhance the competitiveness of the enterprise.

Contents of the paper on catering management system design

Keywords: catering; management system; database

1. Introduction

With the development of social economy With sustained rapid growth, social wealth has increased rapidly, the income level of the people has continued to increase, and life styles have undergone tremendous changes. At the same time, with the establishment and rapid development of the market economic system, social material products are greatly enriched, and the catering industry is booming. The traditional manual work method can no longer meet the needs of catering operators. Manual accounting, accounting, inquiry and other tasks are time-consuming, laborious and error-prone. By running the catering management system on the computer, it not only reduces human resources but also improves efficiency. It can earn greater profits for the catering industry and provide consumers with a lot of convenience.

In recent years, computer network and distribution technologies have become increasingly mature. With the development of science and technology, competition in the catering industry has become increasingly fierce. If you want to survive in such a fiercely competitive environment, you must use scientific management ideas and advanced management methods to integrate ordering and management. This not only improves work efficiency, but also avoids the trouble of previous manual work, allowing managers to manage accurately and effectively. Therefore, it is necessary to establish a scientific catering management system.

2. System analysis

(1) Feasibility analysis

1. Technical feasibility

The system is a small catering management system. Using C/S mode, the client is installed on the front-end computer, the information is processed, and the processing results are stored on the data server. At present, many enterprises use SQL Server database, which is very convenient to process data. It has been widely used and is technically feasible.

2. Economic feasibility

Analyze the economic benefits and development costs of this system. This system adopts a C/S structure. As long as you have a PC, it can be implemented without complicated settings. Compared with manual operations, it saves manpower and material resources and has better economic benefits.

3. Operational feasibility

Operational feasibility refers to whether the system’s operation method is feasible in the user organization. The functions of the catering management system are relatively simple, the page is simple and clear, and there are no cumbersome and unnecessary operations. Users can know what to do at a glance. The administrator's interface is also relatively simple, with some basic operations that employees can quickly master and are easy to implement in terms of operations.

(2) Functional requirements analysis

The catering management system is a digital management of catering processes. It can not only help restaurants better manage staff information, but also facilitate customer consumption, and Different users have different permissions. Specific functions include: user login, basic information, ordering/adding dishes, bill inquiry, checkout, auxiliary functions, system maintenance, system settings, etc.

User login: The user selects his or her identity (super administrator, manager, customer) to log in. If the identity is selected incorrectly, the user will not be able to log in. Users log in to the main interface of the system according to their account number, password and correct identity.

Employee information: Super administrators and managers have the authority to manage basic information of employees. The staff information function module includes query of overall staff, addition of staff information, modification of staff information and deletion of staff information.

Desk information: Super administrators and managers have the authority to manage the basic information of the table. The table information function module includes table query, table information addition, table information modification and table information deletion.

Order/add dishes: This function allows customers to order and add dishes.

Bill inquiry: Customers can inquire about their bills according to their consumption situation.

Checkout: Based on the consumption of the table and the private room fee, the total price is summarized, and the actual receipt and change can be calculated.

Auxiliary functions: As a system, it should have some auxiliary functions, such as calendars and calculators.

System maintenance: Only super administrators have such permissions to implement permission management, system backup, and system recovery.

System settings: including system password settings and system locking.

3. System design and implementation

The system module mainly includes five main modules: basic information module, desktop operation module, system setting module, auxiliary tool module, and exit module. The basic information module is divided into two sub-modules: basic information on desks and basic information on staff. Table operation is the main function of this system. It includes the operations of opening tables and ordering dishes. At the same time, consumption inquiry and checkout can be performed for a certain table. The system setting module mainly includes password setting and locking system. This module is mainly a guarantee for the security of the system and is also an indispensable part of the system. As a system, it should have some auxiliary tools, such as calendars, calculators, and notepads, so the system has an auxiliary tool module. A complete system must have an exit module, that is, exit the system.

The detailed design of the main functions in the catering management system is as follows.

(1) Login module design

The login module uses the logged-in user name, password and user permissions as search conditions to query in the database. When the login button is clicked, the login module first determines whether the user name and password have been entered. If the user name and password are not entered, a prompt box will pop up, prompting the user to enter the user name and password to log in to the system; if the user name and password are entered, the system will determine the user name. , password and permissions match. If they match, the login is successful.

(2) Main interface module design

After successful login, the main interface will be displayed, which should include the menu bar, table display and system status bar. When the form is loaded, the permissions of the logged-in user are first determined, and different functions are assigned based on the user's permissions. When the form focus is triggered, the system retrieves the status information of all tables from the database, and then calls the custom AddItem method to add tables. When the user clicks on a table, the system will pop up different right-click menus based on the current status of the table.

(3) Table opening module design

The table opening form should have table information, staff information and the number of diners. When the form is loaded, all tables in the database will be The station information and employee information are retrieved and displayed on the ComboBox control. The number of diners should be entered in the number of diners text box, and the number of diners should be an integer number greater than 0. After saving, the table will be opened.

(4) Ordering module design

The ordering module can use the TreeView control to display all cuisines, and the DataGridView control to display all customer consumption information. When designing this module, all the cuisine names are retrieved from the database and displayed in the TreeView. After the user selects the cuisine, a data table should be designed to store the selected cuisines and be displayed in the module so that the dishes ordered by mistake can be avoided. Can be deleted.

(5) Checkout module design

In the checkout module, all the items consumed by the customer can be retrieved in the database. There should be cuisine consumption and private room consumption. According to the two Consumption, showing total consumption. When the customer enters the amount, the system can automatically provide change and display it on the interface.

(6) Basic table information module design

The basic information of the table should have operations such as adding, deleting, modifying, and querying the table.

When adding table information, the data table of the table information is retrieved from the database and the information is added to the information table. When querying table information, the system connects to the database, retrieves the database data table in the database, and displays the table information on the interface.

IV. Summary

The small physical store catering management system is carried out on the .net platform, combined with the back-end SQL Server 2000 database technology, to complete the management of tables and staff. , customers can open the table, order/add dishes, account inquiry and consumption account settlement and other functions. System information query is flexible and convenient, data storage is safe and reliable, and the cost is low. In addition, the system itself has the following advantages.

First, it is more convenient to use and users can get started quickly.

Second, the system automatically checks out, and the checkout speed is fast and accurate.

Third, the system provides effective technical guarantee for improving customer service quality.

The small physical store catering management system can effectively guide staff to standardize business operation procedures, realize business management more efficiently and quickly, ensure the security of customer information, and improve management level and work efficiency. thereby improving business competitiveness.

Catering management system design thesis literature

[1] Lu Pin, Chen Fengpei. Design and development of a management information system for a small and medium-sized restaurant [J]. Guilin Aerospace Industry College Journal of Chinese Academy of Sciences, 2011(04).

[2] Cui Hailong, Li Yun. Application of e-commerce in the catering industry [J]. Management Observation, 2009(18).

[3] Yu Wei, Zhao Liang. Design and architecture of bank intermediary transaction platform based on SOA [J]. Science and Technology Square, 2011(07). Catering Management System Design Paper Part 2

Data in Catering Management System Design of Integrity

Abstract of Catering Management System Design Paper

Abstract: Taking some tables in the catering management system database as an example, this article introduces in detail personal design ideas and methods for data integrity. The application of data integrity in practice is explained through examples, and a description based on SQLSERVERDE language is given.

Catering management system design paper content

Keywords: database; data integrity; constraints; triggers

CLC classification number: TP311 Document identification code: A Article number: 1671-7597(2011)1210173-01

Creating a database is a very easy thing, but designing a rigorous, safe, and reliable database is not so easy. It requires you Having a solid theoretical knowledge as a foundation, you also need to have a certain ability to analyze and solve problems. After the database design has gone through requirements analysis, database conceptual structure design, and logical structure design, we should consider the design of data integrity. Data integrity is to ensure the correctness, reliability, and consistency of data to the greatest extent possible. Data integrity includes three aspects: entity integrity, referential integrity (referential integrity) and user-defined integrity (domain integrity).

The following takes the table in the catering management system that can implement ordering and checkout as an example to illustrate the above complete design. The relationship model of the tables involved in catering management is: table table zt (table number zh, table name zm, capacity rnrs, status zt, type lx), menu table cd (dish number cpbh, dish name cpmc, specification gg, category lb, unit price dj, cost price cbj), order table dd (order number ddbh, order date ddrq, table number zh, consumption amount xfje), order table dc (order number ddbh, dish number cpbh, quantity sl).

The definitions of the above four tables are as follows:

Create table zt (zh char(4) primary key,zm char(8) unique, rnrs int check (rnrs>=0),zt bit, lx char( 8) check (lx='lobby' or lx='box' lx='vip'))

Create table cd(cpbh char(5) primary key, cpmc char(12),gg char( 10),lb char(8),dj numeric(6,1) check(dj>=0),cbj numeric(6,1) check(cbj>=0))

Create table dd ( ddbh char(10) primary key,ddrq datetime,zh char(4) foreign key references zt(zh), xfje numeric(10,1))

Create table dc (ddbh char(10) foreign key references dd(ddbh),cpbh char(5) foreign key references cd(cpbh),sl int check(sl>=0) default 1,primary key(ddbh,cpbh))

 1 Entity integrity (Table integrity)

Entity integrity, also called table integrity, is a constraint on the primary key in the table. The rules of entity integrity require that in any tuple of any relationship, the value of the primary key cannot be null or have duplicate values. The purpose of establishing entity integrity is to ensure that each tuple in the database table is unique. Whether a primary key value can be changed or an entire row deleted depends on the required integrity level between the primary key and other tables. The definition of entity integrity is relatively simple. Methods to achieve "entity integrity" include primary key constraints, unique constraints, identity columns, and unique indexes. Here, primary key constraints are defined for the table number zh in the table table zt, the dish number cpbh in the menu table cd, and the order number ddbh in the order table dd. When defining, be sure to note that a complete table definition can only have one primary key (PRIMARY KEY), but it does not need UNIQUE constraints.

 2 Referential integrity rules (referential integrity rules)

There is a certain relationship between entities in the real world. In the relational model, entities and the connections between entities are described by relationships, so there are naturally references between relationships. This is achieved by performing primary key constraints and foreign key constraints in two tables in the same database. The referencing column and the referenced column must have the same attributes.

Reference integrity rules rule requirements: ?Do not reference non-existent entities?. That is: it is not allowed to reference tuples in one relation that do not exist in another relation. Its purpose is to ensure that the data between related tables is consistent. Referential integrity is a constraint on foreign keys, which requires that the value of a foreign key can only be in two situations: if it is a non-null value, it must be a value that exists in the main table. Either take the null value (null). Setting referential integrity prohibits inserting data rows in the slave table that contain keywords that do not exist in the master table; prohibits deleting master table records that have corresponding records in the slave table.

In the above four tables, foreign keys are set for the table number zh of the order table dd, and the order number ddbh and dish number cpbh of the order table dc. In addition, the design of foreign keys can also be set by triggers or programming languages.

Taking the order table dd as an example, the trigger setting method is as follows:

CREATE TRIGGER insert_xs ON dd

AFTER INSERT

AS

IF EXISTS

 (SELECT * FROM INSERTED

 WHERE zh IN (SELECT zh FROM zt))

 PRINT 'Added successfully!?

ELSE

BEGIN

PRINT 'The table number does not match the existing table number!?

ROLLBACK TRANSACTION

END

You can also set a trigger on the ordering table to require DC's order number ddbh and dish number cpbh to also be referenced. Referential integrity is a method used to maintain data consistency between related data tables. By implementing referential integrity, you can prevent the data in another data table from becoming invalid values ??due to changes in records in one data table.

 3 Field integrity

Field integrity, also known as column integrity or user-defined integrity, is used to limit what users enter into a column. Domain integrity rules require users to define the value range of attributes in the table based on actual conditions. Its purpose is to ensure the validity of the data in a given field, that is, to ensure that the value of the data is within the valid range.

The way to set domain integrity is to limit the data type, precision, range, format, length, etc. of the column. It can be implemented by specifying database objects such as data types, CHECK constraints, DEFAULT constraints, NOT NULL constraints, and creation rules, default values, etc.

The data stored in the database is diverse. Specifying an accurate data type for each column is the first step in designing a table. The data type of a column specifies the data values ??allowed on the column. When adding or modifying data, its type must conform to the data type specified when creating the table. This method provides the most basic guarantee for data integrity in the database.

Constraints are a method provided by SQL Server to automatically maintain data integrity and are independent of the table structure. Rules are one of the methods to achieve domain integrity and are used to verify whether the data in a database is within a specified value range and matches a specific format. When data values ??in the database are updated or inserted, it is checked whether the new values ??follow the rules. If the rules are not met, update or insert operations are refused.

In the related tables of the catering system, we have set data type and length restrictions on the corresponding columns, and set check (dj>=0) constraints on the unit price dj of the menu table cd, and on the ordering The number sl column of table dc (sl int check(sl>=0) default 1) sets the check constraint and the default value constraint. Of course, we can implement the above constraints by defining rules. For example:

Use create rule dyl as@x>=0 to define a constraint greater than zero, and then use sp_bindrule dyl, 'cd.dj? statement and sp_bindrule dyl, 'dc.sl' statement to Bind to the unit price dj column of the menu table cd and the quantity sl column of the order table dc.

For the dish number cpbh, we stipulate that the dish must be represented by the representative letter of the category as the first character, and the representative letter of the sub-category as the second character followed by 3 digits. For example, CL001 represents vegetables, and LN001 can represent milk beverages.

The category classification is as shown in Table 1:

Table 1 Menu category table

In order to implement the above coding, we use rules to implement the following:

Create rule cpbm as

@BM like 'C[LQRT][0-9][0-9][0-9]'

Or @BM like 'J[PBNM][0-9][ 0-9][0-9]'

Or @BM like 'Y[CNGT][0-9][0-9][0-9]'

Or @BM like 'z[fm][0-9][0-9][0-9]'

sp_bindrule cpbm, 'cd.cpbh'

4 trigger implementation Data integrity

When users have more specific and complex data integrity requirements, the above three types of integrity cannot meet the user's requirements. In this case, the user needs to define the required integrity himself. An important way to achieve custom integrity is to create triggers. A trigger is a database object. It is a special stored procedure that is automatically executed by the system when a table or view performs insert, delete, or update operations. The purpose of creating triggers is to implement complex data integrity constraints on tables to prevent incorrect operations. It is associated with the data modification operation of a certain table in the database. The modification operation can be one or more of the three operations: INSERT, UPDATE, and DELETE. The trigger automatically executes when the user performs trigger-related modification operations on the related table. It is often used to set referential integrity restrictions on data and operations such as cascade deletion and cascade update. Taking cascade update as an example, analyze how to use triggers to implement such an operation when the dish numbers in the menu table are modified and the dish numbers in the ordering table are updated at the same time:

create trigger upd on cd after update

as

declare @jbh char(5),@xbh char(5)

select @jbh=deleted.cpbh, @xbh= inserted.cpbh

 from deleted,inserted where deleted.cpbh=inserted.cpbh

print 'Prepare to cascade update the dish number information in the ordering table?.'

update dc set cpbh=@xbh where cpbh=@jbh

print 'The information of the original dish number '+ @jbh +' in the ordering table has been cascade updated'

5 Application interface programming

Application interface programming is the most burdensome method for database application design, but it is also the most basic and flexible method. No matter how rich the integrity constraints provided by the database management system, using programming interfaces to ensure data integrity is still one of the key technologies that all database application designers must master.

6 Summary

Ensuring the data integrity of the database is very important in the database management system. Reasonable use of various measures provided by SQL Server for data integrity and the required constraints on data can effectively reduce errors that may occur during the use of the database, improve the availability of the database system, and reduce the time spent on processing data errors. cost.

Catering management system design paper documents

[1] Chen Wei, Sql Server2005 application system development tutorial [M]. Beijing: Tsinghua University Press.

[2] Andrew J.Brust Stephen Forte, Proficient in SQLServer 2005 Programming, translated by Jia Hongfeng, Tsinghua University Press, 2007.

[3] Sa Shixuan, Wang Shan, Introduction to Database Systems (Vol. Third Edition) [M]. Beijing: Higher Education Press, 2004.

Recommended papers on catering management system design:

1. A brief discussion of catering service and management papers

2. Graduation thesis on high-end catering service management research

3. Graduation thesis on hotel management system

4. Thesis on catering service and management

5 . Student Management System Thesis

6. Student Status Management System Graduation Thesis