1. System screenshots (you can chat privately if you need a demonstration video)
Summary
With the increasingly in-depth and extensive application of information technology in management, the implementation of management information systems has gradually matured technically. This article introduces the entire process of development of a catering handheld device ordering system. By analyzing the shortcomings of the management of the catering handheld device ordering system, a computer management scheme for the catering handheld device ordering system was created. The article introduces the system analysis part of the catering handheld device ordering system, including feasibility analysis, etc. The system design part mainly introduces the system function design and database design.
This restaurant handheld device ordering system has four roles: administrator, user, restaurant, and employee. Administrators can manage information such as employees, cuisines, tables, dishes, orders, and franchise applications. Users can view and place orders, employees can view users' order information, restaurants can manage related dishes and order information, and can apply for franchise and other operations. Therefore it has certain practicality.
The backend of this site uses Java's SSM framework for backend management and development. The frontend uses the VUE framework, which allows you to log in on the browser for backend data management. MySQL is used as a local database, and WeChat developer tools are used to fully ensure the stability of the system. The system has the characteristics of clear interface, simple operation and complete functions, making the management of the catering handheld device ordering system systematic and standardized.
Keywords: catering handheld device ordering system; SSM framework; MYSQL database; VUE framework
Table of contents
2.2 Introduction to VUE framework
2.3 Introduction to SSM framework
3.2 System performance analysis
5 system detailed implementation
5.1 Implementation of the administrator module
5.1.1 Dishes information management
5.1.2 User information management
5.2 Implementation of user modules
5.3 Implementation of employee module
5.4 Implementation of restaurant module
5.4.1 Dishes information management
1System overview
1.1 Research background
Nowadays, the Internet is developing rapidly and the network is spread all over the world. The domestic mobile information field is unique. News released through WeChat can be quickly and conveniently spread to every corner of the world, and the information that can be spread on the Internet is also very wide, such as text, pictures, sounds, Video etc. Therefore, these various benefits have made the Internet the main way for information dissemination. All kinds of information in society are trying their best to spread through the Internet, and the Internet has an increasing impact on society.
Therefore, the development of a suitable catering handheld device ordering system can facilitate the management of the catering handheld device ordering system and improve the efficiency of information management and query. Users can order meals on their mobile phones, which is more convenient and conducive to Serve people better.
1.2 Research purpose
With the rapid development of Internet technology and the advent of the Internet era, network information will also change today's society. All walks of life are also slowly converging towards standardization and networking in terms of daily business operations and management. The degree of informatization of the catering handheld device ordering system is reflected in the application of the Internet and information technology to operation and management, and the replacement of traditional manual work with modern tools. Undoubtedly, the use of network information management makes information management more advanced, more efficient, more scientific, and information exchange faster.
For the previous management of the ordering system, most of them were managed using traditional manual methods, which resulted in low management efficiency and high frequency of errors. Moreover, over time, the accumulated data information is not easy to save, which will cause many problems for query, update and maintenance. There are also great hidden dangers in data handover. If the electronic storage method is adopted, it will bring great improvements and bring great convenience to users' inquiries. Therefore, it is urgent to design a catering handheld device ordering system, which can improve the level of information management.
1. 3 System design ideas
A successful website should clearly define the purpose of building the website, determine the functions of the website, determine the scale of the website, investment costs, and conduct necessary market analysis, etc. Only detailed planning can avoid many problems that occur during website construction and ensure that website construction can proceed smoothly. At the same time, a large-scale computer website system must have a correct design guiding ideology, and form a complete network architecture through reasonable selection of data structure, network structure, operating system and development environment, in order to give full play to the advantages of computer information management. Based on the actual needs of netizens in real life, this system is designed according to the following principles.
- Effectiveness: In fact, effectiveness here includes two aspects: usefulness and usability. Usefulness refers to the potential of a site to meet user needs, while usability refers to the ability to achieve specific goals through the operation of the site. It can be seen that a site is not a good site if it does not function properly or is poorly designed. A usable site should be highly efficient, easy to learn, and satisfying in achieving user goals without making mistakes.
- High reliability: A practical website must be reliable at the same time. This design can ensure the reliability and fault tolerance of the website through reasonable and advanced network design and optimized selection of software and hardware.
- High security: In the design, various security measures provided by network software and hardware will be fully utilized to ensure that users share resources and fully consider the requirements for disaster recovery, backup, and recovery of system and data resources. Provides powerful database backup tools for the system. The security of critical data can be guaranteed. Operation permission levels, set different roles to ensure the operation permissions of each step, can be set by the administrator.
- Advancedness: Adopting the most advanced development technology in the world, using JSP development technology, and MYSQL as the website back-end database. The use of these technologies reduces future system operating costs and improves system stability and ease of maintenance.
- Adopt standard technology: All designs of this website follow current international standards to improve the openness of the system.
- Balance between appearance and technology: The system adopts a Web-style interface design, which is friendly, beautiful, easy to use, easy to learn and use. The key issue in website design is the balance between appearance and technology. A website that looks bad is annoying. The site may work well but fail to motivate users. On the contrary, if the appearance is very expressive but the technology is limited, users will be very disappointed. A clear and continuous relationship needs to be determined between appearance and technology, that is, appearance is related to the intention of the site, and different types of websites are treated differently.
2Related technologies
2. 1 MYSQL database
MySQL is a true multi-user, multi-threaded SQL database server. It is a relational database management system based on SQL client/server model. Its advantages include powerful functions, simple use, convenient management, high security and reliability, fast running speed, multi-threading, cross-platform, complete networking, and stability. etc., which is very suitable for the development of database backends for Web sites or other application software. In addition, users can write programs that access MySQL databases in many languages. As one of the products of the open source movement, the MySQL relational database management system is becoming more and more popular and its application scope is becoming wider and wider. Speed and ease of use make MySQL particularly suitable for the development of database backends for Web sites or application software.
MYSQL database has the following characteristics:
1. Compilers used and tested in C and C++ to ensure source code portability and flexibility.
2. Supports multiple operating systems: AIX, FreeBSD, HP-UX, Linux and Mac OS, Novell's Netware, OpenBSD systems, OS/2, Solaris, Windows, etc.
3. Provides APIs for different programming languages. Programming languages such as C, C++, Python, Java, Perl, PHP, Eiffel, Ruby and Tcl.
4. And the CPU resources used to support multi-threading.
5. The algorithm optimizes query SQL and effectively improves search speed.
6. Clients and servers on the network can be used to program any independent programming environment. There are also Chinese, GB2312, BIG5, Japanese writing, general funds, used to support multiple languages, and can be embedded in data tables and other software shift_jis access columns Can be used as a name.
7. TCP/IP, ODBC and JDBC databases and provide connections to others.
8. Management of management tools, control and optimization of database operations.
9. Tens of millions of records can be stored in a large database.
2. 2 Introduction to VUE framework
Vue.js (pronounced /vjuː/, similar to view) is a progressive framework for building user interfaces.
Vue only focuses on the view layer and adopts a bottom-up incremental development design.
The goal of Vue is to implement responsive data binding and composed view components through the simplest possible API.
2. 3 Introduction to SSM Framework
SSM framework is the abbreviation of Spring+Spring MVC+MyBatis. This is the current mainstream Java EE enterprise-level framework after SSH and is suitable for building various large-scale enterprise-level application systems.
1.Spring Introduction
Spring is an open source framework. Spring is a lightweight Java development framework that emerged in 2003. It is derived from some of the concepts and prototypes expounded by Rod Johnson in his book Expert One-On-One J2EE Development and Design. It was created to solve the complexities of enterprise application development. Spring uses basic JavaBeans to accomplish things that were previously only possible with EJBs. However, Spring's uses are not limited to server-side development. Any Java application can benefit from Spring in terms of simplicity, testability, and loose coupling. Simply put, Spring is a lightweight Inversion of Control (IoC) and Aspect-Oriented (AOP) container framework.
A. What is Inversion of Control (IOC)?
IOC: Inversion of control is also called dependency injection. The factory pattern is used to hand over the object to the container for management. You only need to configure the corresponding bean in the spring configuration file and set the relevant attributes to let the spring container generate instance objects and management objects of the class. When the spring container starts, spring will initialize all the beans you configure in the configuration file, and then when you need to call it, it will assign the beans it has initialized to the class you need to call these beans (assuming The class name is A), and the allocation method is to call the setter method of A to inject, without the need for you to new these beans in A.
B. What is aspect-oriented (AOP)?
First of all, it needs to be explained that AOP is just a feature of Spring. It is a programming idea like OOP, not a certain technology. AOP can be said to be a supplement and improvement to OOP. OOP introduces concepts such as encapsulation, inheritance, and polymorphism to establish an object hierarchy to simulate a collection of common behaviors. When we need to introduce public behavior to dispersed objects, OOP is powerless. In other words, OOP allows you to define relationships from top to bottom, but it is not suitable for defining relationships from left to right. For example, the logging function. Logging code tends to be spread horizontally across all object hierarchies, having nothing to do with the core functionality of the objects it's spread to. In OOP design, it leads to a large amount of code duplication, which is not conducive to the reuse of various modules. Encapsulate the cross-cutting business logic in the program (such as security, logs, transactions, etc.) into an aspect, and then inject it into the target object (specific business logic).
The technology to implement AOP is mainly divided into two categories: one is to use dynamic proxy technology to decorate the message by intercepting the message to replace the execution of the original object behavior; the other is to use static weaving to introduce A specific syntax creates "aspects" so that the compiler can weave in code about the "aspects" during compilation.
2.Introduction to Spring MVC
Spring MVC is a follow-up product of Spring Framework and has been integrated into Spring Web Flow. The Spring features it natively supports make development very simple and standardized. Spring MVC separates the roles of controllers, model objects, dispatchers, and handler objects, making them easier to customize.
3.Introduction to MyBatis
MyBatis was originally an open source project iBatis of Apache. In 2010, the project was moved from Apache Software Foundation to Google Code and renamed MyBatis. MyBatis is a Java-based persistence layer framework. The persistence layer framework provided by iBATIS includes SQL Maps and Data Access Objects (DAO). MyBatis eliminates almost all JDBC code and manual setting of parameters and retrieval of result sets. MyBatis uses simple XML or annotations for configuration and original mapping, mapping interfaces and Java POJOs (Plain Old Java Objects, ordinary Java objects) into records in the database. It can be understood that MyBatis is a framework used to help you manage data additions, deletions, modifications and queries.
3 System analysis
3.1 Feasibility analysis
Through preliminary investigation and analysis of the purpose of implementing this catering handheld device ordering system, feasibility plans are proposed and demonstrated one by one. Here we mainly analyze from the aspects of technical feasibility, economic feasibility, operational feasibility and so on.
3.1.1 Technical feasibility
The backend of this catering handheld device ordering system is developed using the SSM framework. It is a mature framework. There are many tutorials for development. There are also many tutorials for WeChat development, and there are many free tutorials on the Internet.
Therefore, the development technology of the catering handheld device ordering system is very feasible, and the developers have mastered certain development technology, so the development technology of this system is feasible.
3.1.2 Economic feasibility
The software used in this restaurant handheld device ordering system is all open source, which can save a lot of energy and resources and reduce development costs. At the same time, the computer configuration requirements are also extremely low, and even obsolete computers can meet the needs. Therefore, this system is completely economically feasible, so it is very economically feasible.
3.1.3 Operational feasibility
The interface of this catering handheld device ordering system is simple and easy to operate, and users can access and operate it as long as they have used a computer. This system has the characteristics of easy operation, easy management and good interactivity. It is very simple in operation, so it has high feasibility in operation.
To sum up, the development goals of this system have been clearly defined, and it is highly feasible in terms of technology, economy and operation. It also requires low investment, perfect functions and convenient management, so the development of the system is completely feasible.
3.2 System performance analysis
3.2.1 System security
This catering handheld device ordering system must strictly control management permissions. The specific requirements are as follows:
(1) If you want to manage the catering handheld device ordering system, you must first log in to the system with your user name and password. Users without permission cannot log in to the system in any way and view any information and data in the system. This can Ensure the safety, reliability and accuracy of the system.
(2) Set different permissions in the specific implementation. Users with different permissions cannot perform skip-level operations after logging in to the system.
3.2.2 Data integrity
(1) All recorded information must be kept comprehensive, and the information recorded content cannot be empty.
(2) The correlation between various data must be kept correct.
(3) The same data must be consistent in different records.
At present, interface design has become a key indicator for evaluating software quality. A good user interface can increase users' confidence and interest in using the system, thereby improving work efficiency. Keep the page as concise as possible to make it fresh and clear, so that the access speed can be improved, and access to the server interface will be faster and faster.
1. Output design
Output is when the computer solves the input basic information, generates high-quality and effective information, and makes it available to managers in a certain format. This is the main responsibility and goal of output design.
The process of system development is opposite to the implementation process, not from input design to output design, but from output design to input design. This is because the output form is directly related to the user, and the design purpose should be to ensure that the user can use the output form easily and to reflect useful information from each department in a timely manner. The principle of output design is to consider all the needs of different management levels as a whole, but also to be concise and not to provide users with unnecessary information.
2. Enter the design
The collection and entry of input data is cumbersome, requires a lot of manpower and certain equipment, and often makes mistakes. Once the data input into the system is incorrect, the processed output will amplify these errors, so the accuracy of the input data plays a decisive role in the performance of the entire system.
The input design has the following principles:
1) The input volume should be kept as low as possible to meet the processing requirements. With less input, there will be fewer errors and less time to prepare the data.
2) The input preparation and input process should be made as convenient as possible, so as to reduce the incidence of errors.
3) The input data should be checked as early as possible (as close as possible to the point where the original data occurred) so that errors can be corrected in a timely manner.
4) Input data is recorded as early as possible into the form required for its processing to prevent errors that may occur when the data is transferred from one medium to another and needs to be transcribed.
3. 4 System process and logic
Figure 3-3 Login flow chart
Figure 3-4 Password changing flow chart
4 System outline design
4.1Overview _ _
The background of this system adopts two modes: B/S structure (Browser/Server, browser/server structure) and Web service-based model. It is a model structure suitable for the Internet environment. As long as users can connect to the Internet, they can use it at any time and anywhere. The system working principle diagram is shown in Figure 4-1:
Figure 4-1 System working principle diagram
4.2 System structure
The designed system functional structure diagram is shown below:
4.3.Database design _
4.3.1 Database entities _ _ _
The goal of conceptual design is to design a conceptual model of a database system that reflects the information needs of an organizational department. The conceptual model of the database system is independent of the logical structure of the database system, the database management system (DBMS), and the computer system.
The design method of conceptual schema is to use conceptual data models (such as ER models) to represent data and the interconnections between data based on demand analysis, and to design a database system conceptual schema that reflects user information needs and processing needs. The goal of conceptual design is to accurately describe the information model in the application field and support various applications of users, so that it can be easily converted into a logical model of the database system and easily understood by users. The database system conceptual model is a data model oriented to the real world and cannot be directly used for the implementation of the database system. At this stage, users can participate in and evaluate the design of the database system, which helps ensure that the design of the database system matches the needs of users. In the design of conceptual models, the ER model method is the most common design method. The ER diagram of this system is shown below:
Franchise application entity attribute diagram
4.3.2 Database design table _ _
The catering handheld device ordering system requires a backend database. The detailed information of each table in the database is introduced below:
Table 4.1 Dishes information table
| serial number |
List |
type of data |
illustrate |
Allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
addtime |
Date |
creation time |
yes |
| 3 |
caipinbianhao |
String |
Dishes number |
yes |
| 4 |
caipinmingcheng |
String |
Dishes name |
yes |
| 5 |
caixi |
String |
Cuisine |
yes |
| 6 |
tupian |
String |
picture |
yes |
| 7 |
jiage |
Integer |
price |
yes |
| 8 |
kouweipianhao |
String |
Taste preference |
yes |
| 9 |
jianjie |
String |
Introduction |
yes |
| 10 |
canyindianzhanghao |
String |
Restaurant account |
yes |
| 11 |
canyindianmingcheng |
String |
Restaurant name |
yes |
Table 4.2 Cuisine list
| serial number |
List |
type of data |
illustrate |
Allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
addtime |
Date |
creation time |
yes |
| 3 |
caixi |
String |
Cuisine |
yes |
Table 4.3 Restaurant table
| serial number |
List |
type of data |
illustrate |
Allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
addtime |
Date |
creation time |
yes |
| 3 |
canyindianzhanghao |
String |
Restaurant account |
yes |
| 4 |
mima |
String |
password |
yes |
| 5 |
canyindianmingcheng |
String |
Restaurant name |
yes |
| 6 |
tupian |
String |
picture |
yes |
| 7 |
dizhi |
String |
address |
yes |
| 8 |
canyindianxiangqing |
String |
Restaurant details |
yes |
| 9 |
lianxifangshi |
String |
Contact information |
yes |
Table 4.4 Dining table
| serial number |
List |
type of data |
illustrate |
Allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
addtime |
Date |
creation time |
yes |
| 3 |
zhuohao |
String |
Table number |
yes |
Table 4.5 Table status table
| serial number |
List |
type of data |
illustrate |
Allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
addtime |
Date |
creation time |
yes |
| 3 |
canyindianzhanghao |
String |
Restaurant account |
yes |
| 4 |
canyindianmingcheng |
String |
Restaurant name |
yes |
| 5 |
tupian |
String |
picture |
yes |
| 6 |
canzhuo |
String |
dining table |
yes |
| 7 |
canzhuozhuangtai |
String |
table status |
yes |
| 8 |
yongcanrenshu |
Integer |
Number of people dining |
yes |
| 9 |
yongcanshijian |
String |
dining time |
yes |
| 10 |
gonghao |
String |
Job number |
yes |
| 11 |
yuangongxingming |
String |
employee's name |
yes |
| 12 |
userid |
Integer |
user id |
yes |
Table 4.6 Configuration file table
| serial number |
List |
type of data |
illustrate |
Allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
name |
String |
Configuration parameter name |
yes |
| 3 |
value |
String |
Configuration parameter values |
yes |
Table 4.7 Franchise Application Form
| serial number |
List |
type of data |
illustrate |
Allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
addtime |
Date |
creation time |
yes |
| 3 |
shenqingbianhao |
String |
Application number |
yes |
| 4 |
canyindianzhanghao |
String |
Restaurant account |
yes |
| 5 |
canyindianmingcheng |
String |
Restaurant name |
yes |
| 6 |
tupian |
String |
picture |
yes |
| 7 |
jiamengmingcheng |
String |
加盟名称 |
是 |
| 8 |
jiamengdiqu |
String |
加盟地区 |
是 |
| 9 |
zhanghao |
String |
账号 |
是 |
| 10 |
xingming |
String |
姓名 |
是 |
| 11 |
shouji |
String |
手机 |
是 |
| 12 |
shenqingshijian |
Date |
申请时间 |
是 |
| 13 |
sfsh |
String |
是否审核 |
是 |
| 14 |
shhf |
String |
审核回复 |
是 |
表4.8token表表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
userid |
Integer |
用户id |
是 |
| 3 |
username |
String |
用户名 |
是 |
| 4 |
tablename |
String |
表名 |
是 |
| 5 |
role |
String |
角色 |
是 |
| 6 |
token |
String |
密码 |
是 |
| 7 |
addtime |
Date |
新增时间 |
是 |
| 8 |
expiratedtime |
Date |
过期时间 |
是 |
表4.9退单信息表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
addtime |
Date |
创建时间 |
是 |
| 3 |
dingdanbianhao |
String |
订单编号 |
是 |
| 4 |
caipinmingcheng |
String |
菜品名称 |
是 |
| 5 |
caixi |
String |
菜系 |
是 |
| 6 |
tupian |
String |
图片 |
是 |
| 7 |
jiage |
String |
价格 |
是 |
| 8 |
shuliang |
String |
数量 |
是 |
| 9 |
zongjine |
String |
总金额 |
是 |
| 10 |
canyindianzhanghao |
String |
餐饮店账号 |
是 |
| 11 |
canyindianmingcheng |
String |
餐饮店名称 |
是 |
| 12 |
xiadanshijian |
Date |
下单时间 |
是 |
| 13 |
canzhuo |
String |
餐桌 |
是 |
| 14 |
zhanghao |
String |
账号 |
是 |
| 15 |
xingming |
String |
姓名 |
是 |
| 16 |
tuidanshijian |
Date |
退单时间 |
是 |
| 17 |
tuidanyuanyin |
String |
退单原因 |
是 |
| 18 |
sfsh |
String |
是否审核 |
是 |
| 19 |
shhf |
String |
审核回复 |
是 |
表4.10用户表表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
username |
String |
用户名 |
是 |
| 3 |
password |
String |
密码 |
是 |
| 4 |
role |
String |
角色 |
是 |
| 5 |
addtime |
Date |
新增时间 |
是 |
表4.11我的订单表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
addtime |
Date |
创建时间 |
是 |
| 3 |
dingdanbianhao |
String |
订单编号 |
是 |
| 4 |
caipinmingcheng |
String |
菜品名称 |
是 |
| 5 |
caixi |
String |
菜系 |
是 |
| 6 |
tupian |
String |
图片 |
是 |
| 7 |
jiage |
Integer |
价格 |
是 |
| 8 |
shuliang |
Integer |
数量 |
是 |
| 9 |
zongjine |
String |
总金额 |
是 |
| 10 |
canyindianzhanghao |
String |
餐饮店账号 |
是 |
| 11 |
canyindianmingcheng |
String |
餐饮店名称 |
是 |
| 12 |
xiadanshijian |
Date |
下单时间 |
是 |
| 13 |
zhanghao |
String |
账号 |
是 |
| 14 |
xingming |
String |
姓名 |
是 |
| 15 |
canzhuo |
String |
餐桌 |
是 |
| 16 |
sfsh |
String |
是否审核 |
是 |
| 17 |
shhf |
String |
审核回复 |
是 |
| 18 |
ispay |
String |
是否支付 |
是 |
表4.12销售统计表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
addtime |
Date |
创建时间 |
是 |
| 3 |
canyindianzhanghao |
String |
餐饮店账号 |
是 |
| 4 |
canyindianmingcheng |
String |
餐饮店名称 |
是 |
| 5 |
tupian |
String |
图片 |
是 |
| 6 |
zongyingli |
Integer |
总盈利 |
是 |
| 7 |
tongjishijian |
Date |
统计时间 |
是 |
表4.13用户表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
addtime |
Date |
创建时间 |
是 |
| 3 |
zhanghao |
String |
账号 |
是 |
| 4 |
mima |
String |
密码 |
是 |
| 5 |
xingming |
String |
姓名 |
是 |
| 6 |
xingbie |
String |
性别 |
是 |
| 7 |
shouji |
String |
手机 |
是 |
| 8 |
youxiang |
String |
邮箱 |
是 |
| 9 |
shenfenzheng |
String |
身份证 |
是 |
| 10 |
zhaopian |
String |
照片 |
是 |
表4.14员工表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
addtime |
Date |
创建时间 |
是 |
| 3 |
gonghao |
String |
工号 |
是 |
| 4 |
mima |
String |
密码 |
是 |
| 5 |
yuangongxingming |
String |
员工姓名 |
是 |
| 6 |
xingbie |
String |
性别 |
是 |
| 7 |
shouji |
String |
手机 |
是 |
| 8 |
youxiang |
String |
邮箱 |
是 |
| 9 |
zhaopian |
String |
照片 |
是 |
| 10 |
canyindianzhanghao |
String |
餐饮店账号 |
是 |
| 11 |
canyindianmingcheng |
String |
餐饮店名称 |
是 |
5系统详细实现
5.1 管理员模块的实现
5.1.1 菜品信息管理
管理员可以查询，修改，删除餐饮店发布的菜品信息。具体界面的展示如图5.1所示。
图5.1 菜品信息界面
5.1.2 用户信息管理
管理员可以对用户进行查询修改，删除操作。具体界面如图5.2所示。
图5.3 用户信息管理界面
5.1.3 我的订单管理
系统管理员可以对我的订单进行查询，修改，删除操作。界面如下图所示：
图5.4 我的订单管理界面
5.1.4 菜系管理
系统管理员可以对菜系进行添加修改删除操作。界面如下图所示：
5.2 用户模块的实现
5.2.1 菜品信息
系统首页上面有导航，可以餐饮店，菜品信息，个人中心等导航，不管是查看餐饮店还是菜品信息都可以查到具体的菜品信息，用户只有登录后才可以进行下单操作。界面如下图所示：
图5.5 菜品信息
5.2.2 我的订单
用户登录后，在我的后台里面可以看到自己的订单，可以对订单进行支付操作。界面如下图所示：
图5.6 我的订单
5.3 员工模块的实现
5.3.1 餐桌状态管理
员工登录后可以在餐桌状态管理里面对餐桌状态信息进行添加，修改，删除，查询操作。界面如下图所示：
图5.7 餐桌状态界面
5.4 餐饮店模块的实现
5.4.1 菜品信息管理
餐饮店可以对菜品信息进行添加，修改，删除，查询操作。界面如下图所示：
图5.8 菜品信息管理界面
5.4.2 销售统计管理
餐饮店可以对销售进行统计操作，也可以查看统计报表。界面如下图所示：
图5.9 统计报表界面
5.4.3 员工管理
餐饮店可以对员工信息进行添加，修改，删除，查询操作。界面如下图所示：
图5.10 员工管理界面
6系统测试
6.1概念和意义
测试的定义：程序测试是为了发现错误而执行程序的过程。测试(Testing)的任务与目的可以描述为：
目的：发现程序的错误；
任务：通过在计算机上执行程序，暴露程序中潜在的错误。
另一个预测是相关的术语叫纠错(Debugging)。它的目的与任务可以规定为：
目的：定位和纠正错误；
任务：消除软件故障，保证程序的可靠运行。测试与纠错的关系，可以用图6-1的数据流图来说明。图中表明，每一次测试都要准备好若干必要的测试数据，与被测试程序一道送入计算机执行。通常把一次程序执行需要的测试数据，称为一个“测试用例(Test Case)。每一个测试用例产生一个相应的“测试结果”。如果它与“期望结果”不想符合，便说明程序中存在错误，需要用纠错来改正。
图6.1测试与纠错信息流程
6.2特性
（1）挑剔性
测试是为了证明程序有错，而不是证明程序无错。因此，对于被测程序就是要“纯毛求疵”，就是要“鸡蛋里挑骨头”。
（2）复杂性
测试仪程序则比较容易，这其实是一个误区。设计测试用力是一项需要细致和高度技巧的高能工作，稍有不慎就会顾此失彼，发生不应用得数楼。
（3）不彻底性
实际测试都是不彻底的，当然不能够保证测试后的程序不存在遗漏的错误。
（4）经济性
通场这种测试称为“选择测试（Selective Testing）”。为了降低测试成本，选择测试用力是应注意遵守“经济性”的原则。
6.3重要性
软件测试在软件生命周期中占据重要的地位，在传统的瀑布模型中，软件测试学仅处于运行维护阶段之前，是软件产品交付用户使用之前保证软件质量的重要手段。近来，软件工程界趋向于一种新的观点，即认为软件生命周期每一阶段中都应包含测试，从而检验本阶段的成果是否接近预期的目标，尽可能早的发现错误并加以修正，如果不在早期阶段进行测试，错误的延时扩散常常会导致最后成品测试的巨大困难。
6.4测试方法
首先我们来说界面测试，界面测试是为了使程序在不同的的操作平台上能够运行界面，并且能够保持原来的风格。我把完整程序拷贝到Windows 7环境下，似的程序运行正常，运行界面上的字体图片等设置都能够保持得非常好。不出现字体变形等情况！
其次进行功能测试。该系统测试采用的是单元测试，集成测试，完善性测试等多种方式进行测试。
经过测试，所有功能都能得以实现，没有任何变形。至此，在功能的测试上也已经比较圆满的完成了。
由于经验不足，写代码时出现了一些考虑不周的系统缺陷，写代码的时候会出现与设想不一致，比如说代码不规范导致接口与接口之间出现问题，功能与客户的要求不符合，这样导致产品不能过关，无法交付。所以产品在上线前必须反复测试，经过反复测试，修改，再测试，再修改，产品才能够不断完善。在整个系统测试中，根据需求文档和设计文档，逐一对功能进行检测并写好测试用例，有效避免残片缺陷，因为产品出现缺陷不仅影响功能，而且可以导致数据的不准确，导致产品质量的降低，经过测试，才能使得产品的稳定性和成熟度得到极大的提升，产品质量也才有保证。
6.5 功能测试
功能测试主要包括五项内容：适用性、准确性、可操作性、依从性、安全性。
本系统功能测试如表6.1所示：
表6.1 系统功能测试
| 测试内容 |
测试结果 |
| 适用性 |
好 |
| 准确性 |
好 |
| 可操作性 |
好 |
| 依从性 |
好 |
| 安全性 |
好 |
6.6可用性测试
可用性测试用于检测系统的可操作性、可理解性、可学习性等方面内容。具体测试方面如表6.2所示。
表6.2 系统可用性测试
| 测试项 |
测试人员的评价 |
| 窗口移动、大小改变、关闭等操作是否正常 |
是 |
| 操作模块是否友好 |
是 |
| 模块、提示内容等文字描述是否正确 |
是 |
| 模块布局是否协调、合理 |
是 |
| 模块的状态是否正确（对选中项能否发生对应切换） |
是 |
| 鼠标、键盘操作是否支持 |
是 |
| 所需数据项是否正确显示 |
是 |
| 操作流程是否合理 |
是 |
| 是否提供帮助信息 |
是 |
6.7性能测试
性能测试主要通过模拟系统运行环境，测试系统性能是否符合客户需求。性能测试的重要技术指标就是：系统运行速度、网络响应时间和支持并发节点数。
1）系统运行速度：通过在不同计算机上试运行本系统，没有发现有任何迟滞、停顿现象。
2）网络响应时间：网络响应时间主要包括网络最小响应时间、平均响应时间、最大响应时间三个参数。经过测试，在网络运营良好状态下，NBA局域网内响应时间三参数为：1/2/6s，NBA外网响应时间三参数为3/7/12s，符合客户需求，属于用户心理可承受范围。
3）支持并发节点数：经过模拟环境测试，本系统在并发节点达46个时，网络运营速度会发生较大波动，延迟时间10秒左右，符合客户需求。
6.8测试分析
本网站设计时借鉴了国内外优秀网站的优点，从界面到系统设计都保证了用户能够方便操作。系统的主要特点和优点归纳如下：
（1）本系统用的移置性和针对性都比较高，因为针对性高可以提供更好的服务而移置性可以在多个系统上运行，更给客户带来了极大的方便。
（2）该完整内容全面，管理方便可以及时的全面的处理各种错误，异常，这样避免了很多因用户的马虎操作而出现的失误，其操作方便，用户界面友好，能够上网的人都可以很好的进行操作。
6.9测试结果分析
经过对上述测试结果分析，本系统符合用户需求。所有基本功能点实现，操作简单，操作流程简单合理，产品运行性能良好，是一款值得推广的餐饮掌上设备点餐系统。
结论
在这次毕业设计中遇到的最困难的方面就是在数据库方面的知识，在刚开始进行毕业设计的时候感觉十分困难，根本不知道该从何处下手，但不断的坚持，设计最终被完成。无论多么的困难，只要能够坚持下来，善于去找到好的材料来研究，在研究中充分利用资源，没有困难是不会被成功解决的。
在开发系统的过程中，本人运用到了开发技术和平时学习中所了解的一些技术，通过实现这些技术，大大提高了整个系统的性能。在论文中这些技术都做了比较详细的介绍。本系统还存在很多缺点和不完善的地方，例如有些细节上做的还不够完善，有些功能模块还需要加强。在今后的日子里，能够对这些不足进行改善。
通过这次最终的毕业设计，平时所学到的知识不仅融合了，而且获得了许多计算机知识。在整个设计过程中明白了许多东西，也培养独立工作能力，树立信心，对自己能力的工作能力，我相信以后会学习和工作生活中有至关重要的作用。同时也大大提高了手的能力，使其难以充分体会探索的乐趣和成功的创作过程，设计过程中汲取的东西，是一笔宝贵的财富。
回顾过去做毕业设计的整个过程，充满了付出和收获，但是当你看到成果的时候的感觉，是一种难以用言语表达的喜悦之感这些在毕业设计过程中学习到的东西将会使我终身受益！
最后，感谢指导老师的关心和指导，在我毕业设计的整个过程中，他给与了我很多的帮助和讲解，在导师的帮助下我的毕业设计才能如此顺利的完成。
致谢语
经过几个多月的不断学习，我的毕业设计终于如期完成。此次毕业设计是对我们日常所学计算机理论知识的一次综合性评测，也是将理论应用到实践的一项考察。
首先我要感谢此次指导我的老师，是他的及时纠正我在设计当中出现的问题，使得我的设计高质量完成。指导老师在我本次餐饮掌上设备点餐系统的开发过程中，为程序、框架的设计、代码等方面以及论文设计提供了很多宝贵的意见，并且为我推荐了许多相关的资料，他的指导和建议使我受益匪浅，通过老师的耐心辅导和指点，我的论文顺利完成，在此，我表示深刻的感谢。
我也要感谢帮助过我的同学们，和我一起探讨论文的不足，给我的设计提出宝贵的建议，在这次设计中他们的帮助使得我的设计更加完善更加具体。
最后，我也要感谢学校为我们提供了一个良好的学校环境。祝愿学校的领导教师以及和我一起奋斗的同学们工作顺利，事业有成，也要祝愿学校的前景更加辉煌。
参考文献
[1]付昕. 基于B/S模式仓库管理系统的实现[J].山东省农业管理干部学院学报, 2010, 27(4):166-168
[2] 王玉英. 基于JSP的MySQL数据库访问技术[J]. 现代计算机：专业版, 2010, 19(14):63-66
[3] David L.Anderson.Managing Information Systems.清华大学出版社，2002：16
[4] 王家华．软件工程[M]，沈阳：东北大学出版社，2011：46
[5] 张孝祥,徐明华.软件开发课堂.清华大学出版社，2009：55
[6] 崔洋.MySQL数据库应用从入门到精通.中国铁道出版社，2013：27
[7] 王珊,萨师煊.数据库系统概论.高等教育出版社, 2006：16
[8] 崔洋.MySQL数据库应用从入门到精通.中国铁道出版社，2013：27
[9] 王珊,萨师煊.数据库系统概论.高等教育出版社, 2006：16
[10] 张海潘.软件工程导论.清华大学出版社，2008：86
[11] 黄艳峰. 在Java语言中实施“案例教学”的研究与探索[J]. 电脑知识与技术, 2010, 6(5):1148-1149
[12] 王玉英. 基于JSP的MySQL数据库访问技术[J]. 现代计算机：专业版, 2010, 19(14):63-66
[13]邱丹萍.Web开发中SSM框架的分析[J].电脑知识与技术,2020,16(17):81-82.
[14]薛茹.基于SSM框架的Web系统研究与应用[J].计算机产品与流通,2018(07):30.
[15]唐权.SSM框架在JavaEE教学中的应用与实践[J].福建电脑,2017,33(12):93-94+61.
[16]袁堂青,亓婧.基于的开发与研究[J].网络安全技术与应用,2020(04):66-67.
[17]邢榕珊,匡芳君.设计[J].计算机时代,2018(08):9-12.