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 APP , 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 impact of the system. The design and implementation were also discussed in detail. Finally, some specific tests were conducted on the pet adoption system APP .
This article uses SSM as the development technology to implement a pet adoption system APP . The main users of the pet adoption system APP are divided into homepage, carousel, announcement information, resource management (pet information, information classification) communication management (communication forum, forum classification) system users (administrators, member users) module management (pets Information, category management, adoption information, adoption feedback) and other functions. Through the design of these functional modules, the entire pet adoption system APP process is basically realized .
Specifically in the system design, it adopts the SSM structure and uses the Mysql database in the background . It is a very excellent pet adoption system APP .
Keywords: pet adoption system APP ; ssm technology; Mysql database
Abstract
Today in the 21st century, with the continuous development and progress of society, people's understanding of the scientific nature of information has developed from a low level to a high level, and the importance of management work has gradually been recognized by people. Scientific management enables information storage to achieve accuracy, speed, and perfection, and can improve work management efficiency and promote its development.
The paper mainly introduces the pet adoption system APP, including the current research status and the development background involved. It also discusses the design objectives of the system, the system requirements, and the entire design scheme. The design and implementation of the system are also discussed in detail. Finally, some specific tests are conducted on the pet adoption system APP.
This article uses SSM as the development technology to implement a pet adoption system APP. The main users of the Pet Adoption System APP are divided into homepage, rotation chart, announcement information, resource management (pet information, information classification), communication management (communication forum, forum classification), system user (administrator, member user) module management (pet information, category management, adoption information, adoption feedback), and other functions. Through the design of these functional modules, the entire process of the pet adoption system APP has been basically implemented.
In terms of system design, the SSM structure is adopted, and the MySQL database is used in the backend, making it an excellent pet adoption system APP.
Keywords: Pet adoption system APP; SSM 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 ssm framework
2.2 Software development environment and development tools
2.3 Working principle of B/S system
2.7 Separation of front and back ends
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
3.4 Non-functional requirements analysis
4.3.1 Database design principles
5.1APP home page function module
5.2 Administrator function module
1 Overview
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 , the management of information related to the pet adoption system APP was done 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 APP 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 the main tools for people to obtain information. This is an era of unlimited communication. Therefore, using the Internet to manage online pet adoption system APPs has also become a general trend. Therefore, it is necessary to develop a pet adoption system APP .
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 ssm framework
The SSM (Spring+SpringMVC+MyBatis) framework set is integrated by the two open source frameworks Spring and MyBatis (SpringMVC is part of Spring). It is often used as a framework for web projects with relatively simple data sources.
2.1.1 Spring
Spring is like a big factory that assembles beans in the entire project. In the configuration file, you can specify the use of specific parameters to call the constructor method of the entity class to instantiate the object. It can also be called the glue in the project.
The core idea of Spring is IoC (Inversion of Control), which means that programmers no longer need to explicitly `new` an object, but let the Spring framework do it all for you.
2.1.2 SpringMVC
SpringMVC intercepts user requests in the project. Its core Servlet, DispatcherServlet, assumes the responsibilities of intermediary or front desk, and matches user requests to the Controller through HandlerMapping. The Controller is the specific operation performed in response to the request. SpringMVC is equivalent to struts in the SSH framework.
2.1.3 mybatis
mybatis is an encapsulation of jdbc, which makes the underlying operations of the database transparent. The operations of mybatis are centered around a sqlSessionFactory instance. Mybatis is associated to the Mapper file of each entity class through the configuration file. The Mapper file is configured with the SQL statement mapping required for each class to the database. Every time you interact with the database, get a sqlSession through sqlSessionFactory, and then execute the sql command.
The page sends a request to the controller, the controller calls the business layer processing logic, the logic layer sends a request to the persistence layer, the persistence layer interacts with the database, and then returns the result to the business layer, the business layer sends the processing logic to the controller, and the controller then Call the view to display the data.
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: 2.10GHz 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 Interssm through a 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 Interssm 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.
2.6 Android technology
Android is an operating system based on the Linux kernel. It was developed by Google in the early days and later by the Open Handset Alliance. It adopts a software heap architecture and is mainly divided into three parts. The bottom layer is based on the Linux kernel and only provides basic functions; other application software is developed by each company, using Java as part of the program. In addition, in order to promote this technology, Google and dozens of other mobile phone companies established the Open Mobile Alliance. Android was often rumored to be GPhone before it was made public.
It adopts a software stack (also known as software stack) architecture, which is mainly divided into three parts: the bottom layer is based on the Linux core, developed in C language, and only provides basic functions. The middle layer includes the function library Library and the virtual machine Virtual Machine, which is developed in C++. The top layer is various application software, including call programs, text message programs, etc. The application software is developed by each company and written in Java.
2.7 Separation of front and back ends
The emergence of Ajax has also brought about another problem, that is, with Ajax, functions that were previously implemented using template languages have become simpler, and functions that could not be achieved with template languages before can now be achieved. This causes more and more logic to be transferred to JavaScript, making it more and more complex.
As the complexity of js increased, problems arose with the original development model. It became increasingly unreliable for one programmer to handle the entire site, so at this time the website development position was divided into front-end and back-end. Position. But just dividing the scope of responsibilities of the front-end and back-end is not enough. Under the original development model, the front-end and back-end codes were also together. Now that it has been divided into two waves of development, front-end and back-end, maintaining the same set of code has become less convenient. The more complex the project is, the more situations you will have to wait for me and I will wait for you, which will slow down the overall team's pace. Therefore, for the sake of team efficiency, the front-end and back-end codes must also be separated.
There are two ways to separate the front and back ends: partial separation and full separation. Partial separation means that only scripts and styles are separated, while the HTML template remains in the back end for rendering through Java, Velocity or FreeMarker; the other is complete separation, with scripts Styles and templates are all maintained on the front end.
Partial separation has largely solved the coordination problem during front-end and back-end development, and development efficiency has also been greatly improved. But we have to admit that there are still problems with this approach. When you want to develop HTML templates, you need to set up a complete back-end development environment, or find a back-end programmer to assist.
There are generally two solutions for complete separation. The first is to use Velocity, a page template that can be compiled under both nodejs and java, and put it into the front-end project during development, but when publishing, the template will be published to the back-end. In the template directory, in this way, complete separation is achieved during development. The biggest advantage of this method is that the rendering of online templates is still done by Java, and the result is HTML with dynamic data, which is more conducive to SEO. However, in this way, the complexity of the front-end development environment and publishing system is relatively high, and simple front-end changes still need to be released with the back-end.
The second way of complete separation is to put the purely static html template completely on the front end, and all data is interacted through the RESTful interface. In this way, the front and back ends are completely separated and separated from the back-end template, and the system complexity of this method will be lower than the first completely separated method. However, under this solution, all page data is rendered using js, and there is no dynamic template, which is not conducive to SEO. We can solve this shortcoming by doing server render or making a customized page for the spider.
3 System analysis
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 APP is to realize 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 APP mainly uses Java technology, based on B/S structure and Mysql database. The development of the application 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 APP 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 APP 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 APP is based on Java mode and uses Mysql database to store data. The required hardware and software environment are easy to purchase on the market. Program development is mainly 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 APP 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 APP 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 the pet adoption system APP , first conduct a demand 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 information about stray animals , etc. Users can add information within their own authority. After entering the information, the system will verify the entered information and data on its own. 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 stray animal 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 the database, if the information is illegal, the modification fails and needs to be re-entered. The modified information flow chart is shown in Figure 3-5.
Figure 3-5 Modify information flow chart
3.2.6 Information deletion process
The administrator can delete stray animal 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 save it in the database. To delete information, 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, announcement information, resource management (pet information, information classification) communication management (communication forum, forum classification) system user (administrator, member user) module management (pet information, category management, adoption information, adoption feedback) 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 enter the system through home page, communication forum, pet information, mine (basic information, collections, adoption information, adoption feedback) , etc. The user use case is shown in Figure 3-8 .
Figure 3-8 User use case diagram
3.4 Non-functional requirements analysis
As the number of users increases, the system may need to serve thousands or tens of thousands of pages at the same time. The server needs to respond to the operations of a large number of users at the same time. This requires the system to have good scalability, otherwise the system will experience delays and lags. Even server crashes. High scalability allows the software to maintain strong vitality, and also enables the system to better adapt to changes such as increased users, improved performance requirements, and increased application functions.
A large amount of personal information of users and administrators is stored in the system. Therefore, ensuring the security of the system server and data is an important issue that needs to be considered during the development process. Security includes server security, operating system security, database security, program code security, and user personal information and payment security. The system can enhance its security by using firewall technology, encryption technology, authentication technology, etc. There is only a robust and secure system. Only then can it have long-lasting vitality.
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 APP is shown in Figure 4-1:
Figure 4-1 System working principle diagram
4.2 System structure design
At present, the main data access method of the B/S system is: users can enter the system through the browser page, and the system can automatically process the requests sent by the users to the server. The processing of the requests is carried out in the background of the system. By performing corresponding operations on the page, you can see the processing results delivered by the server. The royalties distribution management system is mainly divided into a three-layer architecture design of view-model-control. In the view layer, it mainly operates the data that is fed back and displayed on the server side to the client. In the model layer, it mainly handles related business logic, data integration, etc. The final control layer is between the view and the model, mainly It is to adjust the relationship between the two layers and finally implement the transmission of data.
The system architecture diagram is shown in the figure below.
Figure 4-2 System architecture diagram
The purpose of system design is to analyze all functional structures included in the system and prepare developers for the design, development and implementation of the system. After preliminary demand investigation, analysis and sorting, the overall demand determined mainly includes multiple modules, namely: home page, carousel chart, announcement information, resource management (pet information, information classification) communication management (communication forum, forum classification) ) System user (administrator, member user) module management (pet information, category management, adoption information, adoption feedback). The overall role of the system is divided into two parts, one is the operator and the other is the administrator. The distribution of permissions is also very obvious. In addition to browsing information, operator users also have permissions to query and manage their own account information, adoption information, adoption feedback, etc.; the administrator is the highest authority owner.
The administrator structure diagram is shown in Figure 4-3.
Figure 4-3 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
When learning programming, we all know that database design is based on the system functions that need to be designed. We need to establish a database relational model to store data information, so that when we are in the program, there is no need to add data to the program page, thereby improving the system s efficiency. The database stores a lot of information and can be said to be the core and foundation of the information management system. The database also provides addition, deletion, modification and inspection, allowing the system to quickly find the information it wants instead of finding it in the program code. Each part of the information table in the database is accurately combined, arranged and combined into a data table according to certain relationships.
The planning through the functions of the pet adoption system APP is divided into several entity information. The entity information will be explained through the ER diagram. The main entity diagram of this system is as follows:
Figure 4-4 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_feedback (adoption feedback)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
adoption_feedback_id |
int |
10 |
0 |
N |
Y |
Adoption Feedback ID |
|
| 2 |
adoption_number |
varchar |
64 |
0 |
Y |
N |
Adoption number |
|
| 3 |
pet_name |
varchar |
64 |
0 |
Y |
N |
pet name |
|
| 4 |
pet_category |
varchar |
64 |
0 |
Y |
N |
pet category |
|
| 5 |
pet_sex |
varchar |
64 |
0 |
Y |
N |
pet gender |
|
| 6 |
pet_age |
varchar |
64 |
0 |
Y |
N |
pet age |
|
| 7 |
adoptive_user |
int |
10 |
0 |
Y |
N |
0 |
Adopt a user |
| 8 |
member_name |
varchar |
64 |
0 |
Y |
N |
Member's name |
|
| 9 |
pet_pictures |
varchar |
255 |
0 |
Y |
N |
pet pictures |
|
| 10 |
feedback_content |
text |
65535 |
0 |
Y |
N |
Feedback content |
|
| 11 |
management_scoring |
varchar |
64 |
0 |
Y |
N |
Management scoring |
|
| 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 |
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 |
adoption_number |
varchar |
64 |
0 |
Y |
N |
Adoption number |
|
| 3 |
pet_name |
varchar |
64 |
0 |
Y |
N |
pet name |
|
| 4 |
pet_category |
varchar |
64 |
0 |
Y |
N |
pet category |
|
| 5 |
pet_sex |
varchar |
64 |
0 |
Y |
N |
pet gender |
|
| 6 |
pet_age |
varchar |
64 |
0 |
Y |
N |
pet age |
|
| 7 |
adoptive_user |
int |
10 |
0 |
Y |
N |
0 |
Adopt a user |
| 8 |
member_name |
varchar |
64 |
0 |
Y |
N |
Member's name |
|
| 9 |
contact_number |
varchar |
64 |
0 |
Y |
N |
contact number |
|
| 10 |
adoption_notes |
text |
65535 |
0 |
Y |
N |
Adoption Notes |
|
| 11 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 12 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
moderation reply |
|
| 13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 15 |
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: |
Table category_management (category management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
category_management_id |
int |
10 |
0 |
N |
Y |
Category Management ID |
|
| 2 |
pet_category |
varchar |
64 |
0 |
Y |
N |
pet category |
|
| 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 |
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: |
Table member_users (member users)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
member_users_id |
int |
10 |
0 |
N |
Y |
Member user ID |
|
| 2 |
member_name |
varchar |
64 |
0 |
Y |
N |
Member's name |
|
| 3 |
member_gender |
varchar |
64 |
0 |
Y |
N |
Member gender |
|
| 4 |
membership_age |
varchar |
64 |
0 |
Y |
N |
Member age |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 8 |
create_time |
datetime |
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 |
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 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 |
pet_category |
varchar |
64 |
0 |
Y |
N |
pet category |
|
| 4 |
pet_sex |
varchar |
64 |
0 |
Y |
N |
pet gender |
|
| 5 |
pet_age |
varchar |
64 |
0 |
Y |
N |
pet age |
|
| 6 |
pet_pictures |
varchar |
255 |
0 |
Y |
N |
pet pictures |
|
| 7 |
introduction_to_pets |
longtext |
2147483647 |
0 |
Y |
N |
Pet introduction |
|
| 8 |
hits |
int |
10 |
0 |
N |
N |
0 |
Clicks |
| 9 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 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 |
| 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 |
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 |
账户状态：[0,10](1可用|2异常|3已冻结|4已注销) |
| 3 |
user_group |
varchar |
32 |
0 |
Y |
N |
所在用户组：[0,32767]决定用户身份和权限 |
|
| 4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
上次登录时间： |
| 5 |
phone |
varchar |
11 |
0 |
Y |
N |
手机号码：[0,11]用户的手机号码，用于找回密码时或登录时 |
|
| 6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
手机认证：[0,1](0未认证|1审核中|2已认证) |
| 7 |
username |
varchar |
16 |
0 |
N |
N |
用户名：[0,16]用户登录时所用的账户名称 |
|
| 8 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称：[0,16] |
|
| 9 |
password |
varchar |
64 |
0 |
N |
N |
密码：[0,32]用户登录所需的密码，由6-16位数字或英文组成 |
|
| 10 |
|
varchar |
64 |
0 |
Y |
N |
邮箱：[0,64]用户的邮箱，用于找回密码时或登录时 |
|
| 11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
邮箱认证：[0,1](0未认证|1审核中|2已认证) |
| 12 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
用户组ID：[0,8388607] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
显示顺序：[0,1000] |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
名称：[0,16] |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]描述该用户组的特点或权限范围 |
|
| 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 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
注册位置: |
| 9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
5统详细设计
5.1APP首页功能模块
宠物领养系统APP，在系统首页可以查看网站首页、交流论坛、宠物资讯、我的（基本信息、收藏、领养信息、领养反馈）等内容，如图5-1所示。
图5-1前台首页功能界面图
交流论坛、交流论坛页面可以查看帖子标题、内容、发布日期等内容，可根据需要进行点赞或者回复等操作，如图5-2所示。
图5-2交流论坛页面界面图
宠物信息，宠物信息页面可查看展示的宠物名称、宠物类别、宠物性别、宠物年龄等信息，根据需要可对宠物进行领养申请。如图5-3所示。
图5-3宠物信息展示页界面图
领养信息，在领养信息页面可填写宠物类别、宠物性别、宠物年龄、领养用户、会员姓名、联系电话、领养用户、会员姓名、联系电话、领养用户列表，如图5-4所示。
图5-4领养信息列表界面图
5.2管理员功能模块
管理员登录，通过填写注册时输入的用户名、密码权限进行登录，如图5-5所示。
图5-5管理员登录界面图
管理员登录进入宠物领养系统APP可以查看个系统后台首页、轮播图、公告信息、资源管理（宠物资讯、资讯分类）交流管理（交流论坛、论坛分类）系统用户（管理员、会员用户）模块管理（宠物信息、类别管理、领养信息、领养反馈）等信息。如图-5-6所示：
图5-6管理员功能界面图
系统用户管理，在系统用户管理页面中可以对管理员用户密码修改功能，如图5-7所示：
图5-7系统用户界面图
宠物信息管理，在宠物信息管理页面中可以查看宠物名称、宠物名称、宠物类别、宠物性别、宠物年龄、宠物图片、创建时间等信息，并可根据需要在宠物信息查询页面对已有的宠物信息进行编辑删除或详细等操作，如图5-8所示。
图5-8宠物信息管理界面图
领养反馈管理，在领养反馈管理页面中可以查看宠物年龄、领养用户、会员姓名、宠物图片、反馈内容、管理打分、创建时间等信息，并可根据需要在领养反馈页面对已有的领养反馈进行回复、编辑、删除或详细等操作，如图5-9所示。
图5-9领养反馈管理界面图
6系统测试
系统开发的最后一个步骤就是系统测试，系统测试也是整个系统十分重要的一个环节，测试的好坏关系到产品的发展。用户对软件的质量、性能和可靠性等需求就要通过测试来实现。测试过程要必须遵循严谨性、完善性、规范性的原则，测试的主要目的就是看看在系统运行中，是否会出现bug，然后对出现的bug进行调试，直到程序完美运行。但是软件的测试只能尽可能的减少bug，理论上来说是无法达到消除bug。但是bug越少，系统出错的几率就越低，用户使用起来也更方便、更安全。
近年来，软件包含测试从现在的检验当中来看，系统接近预期目标可能出现的问题，并对这些错误做出相应的修正，假如我们不进行早期的测试错误就会延续下去，最后所做出的成品就会有很大的困难。
我们要在这个测试的过程当中找出错误。测试成软件开发的主要一部分，自从有了程序的设计那天开始，它就成为了重要的组成部分。经过统计来看，软件测试可以占据这个系统45%的工作量，而在软件开发的成本当中，对于测试成本来说它包含了很多的测试工作。每个程序测试时都会出现和遇到错误。在整个程序的开发过程当中，人为去查找错误是非常复杂和困难的，所以我们一般都会找一些测试的工具来进行测试。
6.1系统测试的意义
随着现代信息的快速发展，在社会各大领域中已经都开始应用网络信息技术，在应用网络技术的同时人们也开始把软件的质量问题作为了一个重要焦点来关注，因为一个软件的好与坏它决定着这个系统在市场上的生存，所以我们必须要把软件质量来做好，这样才有一定的生存能力。对于用户来说它们首先选用的都是保证这个系统软件的质量问题，因为一个系统的软件质量决定着用户在后期上成本经济的问题。图6-1就是纠错测试流程。
图6-1 测试与纠错信息流程
6.2 测试方法
黑盒测试又被人们称作为功能测试，通常是在程序的接口来做一些测试的方法，它一般包括对程序的功能和使用的方法来做出一些数据的接受和输出，同时还可以做出正确的输出信息，并保证与外部信息的完整性。
白盒测试通常被人们称作为结构测试，在整个程序的结构和处理当中它是由程序当中的逻辑测试和检验程序来完成一些正确的工作。
具体的功能测试它是包括：系统的适用性、准确性、安全性等功能测试。
6.3测试分析
本宠物领养系统APP满足相关信息的管理需求，在设计时借鉴了国内外优秀网站的优点，从界面到系统设计都保证了管理员以及用户能够方便操作。系统的主要特点和优点归纳如下：
（1）本系统用的移置性和针对性都比较高，因为针对性高可以提供更好的服务而移置性可以在多个系统上运行，更给用户带来了极大的方便。
（2）该宠物领养系统APP内容全面，管理方便可以及时的全面的处理各种错误，异常，这样避免了很多因用户的马虎操作而出现的失误，其操作方便，用户界面友好，能够上网的人都可以很好的进行操作。
经过对上述的测试结果分析，所有基本功能齐全，操作简单，系统运行性能良好，系统安全可靠，能促进宠物领养系统APP平台的发展，发展前景广阔。
结 论
本系统通过对java和Mysql数据库的简介，从硬件和软件两反面说明了宠物领养系统APP的可行性，本文结论及研究成果如下：实现了java与Mysql相结合构建的宠物领养系统APP，网站可以响应式展示。通过本次宠物领养系统APP的研究与实现，我感到学海无涯，学习是没有终点的，而且实践出真知，只有多动手才能尽快掌握它，经验对系统的开发非常重要，经验不足，就难免会有许多考虑不周之处。比如要有美观的界面，更完善的功能，才能吸引更多的用户。
由于在此之前对于java知识没有深入了解，所以从一开始就碰到许多困难，例如一开始的页面显示不规范、数据库连接有问题已经无法实现参数的传递等等，不过通过在网上寻找有关资料以及同学的帮助下最后都得到了解决，在此过程中，我不仅学到了很多知识，也提高了自己解决问题的能力，尤其是学会如何从大量的信息中筛选出所需有用的信息，同时我更加深刻的体会到了，虽然书本上的大部分知识都是有价值，正确的，但实际上每个人编程的思路和对数据处理的方法、思想都是不同的，这就要求我们一定要通过实践才能找到解决问题的方案。在此次毕业设计活动中，我不断的提高了自己，也得到了宝贵的经验，我相信这些对我以后的发展都会有很大帮助。
通过这次宠物领养系统APP的开发，我参考了很多相关系统的例子，取长补短，吸取了其他系统的长处，逐步对该系统进行了完善，但是该系统还是有很多的不足之处，有待以后进一步学习。
实践证明，宠物领养系统APP有着非常好的发展前景，经过测试运行，系统各项功能都十分完善，界面漂亮，使用方便，操作容易，在技术理论上已经成熟。
致 谢
大学的学习生活在这个季节将结束，但是在我的生命这仅仅只是一个逗号，我将面对另一个新的环境开始。通过这次毕业设计的整个开发过程，从需求分析到具体功能实现，再到最终测试和维护的理解有了很大的进步，让我对系统开发有了更深刻的认识，对我个人的实践能力和解决问题的能力，都有了很大的帮助。这是这次毕业设计最大的收获。
首先要感谢我的指导老师，他在论文写作上，给予了我各种无私的帮助，治学严谨，严格要求，使我获得了很大的收获。老师深厚的理论知识和丰富的实践经验，都深深的影响到我，在这方面，我谨表示衷心的感谢。
其次，我还要对所有的老师和同学表示感谢，他们在我学习的过程中，都积极的提供了很多帮助，无论是专业知识，还是实践操作技能，也能够让我在论文写作中，遇到的一些难题迎刃而解。
最后，对阅读和评审本论文的各位老师表示衷心的感谢!
参考文献
[1]Paul Krill. Oracle per-employee Java licensing could benefit rivals[J]. InfoWorld.com,2023.
[2]Paul Krill. JavaScript, Java, and Python skills top demand[J]. InfoWorld.com,2023.
[3]王平泉,逯小青.JAVA程序设计课程的PBL教学模式实践[J].集成电路应用,2023,40(01):90-91.DOI:10.19339/j.issn.1674-2583.2023.01.034.
[4] Luo Yaqiong. Research and implementation of APP software user feedback analysis method technology [J]. Modern Electronic Technology, 2022, 45(24): 161-165.DOI: 10.16652/j.issn.1004-373x.2022.24. 030.
[5] Luo Yaqiong, Jiang Ying, Chen Yongquan. Matching of evaluation objects and evaluation opinions in APP software user reviews [J]. Modern Electronic Technology, 2022, 45(22): 126-132. DOI: 10.16652/j.issn .1004-373x.2022.22.024.
[6] Zheng Xin. Teaching practice of Java programming courses [J]. Integrated Circuit Applications, 2022, 39(11):94-95.DOI:10.19339/j.issn.1674-2583.2022.11.036.
[7] Ren Haoran, Liu Dan, Jing Yongqiang. Research on the application of JAVA in computer software development [J]. Information Recording Materials, 2022, 23(11):83-85.DOI:10.16009/j.cnki.cn13 -1295/tq.2022.11.072.
[8] Cao Kexin, Cui Xinlong, Huang Qi, Chen Xiao. Voice control translation software APP based on Andriod[J]. Computer Programming Skills and Maintenance, 2022(07):59-61.DOI:10.16184/j.cnki.comprg. 2022.07.011.
[9] Jiang Xiuyun. Adopt a perfect pet[J]. Crazy English (Xinyue Reading), 2022(07):38-39+76.
[10] Zhou Xiang. Research on emerging topic identification in App user reviews[D]. Anhui Engineering University, 2022.DOI:10.27763/d.cnki.gahgc.2022.000313.
[11] Gao Shanquan. Research on recommendation issues for Android mobile applications [D]. Jilin University, 2022.DOI:10.27162/d.cnki.gjlin.2022.000384.
[12] Zhao Xinxin. Analysis of personal information protection issues in mobile APP software [D]. Heilongjiang University, 2022.DOI:10.27123/d.cnki.ghlju.2022.000459.
[13] Li Yu. Pet adoption is also "matching" [J]. Sales and Marketing (Management Edition), 2022(03):102.
[14] Liu Bin, Li Jing. Research on technical solutions for on-site scoring App software [J]. Information Technology and Informatization, 2022(02):29-32.
[15] Jin Xin. Design and implementation of pet store online operation system based on SSM [D]. Capital University of Economics and Business, 2021. DOI: 10.27338/d.cnki.gsjmu.2021.000769.
[16]Wang Haoran. Research on Basic Programming System of Computer Science Mobile APP Software Engineering[J]. Journal of Physics: Conference Series,2021,1952(4).
[17] Zhou Fenmei, Wu Renping, Qian Ronghua, Chen Si. Pet adoption website design based on SSM [J]. Journal of Yangzhou Vocational University, 2021, 25(01): 32-35.DOI: 10.15954/j.cnki.cn32 -1529/g4.2021.01.009.
[18] Yang Qin. Design and implementation of pet adoption Web App [D]. Huazhong University of Science and Technology, 2020.DOI:10.27157/d.cnki.ghzku.2020.006892.
[19]Franc Sylvia,Hanaire Helene,Benhamou Pierre Yves,Schaepelynck Pauline,Catargi Bogdan,Farret Anne,Fontaine Pierre,Guerci Bruno,Reznik Yves,Jeandidier Nathalie,Penfornis Alfred,Borot Sophie,Chaillous Lucy,Serusclat Pierre,Kherbachi Yacine,d'Orsay Geneviève,Detournay Bruno,Simon Pierre,Charpentier Guillaume. DIABEO System Combining a Mobile App Software with and without Telemonitoring versus Standard Care: A Randomized Controlled Trial in Diabetic Patients Poorly Controlled with a Basal-Bolus Insulin Regimen.[J]. Diabetes technology & therapeutics,2020,22(12).
[20] Yang Hua. Design and implementation of pet shop information system based on SSM [D]. Jilin University, 2019.
Please follow and like + privately message the blogger to receive the project source code for free