Summary
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 to overcome with technology. subject. In view of issues such as the animal adoption and rescue system, the animal adoption and rescue system is researched and analyzed, and then an animal adoption and rescue system is developed and designed to solve the problem.
The main functional modules of the animal adoption and rescue system include animal information, animal species, urban classification, adoption application, hospital information, about us, my pets and other functions. It adopts an object-oriented development model for software development and hardware installation. It can well meet the needs of actual use, and has improved the corresponding software construction and program coding work. It adopts MySQL as the main storage unit of background data, uses the django framework python language to code and develop the business system, and realizes 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. Analyze the various needs and technical issues of the animal adoption and rescue system, prove the necessity and technical feasibility of the system, and then give a basic introduction to the technical software and design ideas that need to be used to design the system, and finally implement animal adoption and rescue System and deployment operations use it.
Keywords: python development language; django framework technology; animal adoption and rescue system;
Abstract
In the information society, there is a need for targeted access to information, but the expansion of the access is basically the direction of people's efforts. Because of the deviation in the perspective, people can often obtain different types of information, which is also the most difficult subject for technology to overcome. Aiming at the problems of the animal adoption and rescue system, this paper studies and analyzes the animal adoption and rescue system, and then develops and designs the animal adoption and rescue system to solve the problems.
The main functional modules of the animal adoption and rescue system include animal information, animal species, urban classification, adoption application, hospital information, about us and my pet, and other functions. The object-oriented development model is adopted for software development and hardware installation, which can well meet the needs of actual use, improve the corresponding software installation and program coding, and take MySQL as the main storage unit of background data, Using the django framework python language to code and develop the business system, all the functions of the system are realized. This report first analyzes the background, role and significance of the research, laying a foundation for the rationality of the research work. This paper analyzes the various requirements and technical problems of the animal adoption and rescue system, proves the necessity and technical feasibility of the system, and then makes a basic introduction to the technical software and design ideas needed to design the system, and finally realizes the animal adoption and rescue system and deploys and runs it.
Key words:Python development language; Django framework technology; Animal adoption and rescue system;
Table of contents
Chapter 2 Introduction to Related Technologies
2.2 Introduction to django framework
3.2 System functional requirements
3.3 System performance requirements
Chapter 5 System Implementation
5.1 Implementation of login module
5.2 Implementation of user modules
5.2.1 Implementation of registration module
5.2.2 Implementation of password modification module
5.2.3 Implementation of communication community module
5.2.4 Implementation of animal information module
5.2. Implementation of 5 comment module
5.3 Implementation of background module
5.3.1 Implementation of user management module
5.3.2 Implementation of animal information management module
5.3.3 Implementation of animal species management module
5.3.4 Implementation of adoption application management module
Chapter 1 Introduction
1.1 Research purpose
With the continuous development of the domestic economy, the improvement of people's income levels and the increasing emotional needs, pet keeping has become a popular trend. The increase in pets has inevitably led to the proliferation of stray pets, most of which come from animals abandoned by their owners or the offspring of these animals. They are not controlled and wander around the edges of human settlements, causing considerable trouble to people's lives. Nowadays, there are also stray animal rescue stations organized by caring people to adopt some stray dogs. However, sometimes the rescue stations have too many pets and it is difficult to cope with them, so that many pets can only be "euthanized". In order to solve the current problem of stray pets, the traditional inefficient offline registration and adoption is gradually being replaced, followed by a pet adoption and rescue system that can be browsed and accessed using terminal devices.
1.2 Research background
By designing a pet adoption and rescue system based on the Django framework, the efficiency has been greatly improved compared to the traditional offline registration form. First, administrators can intuitively manage existing stray pet information, avoiding missing information in the traditional model; secondly, it provides a convenient adoption and rescue platform for users who need to adopt pets. The pet adoption and rescue system uses a B/S architecture, because the client (computer) is only used as a browser, so maintenance personnel only need good server maintenance. No increase in business intensity regardless of customer size. Using the B/S structure will greatly reduce unnecessary manpower and material resources, thereby improving work efficiency.
Chapter 2 Introduction to Related Technologies
2.1 B/S architecture
B/S architecture (browser/server) is currently the most widely used architecture, which can make system development, operation, and maintenance easy. You can use this structure when you have a database installed on your computer and a few very common browsers. The B/S structure can be directly used in the B/S system, and the B/S structure can greatly reduce the operation and maintenance of the system in practical applications. On the B/S platform, each database is independent of each other and has high security. Because the B/S architecture can clearly observe the business handled by the system, managers can make timely decisions, thereby avoiding corporate losses. The essential feature of the B/S architecture is centralized management. Users store the data generated by the system into the database to facilitate future applications, thereby meeting various needs.
The B/S model consists of three levels: a browser, a network server, and a database server. Data management adopts the presentation layer, application layer and data layer of most existing B/S systems. The Web browser is designed to meet user requirements and is an intermediate application layer used in data processing and logic processes, thus Form a distributed operating model. The logic of the B/S architecture is that the processing completed on the front end leaves the main business logic to the backend, while the front end is only responsible for a small number of requests, rendering, etc. Due to the rapid development of Internet technology, the B/S architecture makes the system accessible at any time and anywhere.
Figure 2-1 Three-layer structure diagram of B/S mode
2.2 Introduction to django framework
Django is an open source model driven by the high-level Python programming language. View, a controller-style web application framework, originated from the open source community. Using this architecture, programmers can easily and quickly create high-quality, easy-to-maintain, database-driven applications. This is the main reason why OpenStack's Horizon component is designed using this architecture. In addition, the Dj ango framework also contains many powerful third-party plug-ins, making Django highly scalable. The Django project originated from an online news Web site and was released as open source in 2005. The core components of the Django framework are:
Object-relational mapping used to create models ;
Design a better management interface for end users;
URL design;
Designer-friendly template language;
Caching system.
Django (pronounced: [`dʒæŋɡəʊ]) is an open source web development framework (open source web framework) written in python language. It encourages rapid development and follows MVC design. Django abides by BSD copyright, was first released in July 2005, and released the first official version 1.0 in September 2008.
Django is named after the Belgian jazz musician Django Reinhardt . He is a gypsy who mainly plays guitar and also plays violin.
Due to the rapid development of Django in recent years, its applications have become more and more widespread. It was selected as the 2013 SD Times 100 by the famous IT development magazine SD Times, ranking 6th in the "API, Library and Framework" category, and is considered the leader in this field. By.
2.3 MySQL database
Microsoft MySQL is a relational database management system that spans laptops, desktops, and enterprise servers. In the 20th century, the original MySQL was developed by Sybase specifically for UNIX systems, and later Microsoft ported it to Windows NT systems. Starting in 1994, Microsoft released a version of MySQL developed independently from Sybase, and Sybase stopped using the name MySQL in the late 1990s.
MySQL provides replication services between multiple copies of MySQL and other database systems. The analysis service is an integral part of the system, including: online analytical processing (OLAP) and data mining tools. MySQL provides a large graphical toolset and wizards to guide database administrators in performing tasks such as setting up regular backups, copying data between servers, and tuning database performance.
Chapter 3 System Analysis
3.1 Feasibility analysis
Feasibility analysis is also to analyze whether the project's development system is valuable for development, and whether it is really necessary to improve the management system's shortcomings in information dictation. Taking the design goals and implementation process of the animal adoption and rescue system of this project as an example, if this system is developed, it is hoped that the user's management information problem can be solved well, and if this enables the animal adoption and rescue system to develop the theory of maximum value, and also It can solve users' problems to a certain extent in disguised form, so the research and development system of this project is the most valuable and meaningful system. But have the R&D goals achieved the desired results, and whether the scientific research tasks have the greatest utility and value after they are realized, and whether they are equal to all total costs. Therefore, the R&D stage is essentially the stage where the R&D system can be truly designed.
3.1.1 Technical feasibility
Technical feasibility means that the identified science and technology or the science and technology in decision-making methods do not break through the boundaries of the scientific and technological resources mastered by the organization or familiar to relevant personnel. In the process of technology research, attention should be paid to comprehensively investigating various key technical issues included in the system development process, selecting mature technologies as much as possible, carefully citing advanced technologies, paying attention to specific research platforms and developers, and evaluating the effectiveness of key technologies.
Python technology is key to the design and implementation of this animal adoption and rescue system. Based on B/S architecture and MySQL database management, it is crucial for front-end applications and back-end database management. In order to effectively apply this program , it is necessary to maintain the characteristics of comprehensive functions, easy to understand and simple to use. When building database management, it is necessary to ensure that the data analysis information is complete, the data analysis information is stable, and the data analysis information is highly stable. In the early days, people had understanding and familiarity with the basic important knowledge points of python, and had a brief mastery and familiarity with the MySQL database. In the early days, people had a general mastery and practice of basic courses such as software engineering testing and UML language. After By practicing the above courses, you will be able to develop, test and judge the corresponding information systems for the above courses.
Python can be combined with MySQL to develop an animal adoption and rescue system, which must be reasonable and effective.
3.1.2 Economic feasibility
The feasibility of implementing the national economy mainly includes two aspects: first, the potential possibility of obtaining and utilizing various resources of the national economy from a certain plan to be implemented; second, the potential possibility of achieving the overall goal of the national economic development policy; second, the potential possibility of achieving the overall goal of the national economic development policy; It refers to the economic costs and benefits obtained in order to complete a certain national economic development policy implementation plan. Since the government's financial resources are limited, each financial resource obtained and utilized from the national economic development policy implementation plan is also limited. Therefore, every public policy measure faces a competition for public financial capital. But in general, "the occupation of social and economic resources of public policy measures is directly proportional to the expected value of its policy measure goals." Of course, this also touches on a cost-efficiency question. If the total cost of a certain method is equal to the profit, it is obvious that this socioeconomic policy measure is ineffective.
The original intention of developing this project was to save money. I did it by myself and basically did not need start-up capital. In addition, the entire process of project development is a self-study process, which is a win-win result. Therefore, in summary, the R&D advantages of this project outweigh the disadvantages, which is in line with the actual development of my country's current socialist market economy.
3.1.3 Operational feasibility
The registration and login page of the animal adoption and rescue system is designed to be simple and easy to use. You can log in to the page through the most common page window, and use a computer to implement the login function. Therefore, users can log in to the application as long as they usually use a computer. The R&D work environment of this operating system uses python technology and the B/S structure. These R&D work environments make the system functions more complete, the entire design more personalized, and the user functions more concise and convenient. This management system has the advantages of easy operation, easy management, good interactivity, and is also very simple in actual operation. Therefore, this management system can also be designed commercially.
To sum up, the research and development of this equipment meets the technical, process and technical requirements, so its research and development is operable.
3.2 System functional requirements
The user information use case diagram is shown below.
Figure 3-1 User information use case diagram
The administrator use case diagram is shown below.
Figure 3-2 Administrator use case diagram
Table 3-1 Information browsing use case description
| Description item |
illustrate |
| Use case name |
Information inquiry |
| Use case description |
Users can view information details |
| participants |
user |
| Preconditions |
The user is an ordinary user type and successfully entered the system |
| postcondition |
Browse successfully |
| main event flow |
(1) Users can browse information modules and information content (2) Users can click on the information to read the information in detail |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
Table 3-1 Communication community use case description
| Description item |
illustrate |
| Use case name |
communication community |
| Use case description |
Users can post what they want to say on the communication board, other users can view it, and registered users can reply. |
| participants |
user |
| Preconditions |
The user is a registered user and successfully entered the system |
| postcondition |
The communication was added successfully and displayed on the communication board |
| main event flow |
The system checks whether it is a normal user Unregistered users can view the content of the communication board The communication form of registered users is displayed and they can communicate and reply to other people's communication. |
| Exception event flow |
e1. Report 500 error e2. Database connection exception e3. The communication content is not displayed |
Table 3-1 Posting use case description
| Description item |
illustrate |
| Use case name |
post |
| Use case description |
Under the condition of successful login, users can publish posts |
| participants |
user |
| Preconditions |
The user logs in successfully and enters the system |
| postcondition |
Posted successfully |
| main event flow |
(1) The system checks whether it is an ordinary user type The user enters the title, description, type, image URL and content to start executing the publishing use case (3) Publish successfully, enter the system homepage |
| Exception event flow |
e1. Report 500 error e2. Database connection exception e3. The data content is too long |
Table 3-1 Personal information management use case description
| Use case name |
Manage and modify personal information |
| participants |
user |
| describe |
Users view and modify personal information |
| Preconditions |
The user is logged into the system |
| postcondition |
none |
| event stream |
(1) Users view personal information (2) Users modify personal information |
| Additional information |
(a) Users can change passwords (b) Users can modify personal information, such as name, avatar, etc. |
Table 3-1 Comment use case description
| Use case name |
Comment |
| participants |
user |
| describe |
User comments |
| Preconditions |
User is logged in |
| postcondition |
The content of the comments does not violate the rules |
| event stream |
(1) Enter the comment data on the comment page and submit the comment (2) Update and display the comment board |
| Additional information |
(a) Comment content cannot be empty |
Table 3-1 Collection use case description
| Use case name |
collect |
| participants |
user |
| describe |
User adds content to favorites |
| Preconditions |
User is logged in |
| postcondition |
none |
| event stream |
(1) Add to favorites on the favorites page (2) Update and display favorites |
| Additional information |
none |
Table 3-1 User management use case description
| Description item |
illustrate |
| Use case name |
User action |
| Use case description |
The administrator can manage users under the condition that the administrator correctly logs in to the background management. |
| participants |
administrator |
| Preconditions |
The administrator logs in successfully and jumps to the main background interface. |
| postcondition |
Successful operation |
| main event flow |
The administrator jumps to the user management page to query user details. Administrators can delete user information |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
Table 3-1 Animal information management use case description
| Description item |
illustrate |
| Use case name |
animal information operations |
| Use case description |
The administrator can manage the animal information module under the condition that the administrator correctly logs in to the background management. |
| participants |
administrator |
| Preconditions |
Administrator successfully logged in |
| postcondition |
Successful operation |
| main event flow |
(1) The administrator enters the animal information management page and queries the animal information. (2) Administrators can add, delete and edit animal information. (3) The administrator adds animal information and jumps to the query page if the addition is successful. |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
The hospital information use case description is shown in the following table.
Table 3-1 Hospital information management use case description
| Description item |
illustrate |
| Use case name |
Hospital information operations |
| Use case description |
The administrator can manage the hospital information module under the condition that the administrator correctly logs in to the background management. |
| participants |
administrator |
| Preconditions |
Administrator successfully logged in |
| postcondition |
Successful operation |
| main event flow |
(1) The administrator enters the hospital information management page and queries the hospital information. (2) Administrators can add, delete and edit hospital information. (3) The administrator adds hospital information and jumps to the query page if the addition is successful. |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
Table 3-1 Mall management use case description
| Description item |
illustrate |
| Use case name |
Mall operation |
| Use case description |
Under the premise that the administrator correctly logs in to the backend management, the mall module can be managed. |
| participants |
administrator |
| Preconditions |
Administrator successfully logged in |
| postcondition |
Successful operation |
| main event flow |
(1) The administrator enters the mall management page and queries the mall information. (2) The administrator can add, delete and edit the mall. (3) The administrator adds a new mall and jumps to the query page if the addition is successful. |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
Table 3-1 Information management use case description
| Description item |
illustrate |
| Use case name |
information operations |
| Use case description |
Under the premise that the administrator correctly logs in to the background management, the information module can be managed. |
| participants |
administrator |
| Preconditions |
Administrator successfully logged in |
| postcondition |
Successful operation |
| main event flow |
(1) The administrator enters the information management page to query information about the information content. (2) Administrators can delete information |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
Table 3-1 Communication management use case description
| Description item |
illustrate |
| Use case name |
communication operations |
| Use case description |
Under the condition that the administrator correctly logs in to the background management, the communication module can be managed. |
| participants |
administrator |
| Preconditions |
Administrator successfully logged in |
| postcondition |
Successful operation |
| main event flow |
(1) The administrator enters the communication interface and queries the communication content information (2) Administrators can delete communications |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
Table 3-1 Comment management use case description
| Description item |
illustrate |
| Use case name |
Comment operation |
| Use case description |
Under the condition that the administrator correctly logs in to the background management, the comment module can be managed. |
| participants |
administrator |
| Preconditions |
Administrator successfully logged in |
| postcondition |
Successful operation |
| main event flow |
(1) The administrator enters the comment management page and queries the information about the comment content. (2) Administrators can delete data from user comments |
| Exception event flow |
e1. Report 500 error e2. Database connection exception |
Table 3-1 File upload use case description
| Use case name |
File Upload |
| participants |
user |
| describe |
User uploads files to server |
| Preconditions |
User is logged in |
| postcondition |
none |
| event stream |
Click the "Upload" button on the file upload page |
| Additional information |
none |
3.3 System performance requirements
First, friendly interface. In the development and design of animal adoption and rescue systems, the friendliness of the interface is more important. Only by meeting this requirement can it reflect the humanized design characteristics and adapt to the convenience of the user's application system. The dynamic human-computer interaction design allows users to feel when using the system. Convenience of operation and improved user experience can help fully bring out the value of system mining design.
第二，稳定性要求。开发设计的动物领养救助系统，需要保持其稳定，系统应用稳定才能有助于各项管理工作高效率完成，提升系统使用体验度。系统运行保障因外部异常造成系统崩溃，系统发生问题后数据能及时备份，第一时间恢复数据信息，保障系统良好运行。
第三，可扩展性。动物领养救助系统的开发设计，需要满足可扩展性的要求，系统的设计需要考虑未来系统业务扩展问题，在测试不断应用下，功能需求会不断扩展，通过良好扩展性作用发挥，满足多样化的需要。
第四，满足需求。为能有效加强对大用户的需求，在开发动物领养救助系统的过程中，要能和实际应用的需求紧密对接，保障系统的实用性。系统开发要能有前瞻性，由于管理系统建设是长期工程，不同阶段需要有先导发展蓝图以及行动纲领为指导。预见性地考虑教材订购信息管理的重要问题。系统的开发要能满足灵活性应用的需要，将系统的价值充分发挥出来。
第4章 系统设计
4.1 总体目标
动物领养救助系统主要服务于动物的领养救助系统管理，利用网络改变宠物领养模式，简化动物领养救助系统管理流程，减轻传统动物领养救助系统管理带来的工作负担和降低大量资源的消耗。本系统达到的目标主要有以下几点：
（1）通过简单的页面设计和便捷的功能操作，保证系统的简单性和实用性，形成良好的用户体验。
（2）本系统主要针对动物领养救助系统需求进行设计开发，突出较强的针对性。
（3）能够具有一定的安全机制，保证用户信息的安全性。
4.2 总体结构设计
层次框图是一系列由多层矩形框架组成的树，其顶部为矩形框架，表示整个数据结构，下方的长方形立方体表示独立的数据，下方的长方形表示该数据的实际数据（不能进行分割）。由于这个架构的精炼，层级方块图描述的资料结构也愈加详尽，这个模型很好地满足了需求分析的要求。首先对最上层的信息进行分类，然后在图表中的每个路径上重复地进行优化，直至完整的数据结构被确定。
这个系统由二个模块组成，一个是管理员，另一个是用户信息，这二个部分看起来是独立的，实际上却是连接着数据库，每个模块都有自己的权限，唯一不同的，就是访问的方式不同。在调研资料的基础上，完成了各个模块的功能。在对上述功能进行分析的基础上，本系统提出了二个主要的模块，每个单元可划分为若干小单元。
系统的功能结构图如下图所示。
图4-2 系统功能结构图
4.3 功能模块设计
1.登录模块：
本动物领养救助系统的用户登录涉及到三类信息的判断：第一类是用户名和密码是否为空；第二类是验证码是否录入和正确；第三类就是用户登录信息、验证码和权限是否匹配通过。在该用户登录流程对会对用户名和密码是否为空进行判断，以及验证码是否正确进行判断，只有以上的几类信息中的一种存在问题的情况下都是无法登录成功的。
2.公告管理模块：
本动物领养救助系统中的公告管理，管理方式都是对信息的三种基本操作：一种是完成公告信息的添加，在这里会对公告信息的录入情况来判断；一种是对公告信息的修改，另一种就是对公告信息的删除。其后两种操作都是要建立在第一种操作而生成的公告列表的基础上完成的。
3.商城模块
本动物领养救助系统中的商城管理，管理方式都是对信息的三种基本操作：一种是完成商城信息的添加，在这里会对商城信息的录入情况来判断；一种是对商城信息的修改，另一种就是对商城信息的删除。其后两种操作都是要建立在第一种操作而生成的商城的基础上完成的。
4.医院信息模块
本动物领养救助系统中的医院信息管理，管理方式都是对信息的三种基本操作：一种是完成医院信息信息的添加，在这里会对医院信息信息的录入情况来判断；一种是对医院信息信息的修改，另一种就是对医院信息信息的删除。其后两种操作都是要建立在第一种操作而生成的医院信息的基础上完成的。
5.交流社区模块：
交流社区模块包括话题板块模块、发帖、回帖、帖子管理等字模块，论坛模块里存在各种各样的话题板块，用户在相应的板块讨论相应的话题，用户在线发帖、回帖，管理人员管理所有论坛的帖子，对违规的在线删帖。
4.4 数据库设计
4.4.1 概念设计
借助先进的系统，ER图使其他用户可以快速轻松地了解系统的功能以及他们之间的关系。根据动物领养救助系统分析结果，整个动物领养救助系统包括以下各个单元：管理员，公告、用户、交流、动物信息、评论等。
系统的主要实体间关系E-R图如下图所示。
总体ER图如下图所示。
图4-3 总体ER图
4.4.2 逻辑设计
所有系统的应用数据相互区分。一旦在相应的系统中实现，它们将与自己相应的网络和服务器通信。所以这个系统可以连接这些数据。当我们选择桥梁截面时，以下将简要介绍如何建立系统。在单击上一个按键的时候，就会自动在对话框中弹出数据源的名字，之后再单击下一个按键时，就在填写相对应的身份验证和登录信息。按照系统功能设计的特点与职能模块的分类，动物领养救助系统的总体设计和实施过程一共涉及到了几个资料表格。
以下就介绍了一些根据各类别主要数据库表的设计结构以及基本功能建立数据库
表about_us (关于我们)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
about_us_id |
int |
10 |
0 |
N |
Y |
关于我们ID |
|
| 2 |
corporate_name |
varchar |
64 |
0 |
Y |
N |
公司名称 |
|
| 3 |
cover |
varchar |
255 |
0 |
Y |
N |
封面 |
|
| 4 |
date_of_establishment |
date |
10 |
0 |
Y |
N |
成立时间 |
|
| 5 |
official_account |
varchar |
64 |
0 |
Y |
N |
公众号 |
|
| 6 |
contact_number |
varchar |
64 |
0 |
Y |
N |
联系电话 |
|
| 7 |
details |
longtext |
2147483647 |
0 |
Y |
N |
详情介绍 |
|
| 8 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击数 |
| 9 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表adoption_application (领养申请)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
adoption_application_id |
int |
10 |
0 |
N |
Y |
领养申请ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
名称 |
|
| 3 |
type |
varchar |
64 |
0 |
Y |
N |
种类 |
|
| 4 |
photo |
varchar |
255 |
0 |
Y |
N |
照片 |
|
| 5 |
coat_color |
varchar |
64 |
0 |
Y |
N |
毛色 |
|
| 6 |
animal_sex |
varchar |
64 |
0 |
Y |
N |
动物性别 |
|
| 7 |
health |
varchar |
64 |
0 |
Y |
N |
健康状况 |
|
| 8 |
urban_area |
varchar |
64 |
0 |
Y |
N |
所在市区 |
|
| 9 |
user_no |
int |
10 |
0 |
Y |
N |
0 |
用户编号 |
| 10 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 11 |
adoption_mode |
varchar |
64 |
0 |
Y |
N |
领养方式 |
|
| 12 |
application_time |
date |
10 |
0 |
Y |
N |
申请时间 |
|
| 13 |
remarks |
varchar |
64 |
0 |
Y |
N |
备注 |
|
| 14 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 15 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
| 16 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 17 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 18 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表animal_information (动物信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
animal_information_id |
int |
10 |
0 |
N |
Y |
动物信息ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
名称 |
|
| 3 |
type |
varchar |
64 |
0 |
Y |
N |
种类 |
|
| 4 |
photo |
varchar |
255 |
0 |
Y |
N |
照片 |
|
| 5 |
coat_color |
varchar |
64 |
0 |
Y |
N |
毛色 |
|
| 6 |
character |
varchar |
64 |
0 |
Y |
N |
性格 |
|
| 7 |
animal_sex |
varchar |
64 |
0 |
Y |
N |
动物性别 |
|
| 8 |
health |
varchar |
64 |
0 |
Y |
N |
健康状况 |
|
| 9 |
social_relations |
varchar |
64 |
0 |
Y |
N |
社会关系 |
|
| 10 |
province |
varchar |
64 |
0 |
Y |
N |
所在省份 |
|
| 11 |
urban_area |
varchar |
64 |
0 |
Y |
N |
所在市区 |
|
| 12 |
active_zone |
varchar |
64 |
0 |
Y |
N |
常活动地带 |
|
| 13 |
detailed_description |
longtext |
2147483647 |
0 |
Y |
N |
详情描述 |
|
| 14 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击数 |
| 15 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 16 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 17 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 18 |
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： |
表goods (商品信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
goods_id |
mediumint |
8 |
0 |
N |
Y |
产品id：[0,8388607] |
|
| 2 |
title |
varchar |
125 |
0 |
Y |
N |
标题：[0,125]用于产品和html的<title>标签中 |
|
| 3 |
img |
text |
65535 |
0 |
Y |
N |
封面图：用于显示于产品列表页 |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]用于产品规格描述 |
|
| 5 |
price_ago |
double |
8 |
2 |
N |
N |
0.00 |
原价：[1] |
| 6 |
price |
double |
8 |
2 |
N |
N |
0.00 |
卖价：[1] |
| 7 |
sales |
int |
10 |
0 |
N |
N |
0 |
销量：[0,1000000000] |
| 8 |
inventory |
int |
10 |
0 |
N |
N |
0 |
商品库存 |
| 9 |
type |
varchar |
64 |
0 |
N |
N |
商品分类： |
|
| 10 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量：[0,1000000000]访问这篇产品的人次 |
| 11 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文：产品的主体内容 |
|
| 12 |
img_1 |
text |
65535 |
0 |
Y |
N |
主图1： |
|
| 13 |
img_2 |
text |
65535 |
0 |
Y |
N |
主图2： |
|
| 14 |
img_3 |
text |
65535 |
0 |
Y |
N |
主图3： |
|
| 15 |
img_4 |
text |
65535 |
0 |
Y |
N |
主图4： |
|
| 16 |
img_5 |
text |
65535 |
0 |
Y |
N |
主图5： |
|
| 17 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 18 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 19 |
customize_field |
text |
65535 |
0 |
Y |
N |
自定义字段 |
|
| 20 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 21 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 22 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 23 |
user_id |
int |
10 |
0 |
Y |
N |
0 |
添加人 |
表goods_type (商品类型)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
type_id |
int |
10 |
0 |
N |
Y |
商品分类ID： |
|
| 2 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
上级分类ID：[0,32767] |
| 3 |
name |
varchar |
255 |
0 |
Y |
N |
商品名称： |
|
| 4 |
desc |
varchar |
255 |
0 |
Y |
N |
描述： |
|
| 5 |
icon |
varchar |
255 |
0 |
Y |
N |
图标： |
|
| 6 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 7 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表hits (用户点击)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hits_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
表hospital_information (医院信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hospital_information_id |
int |
10 |
0 |
N |
Y |
医院信息ID |
|
| 2 |
hospital_name |
varchar |
64 |
0 |
Y |
N |
医院名称 |
|
| 3 |
picture |
varchar |
255 |
0 |
Y |
N |
图片 |
|
| 4 |
city |
varchar |
64 |
0 |
Y |
N |
所在城市 |
|
| 5 |
business_hours |
varchar |
64 |
0 |
Y |
N |
营业时段 |
|
| 6 |
consulting_hotline |
varchar |
64 |
0 |
Y |
N |
咨询热线 |
|
| 7 |
address |
varchar |
64 |
0 |
Y |
N |
地址 |
|
| 8 |
details |
longtext |
2147483647 |
0 |
Y |
N |
详情介绍 |
|
| 9 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击数 |
| 10 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 12 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 13 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表my_pet (我的宠物)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
my_pet_id |
int |
10 |
0 |
N |
Y |
我的宠物ID |
|
| 2 |
user_no |
int |
10 |
0 |
Y |
N |
0 |
用户编号 |
| 3 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 4 |
pet_name |
varchar |
64 |
0 |
Y |
N |
宠物名称 |
|
| 5 |
type |
varchar |
64 |
0 |
Y |
N |
种类 |
|
| 6 |
photo |
varchar |
255 |
0 |
Y |
N |
照片 |
|
| 7 |
coat_color |
varchar |
64 |
0 |
Y |
N |
毛色 |
|
| 8 |
animal_sex |
varchar |
64 |
0 |
Y |
N |
动物性别 |
|
| 9 |
health |
varchar |
64 |
0 |
Y |
N |
健康状况 |
|
| 10 |
adoption_mode |
varchar |
64 |
0 |
Y |
N |
领养方式 |
|
| 11 |
adoption_time |
date |
10 |
0 |
Y |
N |
领养时间 |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 14 |
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 |
更新时间： |
表order (订单)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
order_id |
int |
10 |
0 |
N |
Y |
订单ID： |
|
| 2 |
order_number |
varchar |
64 |
0 |
Y |
N |
订单号： |
|
| 3 |
goods_id |
mediumint |
8 |
0 |
N |
N |
商品id：[0,8388607] |
|
| 4 |
title |
varchar |
32 |
0 |
Y |
N |
商品标题： |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
商品图片： |
|
| 6 |
price |
double |
10 |
2 |
N |
N |
0.00 |
价格： |
| 7 |
price_ago |
double |
10 |
2 |
N |
N |
0.00 |
原价： |
| 8 |
num |
int |
10 |
0 |
N |
N |
1 |
数量： |
| 9 |
price_count |
double |
8 |
2 |
N |
N |
0.00 |
总价： |
| 10 |
norms |
varchar |
255 |
0 |
Y |
N |
规格： |
|
| 11 |
type |
varchar |
64 |
0 |
N |
N |
未分类 |
商品分类： |
| 12 |
contact_name |
varchar |
32 |
0 |
Y |
N |
联系人姓名： |
|
| 13 |
contact_email |
varchar |
125 |
0 |
Y |
N |
联系人邮箱： |
|
| 14 |
contact_phone |
varchar |
11 |
0 |
Y |
N |
联系人手机： |
|
| 15 |
contact_address |
varchar |
255 |
0 |
Y |
N |
收件地址： |
|
| 16 |
postal_code |
varchar |
9 |
0 |
Y |
N |
邮政编码： |
|
| 17 |
user_id |
int |
10 |
0 |
N |
N |
0 |
买家ID： |
| 18 |
merchant_id |
mediumint |
8 |
0 |
N |
N |
0 |
商家ID： |
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 21 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]用于产品规格描述 |
|
| 22 |
state |
varchar |
16 |
0 |
N |
N |
待付款 |
订单状态：待付款，待发货，待签收，已签收，待退款，已退款，已拒绝，已完成 |
表praise (点赞)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
praise_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
status |
bit |
1 |
0 |
N |
N |
1 |
点赞状态:1为点赞，0已取消 |
表registered_user (注册用户)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
registered_user_id |
int |
10 |
0 |
N |
Y |
注册用户ID |
|
| 2 |
user_no |
varchar |
64 |
0 |
N |
N |
用户编号 |
|
| 3 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 4 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表shopping_mall (购物商城)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
shopping_mall_id |
int |
10 |
0 |
N |
Y |
购物商城ID |
|
| 2 |
brand |
varchar |
64 |
0 |
Y |
N |
品牌 |
|
| 3 |
specifications |
varchar |
64 |
0 |
Y |
N |
规格 |
|
| 4 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击数 |
| 5 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
cart_title |
varchar |
125 |
0 |
Y |
N |
标题：[0,125]用于产品html的标签中 |
|
| 8 |
cart_img |
text |
65535 |
0 |
Y |
N |
封面图：用于显示于产品列表页 |
|
| 9 |
cart_description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]用于产品规格描述 |
|
| 10 |
cart_price_ago |
double |
8 |
2 |
N |
N |
0.00 |
原价：[1] |
| 11 |
cart_price |
double |
8 |
2 |
N |
N |
0.00 |
卖价：[1] |
| 12 |
cart_inventory |
int |
10 |
0 |
N |
N |
0 |
商品库存 |
| 13 |
cart_type |
varchar |
64 |
0 |
N |
N |
未分类 |
商品分类： |
| 14 |
cart_content |
longtext |
2147483647 |
0 |
Y |
N |
正文：产品的主体内容 |
|
| 15 |
cart_img_1 |
text |
65535 |
0 |
Y |
N |
主图1： |
|
| 16 |
cart_img_2 |
text |
65535 |
0 |
Y |
N |
主图2： |
|
| 17 |
cart_img_3 |
text |
65535 |
0 |
Y |
N |
主图3： |
|
| 18 |
cart_img_4 |
text |
65535 |
0 |
Y |
N |
主图4： |
|
| 19 |
cart_img_5 |
text |
65535 |
0 |
Y |
N |
主图5： |
|
| 20 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 21 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表slides (轮播图)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
slides_id |
int |
10 |
0 |
N |
Y |
轮播图ID： |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
标题： |
|
| 3 |
content |
varchar |
255 |
0 |
Y |
N |
内容： |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
链接： |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
轮播图： |
|
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量： |
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表upload (文件上传)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
upload_id |
int |
10 |
0 |
N |
Y |
上传ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
文件名 |
|
| 3 |
path |
varchar |
255 |
0 |
Y |
N |
访问路径 |
|
| 4 |
file |
varchar |
255 |
0 |
Y |
N |
文件路径 |
|
| 5 |
display |
varchar |
255 |
0 |
Y |
N |
显示顺序 |
|
| 6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
父级ID |
| 7 |
dir |
varchar |
255 |
0 |
Y |
N |
文件夹 |
|
| 8 |
type |
varchar |
32 |
0 |
Y |
N |
文件类型 |
表urban_classification (市区分类)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
urban_classification_id |
int |
10 |
0 |
N |
Y |
市区分类ID |
|
| 2 |
city_name |
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 |
更新时间 |
第5章 系统实现
5.1 登录模块的实现
用户登录的验证将不再局限于登录信息和权限的匹配验证，而是另外增加了一个验证码，只有界面上所有的编辑框数据都准确的情况下才能实现登录成功。管理员的登录和前台用户登录是一样的过程，其主要就是利用权限字段来完成对用户或管理员的角色识别。
用户登录流程图如下所示。
图5-1 用户登录流程图
登录界面如下图所示。
图5-1 登录界面
5.2 用户模块的实现
5.2.1 注册模块的实现
系统的用户通过自行注册生成，在系统首页点击用户注册菜单，系统跳转到对应的注册页面。点击重置按钮，清空所填数据，点击注册按钮完成注册。
用户注册流程图如下所示。
图5-1 用户注册流程图
用户注册界面如下图所示。
图5-1 用户注册界面
5.2.2 密码修改模块的实现
用户使用该动物领养救助系统注册完成后，用户对登录密码有修改需求时，系统也可以提供用户修改密码权限。系统中所有的操作者能够变更自己的密码信息，执行该功能首先必须要登入系统，然后选择密码变更选项以后在给定的文本框中填写初始密码和新密码来完成修改密码的操作。在填写的时候，假如两次密码填写存在差异，那么此次密码变更操作失败，下面的图片展示的就是该板块对应的工作面。
密码修改流程图如下所示。
图5-1 密码修改流程图
密码修改界面如图所示。
图5-1 密码修改界面
5.2.3 交流社区模块的实现
当用户和用户之间交流之后，管理者可以在主界面中可以选择交流功能，管理者可以进行用户的交流查看，可以进行填写交流回复，也可以对交流社区进行删除。通过这种方式，管理者可以和用户进行密切的交流社区。
发表交流社区流程图如下所示。
图5-1 发表交流社区流程图
发表交流社区界面如图所示。
图5-1 发表交流社区界面
5.2.4 动物信息模块的实现
用户执行动物信息，并可以操作相关内容，例如查看，编辑。动物信息的添加操作是建立在动物信息的列表基础上，单击查看动物信息下的动物信息链接；然后单击“动物信息”进行添加，添加成功后的信息会载入到动物信息查询列表中。
动物信息流程如下图所示。
图5-1 动物信息流程
动物信息界面如下图所示。
图5-1 动物信息界面
5.2.5 评论模块的实现
用户点击某个动物信息进入动物详细页，点击评论按钮进入评论页，提交评论信息，成功发布评论，管理员管理用户的评论信息。
发布评论流程图如下所示。
图5-1 发布评论流程图
发布评论界面如图所示。
图5-1 发布评论界面
5.3 后台模块的实现
5.3.1 用户管理模块的实现
用户通过注册了方可获得登录使用权限，此时选择注册用户选项，系统就会自动转到用户注册工作面，在注册该部分信息时系统会自动调用add函数，然后在给定的文本框中填写有关该用户的基础信息后选择确认即可完成注册。检索用户信息，在新增用户信息以后，在检索工具栏中填写对应的用户信息，系统就会将该用户有关的所有信息展示出来。
用户管理流程图如下所示。
图5-1 用户管理流程图
用户管理界面如下图所示。
图5-1 用户管理界面
5.3.2 动物信息管理模块的实现
管理员执行动物信息管理，并可以操作相关内容，例如添加，查看，编辑和删除。通过单击“添加动物信息”，可以通过动物信息添加界面添加详细信息。单击查看字段级别链接以查看有关所选字段级别的信息。然后单击“提交”跳转重返到添加页面。添加成功后的信息会载入到动物信息查询列表中，管理员可进行编辑以及修改。
动物信息添加流程图如下所示。
图5-1 动物信息添加流程图
动物信息管理界面如图所示。
图5-1动物信息管理界面
5.3.3 动物种类管理模块的实现
管理员执行动物种类管理，并可以操作相关内容，例如添加，查看，编辑和删除。通过单击“添加动物种类”，可以通过动物种类添加界面添加详细信息并添加动物种类注释。单击查看字段级别链接以查看有关所选字段级别的信息。然后单击“提交”跳转重返到添加页面。添加成功后的信息会载入到动物种类查询列表中，管理员可进行编辑以及修改。
动物种类管理流程如下图所示。
图5-1 动物种类管理流程
动物种类添加界面如下图所示。
图5-1 动物种类展示界面
动物种类管理界面如下图所示。
图5-1 动物种类管理界面
5.3.4 领养申请管理模块的实现
管理员执行领养申请管理，并可以操作相关内容，例如添加，查看，编辑和删除。通过单击“添加领养申请”，可以通过领养申请添加界面添加详细信息。单击查看字段级别链接以查看有关所选字段级别的信息。然后单击“提交”跳转重返到添加页面。添加成功后的信息会载入到领养申请查询列表中，管理员可进行编辑以及修改。
领养申请添加流程图如下所示。
图5-1 领养申请添加流程图
领养申请管理如下图所示。
图5-1 领养申请管理界面
第6章 系统测试
6.1 测试目的
在这个产品被投入使用前，首先需要进行试用，这是重要的环节。考虑到某个部分的开发没有缺陷情况下，把各种模块拼接，也有一定概率就存在矛盾。这就好比每个人都很独特，但聚在一起就显得杂乱无章，需要保证有默契的配合。对于测试，要看它的各项内容是否契合的原则。若与最初定下的标准有一定程度上的出入，那么就需要做出一些调整，让最终的大方向朝着目标前进。
测试是为了发现在开发的程序中所存在的问题，测试这一工作是非常艰巨的，而又是非常困难的，这一部分在程序的设计中占有很大比例，可以说一个程序的开发工作量要是占据了百分至六十，那么剩下的百分之四十必然是测试这一部分，甚至更高。
6.2 测试用例
6.2.1 公告消息测试
公告消息测试用例如下表所示。
表6-3 公告消息测试用例
| 测试用例编号 |
YL_03 |
|
| 测试用例名称 |
系统使用者进行在线交流 |
|
| 测试用例描述 |
使用者输入交流标题、内容等信息 |
|
| 系统入口 |
浏览器 |
|
| 步骤 |
预期结果 |
实际结果 |
| 输入完整的交流标题和内容 |
提示“交流成功”，并进入系统 |
预期结果 |
| 不输入的交流标题和内容 |
提示“请输入完整” |
预期结果 |
6.2.2 创建数据测试
在系统中，创建功能也是基础功能之一，因此创建功能的测试很有代表性。在此章节主要列举在创建时各种情况下系统结果的测试。由于系统涉及创建功能操作过多，因此将多处统称创建功能。
创建数据用例如下表所示。
表6-5 创建数据测试用例
| 测试用例编号 |
YL_05 |
|
| 测试用例名称 |
系统使用者进行创建数据 |
|
| 测试用例描述 |
使用者输入要创建的数据 |
|
| 系统入口 |
浏览器 |
|
| 步骤 |
预期结果 |
实际结果 |
| 输入完整并且格式正确的数据 |
提示“创建成功”，并显示所有数据 |
预期结果 |
| 核心位置数据但非必要位置不输入数据 |
提示“创建成功”，并显示所有数据 |
预期结果 |
| 核心数据位置不输入数据 |
提示“创建失败” |
预期结果 |
6.2.3 修改数据测试
在系统中，修改功能是系统主要实现功能，因此修改功能的测试很有代表性。在此章节主要列举在修改时各种情况下系统结果的测试。由于系统涉及修改功能操作过多，因此将多处数据表记录修改和状态修改统称修改功能。
修改数据用例如下表所示。
表6-6 修改数据测试用例
| 测试用例编号 |
YL_06 |
|
| 测试用例名称 |
系统使用者进行修改数据 |
|
| 测试用例描述 |
使用者对可修改的数据项进行修改 |
|
| 系统入口 |
浏览器 |
|
| 步骤 |
预期结果 |
实际结果 |
| 将现有数据修改成正确的数据 |
提示“修改成功”，并显示所有数据 |
预期结果 |
| 将现有数据修改成错误的数据 |
提示“修改失败” |
预期结果 |
6.2.4 查询数据测试
在系统中，查询功能是使用系统使用最多也是最基础的功能，因此查询功能的测试很有代表性。在此章节主要列举在查询时各种情况下系统结果的测试。
查询数据用例如下表所示。
表6-7 查询数据测试用例
| 测试用例编号 |
YL_05 |
|
| 测试用例名称 |
系统使用者进行查询数据 |
|
| 测试用例描述 |
全部查询以及输入关键词查询 |
|
| 系统入口 |
浏览器 |
|
| 步骤 |
预期结果 |
实际结果 |
| 界面自动查询全部 |
显示对应所有记录 |
预期结果 |
| 输入已存在且能匹配成功的关键字 |
显示所查询到的数据 |
预期结果 |
| 输入不存在的关键字 |
显示数据界面为空 |
预期结果 |
6.3 测试结果
在本次测试的过程主要针对所有功能下的添加操作，修改操作和删除操作，并以真实数据一一进行相关功能项目的输入，最终能够保证每个项目涉及的功能都是能够正常运行，因此能够保证本次设计的，已实现的功能能够正常运行并且相关数据库的信息也同样保证正确。
结 论
本次动物领养救助系统利用了Web应用同现实研发方案工作进行相结合，在系统功能开始编码之前，作者花费了大量时间在图书馆内进行资料文献的收集和总结，通过大量文献的分析，能够发现，动物领养救助系统管理的方式在宠物医院中扮演的位置是越来越重要，而使用的方式也是越来越多元化，也正是因为这个原因，作者深深的希望能够开发出一种专门针对动物领养救助系统，以满足用户的需求。
在本次动物领养救助系统中，利用了目前市场上普遍使用的python技术，以及数据库管理功能MySQL，和目前比较流行的django框架，最后配合使用到了VUE页面布局技术进行系统界面的布置，以现实生活的用户运动过程为标准，设计实现了公告消息、资讯浏览、动物信息、医院信息、领养申请、评论、交流等功能，并维护好后台的信息和整体系统的稳定性。
However, due to the limitations of the author's technical level, in the limited time, he can only realize the functions of the system function simulation. There are still great disadvantages in many functions, and these disadvantages require continuous testing, continuous summary, and continuous improvement of. For example, in this system design, the data storage is not comprehensive enough, and it is easy to risk information leakage; for example, the settings for user permissions are also not comprehensive and complete, and it does not consider whether the permissions can be perfectly executed in actual situations. In the following days, the author will continue to learn python technology and related information technology, conduct a more complete and detailed analysis of the system functions, improve the system functions one by one, and help users complete the corresponding operations.
references
[1] Shen Cuixin. Reform and practice of the project-based course "Python Language and Its Application" [J]. Journal of Shenzhen Vocational and Technical College, 2022, 21(05): 71-77. DOI: 10.13899/j.cnki. szptxb. 2022.05.012.
[2] Lu Longbin, Wang Xiaoyin, Xu Xuebin, Jin Xiaomin, Hua Wenqiang. Multi-angle ideological and political education teaching of Python language programming [J]. Computer Education, 2022(09):58-62.DOI:10.16512/j .cnki.jsjjy.2022.09.022.
[3] Gong Junmei, Liu Yang. Research on the Reform of "Python Language" Course Teaching System [J]. Science and Technology Wind, 2022(22):112-114.DOI:10.19392/j.cnki.1671-7341.202222036.
[4] Miao Xiu. Research on case-based teaching in Python environment [J]. Liberal Arts Navigation (Mid-term), 2022(08):79-81.
[5] Guo Hanting. Design and development of file sharing platform based on Django framework [J]. Information Recording Materials, 2022, 23(03):139-141.DOI:10.16009/j.cnki.cn13-1295/tq.2022.03 .075.
[6]Li Hui chao,Shen Shun fa. Construction of College Students’ Physical Health Data Sharing System Based on Django Framework[J]. Journal of Sensors,2021,2021.
[7] Cai Ziwei. Design of quantitative trading system based on Django framework [J]. Journal of Shanxi Datong University (Natural Science Edition), 2021, 37(05): 39-42.
[8] Qiu Hongli, Zhang Shuya. Research on web project development based on Django framework [J]. Science and Technology Innovation, 2021(27):97-98.
[9] Jiang Su. Feasibility study on solving the problem of stray animals in society based on Internet platform[D]. Shandong Agricultural University, 2020.DOI:10.27277/d.cnki.gsdnu.2020.001043.
[10] Liu Qinqin. Legal research on the standardized management of stray animals in my country [D]. Northwest University, 2020.DOI:10.27405/d.cnki.gxbdu.2020.002158.
Thanks
On the occasion of the completion of this thesis, I would like to thank my supervisor. In the web design class of the instructor, I learned a lot, which also laid a certain foundation for my internship. The instructor also made many suggestions for my design and gave me careful guidance. They patiently guided me to improve the problem, gave me the experience of writing thesis, and often encouraged me. In addition, I would like to thank the front-end classmates who taught me to improve this project. For this project, I completed it while learning, and there are many things to start with. I don’t understand it very well, but my front-end development classmates very patiently guided me to complete this project. In the back-end development of the system, the back-end development technology used was often explained to me, which helped me better write the paper. Completed, I would like to express my heartfelt thanks to the classmates who helped me and the instructors who have always taught me, and wish me a successful career.