Summary
Today in the 21st century, with the continuous development and progress of society, people's scientific understanding of information has developed from low level to high level, from the original perceptual understanding to rational understanding. The importance of management work has gradually been recognized by people. It is understood that scientific management can make information storage accurate, fast and complete, and can improve the efficiency of work management and promote its development.
The paper mainly introduces the pet adoption system , including the current status of the research and the development background involved. It also discusses the design goals of the system, the requirements of the system, the entire design plan, and the design of the system. and implementation were also discussed in detail. Finally, some specific tests were conducted on the pet adoption system .
This article uses springboot as the development technology to implement a pet adoption system . The main users of the pet adoption system are divided into users and administrators; the main functions include: homepage, carousel, notifications and announcements, resource management (news information, news classification) communication management (communication forum, forum classification) system users (management Members, system users) module management (pet type, pet information, adoption information) personal management and other functions. Through the design of these functional modules, the entire pet adoption system process is basically realized .
Specifically in the system design, the springboot structure is adopted , and the Mysql database is used in the background . It is a very excellent pet adoption system .
Keywords: pet adoption system ; springboot technology; Mysql database
Abstract
Today in the 21st century, with the continuous development and progress of society, people's understanding of information science has developed from low level to high level, from the original perceptual knowledge to rational knowledge, and the importance of management has gradually been recognized by people. Scientific management can make information storage accurate, fast and perfect, and can improve the efficiency of work management and promote its development.
The paper mainly introduces the pet adoption system, including the current situation of research and the development background involved, and then discusses the design objectives of the system, the system requirements, and the whole design scheme. The design and implementation of the system are also described in detail. Finally, some specific tests are carried out on the pet adoption system.
This paper uses spring boot as the development technology to implement a pet adoption system. The main users of the pet adoption system are divided into users and administrators; The main functions include: home page, rotation chart, notice announcement, resource management (news information, news classification) communication management (exchange forum, forum classification) system user (administrator, system user) module management (pet type, pet information, adoption information) individual management and other functions. Through the design of these functional modules, the whole process of pet adoption system is basically realized.
In terms of system design, spring boot structure is adopted, and MySQL database is used in the background, which is a very excellent pet adoption system.
Key words: pet adoption system; Spring boot technology; MySQL database
Table of contents
1.1 Background and significance of the topic
1.2 Research status at home and abroad
2 System development environment
2.1 Introduction to springboot framework
2.2 Software development environment and development tools
2.3 Working principle of B/S system
3.2.1 System development process
3.2.3 System operation process
3.2.6 Information deletion process
3.3.1 Administrator use case diagram
4.3.1 Database design principles
5.1 Front page function module
5.2 Administrator function module
1.1 Background and significance of the topic
The rapid development of the Internet has fundamentally changed the management methods of organizations around the world. Since the 1990s, our country's government, enterprises and institutions have imagined that information can be managed through the Internet system. Due to various reasons in the past, such as low network penetration, user rejection, insufficient Internet-related laws and regulations, and immature development technology, the development speed of the Internet in major institutions was hindered. After entering the 21st century, my country's economy has developed rapidly, and various problems restricting institutional management have been solved one by one. All major domestic institutions have joined the electronic information management model.
In the past , information related to the pet adoption system was managed manually by staff. This method is not only timely but also inconvenient when searching and changing. With the advancement of science, the maturity of technology, and the rapid development of computer informatization, society has also gained a profound understanding that computers are very powerful. Computers have entered various fields of the development of human society and play a very important role. This system uses network communication and computer information storage and management, and has advantages that cannot be replaced by traditional methods. For example, the calculation and retrieval speed is extremely fast, the reliability is extremely high, the storage capacity is extremely large, the confidentiality is extremely good, the storage time is extremely long, and the cost is extremely low. In terms of work efficiency, it can be greatly improved, and there will also be good gains when extended to service levels. With the Internet, the management of all aspects of the online pet adoption system is more scientific and systematic, more standardized and simpler.
1.2 Research status at home and abroad
With the continuous penetration of computer networks, the way people live, work, and study is slowly changing. Traditional user -related information management methods generally adopt manual methods, and the acquisition, organization, modification, and storage of information are still in the manual stage. On the one hand, this method requires a lot of manpower, material resources and money, is difficult to interact with, and wastes time; on the other hand, the management of user and other information, especially as the number of users increases, is particularly difficult to query and modify. ; Finally, due to the continuous increase of users and other information, the storage of information has also become a problem.
In some developed countries, the Internet has developed relatively quickly and has largely completed the transition from manual to computer management. Computer application in our country started relatively late, and the development regions are unbalanced. There are still many regions or units using traditional methods for management. However, computers are developing rapidly, including the popularization of the Internet. Many units and users are slowly beginning to come into contact with network management. system. Looking at these systems, they mainly have the following characteristics:
(1)Advancement: realize network management.
(2) Versatility: It can basically be used in the same industry.
(3) Convenience: Management work can be completed through the Internet.
(4) Timeliness: Information is updated in a timely manner.
( 5 ) Scalability: Modules can be added as needed.
( 6 ) Security: Encrypt unit, user and other information.
Up to now, the Internet has penetrated deeply into people's lives. Smartphones, laptops, etc. have become people's main tools for obtaining information. This is an era of unlimited communication. Therefore, using the Internet to manage online pet adoption systems has also become a general trend. Therefore, , it is necessary to develop a pet adoption system .
1.3 Main work of this topic
At the beginning, this article gives an overall description of the basic knowledge discussed in the system, and conducts a system analysis on this basis. In order to enable this system to be designed and implemented in a better and more complete manner, analysis and investigation must be conducted first. Based on the previous related foundations, a detailed analysis of the new system was carried out in terms of functionality. Then through detailed analysis, system design was carried out. Secondly, in terms of the feasibility of system implementation, I chose Java technology for development and design. For data storage, I used Mysql database for design. Since both Java and Mysql are very mature, they are very reliable, safe and practical in all aspects. Finally, the system is tested, perfected and released.
2 System development environment
2.1 Introduction 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. The Spring framework has an 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.
2.2 Software development environment and development tools
Software development environment and development tools:
Operating system: Windows 10, Windows 7, Windows 8
Development language: Java
Using framework: spring boot
Front-end technology: JavaScript, VUE.js (2.X), css3
Development tools: IDEA (2020 version)/MyEclipse (10)/Eclipse, Visual Studio Code
Database: MySQL 5.7.26 (version number)
Database management tool: phpstudy/Navicat
JDK version: Java sdk8
Maven:apache-maven 3.8.1-bin
Hardware environment:
CPU: 1.60GHz and above
Memory: 4GB and above
Hard disk: 500MB or more
Graphics card: Image-level graphics card or above
2.3 Working principle of B/S system
The B/S architecture adopts the working mode of browser request and server response.
Users can access text, data, pictures, animations, video on demand, sounds and other information generated by the Web server on Interspringboot through the browser;
Each Web server can be connected to the database server in various ways, and a large amount of data is actually stored in the database server;
Download the program from the Web server to the local for execution. If you encounter instructions related to the database during the download process, the Web server will hand it over to the database server for interpretation and execution, and return it to the Web server, and the Web server will return it to the user. In this structure, many networks are connected together to form a huge network, that is, the global network. Each enterprise can build its own Interspringboot based on this structure.
In the B/S mode, the user requests access through the browser to many servers distributed on the network. The browser's request is processed by the server, and the processing results and corresponding information are returned to the browser. Other data All processing and requests are completed by the Web Server. Through this framework structure and the browser embedded inside the operating system, this structure has become the mainstream structure pattern of today's software applications. .
2. 5 Mysql database
Databases are an integral part of the system development process. In terms of WEB applications, MySQL AB has developed a MySQL relational database management system with great advantages. MySQL can store data in different tables, which is very flexible and can also increase the speed of the system in practical applications. Database access is most commonly used in the standard SQL language, and MySQL is used in the SQL language, so it is highly compatible. Database operations are essential, including functions such as adding, deleting, modifying, and querying database tables. Nowadays, databases can be divided into relational databases and non-relational databases. Mysql is a relational database. Mysql database is a small relational database. It has its own characteristics: small size, fast speed, low cost, etc. Mysql Database is currently the most popular open source database.
In WEB application technology, the Mysql database supports different operating system platforms. Although the installation and configuration under different platforms are different, the difference is not very big. There are two installation methods for Mysql on the Windows platform, binary version and installation-free. Version. After installing the Mysql database, you need to start the service process, and the corresponding client can connect to the database. The client can log in to the database through the command line or graphical interface tool.
The so-called system analysis means that demand personnel obtain information through communication with users , and then display this information to users and developers in the form of demand specifications. In the long history of the development of software functions, for a long time, especially in the beginning, the importance of requirements analysis was not recognized by people. For example, at that time, the American company IBM developed an information management system for British Telecom. Development started without clarity, and the initial construction period was one year. Due to unclear requirements, the construction period was delayed by more than half a year, causing huge losses. This situation also exists in many of our software companies. They develop while developing, and even without clear communication with users , they directly copy the same type of projects and make changes. As a result, changes are made again when the system is accepted, resulting in a loss of manpower and material resources. A huge waste. The reason for all these consequences is that the demand acquisition is not timely, unclear, and incomplete.
3.1 Feasibility analysis
The main goal of the pet adoption system is to achieve online related information management services. After determining the goals, we conduct a feasibility analysis on whether the goals of this system can be achieved from the following four aspects.
3.1.1 Technical feasibility
The pet adoption system mainly uses Java technology, based on B/S structure and Mysql database. The development of applications requires complete functions, simple use, and the establishment of a database with complete, safe and stable data. The development technology of the pet adoption system is highly feasible, and the developers have mastered certain development technologies, so the development of the system is feasible.
3.1.2 Operational feasibility
The login interface of the pet adoption system is simple and easy to operate. It uses a common interface window to log in to the interface and access it through a computer. Members can access it as long as they have used a computer. The development of this system uses Java language and is based on B/S structure. These development environments make the system more complete. This system has the characteristics of easy operation, easy management, good interactivity, and is very simple in operation. Therefore this system can be developed.
3.1.3 Economic feasibility
The pet adoption system is based on Java mode and uses Mysql database to store data. The required hardware and software environments are easily purchased on the market. Program development mainly involves the development and maintenance of the management system. Therefore, the program does not require high development manpower and financial resources, and the system is not very complex, the development cycle is short, and it has high economic feasibility.
3.1.4 Legal feasibility
This pet adoption system is a self-designed management system and has great practical significance. Because both the software and the database use open source code, the development and design of this system does not have problems such as infringement and is completely legally feasible.
In summary, the pet adoption system is technically, economically, operationally and legally feasible, and it is feasible to develop this program.
3.2 System process analysis
3.2.1 System development process
When developing a pet adoption system , we first conduct a needs analysis, and then conduct an overall design plan for the system, design system functional modules, database selection, etc. The development process of this system is shown in Figure 3-1.
Figure 3-1 System development flow chart
3.2.2 User login process
In order to ensure the security of the system, if you want to use this system to manage system information, you must first log in to the system. As shown in Figure 3-2.
Figure 3-2 Login flow chart
3.2.3 System operation process
After the user opens and enters the system, the login interface will be displayed first, and the correct user name and password will be entered. The system will automatically detect the information. If the information is correct, the user will enter the system function interface and perform operations. Otherwise, an error will be displayed and the user cannot log in. Operation process As shown in Figure 3-3.
Figure 3-3 System operation flow chart
3.2.4 Add information process
Administrators can add pet information, etc. Users can add information within their own authority. After entering the information, the system will verify the entered information and data. If the information is correct, it will be added to the database. If the information is incorrect, you will be prompted to re-enter the information. The process of adding information is shown in Figure 3-4.
Figure 3-4 Add information flow chart
3.2.5 Modify information flow
Administrators can modify pet information, etc. Users can modify information within their own authority. First, enter the modification information interface and enter the modification information data. The system will judge and verify the data. If the modified information is legal, the modification will be successful and the information will be updated to Database, if the information is illegal, the modification will fail and re-enter. The modified information flow chart is shown in Figure 3-5.
Figure 3-5 Modify information flow chart
3.2.6 Information deletion process
Administrators can delete pet management information and other information. After selecting the information to be deleted, click the delete button, and the system will ask if you are sure. If you click OK, the system will delete the selected information and compare it in the database. The information is deleted. The flow chart of deleting information is shown in Figure 3-6.
Figure 3-6 Deletion information flow chart
3.3 System use case analysis
3.3.1 Administrator use case diagram
The core user in the system is the system administrator . After the administrator logs in, he manages the backend system through the administrator. The main functions are: homepage, carousel, notifications and announcements, resource management (news information, news classification) communication management (communication forum, forum classification) system user (administrator, system user) module management (pet type, pet information, adoption Information) personal management and other functions . The administrator use case is shown in Figure 3-7 .
Figure 3-7 Administrator use case diagram
3.3.2 User use case diagram
Users can access the homepage, communication forum, adoption information, etc. when entering the system. The user use case is shown in Figure 3-8 .
Figure 3-8 User use case diagram
4 System design
4.1 System Overview
After system analysis, system design begins. System design includes overall design and detailed design. The overall design is just a general design. After the overall design, we can divide some things of the system, such as files, documents, data, etc. And through the overall design, we can roughly divide the modules and functions of the program. But it is only a preliminary classification and has no real implementation.
The overall design is just a preliminary design. Moreover, for a project, we can carry out multiple overall designs. Through comparison, including performance comparison, cost comparison, and benefit comparison, we can finally determine an optimal design plan and choose the best one. The overall design can reduce development costs and increase company benefits. From this point of view, the overall design is still very important.
The working principle diagram of the pet adoption system is shown in Figure 4-1:
Figure 4-1 System working principle diagram
4.2 System structure design
The system architecture diagram belongs to the system design stage. The system architecture diagram is only a product of this stage. The overall architecture of the system determines the model of the entire system and is the foundation of the system. The overall structural design of the pet adoption system is shown in Figure 4-2.
Figure 4-2 System structure diagram
4.3 Database design
Database is the basis of computer information system. At present, the key and core part of the computer system is the database. The quality of database development has a direct impact on the quality and speed of the entire system.
4.3.1 Database design principles
The conceptual structure design of the database adopts the entity-relationship (ER) model design method. The constituent elements of the ER model method are: entities, attributes, and relationships. The ER model is represented by an ER diagram, which reminds the user of things involved in the work environment, and attributes are descriptions of entity characteristics. The database plays a decisive factor in system design. The entity-relationship diagram of these key entities is designed below .
4.3.2 Database entities
Entities in the data model, also called instances, correspond to "events" or "things" that can be distinguished from other objects in the real world. For example, every employee in your company, every piece of furniture in your home.
Figure 4-3 System ER diagram
4.3.3 Database table design
The table information of the database is part of the design. The detailed information of each table in the database is introduced below.
Table access_token (login access duration)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
token_id |
int |
10 |
0 |
N |
Y |
Temporary access badge ID |
|
| 2 |
token |
varchar |
64 |
0 |
Y |
N |
temporary access badge |
|
| 3 |
info |
text |
65535 |
0 |
Y |
N |
||
| 4 |
maxage |
int |
10 |
0 |
N |
N |
2 |
Maximum lifespan: Default 2 hours |
| 5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
user ID: |
Table adoption_information (adoption information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
adoption_information_id |
int |
10 |
0 |
N |
Y |
Adoption information ID |
|
| 2 |
pet_name |
varchar |
64 |
0 |
Y |
N |
pet name |
|
| 3 |
type_of_pet |
varchar |
64 |
0 |
Y |
N |
pet type |
|
| 4 |
pet_color |
varchar |
64 |
0 |
Y |
N |
pet color |
|
| 5 |
pet_sex |
varchar |
64 |
0 |
Y |
N |
pet gender |
|
| 6 |
pet_age |
varchar |
64 |
0 |
Y |
N |
pet age |
|
| 7 |
date_of_adoption |
date |
10 |
0 |
Y |
N |
Adoption date |
|
| 8 |
adoptive_user |
int |
10 |
0 |
Y |
N |
0 |
Adopt a user |
| 9 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table article (article: article for content management system)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
article_id |
mediumint |
8 |
0 |
N |
Y |
Article id: [0,8388607] |
|
| 2 |
title |
varchar |
125 |
0 |
N |
Y |
Title: [0,125] is used in the title tag of articles and html |
|
| 3 |
type |
varchar |
64 |
0 |
N |
N |
0 |
Article classification: [0,1000] is used to search for articles of the specified type |
| 4 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of clicks: [0,1000000000] Number of people who visited this article |
| 5 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 6 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 7 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 8 |
source |
varchar |
255 |
0 |
Y |
N |
Source: [0,255] Source of article |
|
| 9 |
url |
varchar |
255 |
0 |
Y |
N |
Source address: [0,255] used to jump to the website where the article was published |
|
| 10 |
tag |
varchar |
255 |
0 |
Y |
N |
Tag: [0,255] is used to mark the relevant content of the article. Multiple tags are separated by spaces. |
|
| 11 |
content |
longtext |
2147483647 |
0 |
Y |
N |
Text: the main content of the article |
|
| 12 |
img |
varchar |
255 |
0 |
Y |
N |
cover picture |
|
| 13 |
description |
text |
65535 |
0 |
Y |
N |
Article description |
Table article_type (article classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
smallint |
5 |
0 |
N |
Y |
Category ID: [0,10000] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
Display order: [0,1000] determines the order in which categories are displayed. |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
Category name: [2,16] |
|
| 4 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 5 |
description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] describes the role of this classification |
|
| 6 |
icon |
text |
65535 |
0 |
Y |
N |
Category icon: |
|
| 7 |
url |
varchar |
255 |
0 |
Y |
N |
External link address: [0,255] If this category jumps to other websites, set it on the URL |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table auth (user rights management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
auth_id |
int |
10 |
0 |
N |
Y |
Authorization ID: |
|
| 2 |
user_group |
varchar |
64 |
0 |
Y |
N |
user group: |
|
| 3 |
mod_name |
varchar |
64 |
0 |
Y |
N |
Module name: |
|
| 4 |
table_name |
varchar |
64 |
0 |
Y |
N |
Table Name: |
|
| 5 |
page_title |
varchar |
255 |
0 |
Y |
N |
page title: |
|
| 6 |
path |
varchar |
255 |
0 |
Y |
N |
Routing path: |
|
| 7 |
position |
varchar |
32 |
0 |
Y |
N |
Location: |
|
| 8 |
mode |
varchar |
32 |
0 |
N |
N |
_blank |
Jump method: |
| 9 |
add |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to add: |
| 10 |
of the |
tinyint |
3 |
0 |
N |
N |
1 |
Can it be deleted: |
| 11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
Whether it can be modified: |
| 12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to view: |
| 13 |
field_add |
text |
65535 |
0 |
Y |
N |
Add fields: |
|
| 14 |
field_set |
text |
65535 |
0 |
Y |
N |
Modify fields: |
|
| 15 |
field_get |
text |
65535 |
0 |
Y |
N |
Query fields: |
|
| 16 |
table_nav_name |
varchar |
500 |
0 |
Y |
N |
Cross-table navigation name: |
|
| 17 |
table_nav |
varchar |
500 |
0 |
Y |
N |
Cross-table navigation: |
|
| 18 |
option |
text |
65535 |
0 |
Y |
N |
Configuration: |
|
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
collect_id |
int |
10 |
0 |
N |
Y |
Collection ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Collector ID: |
| 3 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 4 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| 6 |
title |
varchar |
255 |
0 |
Y |
N |
title: |
|
| 7 |
img |
varchar |
255 |
0 |
Y |
N |
Cover: |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
comment_id |
int |
10 |
0 |
N |
Y |
Comment ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Commenter ID: |
| 3 |
reply_to_id |
int |
10 |
0 |
N |
N |
0 |
Reply comment ID: empty is 0 |
| 4 |
content |
longtext |
2147483647 |
0 |
Y |
N |
content: |
|
| 5 |
nickname |
varchar |
255 |
0 |
Y |
N |
Nick name: |
|
| 6 |
avatar |
varchar |
255 |
0 |
Y |
N |
Avatar address: [0,255] |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 9 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 10 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 11 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
forum_id |
mediumint |
8 |
0 |
N |
Y |
Forum id |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
sort |
| 3 |
user_id |
mediumint |
8 |
0 |
N |
N |
0 |
User ID |
| 4 |
nickname |
varchar |
16 |
0 |
Y |
N |
Nickname: [0,16] |
|
| 5 |
praise_len |
int |
10 |
0 |
Y |
N |
0 |
Number of likes |
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of visits |
| 7 |
title |
varchar |
125 |
0 |
N |
N |
title |
|
| 8 |
keywords |
varchar |
125 |
0 |
Y |
N |
Key words |
|
| 9 |
description |
varchar |
255 |
0 |
Y |
N |
describe |
|
| 10 |
url |
varchar |
255 |
0 |
Y |
N |
Source address |
|
| 11 |
tag |
varchar |
255 |
0 |
Y |
N |
Label |
|
| 12 |
img |
text |
65535 |
0 |
Y |
N |
cover picture |
|
| 13 |
content |
longtext |
2147483647 |
0 |
Y |
N |
text |
|
| 14 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 16 |
avatar |
varchar |
255 |
0 |
Y |
N |
Poster's avatar: |
|
| 17 |
type |
varchar |
64 |
0 |
N |
N |
0 |
Forum classification: [0,1000] is used to search for forum posts of specified types |
Table forum_type (forum classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
smallint |
5 |
0 |
N |
Y |
Category ID: [0,10000] |
|
| 2 |
name |
varchar |
16 |
0 |
N |
N |
Category name: [2,16] |
|
| 3 |
description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] describes the role of this classification |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
External link address: [0,255] If this category jumps to other websites, set it on the URL |
|
| 5 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 6 |
icon |
varchar |
255 |
0 |
Y |
N |
Category icon: |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
hits_id |
int |
10 |
0 |
N |
Y |
Like ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Liked by: |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
notice_id |
mediumint |
8 |
0 |
N |
Y |
Announcement id: |
|
| 2 |
title |
varchar |
125 |
0 |
N |
N |
title: |
|
| 3 |
content |
longtext |
2147483647 |
0 |
Y |
N |
text: |
|
| 4 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table ordinary_users (ordinary users)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
ordinary_users_id |
int |
10 |
0 |
N |
Y |
Common user ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 3 |
user_gender |
varchar |
64 |
0 |
Y |
N |
User gender |
|
| 4 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 5 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 6 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table pet_information (pet information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
pet_information_id |
int |
10 |
0 |
N |
Y |
Pet information ID |
|
| 2 |
pet_name |
varchar |
64 |
0 |
Y |
N |
pet name |
|
| 3 |
type_of_pet |
varchar |
64 |
0 |
Y |
N |
pet type |
|
| 4 |
pet_color |
varchar |
64 |
0 |
Y |
N |
pet color |
|
| 5 |
pet_sex |
varchar |
64 |
0 |
Y |
N |
pet gender |
|
| 6 |
pet_age |
varchar |
64 |
0 |
Y |
N |
pet age |
|
| 7 |
pet_pictures |
varchar |
255 |
0 |
Y |
N |
pet pictures |
|
| 8 |
adoption_status |
varchar |
64 |
0 |
Y |
N |
adoption status |
|
| 9 |
introduction_to_pets |
text |
65535 |
0 |
Y |
N |
Pet introduction |
|
| 10 |
hits |
int |
10 |
0 |
N |
N |
0 |
Clicks |
| 11 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
praise_id |
int |
10 |
0 |
N |
Y |
Like ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Liked by: |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| 8 |
status |
bit |
1 |
0 |
N |
N |
1 |
Like status: 1 is like, 0 is canceled |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
slides_id |
int |
10 |
0 |
N |
Y |
Carousel image ID: |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
title: |
|
| 3 |
content |
varchar |
255 |
0 |
Y |
N |
content: |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
Link: |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
Carousel image: |
|
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of clicks: |
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_of_pet_id |
int |
10 |
0 |
N |
Y |
Pet type ID |
|
| 2 |
type_of_pet |
varchar |
64 |
0 |
Y |
N |
pet type |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
upload_id |
int |
10 |
0 |
N |
Y |
Upload ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
file name |
|
| 3 |
path |
varchar |
255 |
0 |
Y |
N |
access path |
|
| 4 |
file |
varchar |
255 |
0 |
Y |
N |
file path |
|
| 5 |
display |
varchar |
255 |
0 |
Y |
N |
display order |
|
| 6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
Parent ID |
| 7 |
dir |
varchar |
255 |
0 |
Y |
N |
folder |
|
| 8 |
type |
varchar |
32 |
0 |
Y |
N |
file type |
Table user (user account: used to save user login information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
user_id |
mediumint |
8 |
0 |
N |
Y |
User ID: [0,8388607] User obtains other user-related data |
|
| 2 |
state |
smallint |
5 |
0 |
N |
N |
1 |
Account status: [0,10](1 available | 2 abnormal | 3 frozen | 4 logged out) |
| 3 |
user_group |
varchar |
32 |
0 |
Y |
N |
User group: [0,32767] determines user identity and permissions |
|
| 4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Last Login Time: |
| 5 |
phone |
varchar |
11 |
0 |
Y |
N |
Mobile phone number: [0,11] User’s mobile phone number, used to retrieve password or log in |
|
| 6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
Mobile phone certification: [0,1] (0 not certified | 1 under review | 2 certified) |
| 7 |
username |
varchar |
16 |
0 |
N |
N |
Username: [0,16] The account name used by the user to log in |
|
| 8 |
nickname |
varchar |
16 |
0 |
Y |
N |
Nickname: [0,16] |
|
| 9 |
password |
varchar |
64 |
0 |
N |
N |
Password: [0,32] The password required for user login, consisting of 6-16 digits or English |
|
| 10 |
|
varchar |
64 |
0 |
Y |
N |
Email: [0,64] User's email, used to retrieve password or log in |
|
| 11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
Email certification: [0,1] (0 not certified | 1 under review | 2 certified) |
| 12 |
avatar |
varchar |
255 |
0 |
Y |
N |
Avatar address: [0,255] |
|
| 13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
Table user_group (user group: used for user front-end identity and authentication)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
User group ID: [0,8388607] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
Display order: [0,1000] |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
Name: [0,16] |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] Describes the characteristics or scope of permissions of this user group |
|
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| 8 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
Registration location: |
| 9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
5.1 Front page function module
In the pet adoption system , you can view the website homepage, communication forums, notifications and announcements, news information, pet information and other contents on the system homepage, as shown in Figure 5-1.
Figure 5-1 Functional interface diagram of the front desk homepage
The communication forum information page is shown in Figure 5-2.
Figure 5-2 Communication forum page interface diagram
The pet display page is shown in Figure 5-3.
Figure 5-3 Pet display page interface diagram
The news information list is shown in Figure 5-4.
Figure 5-4 News information information list interface diagram
5.2 Administrator function module
管理员登录，通过填写注册时输入的用户名、密码权限进行登录，如图5-5所示。
图5-5管理员登录界面图
管理员登录进入宠物领养系统可以查看个系统后台首页、轮播图、通知公告、资源管理（新闻资讯、新闻分类）交流管理（交流论坛、论坛分类）系统用户（管理员、系统用户）模块管理（宠物类型、宠物信息、领养信息）个人管理等信息。如图-5-6所示：
图5-6管理员功能界面图
系统用户管理，在系统用户管理页面中可以对管理员用户密码修改功能，如图5-7所示：
图5-7系统用户界面图
宠物类型管理，在宠物类型管理页面中可以查看宠物类型、创建时间、更新时间等信息，并可根据需要在宠物查询页面对已有的宠物类型进行编辑删除或详细等操作，如图5-8所示。
图5-8宠物类型管理界面图
5.3用户功能模块
用户登录进入宠物领养系统可以填写个人信息进行用户注册等内容。如图5-9。
图5-9用户注册界面图
用户后台功能界面图，功能为：首页、个人中心、领养申请。如图5-10。
图5-10用户后台功能界面图
领养信息，在领养信息页面可以查看宠物名称、宠物类型、宠物颜色、宠物性别、宠物年龄、领养日期、领养用户等信息进行详细操作。如图5-11。
图5-11领养信息界面图
6系统测试
系统开发的最后一个步骤就是系统测试，系统测试也是整个系统十分重要的一个环节，测试的好坏关系到产品的发展。用户对软件的质量、性能和可靠性等需求就要通过测试来实现。测试过程要必须遵循严谨性、完善性、规范性的原则，测试的主要目的就是看看在系统运行中，是否会出现bug，然后对出现的bug进行调试，直到程序完美运行。但是软件的测试只能尽可能的减少bug，理论上来说是无法达到消除bug。但是bug越少，系统出错的几率就越低，用户使用起来也更方便、更安全。
近年来，软件包含测试从现在的检验当中来看，系统接近预期目标可能出现的问题，并对这些错误做出相应的修正，假如我们不进行早期的测试错误就会延续下去，最后所做出的成品就会有很大的困难。
我们要在这个测试的过程当中找出错误。测试成软件开发的主要一部分，自从有了程序的设计那天开始，它就成为了重要的组成部分。经过统计来看，软件测试可以占据这个系统45%的工作量，而在软件开发的成本当中，对于测试成本来说它包含了很多的测试工作。每个程序测试时都会出现和遇到错误。在整个程序的开发过程当中，人为去查找错误是非常复杂和困难的，所以我们一般都会找一些测试的工具来进行测试。
6.1系统测试的意义
随着现代信息的快速发展，在社会各大领域中已经都开始应用网络信息技术，在应用网络技术的同时人们也开始把软件的质量问题作为了一个重要焦点来关注，因为一个软件的好与坏它决定着这个系统在市场上的生存，所以我们必须要把软件质量来做好，这样才有一定的生存能力。对于用户来说它们首先选用的都是保证这个系统软件的质量问题，因为一个系统的软件质量决定着用户在后期上成本经济的问题。图6-1就是纠错测试流程。
图6-1 测试与纠错信息流程
6.2 测试方法
黑盒测试又被人们称作为功能测试，通常是在程序的接口来做一些测试的方法，它一般包括对程序的功能和使用的方法来做出一些数据的接受和输出，同时还可以做出正确的输出信息，并保证与外部信息的完整性。
白盒测试通常被人们称作为结构测试，在整个程序的结构和处理当中它是由程序当中的逻辑测试和检验程序来完成一些正确的工作。
具体的功能测试它是包括：系统的适用性、准确性、安全性等功能测试。
6.3测试分析
本宠物领养系统满足相关信息的管理需求，在设计时借鉴了国内外优秀网站的优点，从界面到系统设计都保证了管理员以及用户能够方便操作。系统的主要特点和优点归纳如下：
（1）本系统用的移置性和针对性都比较高，因为针对性高可以提供更好的服务而移置性可以在多个系统上运行，更给用户带来了极大的方便。
（2）该宠物领养系统内容全面，管理方便可以及时的全面的处理各种错误，异常，这样避免了很多因用户的马虎操作而出现的失误，其操作方便，用户界面友好，能够上网的人都可以很好的进行操作。
经过对上述的测试结果分析，所有基本功能齐全，操作简单，系统运行性能良好，系统安全可靠，能促进宠物领养系统平台的发展，发展前景广阔。
结 论
本系统通过对java和Mysql数据库的简介，从硬件和软件两反面说明了宠物领养系统的可行性，本文结论及研究成果如下：实现了java与Mysql相结合构建的宠物领养系统，网站可以响应式展示。通过本次宠物领养系统的研究与实现，我感到学海无涯，学习是没有终点的，而且实践出真知，只有多动手才能尽快掌握它，经验对系统的开发非常重要，经验不足，就难免会有许多考虑不周之处。比如要有美观的界面，更完善的功能，才能吸引更多的用户。
由于在此之前对于java知识没有深入了解，所以从一开始就碰到许多困难，例如一开始的页面显示不规范、数据库连接有问题已经无法实现参数的传递等等，不过通过在网上寻找有关资料以及同学的帮助下最后都得到了解决，在此过程中，我不仅学到了很多知识，也提高了自己解决问题的能力，尤其是学会如何从大量的信息中筛选出所需有用的信息，同时我更加深刻的体会到了，虽然书本上的大部分知识都是有价值，正确的，但实际上每个人编程的思路和对数据处理的方法、思想都是不同的，这就要求我们一定要通过实践才能找到解决问题的方案。在此次毕业设计活动中，我不断的提高了自己，也得到了宝贵的经验，我相信这些对我以后的发展都会有很大帮助。
通过这次宠物领养系统的开发，我参考了很多相关系统的例子，取长补短，吸取了其他系统的长处，逐步对该系统进行了完善，但是该系统还是有很多的不足之处，有待以后进一步学习。
实践证明，宠物领养系统有着非常好的发展前景，经过测试运行，系统各项功能都十分完善，界面漂亮，使用方便，操作容易，在技术理论上已经成熟。
致 谢
大学的学习生活在这个季节将结束，但是在我的生命这仅仅只是一个逗号，我将面对另一个新的环境开始。通过这次毕业设计的整个开发过程，从需求分析到具体功能实现，再到最终测试和维护的理解有了很大的进步，让我对系统开发有了更深刻的认识，对我个人的实践能力和解决问题的能力，都有了很大的帮助。这是这次毕业设计最大的收获。
首先要感谢我的指导老师，他在论文写作上，给予了我各种无私的帮助，治学严谨，严格要求，使我获得了很大的收获。老师深厚的理论知识和丰富的实践经验，都深深的影响到我，在这方面，我谨表示衷心的感谢。
其次，我还要对所有的老师和同学表示感谢，他们在我学习的过程中，都积极的提供了很多帮助，无论是专业知识，还是实践操作技能，也能够让我在论文写作中，遇到的一些难题迎刃而解。
最后，对阅读和评审本论文的各位老师表示衷心的感谢!
参考文献
[1]Pratap Singh Surya,Singh Jagbir,Pal Anuj. Application on Soil Bearing Capacity by Using SPT Values[J]. IOP Conference Series: Earth and Environmental Science,2023,1110(1).
[2]Maruti Endang Sri,Yulianto Bambang,Suhartono Suhartono,Yohanes Budinuryanta,Cahyono Bambang Eko Hari. Scale development as a measuring tool of critical Javanese language’ awareness for pre-service Javanese teachers[J]. Cogent Arts & Humanities,2022,9(1).
[3]杜瑞庆,李一诺.基于Java语言的即时通讯系统设计与实现[J].电脑知识与技术,2022,18(31):29-32.DOI:10.14004/j.cnki.ckt.2022.2043.
[4]李乐.Java语言应用研究[J].智慧中国,2022(09):80-81.
[5]朱志慧,蔡洁.基于SpringBoot+Vue+Uni-app框架的校园失物招领系统[J].电子技术与软件工程,2022(17):62-65.
[6]贺斌.计算机软件开发中JAVA语言的应用研究[J].中国设备工程,2022(11):247-249.
[7]陈新府豪. 基于SpringBoot和Vue框架的创新方法推理系统的设计与实现[D].浙江理工大学,2022.DOI:10.27786/d.cnki.gzjlg.2022.000649.
[8]杨迎.Java语言异常处理机制的分析[J].电子技术,2022,51(03):42-43.
[9]镇鑫羽,景琴琴.Java语言程序设计的教学实践[J].集成电路应用,2022,39(02):256-257.DOI:10.19339/j.issn.1674-2583.2022.02.111.
[10]熊柏祥.基于Springboot和Vue框架的考试资源服务平台的设计与实现[J].信息与电脑(理论版),2022,34(01):97-99+103.
[11]许亦卿.一种云领养宠物创业模式[J].合作经济与科技,2022(01):116-118.DOI:10.13665/j.cnki.hzjjykj.2022.01.045.
[12]陈玥.基于Java语言开发的宿舍管理系统[J].信息与电脑(理论版),2021,33(21):38-40.
[13]吴迪.Java编程语言在计算机软件开发中的应用[J].信息与电脑(理论版),2021,33(20):29-31.
[14]单树倩,任佳勋.基于SpringBoot和Vue框架的数据库原理网站设计与实现[J].电脑知识与技术,2021,17(30):40-41+50.DOI:10.14004/j.cnki.ckt.2021.2868.
[15]喻佳,吴丹新.基于SpringBoot的Web快速开发框架[J].电脑编程技巧与维护,2021(09):31-33.DOI:10.16184/j.cnki.comprg.2021.09.013.
[16]徐小辉,刘江涛,高涵,丁艳艳.基于SpringBoot+Vue框架的采气方案系统开发[J].计算机仿真,2021,38(06):248-250+382.
[17]张恒铭.基于SpringBoot+MyBatis框架的高校人事信息发布系统设计与实现[J].电脑知识与技术,2020,16(18):68-70.DOI:10.14004/j.cnki.ckt.2020.1865.
[18] Xiong Yongping. Analysis and research on application development technology based on SpringBoot framework [J]. Computer Knowledge and Technology, 2019, 15(36): 76-77. DOI: 10.14004/j.cnki.ckt.2019.4290.
[19] Zhu Yunqiao. Construction and implementation of Web application system based on SpringBoot+SSM framework [J]. Computer Programming Skills and Maintenance, 2019(10):23-25.DOI:10.16184/j.cnki.comprg.2019.10.008.
[20] Lu Yuchen. Discussion of SpringBoot framework in web application development [J]. Science and Technology Innovation Herald, 2018, 15(08): 168+173.DOI: 10.16660/j.cnki.1674-098X.2018.08.168.
To get the project source code for free, please follow ❥ Like, collect and send a private message to the blogger, thank you~