In the information society, there is a need for targeted ways to obtain information, but the expansion of the ways is basically the direction that people strive for. Due to deviations in the perspective, people can often obtain different types of information, which is also the most difficult problem for technology to overcome. subject. In view of issues such as the beauty shopping platform, we conduct research and analysis on the beauty shopping platform, and then develop and design a beauty shopping platform to solve the problem.

The main functional modules of the beauty shopping platform include carousel (carousel management) system announcement management (system announcement) resource management (beauty information, information classification) system users (administrators, ordinary users, employee users) module management (beauty makeup products, product types, product orders, cancellation orders, cancellation confirmations, shipping information, points products, user points, redemption records), etc., using an object-oriented development model for software development and hardware installation, which can be very good To meet the needs of actual use, the corresponding software construction and program coding work has been improved. MySQL is used as the main storage unit of background data, and the springboot framework, Java technology, and Ajax technology are used to code and develop the business system, realizing this full functionality of the system. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyzing various needs and technical issues of the beauty shopping platform, proving the necessity and technical feasibility of the system, and then giving a basic introduction to the technical software and design ideas that need to be used in the design system, and finally realizing beauty shopping Platforms and deployments run using it.

Keywords : Java technology; MYSQL; beauty shopping platform

Abstract

In the information society, there is a need for targeted information acquisition channels, but the expansion of channels is basically the direction of people's efforts. Due to the deviation in perspective, people often can obtain different types of information, which is also the most difficult topic for technology to overcome. Conduct research and analysis on beauty shopping platforms and other issues, and then develop and design a beauty shopping platform to solve the problem.

The main functional modules of the beauty shopping platform include rotation chart (rotation chart management), system announcement management (system announcement), resource management (beauty information, information classification), system user (administrator, ordinary user, employee user), module management (beauty products, product types, product orders, cancellation orders, cancellation confirmations, shipping information, point products, user points, and redemption records), etc, Adopting an object-oriented development model for software development and hardware installation can effectively meet practical usage needs, improve the corresponding software installation and program coding work, adopt MySQL as the main storage unit for backend data, and use Spring Boot framework, Java technology, and Ajax technology for business system coding and development, achieving all functions of this system. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyze the various requirements and technical issues of the beauty shopping platform, prove the necessity and technical feasibility of the system, and then provide a basic introduction to the technical software and design ideas required for designing the system. Finally, implement the beauty shopping platform and deploy it for operation.

Keywords:Java technology; MYSQL； Beauty shopping platform

1 Introduction

1.1 Research background and significance

In recent years, with the rapid development of the mobile Internet, in addition to traditional basic applications such as web browsing, information search, and sending emails, most domestic netizens have gradually become accustomed to accepting traditional functions such as shopping, communication, travel, and entertainment through the Internet. In addition, new service models have emerged, in which online shopping has increasingly become an important form of shopping in people's lives. The rapid development of the Internet has provided strong guarantee and support for the development of beauty shopping platforms. In addition, the external environment for online shopping has gradually improved. Mobile Internet terminals (mobile phones, tablets) have made the structure of netizens become more and more popular. Payment and settlement methods are becoming more and more convenient, user points are becoming more and more accessible, and corresponding regulations and policies are becoming more and more perfect. Nowadays, online shopping is becoming more and more attractive to people, and people's views on online shopping have also changed from ignorance at the beginning, from suspicion to gradual trust, from rejection to acceptance and habit. The concept of online shopping has become more and more popular. The main factors that prompt people to shop online are:

(1) Convenient and fast. Online shopping is available 24 hours a day. People do not need to go to the store to shop, and the purchased goods can also be delivered directly to their homes. This allows consumers to buy their favorite products from all over the world without leaving home.

(2) Large amount of information. Compared with traditional shopping methods, e-commerce can accommodate a very large amount of information, including both real products and virtual products. In addition, some special products can also be provided, which can not only protect consumers' personal privacy, but also meet consumers' different psychological needs.

(3) Strong privacy. Consumers sometimes use online shopping when purchasing goods that they do not want others to know. Both sellers and user points can protect the user's privacy, thus avoiding unnecessary troubles.

1.2 Development status

Due to the rise of the online sales industry in recent years, I also learned some relevant information. In China, previous sales were only traditional sales, while online sales seemed to meet market demand. So far, there are some household names like Taobao and Tmall. However, this kind of online sales also has some disadvantages: users cannot pick up the goods immediately after placing an order and paying, and they should also consider whether the goods are damaged. The system was developed based on sales on the merchandise network.

After several years of development, many online shopping malls recognized by consumers have appeared at home and abroad. The content of these online shopping malls is diverse, and they contain relatively complete functions, including ordinary users, searching for products, managing orders, introducing product details, and leaving online messages. Nowadays, the widespread use of the Internet has led to the development of online shopping malls at home and abroad to a certain extent. As long as enterprises type online through this platform, they can manage the content of the system at any time. Encourage consumers to purchase and conduct online transactions by displaying product content and publishing announcements.

1.3Introduction to springboot framework

The Spring framework is an open source application framework on the Java platform that provides a container with control inversion characteristics. Although the Spring framework itself has no restrictions on the programming model, its frequent use in Java applications made it so popular that it was later used as a supplement or even a substitute for the EJB (Enterprise JavaBeans) model. The Spring framework provides a series of solutions for development, such as utilizing the core features of inversion of control and implementing inversion of control through dependency injection to implement containerization of the managed object life cycle, using aspect-oriented programming for declarative transaction management, and integration A variety of persistence technologies manage data access, provide a large number of excellent web frameworks to facilitate development, and so on. The Spring framework has the Inversion of Control (IOC) feature. IOC is designed to facilitate project maintenance and testing. It provides a method for unified configuration and management of Java objects through Java's reflection mechanism. The Spring framework uses containers to manage the life cycle of objects. The container can configure objects by scanning XML files or specific Java annotations on classes. Developers can obtain objects through dependency lookup or dependency injection. Spring framework has aspect-oriented programming(AOP) framework, the Spring AOP framework is based on the proxy mode and is configurable at runtime; the AOP framework mainly modularizes cross-concerns between modules. The AOP framework of the Spring framework only provides basic AOP features. Although it cannot be compared with the AspectJ framework, it can also meet basic needs through integration with AspectJ. Transaction management, remote access and other functions under the Spring framework can be realized by using Spring AOP technology. Spring's transaction management framework brings an abstraction mechanism to the Java platform that enables local and global transactions, as well as nested transactions, to work with savepoints and in almost any environment on the Java platform. Spring integrates a variety of transaction templates. The system can configure transactions through transaction templates, XML or Java annotations, and the transaction framework integrates functions such as messaging and caching. Spring's data access framework solves common difficulties developers encounter when using databases in their applications. It not only provides support for all popular data access frameworks such as Java: JDBC, iBATS/MyBATIs, Hibernate, Java Data Objects (JDO), ApacheOJB and ApacheCayne, but can also be used with Spring's transaction management to provide data access. Flexible abstraction. The Spring framework did not initially intend to build its own Web MVC framework . During the development process, its developers believed that the separation between the presentation layer and the request processing layer of the existing StrutsWeb framework, as well as between the request processing layer and the model, was not enough, so they created SpringMVC.

1.4 Paper structure and chapter arrangement

The paper will be organized hierarchically. In addition to the abstract, acknowledgments, and literature references, the main text will also analyze the website requirements, describe the general design and implemented functions, and finally list some debugging records. The main structure of the paper is as follows:

Chapter 1: Introduction. The first chapter mainly introduces the background of the project research, the current situation of system development and the research content and main work of this article.

Chapter 2: System requirements analysis. Chapter 2 mainly conducts demand analysis from the aspects of users and functions of the system.

Chapter 3: System Design. Chapter 3 mainly carries out functional design of the system framework, system function modules and database.

Chapter 4: System implementation. Chapter 4 mainly introduces the system framework construction and the implementation of the system interface.

Chapter 5: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions.

Chapter 6: Summary.

2 System analysis of beauty shopping platform

System analysis is a prerequisite for developing a project. Through system analysis, the basic needs of the main users of the system can be well understood, and this is also the reason for the development of the project. Then, a feasibility analysis is performed on the system development, which usually includes technical feasibility, economic feasibility, etc. The feasibility analysis is also an analysis from the overall perspective of the project. Then the specific requirements of the project are analyzed. The analysis method is generally implemented through the user's use case diagram. The following is a detailed introduction.

2.1 Feasibility analysis

( 1) Operational feasibility:

The design of this project refers to several cases of website development under this mode, analyzes their operation interfaces, and combines many cases to highlight people-oriented simplified operations, so people with basic computer knowledge can operate this project.

Therefore, there is no problem with operational feasibility.

(2) Technical feasibility:

Technical feasibility refers to the feasibility of building a framework, as well as the system's adaptability to technological upgrading when better technologies emerge, and the development time and cost ratio.

The existing springboot technology can cater to the construction of all e-commerce systems. When developing this beauty shopping platform, I used springboot+MYSQL to run the overall program.

In summary, there is no problem with the technical feasibility.

(3) Legal feasibility:

From a developer's perspective, springboot and MYSQL are open source and free online, and there will be no legal disputes regarding intellectual property rights.

From a user perspective, as long as contraband is no longer sold on the system, treaties and agreements are made with the system, and illegal payments are eliminated.

In summary, there is no problem with the legal feasibility.

2.2 System process analysis

2.2.1 Data flow

The main purpose of the beauty shopping platform is to place orders for beauty products. Figure 2-1 is the data flow diagram of the system.

Figure 2-1 Expanded view of ordering and purchasing operations for beauty products

3.3.2 Business process

After analyzing the data flow of the system, let’s look at the business process of the system. Figure 2-2 is the business flow chart:

Figure 2-2 Business flow chart

2.3 System function analysis

2.3.1 Functional analysis

According to the roles of the beauty shopping platform, I divided it into three parts: ordinary users, employee users and administrators.

Ordinary user management module:

(1) User registration and login: Users register as users and log in to the beauty shopping platform; users add, delete, modify and check personal information, such as personal information and password changes.

(2) System Announcement: The user clicks the "System Announcement" menu to display all system announcement information released by the administrator in the background, and can view the system announcement details.

(3) Beauty information: When the user clicks the "Beauty Information" menu button, all the beauty information published by the administrator in the background will be displayed. You can view details, collect, like, comment, etc.;

(4) Beauty products: When the user clicks the menu button "Beauty Products", all the beauty products released by the administrator in the background will be displayed. It supports searching for beauty products by keywords and selecting the beauty products they need. Click on the product to enter the detailed introduction interface of the beauty product. In the detailed interface, you can view the product number, product name, product type, product brand, product specifications, product unit price, product quantity, product discount, responsible employee and other information. At the same time, you can place orders, like, collect, and comment;

(5) Place an order to purchase: When the user wants to place an order and purchase on the beauty product details interface, click the "Place an order to purchase" button below, and it will jump to the order purchase information filling interface, and enter the order according to the interface prompts. Purchase information, click the "Submit" button, and the order is completed;

(6) Points-based products: Users can view points-based products. When they find the points-based products they want to know about, they can enter to view detailed introductions.

(7) My Account: When the user clicks the "My" button in the upper right corner, a submenu will appear. Clicking "My Account" can set and manage personal information, passwords for logging into the system, and information collected by oneself;

Administrator management module:

(1) Login: The administrator can enter the username + password to log in in the background. The administrator's username and password are set directly in the database.

(2) Carousel image: Administrators can click the "Carousel image" menu to add, delete, modify, and check the carousel image displayed on the home page.

(3) System announcement: The administrator can click the "System Announcement" menu to view all system announcement information in the system. The administrator can modify the existing system announcements, add new system announcements, or delete system announcements.

(4) Resource management: The administrator can click on the "Resource Management" menu to add, delete, modify and check the beauty information and information categories in the submenu.

(5) System users: Administrators can click the "System Users" menu to manage users existing in the system, including administrator users, employee users and ordinary users.

( 6) Module management: Under the "Module Management" menu, we will see beauty products, product types, product orders, cancellation orders, cancellation confirmations, shipping information, point products, redemption records, user points, management Members can perform addition, deletion, modification and query operations on it.

2.3.2 Non-functional analysis

The non-functional requirements of the beauty shopping platform include the security, reliability, performance, scalability, etc. of the beauty shopping platform. The details can be expressed in the following 3-1 table:

Table 3-1 Non-functional requirements table of beauty shopping platform

safety	Mainly refers to the installation of the database of the beauty shopping platform, the use of the database and the setting of passwords must comply with the standards.
reliability	Reliability means that the beauty shopping platform can operate according to the user's instructions. After testing, the reliability is over 90%.
performance	Performance is a necessary condition for a beauty shopping platform to occupy the market, so it is best to have good performance.
Scalability	For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system.
Ease of use	Users only need to follow the page display content of the beauty shopping platform and they are good to go.
maintainability	The maintainability of the development of the beauty shopping platform is very important. After testing, there is no problem with the maintainability.

2.4 System use case analysis

Through the analysis of 2.3 functions, the use case diagram of this beauty shopping platform is obtained:

An example of a common user role is shown in Figure 2-3.

Figure 2-3 Use case diagram of ordinary user roles on the beauty shopping platform

The administrator of the web backend management maintains all data information in the entire beauty shopping platform. An example of the administrator role is shown in Figure 2-4.

Figure 2-4 Beauty shopping platform administrator role use case diagram

2.5 Summary of this chapter

This chapter mainly determines the functions to be realized by the entire beauty shopping platform through feasibility analysis, process analysis, functional requirements analysis, and system use case analysis of the beauty shopping platform. At the same time, it also provides standards for code implementation and testing of beauty shopping platforms.

3 Overall design of beauty shopping platform

The main content discussed in this chapter includes the functional module design and database system design of the beauty shopping platform.

3.1 System architecture design

This beauty shopping platform is divided into three layers in terms of architecture: presentation layer (UI), business logic layer (BLL) and data layer (DL).

Figure 3-1 Beauty shopping platform system architecture design diagram

Presentation layer (UI): Also known as the UI layer, it mainly completes the UI interaction function of this beauty shopping platform. A good UI can improve the user experience and enhance the user's comfort when using this beauty shopping platform. The UI interface design must also adapt to different versions of the beauty shopping platform and different size resolutions to achieve good compatibility. The UI interaction function requirements are reasonable, and users must obtain consistent interaction results when performing interactive operations. This requires the presentation layer to be well connected with the business logic layer.

Business logic layer (BLL): mainly completes the data processing function of this beauty shopping platform. The data transmitted by the user from the presentation layer is processed by the business logic layer and delivered to the data layer. The data read by the system from the data layer is processed by the business logic layer and delivered to the presentation layer.

Data layer (DL): Since the data of this beauty shopping platform is placed in the mysql database on the server side, the parts that belong to the service layer can be directly integrated into the business logic layer. Therefore, there is only a database in the data layer, which mainly completes this task. Data storage and management functions of the beauty shopping platform.

3.2 System function module design

3.2.1 Overall functional module design

In the previous chapter, the functional requirements and non-functional requirements of the system were mainly analyzed, and the use cases in this beauty shopping platform were analyzed based on the requirements. Then the next step is to start designing the architecture, main functions and database of this beauty shopping platform. The beauty shopping platform is based on the demand analysis in the previous chapter. Its overall design module diagram is shown in Figure 3-2.

Figure 3-2 Functional module diagram of the beauty shopping platform

3.2.2 User module design

The backend manager can add, delete, modify and check the users registered in the frontend. The user module structure diagram is as follows:

Figure 3-3 User module structure diagram

3.2.3 Comment management module design

The beauty shopping platform is an open platform for communication. Users can communicate on the platform to increase the interaction between users. But at the same time, in order to better standardize the content of comments and give administrators the function of deleting inappropriate comments, a comment management module needs to be specially designed. The specific structure diagram is as follows:

Figure 3-4 Structure diagram of comment module

3.2.4 Design of beauty product management module

The beauty shopping platform needs to store a lot of beauty product information. Its module functional structure, the specific structure diagram is as follows:

Figure 3-5 Structure diagram of beauty product information module

3.3 Database design

Database design generally includes three major processes: demand analysis, conceptual model design, and database table creation. The demand analysis has been explained in the previous chapter, and the conceptual model design has two parts: conceptual model and logical structure design.

3.3.1 Database conceptual structure design

The following is the main ER entity relationship diagram of the main database tables in the entire beauty shopping platform.

Figure 3-6 Total ER relationship diagram of the beauty shopping platform

3.3.2 Database logical structure design

From the total ER relationship diagram in the beauty shopping platform in the previous section, it can be concluded that a total of many data tables need to be created. Here I mainly list several major database table structure designs.

Table beauty_products (beauty products)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	beauty_products_id	int	10	0	N	Y		Beauty product ID
2	product_number	varchar	64	0	N	N		Product Number
3	trade_name	varchar	64	0	Y	N		product name
4	commodity_type	varchar	64	0	Y	N		Product Types
5	cover	varchar	255	0	Y	N		cover
6	product_brand	varchar	64	0	Y	N		product brand
7	product_specifications	varchar	64	0	Y	N		Product specifications
8	item_pricing	int	10	0	Y	N	0	Commodity price
9	product_quantity	int	10	0	Y	N	0	Number of Products
10	product_discount	varchar	64	0	Y	N		Product discounts
11	product_details	longtext	2147483647	0	Y	N		product details
12	responsible_employees	int	10	0	Y	N	0	Responsible employee
13	hits	int	10	0	N	N	0	Clicks
14	praise_len	int	10	0	N	N	0	Number of likes
15	recommend	int	10	0	N	N	0	Intelligent Recommendation
16	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	creation time
17	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time

Table cancellation_of_order (cancel order)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	cancellation_of_order_id	int	10	0	N	Y		Cancel order ID
2	order_number	varchar	64	0	N	N		order number
3	product_number	varchar	64	0	Y	N		Product Number
4	trade_name	varchar	64	0	Y	N		product name
5	commodity_type	varchar	64	0	Y	N		Product Types
6	product_brand	varchar	64	0	Y	N		product brand
7	product_specifications	varchar	64	0	Y	N		Product specifications
8	item_pricing	int	10	0	Y	N	0	Commodity price
9	product_discount	varchar	64	0	Y	N		Product discounts
10	order_date	date	10	0	Y	N		Order date
11	responsible_employees	int	10	0	Y	N	0	Responsible employee
12	ordinary_users	int	10	0	Y	N	0	普通用户
13	purchase_quantity	int	10	0	Y	N	0	购买数量
14	payment_amount	varchar	64	0	Y	N		支付金额
15	consignee	varchar	64	0	Y	N		收货人
16	receiving_phone_number	varchar	64	0	Y	N		收货电话
17	shipping_address	varchar	64	0	Y	N		收货地址
18	reason_for_cancellation	text	65535	0	Y	N		取消原因
19	examine_state	varchar	16	0	N	N	未审核	审核状态
20	examine_reply	varchar	16	0	Y	N		审核回复
21	recommend	int	10	0	N	N	0	智能推荐
22	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
23	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表cancel_confirmation (取消确认)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	cancel_confirmation_id	int	10	0	N	Y		取消确认ID
2	order_number	varchar	64	0	N	N		订单号
3	product_number	varchar	64	0	Y	N		商品编号
4	trade_name	varchar	64	0	Y	N		商品名称
5	commodity_type	varchar	64	0	Y	N		商品类型
6	product_brand	varchar	64	0	Y	N		商品品牌
7	product_specifications	varchar	64	0	Y	N		商品规格
8	item_pricing	int	10	0	Y	N	0	商品单价
9	product_discount	varchar	64	0	Y	N		商品折扣
10	order_date	date	10	0	Y	N		下单日期
11	responsible_employees	int	10	0	Y	N	0	负责员工
12	ordinary_users	int	10	0	Y	N	0	普通用户
13	purchase_quantity	int	10	0	Y	N	0	购买数量
14	payment_amount	varchar	64	0	Y	N		支付金额
15	consignee	varchar	64	0	Y	N		收货人
16	receiving_phone_number	varchar	64	0	Y	N		收货电话
17	shipping_address	varchar	64	0	Y	N		收货地址
18	reason_for_cancellation	text	65535	0	Y	N		取消原因
19	recommend	int	10	0	N	N	0	智能推荐
20	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
21	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表comment (评论)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	comment_id	int	10	0	N	Y		评论ID：
2	user_id	int	10	0	N	N	0	评论人ID：
3	reply_to_id	int	10	0	N	N	0	回复评论ID：空为0
4	content	longtext	2147483647	0	Y	N		内容：
5	nickname	varchar	255	0	Y	N		昵称：
6	avatar	varchar	255	0	Y	N		头像地址：[0,255]
7	create_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	创建时间：
8	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间：
9	source_table	varchar	255	0	Y	N		来源表：
10	source_field	varchar	255	0	Y	N		来源字段：
11	source_id	int	10	0	N	N	0	来源ID：

表employee_users (员工用户)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	employee_users_id	int	10	0	N	Y		员工用户ID
2	employee_id	varchar	64	0	N	N		员工工号
3	employee_name	varchar	64	0	Y	N		员工姓名
4	examine_state	varchar	16	0	N	N	已通过	审核状态
5	recommend	int	10	0	N	N	0	智能推荐
6	user_id	int	10	0	N	N	0	用户ID
7	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
8	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表notice (公告)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	notice_id	mediumint	8	0	N	Y		公告id：
2	title	varchar	125	0	N	N		标题：
3	content	longtext	2147483647	0	Y	N		正文：
4	create_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	创建时间：
5	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间：

表ordinary_users (普通用户)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	ordinary_users_id	int	10	0	N	Y		普通用户ID
2	user_name	varchar	64	0	N	N		用户姓名
3	user_gender	varchar	64	0	N	N		用户性别
4	examine_state	varchar	16	0	N	N	未审核	审核状态
5	recommend	int	10	0	N	N	0	智能推荐
6	user_id	int	10	0	N	N	0	用户ID
7	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
8	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表point_products (积分商品)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	point_products_id	int	10	0	N	Y		积分商品ID
2	product_number	varchar	64	0	N	N		商品编号
3	trade_name	varchar	64	0	Y	N		商品名称
4	commodity_type	varchar	64	0	Y	N		商品类型
5	cover	varchar	255	0	Y	N		封面
6	product_brand	varchar	64	0	Y	N		商品品牌
7	product_specifications	varchar	64	0	Y	N		商品规格
8	unit_price_of_points	int	10	0	Y	N	0	积分单价
9	product_details	longtext	2147483647	0	Y	N		商品详情
10	responsible_employees	int	10	0	Y	N	0	负责员工
11	hits	int	10	0	N	N	0	点击数
12	recommend	int	10	0	N	N	0	智能推荐
13	limit_times	int	10	0	N	N	0	限制次数
14	limit_type	tinyint	4	0	N	N	1	限制次数类型1-每天次，2-总计次
15	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
16	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表product_orders (商品订单)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	product_orders_id	int	10	0	N	Y		商品订单ID
2	order_number	varchar	64	0	Y	N		订单号
3	product_number	varchar	64	0	Y	N		商品编号
4	trade_name	varchar	64	0	Y	N		商品名称
5	commodity_type	varchar	64	0	Y	N		商品类型
6	product_brand	varchar	64	0	Y	N		商品品牌
7	product_specifications	varchar	64	0	Y	N		商品规格
8	item_pricing	int	10	0	Y	N	0	商品单价
9	product_discount	varchar	64	0	Y	N		商品折扣
10	order_date	date	10	0	Y	N		下单日期
11	responsible_employees	int	10	0	Y	N	0	负责员工
12	ordinary_users	int	10	0	Y	N	0	普通用户
13	purchase_quantity	int	10	0	Y	N	0	购买数量
14	payment_amount	varchar	64	0	Y	N		支付金额
15	consignee	varchar	64	0	Y	N		收货人
16	receiving_phone_number	varchar	64	0	Y	N		收货电话
17	shipping_address	varchar	64	0	Y	N		收货地址
18	pay_state	varchar	16	0	N	N	未支付	支付状态
19	pay_type	varchar	16	0	Y	N		支付类型: 微信、支付宝、网银
20	recommend	int	10	0	N	N	0	智能推荐
21	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
22	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表product_type (商品类型)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	product_type_id	int	10	0	N	Y		商品类型ID
2	product_type	varchar	64	0	Y	N		商品类型
3	recommend	int	10	0	N	N	0	智能推荐
4	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
5	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表redemption_records (兑换记录)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	redemption_records_id	int	10	0	N	Y		兑换记录ID
2	exchange_number	varchar	64	0	Y	N		兑换号
3	product_number	varchar	64	0	Y	N		商品编号
4	trade_name	varchar	64	0	Y	N		商品名称
5	commodity_type	varchar	64	0	Y	N		商品类型
6	product_brand	varchar	64	0	Y	N		商品品牌
7	product_specifications	varchar	64	0	Y	N		商品规格
8	unit_price_of_points	int	10	0	Y	N	0	积分单价
9	responsible_employees	int	10	0	Y	N	0	负责员工
10	ordinary_users	int	10	0	Y	N	0	普通用户
11	consignee	varchar	64	0	Y	N		收货人
12	receiving_phone_number	varchar	64	0	Y	N		收货电话
13	shipping_address	varchar	64	0	Y	N		收货地址
14	recommend	int	10	0	N	N	0	智能推荐
15	user_id	int	10	0	N	N	0	用户ID
16	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
17	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表shipping_information (发货信息)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	shipping_information_id	int	10	0	N	Y		发货信息ID
2	order_number	varchar	64	0	N	N		订单号
3	product_number	varchar	64	0	Y	N		商品编号
4	trade_name	varchar	64	0	Y	N		商品名称
5	commodity_type	varchar	64	0	Y	N		商品类型
6	product_brand	varchar	64	0	Y	N		商品品牌
7	product_specifications	varchar	64	0	Y	N		商品规格
8	item_pricing	int	10	0	Y	N	0	商品单价
9	product_discount	varchar	64	0	Y	N		商品折扣
10	order_date	date	10	0	Y	N		下单日期
11	responsible_employees	int	10	0	Y	N	0	负责员工
12	ordinary_users	int	10	0	Y	N	0	普通用户
13	payment_amount	varchar	64	0	Y	N		支付金额
14	purchase_quantity	int	10	0	Y	N	0	购买数量
15	consignee	varchar	64	0	Y	N		收货人
16	receiving_phone_number	varchar	64	0	Y	N		收货电话
17	shipping_address	varchar	64	0	Y	N		收货地址
18	product_points	varchar	64	0	Y	N		商品积分
19	courier_number	varchar	64	0	Y	N		快递单号
20	recommend	int	10	0	N	N	0	智能推荐
21	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
22	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

表user_points (用户积分)

编号	名称	数据类型	长度	小数位	允许空值	主键	默认值	说明
1	user_points_id	int	10	0	N	Y		用户积分ID
2	ordinary_users	int	10	0	Y	N	0	普通用户
3	total_points	int	10	0	Y	N	0	积分总数
4	recommend	int	10	0	N	N	0	智能推荐
5	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	创建时间
6	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	更新时间

3.4本章小结

整个美妆购物平台的需求分析主要对系统总体架构以及功能模块的设计，通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。

4 美妆购物平台详细设计与实现

美妆购物平台的详细设计与实现主要是根据前面的美妆购物平台的需求分析和美妆购物平台的总体设计来设计页面并实现业务逻辑。主要从美妆购物平台界面实现、业务逻辑实现这两部分进行介绍。

4.1用户功能模块

4.1.1 前台首页界面

当进入美妆购物平台的时候，首先映入眼帘的是系统的导航栏，下面是轮播图以及系统内容，其主界面展示如下图4-1所示。

图4-1 前台首页界面图

4.1.2 用户注册界面

不是美妆购物平台中正式用户的是可以在线进行注册的，如果你没有本美妆购物平台的账号的话，添加“注册”，当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号等后再点击“注册”按钮后将会先验证输入的有没有空数据，再次验证密码和确认密码是否是一样的，最后验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可用户注册成功。其用用户注册界面展示如下图4-2所示。

图4-2 前台用户注册界面图

注册关键代码如下所示。

/**

* 注册

* @param user

* @return

@PostMapping("register")

public Map<String, Object> signUp(@RequestBody User user) {

// 查询用户

Map<String, String> query = new HashMap<>();

query.put("username",user.getUsername());

List list = service.select(query, new HashMap<>()).getResultList();

if (list.size()>0){

return error(30000, "用户已存在");

}

user.setUserId(null);

user.setPassword(service.encryption(user.getPassword()));

service.save(user);

return success(1);

}

/**

* 用户ID：[0,8388607]用户获取其他与用户相关的数据

@Id

@GeneratedValue(strategy = GenerationType.IDENTITY)

@Column(name = "user_id")

private Integer userId;

/**

* 账户状态：[0,10](1可用|2异常|3已冻结|4已注销)

@Basic

@Column(name = "state")

private Integer state;

/**

* 所在用户组：[0,32767]决定用户身份和权限

@Basic

@Column(name = "user_group")

private String userGroup;

/**

* 上次登录时间：

@Basic

@Column(name = "login_time")

private Timestamp loginTime;

/**

* 手机号码：[0,11]用户的手机号码，用于找回密码时或登录时

@Basic

@Column(name = "phone")

private String phone;

/**

* 手机认证：[0,1](0未认证|1审核中|2已认证)

@Basic

@Column(name = "phone_state")

private Integer phoneState;

/**

* 用户名：[0,16]用户登录时所用的账户名称

@Basic

@Column(name = "username")

private String username;

/**

* 昵称：[0,16]

@Basic

@Column(name = "nickname")

private String nickname;

/**

* 密码：[0,32]用户登录所需的密码，由6-16位数字或英文组成

@Basic

@Column(name = "password")

private String password;

/**

* 邮箱：[0,64]用户的邮箱，用于找回密码时或登录时

@Basic

@Column(name = "email")

private String email;

/**

* 邮箱认证：[0,1](0未认证|1审核中|2已认证)

@Basic

@Column(name = "email_state")

private Integer emailState;

/**

* 头像地址：[0,255]

@Basic

@Column(name = "avatar")

private String avatar;

/**

* 创建时间：

@Basic

@Column(name = "create_time")

@JsonFormat(pattern = "yyyy-MM-dd HH:mm:ss")

private Timestamp createTime;

@Basic

@Transient

private String code;

}

4.1.3 用户登录界面

美妆购物平台中的前台上注册后的用户是可以通过自己的账户名和密码进行登录的，当用户输入完整的自己的账户名和密码信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到美妆购物平台的首页中；否则将会提示相应错误信息，用户登录界面如下图4-3所示。

图4-3用户登录界面图

登录关键代码如下所示。

/**

* 登录

* @param data

* @param httpServletRequest

* @return

@PostMapping("login")

public Map<String, Object> login(@RequestBody Map<String, String> data, HttpServletRequest httpServletRequest) {

log.info("[执行登录接口]");

String username = data.get("username");

String email = data.get("email");

String phone = data.get("phone");

String password = data.get("password");

List resultList = null;

Map<String, String> map = new HashMap<>();

if(username != null && "".equals(username) == false){

map.put("username", username);

resultList = service.select(map, new HashMap<>()).getResultList();

}

else if(email != null && "".equals(email) == false){

map.put("email", email);

resultList = service.select(map, new HashMap<>()).getResultList();

}

else if(phone != null && "".equals(phone) == false){

map.put("phone", phone);

resultList = service.select(map, new HashMap<>()).getResultList();

}else{

return error(30000, "账号或密码不能为空");

}

if (resultList == null || password == null) {

return error(30000, "账号或密码不能为空");

}

//判断是否有这个用户

if (resultList.size()<=0){

return error(30000,"用户不存在");

}

User byUsername = (User) resultList.get(0);

Map<String, String> groupMap = new HashMap<>();

groupMap.put("name",byUsername.getUserGroup());

List groupList = userGroupService.select(groupMap, new HashMap<>()).getResultList();

if (groupList.size()<1){

return error(30000,"用户组不存在");

}

UserGroup userGroup = (UserGroup) groupList.get(0);

//查询用户审核状态

if (!StringUtils.isEmpty(userGroup.getSourceTable())){

String sql = "select examine_state from "+ userGroup.getSourceTable() +" WHERE user_id = " + byUsername.getUserId();

String res = String.valueOf(service.runCountSql(sql).getSingleResult());

if (res==null){

return error(30000,"用户不存在");

}

if (!res.equals("已通过")){

return error(30000,"该用户审核未通过");

}

//查询用户状态

if (byUsername.getState()!=1){

return error(30000,"用户非可用状态，不能登录");

}

String md5password = service.encryption(password);

if (byUsername.getPassword().equals(md5password)) {

// 存储Token到数据库

AccessToken accessToken = new AccessToken();

accessToken.setToken(UUID.randomUUID().toString().replaceAll("-", ""));

accessToken.setUser_id(byUsername.getUserId());

tokenService.save(accessToken);

// 返回用户信息

JSONObject user = JSONObject.parseObject(JSONObject.toJSONString(byUsername));

user.put("token", accessToken.getToken());

JSONObject ret = new JSONObject();

ret.put("obj",user);

return success(ret);

} else {

return error(30000, "账号或密码不正确");

}

4.1.4我的账户界面

当用户点击右上角“我的”这个按钮，会出现子菜单，点击“我的账户”可以对个人的资料、登录系统的密码以及自己收藏的信息进行设置管理，我的账户界面如下图4-4所示。

图4-4我的账户界面图

4.1.5美妆资讯界面

当访客点击美妆购物平台中导航栏上的“美妆资讯”后将会进入到该“美妆资讯”列表的界面，然后选择想要看的美妆资讯，点击进入到详细界面，同时可以进行点赞、收藏、评论操作，美妆资讯界面如下图4-5 所示。

图4-5美妆资讯界面图

4.1.6美妆商品界面

当用户点击“美妆商品”这一菜单按钮，会显示管理员在后台发布的所有的美妆商品，支持通过关键词对美妆商品进行搜索，选择需要的美妆商品点击可以进入到美妆商品详细的介绍界面，在详细界面可以查看到商品的商品编号、商品名称、商品类型、商品品牌、商品规格、商品单价、商品数量、商品折扣、负责员工等信息，同时可以进行下单购买、点赞、收藏、评论操作，美妆商品界面如下图4-6所示。

图4-6 美妆商品界面图

4.1.7下单购买界面

当用户在美妆商品详情界面想要进行下单购买，点击下方的“下单购买”按钮，就会跳转到下单购买信息填写界面，根据界面提示输入下单购买信息，点击“提交”按钮，下单购买就完成了，下单购买界面如下图4-7所示。

图4-7 下单购买界面图

4.2管理员功能模块

4.2.1系统公告管理界面

管理员点击“系统公告管理”菜单可以查看到系统中的所有系统公告信息，对已经存在的系统公告，管理员可以修改，也可以添加新的系统公告或者删除系统公告。界面如下图4-8所示。

图4-8系统公告管理界面图

系统公告管理代码如下。

@PostMapping("/add")

@Transactional

public Map<String, Object> add(HttpServletRequest request) throws IOException {

service.insert(service.readBody(request.getReader()));

return success(1);

}

@Transactional

public Map<String, Object> addMap(Map<String,Object> map){

service.insert(map);

return success(1);

}

public Map<String,Object> readBody(BufferedReader reader){

BufferedReader br = null;

StringBuilder sb = new StringBuilder("");

try{

br = reader;

String str;

while ((str = br.readLine()) != null){

sb.append(str);

}

br.close();

String json = sb.toString();

return JSONObject.parseObject(json, Map.class);

}catch (IOException e){

e.printStackTrace();

}finally{

if (null != br){

try{

br.close();

}catch (IOException e){

e.printStackTrace();

}

return null;

}

public void insert(Map<String,Object> body){

StringBuffer sql = new StringBuffer("INSERT INTO ");

sql.append("`").append(table).append("`").append(" (");

for (Map.Entry<String,Object> entry:body.entrySet()){

sql.append("`"+humpToLine(entry.getKey())+"`").append(",");

}

sql.deleteCharAt(sql.length()-1);

sql.append(") VALUES (");

for (Map.Entry<String,Object> entry:body.entrySet()){

Object value = entry.getValue();

if (value instanceof String){

sql.append("'").append(entry.getValue()).append("'").append(",");

}else {

sql.append(entry.getValue()).append(",");

}

sql.deleteCharAt(sql.length() - 1);

sql.append(")");

log.info("[{}] - 插入操作：{}",table,sql);

Query query = runCountSql(sql.toString());

query.executeUpdate();

}

4.2.2资源管理界面

管理员点击“资源管理”菜单能够对其下子菜单美妆资讯和资讯的分类进行增删改查。界面如下图4-9所示。

图4-9资源管理界面图

资源管理代码如下。

@RequestMapping(value = {"/count_group", "/count"})

public Map<String, Object> count(HttpServletRequest request) {

Query count = service.count(service.readQuery(request), service.readConfig(request));

return success(count.getResultList());

}

4.2.3系统用户管理界面

管理员点击“系统用户”菜单可以对系统中存在的用户进行管理，包含了管理员用户、员工用户和普通用户。界面如下图4-10所示。

图4-10系统用户管理界面图

系统用户管理代码如下。

@RequestMapping(value = {"/avg_group", "/avg"})

public Map<String, Object> avg(HttpServletRequest request) {

Query count = service.avg(service.readQuery(request), service.readConfig(request));

return success(count.getResultList());

}

4.2.4美妆商品管理界面

管理员点击“美妆商品”会显示出所有的美妆商品信息，支持输入商品编号或者商品名称对美妆商品信息进行查询，如果想要添加新的美妆商品信息，点击“添加”按钮，输入商品编号、商品名称、商品类型、商品品牌、商品规格、商品单价、商品数量、商品折扣、负责员工等信息，点击“提交”按钮就可以添加了，同时可以选择某一条美妆商品信息，点击“删除”进行删除，也可以对用户提交的美妆商品评论的信息进行管控。界面如下图4-11所示。

图4-11美妆商品管理界面图

4.2.5商品订单管理界面

管理员点击“商品订单”会显示出所有的商品订单信息，支持输入订单号或者商品编号对商品订单信息进行查询，如果想要添加新的商品订单信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条商品订单信息，点击“删除”进行删除，也可以点击后面的“取消订单/订单发货”、“支付”按钮对商品订单的取消订单/订单发货信息进行更新维护、对商品订单的支付信息进行设置。界面如下图4-12所示。

图4-12 商品订单管理界面图

4.2.6用户积分管理界面

管理员点击“用户积分”会显示出所有的用户积分信息，支持通过普通用户或者积分总数对用户积分信息进行查询，如果想要添加新的用户积分信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条用户积分信息，点击“删除”进行删除。界面如下图4-13所示。

图4-13用户积分界面图

5系统测试

5.1系统测试的目的

系统开发到了最后一个阶段那就是系统测试，系统测试对软件的开发其实是非常有必要的。因为没什么系统一经开发出来就可能会尽善尽美，再厉害的系统开发工程师也会在系统开发的时候出现纰漏，系统测试能够较好的改正一些bug，为后期系统的维护性提供很好的支持。通过系统测试，开发人员也可以建立自己对系统的信心，为后期的系统版本的跟新提供支持。

5.2 系统测试用例

系统测试包括：用户登录功能测试、美妆商品展示功能测试、美妆商品添加、美妆商品搜索、密码修改功能测试，如表5-1、5-2、5-3、5-4、5-5所示：

用户登录功能测试：

表5-1 用户登录功能测试表

用例名称	用户登录系统
目的	测试用户通过正确的用户名和密码可否登录功能
前提	未登录的情况下
测试流程	1) 进入登录页面 2) 输入正确的用户名和密码
预期结果	用户名和密码正确的时候，跳转到登录成功界面，反之则显示错误信息，提示重新输入
实际结果	实际结果与预期结果一致

美妆商品查看功能测试：

表5-2 美妆商品查看功能测试表

用例名称	美妆商品查看
目的	测试美妆商品查看功能
前提	用户登录
测试流程	点击美妆商品列表
预期结果	可以查看到所有美妆商品
实际结果	实际结果与预期结果一致

管理员添加美妆商品界面测试：

表5-3 管理员添加美妆商品界面测试表

用例名称	美妆商品发布测试用例
目的	测试美妆商品发布功能
前提	用户正常登录情况下
测试流程	1）用户点击美妆商品管理就，然后点击添加后并填写信息。 2）点击进行提交。
预期结果	提交以后，页面首页会显示新的美妆商品
实际结果	实际结果与预期结果一致

美妆商品搜索功能测试：

表5-4美妆商品搜索功能测试表

用例名称	美妆商品搜索测试
目的	测试美妆商品搜索功能
前提	无
测试流程	1）在搜索框填入搜索关键字。 2）点击搜索按钮。
预期结果	页面显示包含有搜索关键字的美妆商品
实际结果	实际结果与预期结果一致

密码修改功能测试：

表5-5 密码修改功能测试表

用例名称	密码修改测试用例
目的	测试管理员密码修改功能
前提	管理员用户正常登录情况下
测试流程	1）管理员密码修改并完成填写。 2）点击进行提交。
预期结果	使用新的密码可以登录
实际结果	实际结果与预期结果一致

5.3 系统测试结果

通过编写美妆购物平台的测试用例，已经检测完毕用户登录模块、美妆商品查看模块、美妆商品添加模块、美妆商品搜索模块、密码修改功能测试，通过这5大模块为美妆购物平台的后期推广运营提供了强力的技术支撑。

结论

至此，美妆购物平台已经结束，在开发前做了许多的准备，在本系统的设计和开发过程中阅览和学习了许多文献资料，从中我也收获了很多宝贵的方法和设计思路，对系统的开发也起到了很重要的作用，系统的开发技术选用的都是自己比较熟悉的，比如Web、springboot技术、MYSQL，这些技术都是在以前的学习中学到了，其中许多的设计思路和方法都是在以前不断地学习中摸索出来的经验，其实对于我们来说工作量还是比较大的，但是正是由于之前的积累与准备，才能顺利的完成这个项目，由此看来，积累经验跟做好准备是十分重要的事情。

当然在该系统的设计与实现的过程中也离不开老师以及同学们的帮助，正是因为他们的指导与帮助，我才能够成功的在预期内完成了这个系统。同时在这个过程当中我也收获了很多东西，此系统也有需要改进的地方，但是由于专业知识的浅薄，并不能做到十分完美，希望以后有机会可以让其真正的投入到使用之中。

参考文献

[1]苏以鹏,何维,宋朝霞,高阳,李凯,苏芮,林海,周英,汤彪武. 一种基于SpringBoot框架的审批文件加密批量上传方法及装置[P]. 四川省：CN112187948B,2023-04-25.

[2]刘维佳.社区式购物平台发展现状及前景分析[J].产业创新研究,2023(07):68-70.

[3]王振江,练渺渺. 一种基于SpringBoot的轻量级权限认证方法及框架[P]. 北京市：CN115374415B,2023-04-07.

[4]寇婧博,左寸芳.我国消费者反悔权制度浅析——以网络购物平台为视角[J].法制博览,2023(10):118-120.

[5]佟羽齐,刘德华,张栎柯,李剑波,张俊杰.基于SpringBoot框架的钻前管理系统的设计与实现[J].信息与电脑(理论版),2023,35(02):111-113.

[6]李晋华,葛毅,李世川.嵌入Java Web服务的桌面应用开发技术研究[J].电脑编程技巧与维护,2022(11):51-53.DOI:10.16184/j.cnki.comprg.2022.11.003.

[7]沈志元,张文健.基于Java技术的医院管理系统的设计与实现[J].电脑知识与技术,2022,18(32):38-40+54.DOI:10.14004/j.cnki.ckt.2022.1994.

[8]唐乙隽. 平台购物遇商家“消失” 千余元损失究竟谁负责[N]. 解放日报,2022-11-14(005).DOI:10.28410/n.cnki.njfrb.2022.004544.

[9]施炜. 购物平台百花齐放今年“双十一”怎么打？[N]. 台州日报,2022-11-11(005).DOI:10.28812/n.cnki.ntzrb.2022.003198.

[10]宋佳音,卜彩丽.以小见大，挖掘数据价值——《网络购物平台客户行为数据分析》项目学习案例[J].中国信息技术教育,2022(20):43-45.

[11]侯明希,谭筠鹏.线上购物平台中的“信息茧房”现象——用户视角下的新解[J].广西科技师范学院学报,2022,37(05):76-85.

[12]谢霜.基于Java技术的网络管理体系结构的应用[J].网络安全技术与应用,2022(10):14-15.

[13]刘泽青. 移动购物平台用户体验对忠诚度的影响[D].西南大学,2022.DOI:10.27684/d.cnki.gxndx.2022.001953.

[14]王曼维,杨荻,李岩,及松洁.基于SpringBoot框架的智慧医疗问诊系统设计与实现[J].中国医学装备,2022,19(03):133-136.

[15]He Xinbin,Bai Yongbin,Yue Lisen,Wang Haixiao,Liu Yi. Design and Implementation of Information System Based on Java Technology Platform[J]. Journal of Physics: Conference Series,2021,2033(1).

[16]Qu Xiaona. Application of Java Technology in Dynamic Web Database Technology[J]. Journal of Physics: Conference Series,2021,1744(4).

[17]王超,张琪立,田广强,李晶晶.基于Springboot框架的学校机房计费管理系统的设计与实现[J].电子技术与软件工程,2020(23):159-160.

[18]Tian Ming Huang. Design and Implementation of App System for Legal Consulting Based on JAVA Technology[J]. Procedia Computer Science,2020,166(C).

致谢

The deceased is like a man who never gives up day and night. In the blink of an eye, the ordinary user life is coming to an end. When people face parting and the end, they are always full of reluctance and confusion. I am also the same. I still remember that autumn, I couldn’t wait to arrive at school one day early, facing the school Looking at the majestic gate, I was full of expectations: Is this the starting point of my new life? That day, the sun was shining brightly, and the school's welcome ceremony was very warm. I faced my classmates who were smiling at me, as if rays of sunshine shone through my chest into my heart. At the same time, I met my lovely roommate that day, and we joined hands. We spent these two unforgettable two years together. Now, as I look at the acknowledgments of this paper, I can’t help but ask myself: Are we saying goodbye now?

I feel inexplicable and don't know what to say. I remember when I first came to school, I always thought that the engineering school would be too rigid and lack some tenderness. At that time, I was even a little bit repelled. But as I slowly got to know and understand the school, I realized that Her beauty, her tenderness, and I slowly fell in love with this campus, but time passed so quickly that I had to leave before I could fully appreciate her beauty, but the memories she brought to me will never be forgotten. If she leaves me, maybe my eyes will be filled with tears on the day she truly leaves. It’s not because I’m sad, I just want her image to be reflected in my tears and engraved in my heart. Finally, I would like to thank my teachers for teaching us knowledge and principles of life; thank you to my roommates for staying with me for so long; thank you to everyone who cares and supports me.

Young man, chase the wind and the moon without stopping. Wherever there is plain wasteland, there are spring mountains.

Please follow and like + privately message the blogger to receive the project source code for free

(Source code attached) springboot beauty shopping platform computer completion set 13185

1 Introduction

2 System analysis of beauty shopping platform

Table beauty_products (beauty products)

Table cancellation_of_order (cancel order)

表cancel_confirmation (取消确认)

表comment (评论)

表employee_users (员工用户)

表notice (公告)

表ordinary_users (普通用户)

表point_products (积分商品)

表product_orders (商品订单)

表product_type (商品类型)

表redemption_records (兑换记录)

表shipping_information (发货信息)

表user_points (用户积分)

4 美妆购物平台详细设计与实现

5系统测试

Guess you like