Table of contents
1.3 Related Technology Introduction
1.4 Paper Structure and Chapter Arrangement
2 Requirements Analysis of Fishing Service System
2.1.1 Technical Feasibility Analysis
2.1.2 Economic Feasibility Analysis
2.1.3 Operation Feasibility Analysis
2.1.4 Legal Feasibility Analysis
3 Overall Design of Fishing Service System
3.1 System function module design
3.1.1 Overall functional module design
3.1.3 Comment management module design
3.1.4 Commodity Management Module Design
3.1.5 Order Management Module Design
3.2.1 Database concept structure design
3.2.2 Database logical structure design
4 Detailed design and implementation of fishing service system
4.1.2 Member registration interface
4.1.4 Friends circle interface
4.1.5 Delivery address interface
4.1.6 Product Details Interface
4.1.8 Fishing point information interface
4.2 Administrator function module
4.2.1 Site management interface
4.2.2 User Management Interface
4.2.3 Fishing circle management interface
4.2.4 Fishing circle information management interface
4.2.5 Commodity management interface
Since the development of computers, computer-related technologies have been developing faster and faster. Today, with the rapid development of information technology, computer application technology seems to have been applied to various fields. In recent years, due to the improvement of people's quality of life, people's hobbies have also become more It is becoming more and more widespread. People like to fish in their spare time to cultivate their sentiments. At the same time, for anglers, in terms of purchasing and communicating with fishing products, they used to go to fishing tackle shops to purchase fishing products, and user communication is also very important. It is usually carried out through QQ or WeChat groups. Many users’ chat messages are easily overwritten. In terms of product purchases, sometimes you have to go to several fishing tackle shops for one product, and the user’s experience will drop sharply. Therefore, many merchants Started to develop a fishing service system, which brought new experiences to users, especially in time and space, allowing users to conduct transactions and communicate no matter where they are, as long as they are connected to the Internet. The front end of this fishing service system is displayed through a JSP page, the background uses the Springboot framework, and the database uses the currently popular open source relational database MYSQL. In the use of front-end technology, the currently popular vue.js is used to make the page more neat and beautiful.
Keywords : JSP; Springboot framework; MYSQL; fishing service system
Abstract
Since the beginning of computer development, computer-related technologies have developed faster and faster. Today, with the rapid development of informatization, computer application technology seems to have been applied to various fields. More and more, people like to go fishing in their spare time to cultivate their own sentiments. At the same time, for anglers, in terms of fishing commodity purchase and communication, they used to go to fishing gear stores to buy fishing products, and user communication is also very important. It is usually carried out through QQ or WeChat groups. Many chat messages of users are easily covered. In terms of commodity purchases, sometimes it is necessary to go to several fishing gear stores for a commodity, and the user's experience will drop sharply. Therefore, many merchants have Began to develop a fishing service system, such a system brings a new experience to users, especially in terms of time and space, allowing users to conduct transactions and exchanges no matter where they are, as long as they are connected to the Internet. The front-end of this fishing service system is displayed on JSP pages, the back-end uses Springboot framework, and the database uses the current popular open source relational database MYSQL. In the use of front-end technology, the currently popular vue.js is used to make the page more neat and beautiful.
Keywords: JSP; Springboot framework; MYSQL; Fishing service system
1 Introduction
1.1 Research Background
At present, most industries are gradually bringing e-commerce informatization into their own enterprises, mainly Internet platforms dominated by e-commerce services. For example, if you are mainly committed to fishing services at present, you must closely focus on fishing services. Through the empowerment of the Internet platform, it can provide intelligent services to fishing service users and merchants, and improve the efficiency of merchants while providing users with substantial convenience. Therefore, the fishing service system is more in line with the needs of current users and businesses, and can better adapt to the current competitive pressure of the fishing industry [1]. The fishing service system is based on the "Internet +" B2C service model. While providing users with online independent selection of fishing products to inquire about transactions, it also provides users with some fishing location information, which can enable fishing enthusiasts to communicate and share with each other, and help merchants improve their stores. The sales volume can also make efforts for the intelligent development of the fishing industry.
Nowadays, with the popularization of the Internet and the rapid development of information technology, all fields of society are constantly innovating and reforming in keeping with the pace of the times. Great changes have taken place, from the manual processing of information and data in the past to the current computer The intelligent processing of information data has achieved a qualitative change. It has changed the disadvantages of cumbersome, time-consuming, easy to leak, and difficult to save into the advantages of fast operation, time-saving and labor-saving, high confidentiality, and easy storage. This makes everyone in the society All areas benefit.
With the advent of the Internet + era and the sudden rise of e-commerce, the form of online shopping became very popular for a while, and now, online shopping is even more popular. Nowadays, various industries are also expanding their business through online shopping, increasing the popularity of the company and improving performance, satisfying users like online shopping, viewing fishing information online, purchasing goods, and using the current hot computer technology to target fishing services Building a safe, reliable and professional information management system for related businesses can make the management process more convenient, reduce the manpower invested, significantly improve the efficiency, and provide users with higher quality services .
1.3 Related Technology Introduction
(1) The backend of the web background management in the fishing service system no longer uses the ancient jsp+javabean+servlet[5] technology, but uses the current mainstream Sprinboot[6] framework, which reduces java configuration code and simplifies programming Code, the current Sprinboot framework is also one of the frameworks chosen by many companies.
(2) The front end of the web background management in the fishing service system uses the bootstrap[7] framework, which can beautify the page design with ajax[8] and jquery[9].
(3) The popular vue framework combines jQuery technology to extend some plug-ins on the basis of jQuery, and better realize the front-end design by defining plug-ins by yourself.
(4) The mysql5.7[10] used for the database in the fishing service system has high execution efficiency.
1.4 Paper Structure and Chapter Arrangement
This fishing service system is divided into six chapters for introduction, and the content of the chapters is arranged as follows:
Chapter 1: Introduction. The first chapter mainly introduces the research background of the fishing service system, the research significance of the fishing service system, the main development technology and the research content and main work of this paper.
Chapter Two: System Requirements Analysis. The second chapter mainly conducts demand analysis from the aspects of system users and functions.
Chapter Three: System Design. The third chapter mainly carries on the function design to the system frame, the system function module, the database.
Chapter Four: System Realization. The fourth chapter mainly introduces the construction of the system framework and the realization of the system interface.
Chapter Five: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions
2 Requirements Analysis of Fishing Service System
System requirements analysis is a key link in system development, and it plays a connecting role in system design and implementation. System requirements analysis is to mine the requirements of the system that needs to be done. If the analysis is accurate, it can accurately solve the problems encountered in reality. If the analysis is not in place, it will affect the realization of the later system. The requirement analysis of a system's excellence also occupies a very large proportion. If the requirement analysis is not in place, the subsequent system design will be a design that deviates from the navigation.
2.1 Feasibility analysis
System feasibility analysis is a discussion on system-to-system feasibility. In discussing the feasibility of the system, we mainly analyze it from the aspects of technical feasibility, economic feasibility, operational feasibility and legal feasibility. If the four levels pass, we consider the system to be relatively feasible.
2.1.1 Technical Feasibility Analysis
The design and implementation of the fishing service system is a web-based fishing service platform. The technical solution we use to implement this system is a Java-based web implementation solution. The system uses the Spring boot architecture to integrate Spring, SpringMvc, and Mybatis solutions . The SSM framework is a very mature framework. Java has experienced brutal growth since its birth in 1997. Java has very mature solutions in various fields, such as telecommunications, banking, and e-commerce. Spring boot is another set of out-of-the-box technical solutions for the entire project. Therefore, it is a very mature and simple technical solution to implement this system based on spring boot. Technical feasibility is very feasible.
2.1.2 Economic Feasibility Analysis
From the perspective of economic feasibility, the project needs a development PC in the development stage, and a web server and database server in the production stage. A personal PC is not too much of a problem from an economic point of view. In terms of later system deployment and production, the investment in servers will not be too high, and it is relatively feasible from an economic point of view.
2.1.3 Operation Feasibility Analysis
The fishing service system developed this time is relatively simple, as long as users who can access the Internet can use it. After entering the system, they can perform corresponding operations according to the prompts. Regardless of the system operation design, the logical design of the Blackstone system is relatively simple. For example When a user wants to buy a certain product, he must first understand the various parameters of the product. In the process of understanding, we set up a purchase operation on this page to facilitate the user to purchase, so it seems that it is more convenient for users to use. It is easy to operate; let’s look at the administrator management part again. Our system price settings and various parameter settings are fixed. Operators can add, delete, modify, and check as long as they enter, which is very convenient. Generally speaking, the system is operating above is feasible.
2.1.4 Legal Feasibility Analysis
From a legal perspective, the system has no other legal issues for third parties. The system database uses the Mysql open source community database, and the framework uses the open source Spring Boot. System information and related content also comply with legal aspects. In terms of source code management, git open source is used for management, so it is established in terms of legal feasibility.
2.2.1 Data flow
The main purpose of the fishing service system is to realize the online purchase of fishing products. Figure 2-1 is the data flow diagram of the system.
Figure 2-1 Expansion diagram of product purchase operation
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
The design and implementation of the fishing service system is to make it more convenient for managers to manage some information related to fishing services, and it is also beneficial for users to view fishing service information through the web system, online shopping for goods and mutual communication between fans. Communication between users can save a lot of time and energy when searching for a certain information, and effectively reduce unnecessary search time.
The purpose of studying the design and implementation of the fishing service system is to have an intelligent one-stop fishing service management method with simple and friendly interface, simple operation and stable operation. System requirements mainly come from managers and users.
User management module:
(1) User registration and login: Tourists can enter the system at any time and browse the information in the system. However, if they want to realize product purchase and communication, they must have an account of this system. If they do not have an account, they can register as a member user to proceed. At the same time, users can also control personal information and operated information through the "My" button.
(2) View the home page information of the fishing service system: the home page information of the fishing service system includes the home page, fishing friends circle, announcement message, fish circle information, fishing point information, etc.
(3) Fishing Friends Circle: Click "Fishing Friends Circle" to view some communication information released by fishing enthusiasts. After selecting a certain information to enter the details, you can reply your own opinions to the communication information released by fishing enthusiasts, and you can also publish New topics for everyone to discuss together.
(4) Announcements: After clicking the "Announcements" button, all the announcements issued by the background (administrator) will be displayed, so that users can learn about some real-time developments.
(5) Fishing circle information: Click the "Fishing circle information" button to display all fishing circle information released by the background (administrator), and support users to like, bookmark, and comment on fishing circle information.
(6) Fishing point information: After clicking the "Fishing point information" button, all fishing point information released by the background (administrator) will be displayed. Users can bookmark it to find it faster next time, and can also like the fishing point information ,Comment.
(7) Commodity purchase: Users can browse all product information on the homepage, and when they inquire about the product they want to buy, they can enter to view the detailed introduction, and can add purchase, purchase immediately, bookmark, and comment.
(8) Shopping cart: Click the "Shopping Cart" button to display all the products you have added to the shopping cart. If you confirm the purchase, you can proceed to purchase settlement for the selected products.
(9) My order: Click "My order" under the "My" button to display all the order information submitted by yourself, and support the deletion management of the order.
(9) My Favorites: Click "My Favorites" under the "My" button to display all the information in your favorites. If you don't want to favorite a certain information, click the details and click the delete button to delete it. OK.
Administrator management module:
(1) Site management: The administrator can add, delete, modify and check the carousel pictures and announcements displayed on the front desk of the system, which is convenient for users to view.
(2) User management: The administrator can control the user information registered on the front desk, and can also control the administrator information.
(3) Management of fishing circles: the administrator can add, delete, modify and check the information of fishing circles adjusted by member users in the fishing service system and the classification information of fishing circles in the background.
(4) Fishing circle information: the administrator can add, delete, modify and check the fishing circle information and information classification information displayed in the fishing service system in the background.
(5) Classification management: The administrator controls the classification of commodities in the fishing service system.
(6) Commodity management: The administrator controls the commodity information displayed in the fishing service system, making it convenient for users to inquire and purchase.
(7) Order management: The administrator can control the orders submitted by users in the fishing service system.
(8) Fishing point management: the administrator can add, delete, modify and check the fishing point information displayed in the fishing service system in the background.
The non-functional requirements of the fishing service system include the security, reliability, performance, and scalability of the fishing service system. Specifically, it can be expressed in the following table 3-1:
Table 3- 1 Non-functional requirements table of fishing service system
| safety |
It mainly refers to the installation of the database of the fishing service system, the use of the database and the setting of the password must comply with the regulations. |
| reliability |
Reliability means that the fishing service system can be operated according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for the fishing service system to occupy the market, so it is better 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 operate according to the content displayed on the phishing service system page. |
| maintainability |
The maintainability of fishing service system development is very important. After testing, there is no problem with maintainability |
2.4 System use case analysis
Through the analysis of 2.3 functions, the use case diagram of this fishing service system is obtained:
Figure 2-3 shows an example of a user role.
Figure 2-3 User role use case diagram of the phishing service system
The administrator on the web background management maintains all data information in the entire phishing service system. Figure 2-4 shows an example of an administrator role.
Figure 2-4 Fishing service system administrator role use case diagram
This chapter mainly determines the functions to be realized by the entire fishing service system through the feasibility analysis, process analysis, functional requirement analysis, and system use case analysis of the fishing service system. At the same time, it also provides a standard for the code implementation and testing of the fishing service system.
3 Overall design of fishing service system
This chapter mainly discusses the functional module design and database system design of the fishing service system.
3.1 System function module design
3.1.1 Overall functional module design
In the last chapter, the functional requirements and non-functional requirements of the system are mainly analyzed, and the use cases in this fishing service system are analyzed according to the requirements. Then the next step is to start designing the architecture, main functions and database of this fishing service system. The fishing service system is obtained based on the requirements analysis in the previous chapters, and its overall design module diagram is shown in Figure 3-1.
Figure 3-1 Functional module diagram of fishing service system
3.1.2 User module design
The background manager can add, delete, modify and check the users registered in the front desk. The structure diagram of the user module is as follows:
Figure 3-2 Structure Diagram of Member User Module
3.1.3 Comment management module design
The fishing service system is an open platform of communication nature. Member users can communicate on the platform to increase the interaction between users. But at the same time, in order to better regulate 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-3 Comment module structure diagram
3.1.4 Commodity management module design
The fishing service system needs to store a lot of commodity information, and its module function structure, the specific structure diagram is as follows:
Figure 3-4 Commodity module structure diagram
3.1.5 Design of order management module
One of the most important functions of the fishing service system is purchase. Its module function structure, the specific structure diagram is as follows:
Figure 3-5 Order module structure diagram
Database design generally includes three major processes: requirements analysis, conceptual model design, and database table establishment. Requirements analysis has been explained in the previous chapters, and conceptual model design has two parts: conceptual model and logical structure design.
3.2.1 Conceptual structure design of database
The following is the ER entity relationship diagram of the main database tables in the entire fishing service system.
Figure 3-6 Overall ER relationship diagram of the fishing service system
According to the general ER relationship diagram of the database of the fishing service system, it can be concluded that the fishing service system needs many ER diagrams, and some main database ER model diagrams are listed here.
Figure 3-7 Member user information ER relationship diagram
Figure 3-8 Diagram of the ER relationship of fishing circle information
Figure 3-9 ER relationship diagram of commodity management information
Figure 3-10 ER relationship diagram of order information
Figure 3-11 Address information ER relationship diagram
Figure 3-12 ER relationship diagram of fishing circle information
3.2.2 Database logical structure design
From the total ER relationship diagram in the fishing service system in the previous section, it can be concluded that a lot of data tables need to be created. Here I mainly list several major database table structure designs.
(1) The member_user table, as shown in Table 3-1, includes member user id+name+gender+audit status, etc., and is mainly used when the front-end user logs in to the fishing service system.
Table 3-1 member_user member user information table
| column name |
type of data |
length |
allow empty |
illustrate |
| buyers_id |
int |
11 |
no |
member user id |
| full_name |
varchar |
64 |
yes |
Name |
| gender |
varchar |
64 |
yes |
gender |
| examine_state |
varchar |
16 |
yes |
Approval Status |
| recommend |
int |
11 |
yes |
Intelligent Recommendation |
| user_id |
int |
11 |
yes |
user id |
| create_time |
datetime |
yes |
creation time |
|
| update_time |
longtext |
yes |
update time |
(2) The forum table, as shown in Table 3-2, contains the primary key + user id + nickname + cover image + text + title + number of likes + forum classification, etc. It is mainly used for user communication.
Table 3-2 forum fishing friend circle information table
| column name |
type of data |
length |
allow empty |
illustrate |
| forum_id |
mediumint |
8 |
no |
fishing circle id |
| display |
Smallint |
5 |
yes |
to sort |
| user_id |
mediumint |
8 |
yes |
user id |
| nickname |
varchar |
10 |
yes |
Nick name |
| praise_len |
int |
10 |
yes |
Likes |
| hits |
int |
10 |
yes |
number of visits |
| title |
varchar |
125 |
yes |
title |
| keywords |
varchar |
125 |
yes |
Key words |
| description |
varchar |
125 |
yes |
describe |
| url |
varchar |
125 |
yes |
source address |
| tag |
varchar |
255 |
yes |
Label |
| img |
text |
16 |
yes |
cover picture |
| content |
longtext |
16 |
yes |
text |
| avatar |
Varcha |
255 |
yes |
Poster Avatar |
| type |
varchar |
yes |
Forum classification |
|
| create_time |
datetime |
yes |
creation time |
|
| update_time |
longtext |
yes |
update time |
(3) The commodity_management table is shown in Table 3-3. It is mainly in the administrator that you can better adjust the price of the product and recommend product replacement. In the front end (member users) you can effectively search for the product and intuitively see the appearance of the product and product attributes, etc.
Table 3-3 Commodity_management Commodity Management Information Table
| column name |
type of data |
length |
allow empty |
illustrate |
| mall_management_id |
int |
11 |
no |
commodity management id |
| remarks |
int |
11 |
yes |
Remark |
| cart_title |
varchar |
125 |
yes |
title |
| cart_img |
text |
yes |
cover picture |
|
| cart_description |
varchar |
255 |
yes |
describe |
| cart_price_ago |
double |
yes |
original price |
|
| cart_price |
double |
yes |
selling price |
|
| cart_inventory |
int |
11 |
yes |
Commodity stocks |
| cart_type |
varchar |
64 |
yes |
Categories |
| cart_content |
longtext |
64 |
yes |
text |
| cart_img_1 |
text |
10 |
yes |
main image |
| recommend |
int |
11 |
Intelligent Recommendation |
|
| create_time |
datetime |
11 |
yes |
creation time |
| update_time |
timestamp |
yes |
update time |
(4) The order table is shown in Table 3-4. The main order information is formed by the front-end (buyer) and the order administrator executes the management. The buyer administrator can see all the information of the order.
Table 3-4 order information table
| column name |
type of data |
length |
allow empty |
illustrate |
| order_id |
int |
11 |
no |
order id |
| order_number |
varchar |
64 |
yes |
order number |
| goods_id |
varchar |
64 |
yes |
commodity id |
| title |
varchar |
32 |
yes |
product title |
| img |
varchar |
255 |
yes |
product picture |
| price |
double |
yes |
price |
|
| price_ago |
double |
yes |
original price |
|
| num |
int |
11 |
yes |
quantity |
| price_count |
double |
yes |
total price |
|
| norms |
varchar |
255 |
yes |
Specification |
| type |
varchar |
64 |
yes |
Classification |
| contact_name |
varchar |
32 |
是 |
联系人姓名 |
| contact_email |
varchar |
125 |
是 |
联系人邮箱 |
| contact_phone |
varchar |
11 |
是 |
联系人手机 |
| contact_address |
varchar |
125 |
是 |
收货地址 |
| postal_code |
varchar |
11 |
是 |
邮政编码 |
| user_id |
varchar |
10 |
是 |
买家id |
| merchant_id` |
mediumint |
8 |
是 |
商家id |
| description |
varchar |
255 |
是 |
描述 |
| state |
varchar |
16 |
是 |
状态 |
| create_time |
datetime |
是 |
创建时间 |
|
| update_time |
timestamp |
是 |
更新时间 |
（5）address表如表3-5所示，主包含了收货地址id+姓名+手机+邮编+地址，主要用在用户对提交订单选择地址的时候进行使用。
表3-5 address收货地址信息表
| 列名 |
数据类型 |
长度 |
允许空 |
说明 |
| address_id |
int |
11 |
否 |
收货地址id |
| name |
varchar |
32 |
是 |
姓名 |
| phone |
varchar |
16 |
是 |
手机 |
| postcode |
varchar |
8 |
是 |
邮编 |
| address |
varchar |
255 |
是 |
地址 |
| default |
int |
11 |
是 |
默认判断 |
| user_id |
mediumint |
8 |
是 |
用户id |
| create_time |
datetime |
是 |
创建时间 |
|
| update_time |
longtext |
是 |
更新时间 |
（6）article表如表3-6所示，主要在系统后台（管理员）中可以更好的管控新闻，在前端（买家）可以有效的查找新闻等。
表3-6 article渔圈资讯信息表
| 数据类型 |
长度 |
允许空 |
说明 |
|
| article_id |
mediumint |
8 |
否 |
渔圈资讯id |
| title |
varchar |
125 |
是 |
标题 |
| type |
varchar |
64 |
是 |
分类 |
| hits |
int |
10 |
是 |
点击数 |
| praise_len |
int |
11 |
是 |
点赞数 |
| create_time |
datetime |
是 |
创建时间 |
|
| update_time |
timestamp |
是 |
更新时间 |
|
| source |
varchar |
255 |
是 |
来源 |
| url |
varchar |
255 |
是 |
来源地址 |
| tag |
varchar |
255 |
是 |
标签 |
| content |
longtext |
是 |
正文 |
|
| img |
varchar |
255 |
是 |
封面图 |
| description |
text |
是 |
描述 |
整个垂钓服务系统的需求分析主要对系统总体架构以及功能模块的设计，通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。
4 垂钓服务系统详细设计与实现
垂钓服务系统的详细设计与实现主要是根据前面的垂钓服务系统的需求分析和垂钓服务系统的总体设计来设计页面并实现业务逻辑。主要从垂钓服务系统界面实现、业务逻辑实现这两部分进行介绍。
4.1用户功能模块
4.1.1 前台首页界面
当进入垂钓服务系统的时候，首先映入眼帘的是系统的导航栏，下面是轮播图以及系统内容，其主界面展示如下图4-1所示。
图4-1 前台首页界面图
4.1.2 会员注册界面
普通的用户只支持对网站信的浏览，想要购买或者交流就必须登录到系统，如果你没有本垂钓服务系统的账号的话，添加“注册”根据提示输入好用户信息后，点击“注册”按钮后，系统会对输入的信息进行验证，验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可会员注册成功。其用会员注册界面展示如下图4-2所示。
图4-2 前台会员注册界面图
4.1.3 会员登录界面
垂钓服务系统中的前台上注册后的会员是可以通过自己的账户名和密码进行登录的，当会员输入完整的自己的账户名和密码信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到垂钓服务系统的首页中；否则将会提示相应错误信息，用户登录界面如下图4-3所示。
图4-3会员登录界面图
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-8所示。
图4-8 钓点信息界面图
4.2管理员功能模块
4.2.1站点管理界面
管理员可以对系统前台展示的轮播图以及公告进行增删改查，方便用户进行查看。界面如下图4-9所示。
图4-9 站点管理界面图
垂钓服务系统中的管理人员是可以对前台注册的会员进行管理的，也可以对管理员进行管控。界面如下图4-10所示。
图4-10用户管理界面图
垂钓服务系统中的管理人员是可以对前台用户发布的钓友圈信息进行管控的，界面如下图4-11所示。
图4-11钓友圈界面图
垂钓服务系统中的管理人员是可以对前台显示的渔圈资讯信息进行管控，界面如下图4-12所示。
图4-12渔圈资讯界面图
理员对垂钓服务系统所展示的商品信息进行管控，方便用户查询购买。界面如下图4-13所示。
图4-13商品管理界面图
管理员可以对垂钓服务系统中用户提交的订单进行管控，订单列表界面如下图4-14所示。
图4-14订单列表界面图
管理员在后台可以对垂钓服务系统中显示的钓点信息进行增删改查。钓点信息界面如下图4-15所示。
图4-15钓点信息界面图
5系统测试
系统的前台、后台、数据库完成以后，这个系统才算是完成了一半，我们在这之后要对系统进行最后的一个阶段，那就是测试了，测试对一个系统来说是非常重要的，有的时候开发完一个系统，如果测试不合格的话，这个系统是没有办法进行投入使用的，所有我们要用测试对系统的功能进行检验，把不完善的功能尽量完善，把出现的bug解决掉，然后给用户呈现出一个完美的系统。通过对系统最后一步的测试，使得开发人员对自己的系统更加有信心，更加积极的为后期的系统版本的更新提供支持。
系统测试包括：用户登录功能测试、商品展示功能测试、商品添加、商品搜索、密码修改功能测试，如表5-1、5-2、5-3、5-4、5-5所示：
表5-1 用户登录功能测试表
商品查看功能测试：
表5-2 商品查看功能测试表
管理员添加商品界面测试：
表5-3 管理员添加商品界面测试表
商品搜索功能测试：
表5-4商品搜索功能测试表
密码修改功能测试：
表5-5 密码修改功能测试表
通过编写垂钓服务系统的测试用例，已经检测完毕用户登录模块、商品查看模块、商品添加模块、商品搜索模块、密码修改功能测试，通过这5大模块为垂钓服务系统的后期推广运营提供了强力的技术支撑。
至此论文结束，感谢您的阅读。在此我要感谢我的导师，虽然我在实习期间很忙，论文撰写总是停停改改，但是导师依然十分负责，时不时的询问我的任务进展情况，跟进我的论文进度。虽然我在实习期间很忙，以至于很晚才开始进行论文撰写和编写程序的工作，但是在指导老师的帮助下，我逐步完成了自己的论文和程序，从导师身上也学习到很多知识，和经验，这些知识和经验令我受益匪浅。也从导师身上看到了自己的不足，不论是在即使层面上还是在对待工作的态度上，倒数如同明镜一般照出了我的缺点我的不足。此外，我还要感谢在我实习期间在论文和程序上帮助过我的同学和社会人士，此前我对于PHP开发方面的一些知识还不了解，是他们在我编写程序过程中给了我很多的启发和感想，也帮助了我对于程序的调试和检测。没有他们我是不能顺利完成本次毕业设计的。至此，我的毕业设计就花上了一个圆满的句号了。
[1]刘敏. 基于SpringBoot框架社交网络平台的设计与实现[D]. 湖南大学, 2018.
[1]张培利. 基于Vue+SpringBoot框架技术的高校课程平时成绩系统浅析[J]. 2020.
[1]熊永平. 基于SpringBoot框架应用开发技术的分析与研究[J]. 电脑知识与技术：学术版, 2019, 15(12X):2.
[1]杨众. 基于Spring Boot的校园商城系统设计与实现[J]. 信息技术与信息化, 2020(9):2.
[1]叶方超, 张思扬, 李传锴. 基于SpringBoot的旧物回收商城的设计与实现[J]. 智能计算机与应用, 2019, 9(5):3.
[1]贾志勇. 基于SpringBoot的下沉市场交易平台的设计与实现. 安徽大学.
[1]陈宇. 基于Spring Boot的电商管理系统的设计[J]. 现代信息科技, 2020, 4(1):2.
[1]许乐. 基于spring boot技术微信平台的BC新零售点餐系统的设计[J]. 轻松学电脑, 2019.
[1] F Gutierrez. Spring Boot[J]. Apress.
[1] Antonov A . Spring Boot cookbook : over 35 recipes to help you build, test, and run Spring applications using Spring Boot. 2015.
[1] Turnquist G L . Learning Spring Boot learn how to use Spring Boot to build apps faster than ever before.
[1] LiY , GaoS , WuW , etal. Research and Development Housing Rental System with Recommendation System Based on SpringBoot[M]. 2021.
逝者如斯夫，不舍昼夜。转眼间，大学生会员活便已经接近尾声，人面对着离别与结束，总是充满着不舍与茫然，我亦如此，仍记得那年秋天，我迫不及待的提前一天到了学校，面对学校巍峨的大门，我心里充满了期待：这里，就是我新生活的起点吗？那天，阳光明媚，学校的欢迎仪式很热烈，我面对着一个个对着我微笑的同学，仿佛一缕缕阳光透过胸口照进了我心里，同时，在那天我认识可爱的室友，我们携手共同度过了这难忘的两年。如今，我望着这篇论文的致谢，不禁又要问自己：现在，我们就要说再见了吗？
感慨莫名，不知所言。遥想当初刚来学校的时候，心里总是想着工科学校会过于板正，会缺乏一些柔情，当时心里甚至有一点点排斥，但是随着我对学校的慢慢认识与了解，我才认识到了她的美丽，她的柔情，并且慢慢的喜欢上了这个校园，但是时间太快了，快到我还没有好好体会她的美丽便要离开了，但是她带给我的回忆，永远不会离开我，也许真正离开那天我的眼里会满含泪水，我不是因为难过，我只是想将她的样子映在我的泪水里，刻在我的心里。最后，感谢我的老师们，是你们教授了我们知识与做人的道理；感谢我的室友们，是你们陪伴了我如此之久；感谢每位关心与支持我的人。
少年，追风赶月莫停留，平荒尽处是春山。
点赞+收藏+关注 → 私信领取本源代码、数据库