Design of catering management system —— Design and implementation of catering management system in physical store
Abstract of design papers on catering management system
Abstract: With the rapid development of China's market economy and the improvement of people's living standards, the catering industry has developed rapidly. The traditional manual operation mode can no longer meet the needs of catering operators. Managing physical stores through catering management system has incomparable advantages over manual management, which can greatly improve the efficiency of catering management and enhance the competitiveness of enterprises.
Contents of the design paper of catering management system
Keywords: catering; Management system; database
I. Introduction
With the sustained high-speed growth of social economy and the rapid increase of social wealth, the income level of the broad masses of the people has been continuously improved and their lifestyles have undergone tremendous changes. At the same time, with the establishment and rapid development of the market economy system, social material products are extremely rich and the catering industry is booming. The traditional manual operation mode can no longer meet the needs of catering operators. Manual bookkeeping, accounting and inquiry are time-consuming, laborious and error-prone. By running the catering management system in the computer, it not only reduces human resources, but also improves efficiency, which can earn more profits for the catering industry and provide many conveniences for consumers.
In recent years, computer network and distribution technology have become more and more mature. With the development of science and technology, the competition in the catering industry is becoming more and more fierce. In order to survive in such a competitive environment, we must integrate ordering and management with scientific management ideas and advanced management methods. This can not only improve work efficiency, but also avoid the trouble of manual operation in the past, so that managers can manage accurately and effectively. Therefore, it is necessary to establish a scientific catering management system.
Second, the system analysis
feasibility analysis
1. Technical feasibility
This system is a small catering management system. Using C/S mode, the client is installed in the foreground computer, which processes the information and stores the processing results in the data server. At present, many enterprises adopt SQL Server database, which is quite convenient to process data and has been widely used. It is technically feasible.
2. Economic feasibility
The economic benefit and development cost of the system are analyzed. This system adopts C/S structure, which can be realized with only one PC without complicated setup. Compared with manual operation, it saves manpower and material resources and has good economic benefits.
3. Operational feasibility
Operational feasibility refers to whether the operating mode of the system is feasible in the user organization. The function of the catering management system is relatively simple, the page is concise and clear, and there is no complicated and redundant operation. Users know how to operate at a glance. The administrator's interface is also relatively simple, all of which are basic operations, which can be quickly mastered by employees and easily realized in operation.
(B) functional requirements analysis
The catering management system is the digital management of the catering process, which can not only help restaurants to better manage employee information, but also facilitate customers' consumption. Different users have different access rights. Specific functions include: user login, basic information, ordering/adding food, bill inquiry, closing, auxiliary functions, system maintenance, system setup, etc.
User login: users choose their own identities (super administrator, manager, customer) to log in. If they choose the wrong identity, they 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 right to manage the basic information of employees. The employee information function module includes the whole employee query, employee information addition, employee information modification and employee information deletion.
Desk information: Super administrators and managers have the right to manage the basic information of desks. Desk information function module includes desk inquiry, desk information addition, desk information modification and desk information deletion.
Order/Add Meal: This function allows customers to order and add meals.
Bill inquiry: customers can inquire their own bills according to their own consumption.
Check-out: according to the table consumption and room rate, summarize the total price and calculate the paid amount and change.
Auxiliary functions: As a system, there should be some auxiliary functions, such as calendar and calculator.
System maintenance: Only the super administrator has such authority, which can realize authority management, system backup and system recovery.
System settings: including password settings and locking system.
Third, the system design and implementation
The system module mainly includes five main modules: basic information module, foreground operation module, system setting module, auxiliary tool module and exit module. Among them, the basic information module is divided into two sub-modules: table basic information and personnel basic information. Table operation is the main function of this system, including table opening and ordering, and at the same time, a table can be queried and settled. System setting module mainly includes password setting and locking system, which is the guarantee of system security and an indispensable part of this system. As a system, it should have some auxiliary tools, such as calendar, calculator and notepad, so the system has an auxiliary tool module. A complete system must have an exit module, that is, exit system.
The detailed design of the main functions in the catering management system is as follows.
(A) login module design
Login module uses login user name, password and user rights as search conditions to query in the database. When clicking the login button, the login module first judges whether the user name and password are entered, and if not, a prompt box pops up to prompt the user to enter the user name and password for logging in the system; If you enter a user name and password, the system will determine whether the user name, password and permissions match. If there is a match, the login is successful.
(2) Design of main interface module
After successful login, the main interface will be displayed, which should include menu bar, desktop display and display system status bar. When loading the form, first judge the authority of the login user, and assign different functions according to the login authority of the user. When the focus of the form is triggered, the system retrieves the status information of all tables from the database, and then calls the user-defined add method to add tables. When the user clicks a table, different right-click menus will pop up according to the current status of the table.
(3) Design of open module of the platform.
The table opening list should have table information, staff information and the number of people dining. When the form is loaded, all the table information and employee information in the database will be 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 greater than 0. After saving, the form will be opened.
(4) Design of ordering module
The ordering module can display all cuisines with TreeView control and all the information of customer consumption with DataGridView control. When designing this module, all the names of dishes are retrieved from the database and displayed in the tree view. After the user selects the cuisines, a data table for storing these selected cuisines needs to be designed and displayed in this module, so as to delete the delayed cuisines.
(5) Design of checkout module
In the checkout module, all the items consumed by customers can be retrieved from the database, including the consumption of cuisines and the consumption of private rooms, and the total consumption can be displayed according to their consumption. When the customer enters the amount, the system can automatically change it and display it on the interface.
(6) Design of the basic information module of the desk.
The basic information of the form should be added, deleted, modified and queried. When adding table information, retrieve the data table of table information from the database and add the information to the information table. When querying the form information, the system connects to the database, retrieves the data table of the database from the database, and displays the form information on the interface.
Four. abstract
The catering management system of small physical stores is based on. Net platform. Combined with the background SQL Server 2000 database technology, the functions of foreground management, employee management, customer account opening, ordering/adding food, account inquiry, consumer account settlement and so on have been completed. The system information query is flexible and convenient, the 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, which is fast and accurate.
Thirdly, the system provides effective technical support for improving customer service quality.
The catering management system of small physical stores can effectively guide staff to standardize business operation process, realize business management more efficiently and quickly, ensure customer information security, improve management level and work efficiency, and then improve business competitiveness.
Design documents of catering management system
[1] Lv Pin, Chen Fengpei. Design and development of a small and medium-sized catering management information system [J]. Journal of Guilin Institute of Aerospace Technology, 20 1 1(04).
[2] Cui Hailong and Liu Yun. E-commerce in catering industry [J]. Management observation, 2009( 18).
[3] Yu Wei and Zhao Liang. Design and Architecture of Bank Intermediate Trading Platform Based on SOA [J]. Science and Technology Plaza, 20 1 1(07).
Design of catering management system (2) Data integrity design of catering management system
Abstract of design papers on catering management system
Taking some tables in the database of catering management system as examples, this paper introduces the design ideas and methods of personal data integrity in detail, expounds the application of data integrity in practice through examples, and gives a description based on SQLSERVERDE language.
Contents of the design paper of catering management system
Keywords: database; Data integrity; Constraints; trigger
Classification number of China Library: TP3/KOOC-0//KOOC-0/Document ID: A document number:/KOOC-0/67/KOOC-0/-7597 (20/KOOC-0/)/KOOC-0/2/KOOC-0.
It is very easy to create a database, but it is not so easy to design a rigorous, safe and reliable database. It requires you to have solid theoretical knowledge as the foundation, and you also need to have certain ability to analyze and solve problems. After the analysis and design of database requirements, the design of database conceptual mechanism and logical structure, the design of data integrity should be considered. Data integrity is to ensure the correctness, reliability and consistency of data to the greatest extent. Data integrity includes three aspects: entity integrity, referential integrity (referential integrity) and user-defined integrity (domain integrity).
The following table, which can realize ordering and checkout in the catering management system, is taken as an example to illustrate the design of the above completeness. The relational model of dining table involved in catering management is: dining table zt (table number zh, table name zm, number of people to accommodate rnrs, status zt, type lx), menu cd (dish number cpbh, dish name cpmc, specification gg, category lb, unit price dj, cost price cbj), ordering dd (order number ddbh, ordering date ddrq, table number zh, consumption amount). The above four tables are defined 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=' hall' 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 (6,1) check (DJ > =0), cbj value (6, 1) check (cbj & gt=0))
Create table dd (ddbh char( 10) primary key, ddrq datetime, zh char(4) foreign key reference zt(zh), xfje numerical (1 0,1)).
Create table dc (ddbh char( 10) foreign key reference dd(ddbh), cpbh char(5) foreign key reference cd(cpbh), slintcheck (sl > =0) default 1, primary key (ddbh, cpbh))
1 entity integrity (table integrity)
Entity integrity, also known as table integrity, is a constraint on the primary key in a table. Entity integrity's rules require that the value of the primary key cannot be empty or duplicate in any tuple of any relationship. The purpose of establishing entity integrity is to ensure that each tuple in the database table is unique. Whether you can change the primary key value or delete an entire row depends on the level of integrity required between the primary key value and other tables. Entity integrity's definition is relatively simple. Realize? Entity integrity? The methods of are primary key constraint, unique constraint, identity column and unique index. Here, primary key constraints are defined for table number zh in table zt, dish number cpbh in menu table cd and order number ddBH in order table DD. It must be noted that a complete table definition can only have one primary key, but not a unique constraint.
2 Reference Integrity Rules (Reference Integrity Rules)
There is some connection between entities in the real world. In the relational model, the relationship between entities is described by relationships, so there are naturally references between relationships. In two tables of the same database, it is realized by primary key constraint and foreign key constraint. The referenced column and the referenced column must have the same properties.
Reference integrity rule:? Don't reference entities that don't exist? . That is, it is not allowed to refer to tuples that do not exist in another relationship in one relationship. Its purpose is to ensure that the data between related tables is consistent. Referential integrity is a constraint on foreign keys, and the value of foreign keys can only be taken in two cases: if it is a non-empty value, it must be an existing value in the main table. Either take a null value (null). Referential integrity is set to prohibit inserting data rows containing keywords that do not exist in the master table in the slave table; It is forbidden to delete the records in the master table and the 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, the order number ddbh and the dish number cpbh of the dc in the order table. In addition, the design of foreign keys can also be set through triggers or programming languages. Taking the order table dd as an example, the trigger setting method is as follows:
Create the trigger insert_xs on dd.
After insertion
be like
If it exists,
(Select from Insert *
In which zh IN (selected from zt))
Print was added successfully! ?
other
begin
The "Print" table number does not match the existing table number! ?
Rollback transaction
end
Similarly, a trigger can be set on the order form, requiring that the order number ddbh and the dish number cpbh of dc are also referenced. Referential integrity is a way to maintain data consistency between related data tables. By implementing referential integrity, data in one data table can be prevented from becoming invalid due to record changes in another data table.
3 domain integrity
Domain integrity, also known as column integrity or user-defined integrity, is used to limit what users enter in a column. Domain integrity rules require users to define the value range of attributes in the table according to the actual situation. 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 and length of columns. It can be achieved by specifying data types, checking constraints, default constraints, non-empty constraints, creation rules, default values and other database objects.
There are many kinds of data stored in the database. Specifying the exact 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 match the data type specified when creating the table. This method provides the most basic guarantee for the data integrity in the database.
Constraint is a method provided by SQL Server to automatically maintain data integrity, which has nothing to do with table structure. Rules are one of the methods to achieve domain integrity, which are used to verify whether the data in the database is within the specified value range and whether it matches a specific format. When data values in the database are updated or inserted, it is necessary to check whether the new values follow the rules. If it does not meet the rules, it will refuse to perform the update or insert operation.
In the related tables of the catering system, we set data types and length restrictions for the corresponding columns, and set check(DJ >；; =0), the number of dc sl columns in the order table (sl int check (sl >; =0) Default 1) Constraint with check constraint and default value set. Of course, we can achieve the above constraints by defining rules. For example:
Use create rule dyl as @ x & gt=0 to define a constraint greater than zero, and then use sp _ binderuledyl,' cd.dj? Statement and sp _ binderuledyl,' dc.sl' statement bind it to dj column of menu table cd and sl column of order table dc.
For the menu number cpbh, we stipulate that the menu must take the representative letter of the category as the first character, and the representative letter of the subcategory as the second character followed by three digits. For example, CL00 1 stands for vegetables and LN00 1 stands for milk drinks. See table 1 for category classification:
Table 1 menu category table
In order to realize the above coding, we use the following rules to realize it:
Create the rule cpbm as
@BM like 'C[LQRT][0-9][0-9][0-9]'
Or @BM image' J[PBNM][0-9][0-9][0-9]'
Or @BM such as' 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 to achieve data integrity
When the user's requirements for data integrity are more special and complex, the above three kinds of integrity can not meet the user's requirements. In this case, users need to define the required integrity by themselves. An important way to achieve custom integrity is to create triggers. A trigger is a database object. It is a special stored procedure, which is automatically executed by the system when a table or view is inserted, deleted and updated. 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 tables in the database, which can be one or more of three operations: insert, update and delete. When a user performs a modification operation related to a trigger on a related table, the trigger is automatically executed. It is often used to set referential integrity limit of data, cascade deletion, cascade update and other operations. Taking the cascade update as an example, this paper analyzes how to update the menu number in the order table at the same time when modifying the menu number with a trigger:
Create a trigger update on the cd after the update
be like
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 update the dish number information in the order table in cascade? .'
Update dc set cpbh=@xbh, where cpbh=@jbh.
Print updates the information of the original menu item number "+@jbh+" in the cascade.
5 application program interface programming
Application programming interface is the most complicated method in database application programming, but it is also the most basic and flexible method. No matter how rich the integrity constraint means provided by the database management system are, using programming interface to ensure data integrity is still one of the key technologies that all database application designers must master.
6 abstract
In the database management system, it is very important to ensure the data integrity of the database. Reasonable use of various measures provided by SQL Server for data integrity and necessary constraints on data can effectively reduce possible errors in database use, improve the availability of database system and reduce the cost of dealing with data errors.
Design documents of catering management system
[1] Chen Wei, Sql Server2005 application system development tutorial [M]. Beijing: Tsinghua University Publishing House.
[2] Andrew J. Brewster Stephen Forte, proficient in SQLServer 2005 programming, translated by Jia Hongfeng, Tsinghua University Publishing House, 2007.
[3] Sashixuan, Susan Wang, Introduction to Database System (3rd Edition) [M]. Beijing: Higher Education Press, 2004.
Recommended design papers of catering management system;
1. On catering service and management
2. High-end catering service management research graduation thesis
3. Graduation thesis of hotel management system
4. Paper on Catering Service and Management
5. Papers on student management system
6. Graduation design thesis of student status management system