1. Screenshots of the system (if you need a demo video, you can chat privately)
Since the development of network technology and computer technology, they already have a profound theoretical foundation and have been fully used in reality, especially the software based on computer operation has attracted the attention of all walks of life. In addition, people have entered the information age, so the promotion and management of information is very important. Therefore, it is necessary to computerize and systematize the management of barber shop member information. Designing and developing a barber shop member management system will not only save manpower and management costs, but also safely save a huge amount of data. It does not take a lot of time to maintain and retrieve barber shop member information, which is very convenient.
The barber shop member management system is to create a data table in MySQL to save information, and use the SSM framework and Java language to write. Design and implement according to the software design and development process. The system is friendly and fully functional. The functions realized by the system include store management, hairdressing management, user appointment management, user sharing management, message management and other functions.
While the barber shop member management system standardizes the barber shop member information, it can also detect wrong data in a timely manner through the validity rules of data input, so that the data entry can achieve the purpose of accuracy, thereby improving the data provided by the barber shop member management system The reliability of the system minimizes the error rate of the system data.
Key words : barber shop membership management system; MySQL; SSM framework
directory
1.1 Background of topic selection
1.2 Significance of topic selection
2 System Development Technology
3.2 System performance analysis
3.2.1 Ease of use of the system
4.2 Functional structure design
4.3.2 Database table structure
5.1 Administrator function realization
5.1.1 Hairdressing Information Management
5.1.2 User reservation management
5.1.4 Management of preferential activities
1 Introduction
1.1 Background of topic selection
Since the development of network technology and computer technology, they already have a profound theoretical foundation and have been fully used in reality, especially the software based on computer operation has attracted the attention of all walks of life. Computer software can set different functions according to the business characteristics and management needs of different industries, which can meet the actual operation requirements of various industries. Its fast and convenient information processing mode can already free information managers from tedious work. Easy maintenance and security of data can be realized. In addition, people have entered the information age, so the promotion and management of information is very important. Therefore, the information management mode is also the current management trend. For barber shop member information, if the old method is still used, it will affect its competitiveness in the industry, and it will be easily eliminated by the times. Therefore, it is necessary to computerize and systematize the management of barber shop member information. Designing and developing a barber shop member management system will not only save manpower and management costs, but also safely save a huge amount of data. It does not take a lot of time to maintain and retrieve barber shop member information, which is very convenient.
1.2 Significance of topic selection
In practical application, the barber shop membership management system is also helpful to improve the comprehensive quality of administrators. Because the barber shop membership management system not only reduces the workload of the barber shop member information management personnel, but also allows them to use the time saved to enrich themselves and improve their personal abilities, so that they can give full play to the barber shop member management system. The service allows the barber shop member management system to display data information and at the same time complete data processing quickly to improve service levels. Moreover, the development of the barber shop member management system requires relatively low investment costs, but in the later application, it will generate a lot of benefits, especially when the barber shop member management system is in high-load operation, it can also ensure the quality of data processing and data security. The optimization of the process of processing work can save the manpower and capital invested in the traditional mode, thereby reducing the cost of information management. In addition, while the barber shop member management system standardizes the barber shop member information, it can also detect wrong data in a timely manner through the validity rules of data input, so that the data entry can achieve the purpose of accuracy, thereby improving the barber shop member management system. The reliability of the data reduces the error rate of the system data to a minimum.
1.3 Research content
To describe the system according to the common process of designing and developing a system, the system can be divided into analysis phase, design phase, implementation phase, and testing phase. Therefore, when writing the description document of the system, describe the content of the system according to the stage of the system.
Introduction: This is an introduction to the background and significance of the selected topic.
System development technology: This is an introduction to the technology to be used by the system, including the tools used, programming language, etc.
System analysis: This is an analysis of the system, including the necessary feasibility analysis in the early stage of investment, including the introduction of the needs of user research and acquisition, including the performance of the system operation.
System design: This is the design of the system, including the introduction of the system function structure designed by using drawing tools, including the storage structure of the designed data table to be created in the database.
System Implementation: This is the coding implementation of the system. Including the operation effect of each module of the implemented system, etc., to make an introduction.
System testing: This is to test the compiled system. Including functional testing and other content to make an introduction.
2 System Development Technology
This part mainly introduces the technology used in this system, including the tools used, programming language and so on.
2.1 Java language
The Java language has been used for more than 25 years since 1995, and it still has a large market share in software development. Back then, Sun invented Java to develop a cross-platform high-level programming language, allowing program developers to focus on the program development process without paying attention to which platform the server belongs to, because the cross-platform feature makes the language develop rapidly. The development of Java has absorbed the advantages of languages such as C++, because new things generally solve some pain points of old things. Although Java also has many shortcomings, it is at least a development direction. Learning Java does not require too many concepts of pointers, nor does it need to learn too complicated data structure theories, such as stack concepts, unless some special industries have strict requirements for these, generally developing programs in Java does not need to consider various various data structures. Because Java is a strongly typed language, various corresponding types have been defined for various data. Java defines two types of data types, one is the basic type, which contains 8 basic attributes, and the other is the wrapper class. There is a clear distinction between the basic class and the wrapper class in terms of fundamental definitions, and the computer operation will also have obvious differences. If you use it wrong, it will cause compilation errors and affect the running effect. The various advantages of Java only need to be done step by step. You can use it for learning.
2.2 SSM framework
The framework technology mainly used in the application program developed in this project is SSM, which is the abbreviation of a set of frameworks in the Java language. At present, there are two main branches in the Java language. One is to focus on the Java language. After learning the basics of Java, you will There are many Java advanced frameworks to learn, mainly for the development and design of the application background, and on the other hand, to switch to learn the Android language, mainly for the front-end design of Android, although it is also the Java language, but mainly to learn the Android platform Various architectures and frameworks too. But regardless of the front-end application, the SSM framework is mainly a collection of mainstream frameworks developed for the server side. Aiming at the bloat and cumbersome configuration of the traditional SSH framework, both development and secondary development will cause a lot of waste of time, and the learning above cannot be effectively connected. It is necessary to adapt to various designs of the framework, and the framework design is relatively rigid. Error-prone. The SSM framework is currently the most popular. It bid farewell to the cumbersome configuration, makes the configuration more flexible, and makes the data operation more convenient. It feels very appropriate to choose the SSM framework for development.
2.3 MYSQL database
The relational database design, the design of the database field type and the design of the field length, all the time affect the operation efficiency of a large number of data operations after the subsequent program development. Relational databases have explanations for different field types. Based on the application development required by the subject, finding the most suitable relational database is basically considered. Relational databases have been developed for decades. Survival of the fittest leads to the fact that there are not many relational databases that still exist, and they can basically meet the functional needs of applications. Therefore, it is necessary to consider databases from other aspects. choose. From the perspective of installation and maintenance, the SQL Server database has several G installation packages, and many unnecessary functions will be installed during the installation process, which consumes a lot of resources. The Oracle database is not smaller than the SQL Server installation package, and there will be many problems in the installation. For the needs of the project, it is not necessary to be so troublesome, and the installation also requires various activations. Only the MySQL database is completely suitable, and the installation package is tens of megabytes in size. , it is not stressful to run. After all, there are many other useful things on the development computer, and it is completely free, so I chose the MySQL database as the preferred database.
3 System Analysis
Although this part is at the beginning of the development process, it plays an important role in the subsequent design and implementation, because the quality of the system analysis results will directly affect the development of the subsequent links.
3.1 Feasibility study
There are many factors that affect system development. For example, the development cost is high and it is not suitable for development, or the development time exceeds expectations and it is not suitable for development. Therefore, before formally making a development decision, study the feasibility of the system, and demonstrate whether the system can be developed from the perspectives of economy, time, and operation.
3.1.1 Economic feasibility
The barber shop membership management system can simplify the workflow, provide information processing functions, and save data for a long time. It consumes less time in later data query and editing, improves the efficiency of information management, and brings considerable benefits. For the development of this system, no matter the computer needed for development or the development tools, the investment cost is very low. The computer is the computer in the computer room, and the development tools are downloaded and installed from the Internet, and no fees are charged.
3.1.2 Time Feasibility
The barber shop member management system is a work of my final project. The college also fully reserved the production time, and arranged corresponding tasks in each time period. Therefore, it is possible to carry out work according to this schedule. Design is done.
3.1.3 Operation Feasibility
With the popularity of computers, many people can operate computers independently. This system runs on a computer equipped with a running environment. Its functions are simple and save a lot of cumbersome operation logic. Users can directly enter the functional operation area through page navigation, so anyone who knows a little bit about computers can easily Complete the use of the system.
In summary, the system can carry out the next work.
3.2 System performance analysis
In order to reduce the error rate of the system in actual use, it is necessary to analyze the performance of the system. Common indicators that can evaluate system performance include security, usability, and robustness.
3.2.1 Ease of use of the system
The information and services provided by the system have specific user groups. Therefore, users prefer an easy-to-use system to an inconvenient one. So it is very important that the system is easy to use.
3.2.2 System Robustness
In the process of interacting with the user, the system should have a corresponding feedback mechanism to deal with the user's misoperation behavior, instead of entering a system crash state. There are many functions set up in the system. When an abnormal situation occurs in a certain function of the system, other functions of the system can still be used by users. This is the embodiment of the robustness of the system.
3.2.3 System security
The data stored in the system are relatively important system resources. Once these resources are leaked, not only will there be property losses, but many customers will also be lost. Therefore, the data in the system must be in a safe environment at all times, so measures need to be taken to ensure data security, such as setting the login function, using security verification technology to guide conditional users to enter the specified page, and let non-conditional users stay on the login page. Unable to access the system.
3.3 System flow analysis
The idea of software development and design runs through this system, and its development process is shown in the figure below. In the early stage, functional analysis, functional design, and the design of the system's back-end support database are required. The designed system is implemented using coding technology, and then tested and improved.
Figure 3.1 System Development Flowchart
The reason why a visitor can access the barber shop member management system is that its database has the record information of the visitor, and this record is the data written through registration. The registration process is shown in the figure below. Whenever a visitor registers with the barber shop membership management system, each record registered will be judged one by one in the background of the system. This judgment rule is set in advance. Once the visitor's registration information is saved in the database, it means that the visitor becomes a member of the barber shop member management system.
Figure 3.2 Registration flow chart
The premise of the visitor's operating system is that identity verification is required, and the setting of the login function is to guide the users of the system into the background operation area and keep out the users who are not the system. Its process is shown in the figure below.
Figure 3.3 Login flow chart
3.4 System function analysis
After clarifying the purpose of the system and the target user group of the system, the functions of the system can be set, the requirements of the research users for the functions can be obtained, and the functions of the system can be obtained by analyzing and summarizing similar systems in the market.
The barber shop membership management system has set up administrator privileges, and its use case diagram is shown in the figure below. After the administrator logs in to his background, he can manage hairdressing, shops, promotional activities, share information with users, and review the hairdressing information reserved by users.
Figure 3.4 Administrator use case diagram
The barber shop membership management system has set user permissions, and its use case diagram is shown in the figure below. Users make appointments for hairdressing, view and comment on shops, promotions and user sharing information.
Figure 3.5 User use case diagram
4 System Design
At present, there are many types of systems. Judging from the content presented by the system, the types of systems include social, business, government, and news. Then, among the many types of systems, the primary task of system design is to first clarify the type of system to be designed, and then specify the user group, functions, etc. of the system on this basis, and design a system with unique experience and vision based on this information . Only in this way can the system be more distinctive, and it can also leave a deep impression on users among many similar systems.
4.1 System Objectives
In terms of function formulation, the system strictly refers to the requirements of users, but when designing this system, it must also meet the design requirements of easy operation and convenient use. Therefore, to design a system that is standardized and meets user needs, the following system goals must be achieved.
The first system goal: the operation mode between the user and the system is based on man-machine dialogue, and the design of the visual interface is not only beautiful, but also friendly. All kinds of information provided by the visual interface meet the requirements of accuracy and reliability, and can be viewed flexibly by users.
The second system goal: the data generated by the interaction between the user and the system must be stored in the database in a strict and standardized manner, and the data security must be ensured whether it is searched and managed by the management personnel in the later stage.
The third system goal: to realize the functions required by users. According to the functional requirements obtained from the user survey, the design and implementation of the barber shop membership management system are completed.
The fourth system goal: In the necessary link, check the data registered by the user, including the length of the data, and the type of data input, etc., and timely feedback when errors are found, and guide the user to standardize the registration data. Common data verification includes password modification, registration and login, and user information filling.
The fifth system goal: To design and develop this system, we need to do our best. In addition to the characteristics of easy operation of the system, it is also required that the system is easy to maintain during later use, so that the system has the characteristics of easy maintenance.
The sixth system goal: when the system is delivered to users, it can achieve the goal of stable operation. In addition, the system is safe and meets the requirements of reliability, so users can use it with confidence.
4.2 Functional structure design
The function analysis done above is only a general function of the system, and this part needs to carry out the detailed design of each module on this basis.
The detailed functions of the designed administrator are shown in the figure below. After the administrator logs in to his background, he can manage hairdressing, shops, promotional activities, share information with users, and review the hairdressing information reserved by users.
Figure 4.1 Administrator function structure diagram
The detailed functions of the designed users are shown in the figure below. Users make appointments for hairdressing, view and comment on shops, promotions and users share information.
Figure 4.2 User function structure diagram
4.3 Database design
Compared with non-relational databases, the most widely used and easy-to-maintain databases in the market are relational databases. This database is mainly based on the relational model to organize data information. That is, the common two-dimensional table model. It can be said that the relationship between two-dimensional tables and two-dimensional tables constitutes a relational database.
4.3.1 Database ER Diagram
In order to better save the data generated by the barber shop member management system, it is necessary to establish the ER model in the database design phase and complete the creation of the table structure in the database. The main reasons for the design of the database are as follows:
The first point: prevent code redundancy;
The second point: prevent excessive memory consumption;
The third point: improve the overall performance of the database to facilitate program development and data update;
The fourth point: to ensure the integrity of the data;
The content of this part is mainly to establish the ER model of this system. It is necessary to collect data first, and then analyze the needs of users according to the idea of database implementation. During this period, it is necessary to identify entities, attributes, and relationships to draw the ER model. Well prepared. At the same time, in the drawing, we must also pay attention to the drawing specifications and pay attention to the correct use of each symbol.
(1) The attributes of the designed store entity are shown in the figure below.
Figure 4.4 Store entity attribute map
(2) The properties of the designed hairdressing entity are shown in the figure below.
Figure 4.5 Property map of hairdressing entity
(3) The designed user entity, its attributes are shown in the figure below.
Figure 4.6 User entity attribute graph
(4) The attributes of the designed message entity are shown in the figure below.
Figure 4.7 Message entity attribute diagram
(5) The relationship between the designed entities is shown in the figure below.
Figure 4.8 ER diagram of relationship between entities
4. 3 .2 Database table structure
In order to design a database with reasonable structure and excellent performance, three paradigms need to be followed when designing the database:
First normal form: ensure that the field values represented by each column in the data table can no longer be decomposed;
The second normal form: on the basis of satisfying the first normal form, let each column in the data table be related to the primary key;
Third normal form: On the basis of satisfying the second normal form, ensure that each column of data is directly related to the primary key, not indirectly.
It can be seen from the above statement that these three paradigms are differentiated in terms of levels. The lowest level is the first normal form, the highest level is the third normal form, and the one that tends to be in the middle is the second normal form. In short, database design is carried out according to these three paradigms, which can simplify the design process and reduce data redundancy, which is also very helpful for improving the efficiency of data retrieval.
Table 4.1 Hairdressing Review Information Form
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| refid |
bigint(20) |
no |
Association table id |
|
| userid |
bigint(20) |
no |
user id |
|
| nickname |
varchar(200) |
yes |
NULL |
username |
| content |
longtext |
no |
comments |
|
| reply |
longtext |
yes |
NULL |
reply content |
Table 4.2 Store Review Information Form
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| refid |
bigint(20) |
no |
Association table id |
|
| userid |
bigint(20) |
no |
user id |
|
| nickname |
varchar(200) |
yes |
NULL |
username |
| content |
longtext |
no |
comments |
|
| reply |
longtext |
yes |
NULL |
reply content |
Table 4.3 User sharing comment information table
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| refid |
bigint(20) |
no |
Association table id |
|
| userid |
bigint(20) |
no |
user id |
|
| nickname |
varchar(200) |
yes |
NULL |
username |
| content |
longtext |
no |
comments |
|
| reply |
longtext |
yes |
NULL |
reply content |
Table 4.4 Promotional Activity Review Information Form
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| refid |
bigint(20) |
no |
Association table id |
|
| userid |
bigint(20) |
no |
user id |
|
| nickname |
varchar(200) |
yes |
NULL |
username |
| content |
longtext |
no |
comments |
|
| reply |
longtext |
yes |
NULL |
reply content |
Table 4.5 Hairdressing Information Form
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| mingcheng |
varchar(200) |
yes |
NULL |
name |
| Xiangmuleixing |
varchar(200) |
yes |
NULL |
project type |
| hulixiaoguo |
longtext |
yes |
NULL |
Nursing effect |
| jiage |
int(11) |
yes |
NULL |
price |
| Xiangqing |
longtext |
yes |
NULL |
details |
| tupian |
varchar(200) |
yes |
NULL |
picture |
| thumbsupnum |
int(11) |
yes |
0 |
Thumbs up |
| crazilynum |
int(11) |
yes |
0 |
step on |
Table 4.6 Message board information table
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| userid |
bigint(20) |
no |
message id |
|
| username |
varchar(200) |
yes |
NULL |
username |
| content |
longtext |
no |
Message content |
|
| reply |
longtext |
yes |
NULL |
reply content |
Table 4.7 Hairdressing Information Information Sheet
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| title |
varchar(200) |
no |
title |
|
| introduction |
longtext |
yes |
NULL |
Introduction |
| picture |
varchar(200) |
no |
picture |
|
| content |
longtext |
no |
content |
Table 4.8 Store information table
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| shangpumingcheng |
varchar(200) |
no |
store name |
|
| shangpudizhi |
varchar(200) |
yes |
NULL |
shop address |
| jingyingfanwei |
varchar(200) |
yes |
NULL |
Business Scope |
| lianxiren |
varchar(200) |
yes |
NULL |
contact person |
| lianxidianhua |
varchar(200) |
no |
contact number |
|
| shangpujieshao |
longtext |
yes |
NULL |
Store introduction |
| tupian |
varchar(200) |
yes |
NULL |
picture |
| thumbsupnum |
int(11) |
yes |
0 |
Thumbs up |
| crazilynum |
int(11) |
yes |
0 |
step on |
Table 4.9 Collection information table
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| userid |
bigint(20) |
no |
user id |
|
| refid |
bigint(20) |
yes |
NULL |
collection id |
| tablename |
varchar(200) |
yes |
NULL |
Table Name |
| name |
varchar(200) |
no |
favorite name |
|
| picture |
varchar(200) |
no |
favorite picture |
Table 4.10 Administrator Information Form
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| username |
varchar(100) |
no |
username |
|
| password |
varchar(100) |
no |
password |
|
| role |
varchar(100) |
yes |
administrator |
Role |
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
add time |
Table 4.11 User Information Table
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| zhanghao |
varchar(200) |
no |
account |
|
| mima |
varchar(200) |
no |
password |
|
| xingming |
varchar(200) |
no |
Name |
|
| xingbie |
varchar(200) |
yes |
NULL |
gender |
| shouji |
varchar(200) |
yes |
NULL |
cell phone |
| youxiang |
varchar(200) |
yes |
NULL |
|
| shenfenzheng |
varchar(200) |
yes |
NULL |
ID card |
| tupian |
varchar(200) |
yes |
NULL |
picture |
Table 4.12 User sharing information table
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| zhanghao |
varchar(200) |
yes |
NULL |
account |
| mima |
varchar(200) |
yes |
NULL |
password |
| mingcheng |
varchar(200) |
yes |
NULL |
name |
| Xiangmuleixing |
varchar(200) |
yes |
NULL |
project type |
| hulixiaoguo |
longtext |
yes |
NULL |
Nursing effect |
| jiage |
int(11) |
yes |
NULL |
price |
| Xiangqing |
longtext |
yes |
NULL |
details |
| tupian |
varchar(200) |
yes |
NULL |
picture |
| thumbsupnum |
int(11) |
yes |
0 |
Thumbs up |
| crazilynum |
int(11) |
yes |
0 |
step on |
| clicktime |
datetime |
yes |
NULL |
last click time |
| clicknum |
int(11) |
yes |
0 |
The number of clicks |
Table 4.13 User reservation information form
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| mingcheng |
varchar(200) |
yes |
NULL |
name |
| Xiangmuleixing |
varchar(200) |
yes |
NULL |
project type |
| jiage |
int(11) |
yes |
NULL |
price |
| yuyueshijian |
date |
yes |
NULL |
Appointment |
| zhanghao |
varchar(200) |
yes |
NULL |
account |
| mima |
varchar(200) |
yes |
NULL |
password |
| sfsh |
varchar(200) |
yes |
no |
Whether to review |
| shhf |
longtext |
yes |
NULL |
review reply |
| pee |
varchar(200) |
yes |
unpaid |
whether to pay |
Table 4.14 Promotional Activity Information Sheet
| field |
type |
null |
default |
note |
| id (primary key) |
bigint(20) |
no |
primary key |
|
| addtime |
timestamp |
no |
CURRENT_TIMESTAMP |
creation time |
| Huodongzhuti |
varchar(200) |
yes |
NULL |
activity theme |
| huodongmude |
varchar(200) |
yes |
NULL |
Objectives |
| youhuixiangmu |
longtext |
yes |
NULL |
Promotional items |
| kaishishijian |
date |
yes |
NULL |
Starting time |
| jieshushijian |
date |
yes |
NULL |
End Time |
| Xiangqing |
longtext |
yes |
NULL |
details |
| fengmian |
varchar(200) |
yes |
NULL |
the cover |
| thumbsupnum |
int(11) |
yes |
0 |
Thumbs up |
| crazilynum |
int(11) |
yes |
0 |
step on |
5 system realization
在此部分内容中，主要通过系统功能的运行效果图展示前面设计的最终结果。系统实现对编制人员的技术能力有较高要求，因为需要他们使用编程的方式去实现系统设计的方案。
5.1 管理员功能实现
5.1.1 美发信息管理
管理员权限中的美发信息管理，其运行效果见下图。管理员查看美发相关评论，修改美发信息，查询美发信息。
图5.1 美发信息管理页面
5.1.2 用户预约管理
管理员权限中的用户预约管理，其运行效果见下图。管理员需要审核用户预约的美发，查看用户是否完成支付。
图5.2 用户预约管理页面
5.1.3 用户分享管理
管理员权限中的用户分享管理，其运行效果见下图。管理员查看用户分享的信息，查询，修改用户的分享信息。
图5.3 用户分享管理页面
5.1.4 优惠活动管理
管理员权限中的优惠活动管理，其运行效果见下图。管理员修改优惠活动信息，查看用户评论优惠活动的信息，删除指定的优惠活动信息。
图5.4 优惠活动管理页面
5.2 用户功能实现
5.2.1 商铺信息
用户权限中的商铺信息，其运行效果见下图。用户查看商铺介绍，评论商铺。
图5.5 商铺信息页面
5.2.2 美发信息
用户权限中的美发信息，其运行效果见下图。用户收藏美发信息，评论美发信息，预约美发。
图5.6 美发信息页面
5.2.3 用户分享
用户权限中的用户分享，其运行效果见下图。用户查看别人发布的分享信息，可以收藏分享信息，评论分享信息。
图5.7 用户分享页面
5.2.4 优惠活动
用户权限中的优惠活动，其运行效果见下图。用户查看优惠活动详细信息，评论优惠活动。
图5.8 优惠活动页面
6系统测试
这部分内容主要是把前期编码完成的系统，当成是计算机系统的一部分，并结合一些数据，计算机硬件和支持的软件进行集成测试和确认测试。之所以要进行最后的测试步骤，原因在于检查制作的系统与需求说明书的比较中，存在的差异问题。进一步确认制作的系统在功能与性能上跟需求说明书当中的要求相符。
6.1 系统测试的类型
检测系统是否合格，需要用到很多的测试类型。接下来就对这部分内容进行描述。
功能测试：这是系统测试中，首先进行的测试内容，其属于黑盒测试。主要检验制作的系统与需求说明文档的相符程度，还有它们之间存在的差异问题。
性能测试：主要测试制作的系统，在同时面对很多的用户请求时，该系统的应对能力。同时也是检查制作的系统跟事先预定的系统性能存在的差距问题。这样的方法通常在实时系统中，或者是嵌入式系统中运用得比较多。
容量测试：这种方法针对数据。检查正常运行的系统对数据处理的容量值。
安全性测试：这种方法常用于检验系统中设置的安全保护机制对来自非法用户的攻击时是否有效。而检测系统中的信息保护机制就需要使用常见安全测试中的保护测试来验证。
健壮性测试：这种测试还有一个别称是容错测试，通常运用故障插入法来检测系统的容错能力，看系统是否可以忽略故障保持继续运行，或者是检测系统应对故障时的自动恢复能力。
兼容性测试：面对计算机的各种软硬件环境，检测本系统是否可以兼容。
易用性测试：这种方法主要是面向用户，检测用户是否很容易理解和使用系统。
6.2 功能测试
理发店会员管理系统在经历最后的测试环节，需要检验本系统的功能安全性，功能适用性等内容，最终得出测试结论。
表6.1 功能测试数据表
| 测试结果 |
|
| 符合要求 |
|
| 符合要求 |
|
| 符合要求 |
|
| 符合要求 |
|
| 符合要求 |
6.3 可用性测试
通常来说，一个布局合理，显示的内容无错别字，并具备合理正常的操作逻辑的系统往往很受欢迎，而且可以提升访问者的使用时间以及访问率。
表6.2 可用性测试数据表
| 测试内容 |
测试结果 |
| 合理 |
|
| 合理 |
|
| 能 |
|
| 无 |
|
| 检查系统功能有无友好性 |
有 |
| 能 |
|
| 无 |
|
| 检查系统有无提供帮助信息 |
有 |
6.4 测试结果分析
理发店会员管理系统经过了编码阶段的单元测试，和最后的系统整体测试等测试后，对于用户要求的功能，本系统都进行了实现，各个模块都运行正常。在面对一些故障性问题时，本系统也有相应的应对办法，并且本系统可以保持24小时正常运转。因此，理发店会员管理系统可以交付用户使用。
结 论
理发店会员管理系统的开发设计并不是一件轻松事，因为毕设制作都是依照一定流程进行的。最开始是选择题目，然后通过各种方式查阅资料，以及对使用用户的需求进行调研，确定本系统的功能，为了降低系统编码的出错率，在设计阶段也需要下功夫，认真设计功能模块，使用大学所学的数据库知识，设计数据库。这样一来，对系统编码时，就会根据设计方案进行。编码完成，进行测试就能对合格的系统进行验收了。
借助身边同学还有导师提供的帮助，本人也顺利完成本系统的制作工作。对理发店会员管理系统的分析与总结，发现理发店会员管理系统具有如下特点：
（1）理发店会员管理系统有着详细的功能设计，所以编码时，基本依照设计的功能进行开发，因此具备较完善的功能；
（2）理发店会员管理系统在界面设计与布局时，参考了很多系统的界面设计风格，也从图书馆查阅了关于系统界面设计方面的资料，并把对本系统有用的知识做好笔记，有了这些知识积累，所以我在开发系统时，注重页面文字的排版，以及精确定位各页面元素，合理使用颜色搭配技巧，让本系统在不影响浏览效果的同时，让访问者产生一种简洁干净的视觉效果；
（3）理发店会员管理系统为了让用户易于使用，在能够直观表达系统内容的同时，也把页面的导航放在了页面中最关键的位置，这个位置也是充分考虑了用户的浏览习惯。所以用户操作系统，可以在短时间内找到需要的内容。
由于本人并不是专门从事开发工作的技术人员，目前在校学习的开发类知识处于初级阶段，只是对开发类技术有着简单了解和使用，加上日常完成的作业，也只是局限在某个系统的某个功能模块上，因此，完成一个功能完善的整个系统，对于我来说，还是有一定的压力。所以这也确定了我开发的系统具有缺陷。
（1）对于理发店会员管理系统的编码并没有完全依照编码规范，整个系统存在代码冗余的缺陷；
（2）理发店会员管理系统在数据输入上，对数据有效性检测还不够严格；
（3）对理发店会员管理系统的误操作提示，只是对部分功能进行了设计，还有很多功能都没有设计报错提示。
综上所述，本人仍需花费时间去学习编程知识，在后期，我将会学习代码模块化，将一些通用的函数，变量等进行单独设置，然后直接在需要的页面上进行调用，这样可以降低代码冗余率，同时也会多学习针对程序易出错地方的解决方案等知识。学习这些知识除了完善本系统之外，也是弥补自身编程能力不足的缺陷。
参考文献
[1]梁增华,张书锋,尤澜涛.商业零售会员管理系统的设计与实现[J].电脑知识与技术,2021,17(05):67-70.
[2]朱文辉,田若松,乔云,张玮琳.会员服务的信息化[J].学会,2019(07):11-20.
[3]李丹,刘旭.会员信息管理系统的设计与研究[J].内燃机与配件,2017(17):90-91.
[4]王子虎,胡丽珍.基于计算机软件安全开发的Java编程语言研究[J].数字技术与应用,2019,37(12):133-134.
[5]谢懿.计算机软件Java编程特点及其技术分析[J].农家参谋,2020(01):166.
[6]欧阳桂秀.Java语言存取文本文件的研究[J].科技传播,2019,11(24):128-129+162.
[7]左兆丰.Java嵌入式数据库程序的开发[J].电脑编程技巧与维护,2020(01):101-103.
[8]黄守涛.基于Java语言的异常处理探讨分析[J].自动化技术与应用,2020,39(02):30-32+107.
[9]邹红霆.基于SSM框架的Web系统研究与应用[J].湖南理工学院学报(自然科学版),2017,30(01):39-43.
[10]汪维,胡帅.MySQL数据库有关数据的备份方法分析[J].信息技术与信息化,2020(07):36-37.
[11]丁佳.基于JSP+MySQL的用户登录系统SQL注入实例及防范[J].网络安全技术与应用,2020(09):49-51.
[12]曾志明.网站开发技术的比较研究[J].电脑知识与技术,2015,6(05):1075-1078.
[13]卫红春.信息系统分析与设计[M].北京：清华大学出版社,2015.
[14]Oscar Rodriguez-Prieto,Francisco Ortin,Donna O’Shea. Efficient runtime aspect weaving for Java applications[J]. Information and Software Technology,2018,100.
[15]Raffi Khatchadourian. Automated refactoring of legacy Java software to enumerated types[J]. Automated Software Engineering,2017,24(4).
致 谢
伴随着毕设项目的制作完成，也就意味着我们即将离开校园。回想几年的大学时光，不由得想起身边常伴的同学，授课的老师，还有毕设指导的老师们。
大学这几年，身边的同学为我提供了很多的帮助，不管是生活上，还是学习上，每次遇到问题，这些同学们都会耐心解答，有时为了避免我再次犯错，他们也会时不时提醒我。本次毕设制作期间，这些老同学也是互相分享开发经验，还有文档编写的技巧，从开题报告，还有任务书以及最后的论文等文档上，大家都是互相提出建议，互相参考一些编写经验和技巧。如此，我们才会进展得比较顺利。此刻，真心感谢这些老同学！
唯一不能忘记的是导师，平均每个导师都带了很多个毕业生，所以能够想象他们非常忙，因为一到毕业季，他们需要指导学生们毕业，还需要正常授课。作为本届毕业生，我也能够体会导师的辛苦和不容易。毕设制作的环节有很多，但是我的导师在进行的每个环节都严格要求我认真努力对待本项目，也对我编程技术上提出了很多至关重要的建议，还对一些比较细微但是也比较关键的部分向我进行了多次强调，让我少走弯路，可以如期实现本系统。此刻，真心感谢导师！
校园里的授课老师不仅有本专业的老师，也有其他专业的老师们，他们都教过我们课程，向我们传授知识，有了这些知识积累，我在本次毕设制作中，才知道有些问题该如何运用知识处理，此刻，感谢那些授课老师。
最后时刻，我要感谢校园，祝愿校园更加强大！