springboo campus epidemic prevention management system
Summary
With the development of society, all walks of life in society are taking advantage of the information age. The dominance and popularity of computers necessitated the development of various information systems.
Campus epidemic prevention management, the main modules include viewing the home page, user management (administrators, operators,) more management (purchase plan, material information, classification management, storage management, storage management, supplier information, announcement information, epidemic situation data) and other functions. The administrator in the system is mainly to store and manage all kinds of information safely and effectively, and can also manage, update and maintain the system, and has corresponding operation authority on the background.
In order to realize various functions of campus epidemic prevention management, the strong support of the background database is needed. A large amount of data, such as administrators verifying registration information, collecting user information, and related information obtained through analysis, are all managed by the database management system. In this paper, the database server uses Mysql as the background database, which makes the Web and the database closely linked. During the design process, the system code is fully guaranteed to be readable, practical, easy to expand, universal, easy to maintain later, easy to operate, and the page is concise.
The development of this system makes it more convenient and quick to obtain campus epidemic prevention management information, and at the same time makes the campus epidemic prevention management information more systematic and orderly. The system interface is more friendly and easy to operate.
Keywords : campus epidemic prevention management; springboot; Mysql
Springboo campus epidemic prevention management system
Abstract
With the development of society, all walks of life are taking advantage of the advantages of the information age. The advantages and popularity of computers make the development of various information systems necessary.
The main modules of campus epidemic prevention management include viewing the home page, user management (administrator, operator) and more management (procurement plan, material information, classification management, warehousing management, outbound management, supplier information, announcement information, epidemic data), etc. The administrator in the system is mainly to store and manage all kinds of information safely and effectively. He can also manage, update and maintain the system, and has corresponding operation authority on the background.
In order to realize the functions of campus epidemic prevention management, we need the strong support of background database. The administrator verifies the registration information, collects the user information, and analyzes the related information. A large amount of data are managed by the database management system. In this paper, the database server uses MySQL as the background database to closely connect the web with the database. In the design process, the system code has the characteristics of good readability, practicability, easy expansibility, universality, convenient later maintenance, convenient operation and concise page.
The development of this system makes it more convenient to obtain the campus epidemic prevention management information. At the same time, it also makes the campus epidemic prevention management information more systematic and orderly. The system interface is friendly and easy to operate.
Key words: campus epidemic prevention management; springboot； Mysql
Table of contents
1.2 Significance of the subject 1
2 System Development Environment 2
2.3 Implementation method for accessing database 4
2.4 Two connection methods of the system to the MySQL database 4
3.1 Technical Feasibility: Technical Background 5
5. 1 Administrator function module 20
5. 2 User background function module
1 System overview
1.1 Overview
With the rapid development of society, the impact of computers is comprehensive and in-depth. With the continuous improvement of people's living standards, people's requirements for epidemic prevention and control information management in daily life are also increasing, and the number of people who need epidemic prevention and control information is increasing, making the development of campus epidemic prevention management a necessary and urgent matter. Campus epidemic prevention management mainly uses computers to increase user choices through information management required for campus epidemic prevention management, and at the same time facilitates timely query and modification of user information and timely understanding of user information. Campus epidemic prevention management brings more convenience to users, and the system meets users' needs by cooperating with database management system software.
1.2 Significance of the topic
With the development of global informatization, people's life rhythm is getting faster and faster, and they pay more and more attention to the timeliness of information. The traditional media with traditional propaganda methods as the carrier has long been unable to meet people's needs for the way and convenience of obtaining information. Therefore, campus epidemic prevention management has gradually become the focus of attention. First of all, for campus epidemic prevention management, the real-time and convenience of obtaining information online is much higher than that of traditional media. Once the system is launched, no matter where the user is in the world, as long as they can connect to the Internet, they can get the information they want in the first place.
The application of computer technology in modern management makes computer an important tool for people to apply modern technology. It can effectively solve the problem of convenient and comprehensive access to information and improve efficiency.
1.3 Main content
Campus epidemic prevention management conducts demand analysis from the aspects of function, data flow, feasibility, and operating environment. The database and functions of campus epidemic prevention management have been designed in detail. The main interface design and related component design are analyzed, and the specific implementation of campus epidemic prevention management is introduced.
Using Java technology to obtain data from the database and write data to the database, the system can directly perform various operations on the database, and add dynamic content to the web page, so as to realize various basic functions required for campus epidemic prevention management.
2 System development environment
The front-end framework of this system adopts the popular progressive JavaScript framework Vue.js. Use Vue-Router and Vuex to realize dynamic routing and global state management, Ajax to realize front-end and back-end communication, and Element UI component library to make the page quickly form. Back-end part: use springboot as the development framework, and integrate MyBatis, Redis and other related technologies at the same time.
2.1 Spring Boot framework
The Spring Framework is an open source application framework on the Java platform that provides a container with inversion of control features. Although the Spring framework itself has no restrictions on the programming model, its frequent use in Java applications made it so popular that it was later used as a supplement or even a substitute for the EJB (EnterpriseJavaBeans) model. The Spring framework provides a series of solutions for development, such as using the core features of inversion of control, and implementing inversion of control through dependency injection to realize the containerization of the management object life cycle, using aspect-oriented programming for declarative transaction management, and integrating A variety of persistence technologies manage data access, provide a large number of excellent web frameworks to facilitate development, and so on. The Spring framework has the feature of inversion of control (IOC). IOC is designed to facilitate project maintenance and testing. It provides a method for unified configuration and management of Java objects through the Java reflection mechanism. The Spring framework uses the container to manage the life cycle of objects. The container can configure objects by scanning XML files or specific Java annotations on classes. Developers can obtain objects through dependency lookup or dependency injection. The Spring framework has an aspect-oriented programming (AOP) framework. The Spring AOP framework is based on the proxy mode and is configurable at runtime. The AOP framework is mainly modularized for cross concerns between modules. The AOP framework of the Spring framework only provides basic AOP features. Although it cannot be compared with the AspectJ framework, it can also meet the basic needs through integration with AspectJ. Functions such as transaction management and remote access under the Spring framework can be realized by using Spring AOP technology. Spring's transaction management framework brings an abstraction mechanism to the Java platform that enables local and global transactions, as well as nested transactions, to work with savepoints and in almost any environment on the Java platform.
2.2 Introduction to JAVA
Java mainly adopts CORBA technology and security model, which can protect data in Internet applications. It also provides comprehensive support for EJB (Enterprise JavaBeans), java servlet API, SPRINGBOOT (java server pages), and XML technology. Java is a computer programming language with three main features of encapsulation, inheritance and polymorphism, widely used in enterprise web application development and mobile application development. The difference between the Java language and general compilers and literal translation is that Java first converts the source code into bytecode, and then converts it into an executable file for the JVM, which can run on various JVMs. Therefore, its cross-platform characteristics are realized. While this made Java very slow in its early days, it has improved as Java has been developed.
2.3 Implementation method of accessing database
(1) First introduce the basic steps of web database search on the Internet:
Step 1: Check the consumer's data,
Step 2: You have to establish a connection to the database;
Step 3: Search the database;
The fourth step: the structure of the data;
Step 5: The results for that user are shown.
(2) The system until my MYSQL5.0 PHP integrated development environment, such as using the WAMP server is powered on, and the report development environment for easier access to the database:
A connection to the MySQL database server Mysql_connect-;
Syntax: mysql_connect resource(host, username, password);
Please select the database: mysql_select_db(name of database link ID);
Close the database: then mysql_close();
2.4 Two connection methods of the system to the MySQL database
Active MySQL/MySQL library, or using the ODBC interface, the MySQL database is a two-way link. Permanent and non-permanent connections.
(1) Permanent connection: The biggest advantage of a more permanent connection request is that it can be very effective for clients to stand in close contact. When connecting to the MySQL server, it is even better. Every child in the drafting of the page is in the process, not just at any time, only during the lifetime of the connection to the MySQL server request, once connected. This subprocess is to establish a separate connection to the server which can be permanent.
(2) Non-permanent connection: it is a short circuit. The submission goes on the way to the web server, the server processes the request and the requested page you want to send to the browser client, and then the connection is broken. For most websites, it's often about being efficient by being effective, but in most cases the connection is used, but it's a full time to avoid any problems and can increase the capacity the server hosts.
2.5 MySql database
The language of Mysql is unstructured, and users can work on the data. Because the language and structure of Mysql are relatively simple, but the function and the amount of stored information are very powerful, its speed, reliability and adaptability have attracted much attention and been widely used. The role of Mysql database in the programming process is very extensive, which brings convenience for users to query data. The application characteristics of Mysql database: strong flexibility, powerful functions, and relatively concise language.
Data flow analysis is mainly a storage room for data storage, which is performed on a computer, not a storage room in reality. Database management is mainly data storage, modification and addition, and the establishment of data tables. The establishment of the data table can adjust the data in the data table, recombine and reconstruct the data to ensure the security of the data. Due to the powerful features of the database, the development of this system mainly uses Mysql to manage the data.
2.6 Main functions of Vue.js
Vue.js is a progressive framework for building user interfaces. Unlike other heavyweight frameworks, Vue is designed with bottom-up incremental development. Vue's core library only focuses on the view layer, and is very easy to learn and integrate with other libraries or existing projects. On the other hand, Vue is fully capable of driving complex single-page applications developed with single-file components and libraries supported by the Vue ecosystem.
The goal of Vue.js is to enable responsive data binding and composed view components with the simplest API possible .
Vue.js itself is not a catch-all framework - it only focuses on the view layer. So it's very easy to learn, very easy to integrate with other libraries or existing projects. On the other hand, Vue.js can also power complex single-page applications when used with related tooling and supporting libraries.
3 Demand Analysis
3.1 Technical Feasibility: Technical Background
Campus epidemic prevention management is developed and used in the Windows operating system, and the performance of the current PC is already capable of serving as a web server for ordinary websites. The technology used in system development is also owned by itself, and it is also one of the widely used technologies at present.
The development environment and configuration of the system can be installed by yourself. The system uses Java development tools and a relatively mature Mysql database for data interaction between the foreground and the background of the system. The database can be modified and maintained according to the technical language and combined with the requirements, which can make the website The operation is more stable and safe, so as to complete the development of the website.
(1) Hardware Feasibility Analysis
The design of system management and information analysis has no hard requirements for the computer used. As long as the computer can be used normally, it is feasible to write code and page design. The main reason is that there are some requirements for the server. The server to be uploaded after the platform is built is If there are certain requirements, the server must be selected with relatively high security, and then the opening of the website must be smooth, and the pause should not be too long; cost-effective; high security.
(2) Software feasibility analysis
The entire system is developed using cloud computing. The scalability of traffic and the intelligent adjustment based on traffic are the advantages of cloud computing. safe and efficient operation.
Therefore, we conducted a feasibility study from two aspects, and it can be seen that there is no problem in the development of the system.
3.2 Economic feasibility
There is no cost for the market research and other related management systems before the development of campus epidemic prevention management . All research is done by the developers themselves, and all work is done by themselves. When encountering problems that are difficult to solve, most of them solve related problems with the help of instructors and classmates. Therefore, the development of campus epidemic prevention management is completely feasible economically, without any expenses.
Using relatively mature technology, the system is developed based on Java and uses Mysql database. Therefore, the system does not require high manpower and financial resources for development, and is economically feasible.
3.3 Operation Feasibility:
The operability is mainly for the user experience after the campus epidemic prevention management design is completed, and the administrator can manage relevant data information through the system at any time, and for the two roles of administrator and user, they can easily and clearly enter the With its own system interface, the functional modules can be operated simply and clearly through the interface navigation menu, which is convenient for the operation needs of user information and administrators to manage data information. For the operation of the system, the operation and management of functional modules can be directly carried out without professionals, so the operability of campus epidemic prevention management is completely possible. The operation of this system also uses the interface window to log in, so the operator only needs to know simple computer operations.
3.4 System Design Rules
The campus epidemic prevention management adopts Java technology and Mysql database development, which fully guarantees the stability and integrity of the system.
The design idea of campus epidemic prevention management design and realization is as follows:
The operation is simple and convenient, and the system interface is safe and sound: the simple and clear page layout makes it easy to query relevant information on campus epidemic prevention management.
2. Immediately visible: The processing of the campus epidemic prevention management information will be immediately available in the corresponding location, so as to realize the system function of "instant release, instant effect".
3. Completeness of functions: can manage the home page, user management (administrator, operator,) more management (purchase plan, material information, classification management, storage management, storage management, supplier information, announcement information, epidemic situation data) modification and maintenance operations of the system management module.
3.5 System flow and logic
System business flow chart, as shown in the figure:
Figure 3-1 Login flow chart
Figure 3-2 Flowchart of adding information
Figure 3-3 Registration Information Flowchart
4 System Outline Design
4.1 Overview
Campus epidemic prevention management is based on the Web service model, which is a model structure suitable for the Internet environment. As long as users can connect to the Internet, they can use the system without time and place restrictions. The working principle diagram of campus epidemic prevention management is shown in Figure 4-1:
Figure 4-1 System working principle diagram
4.2 System structure
The system architecture website system, the specific functions of this system are as follows:
Figure 4-2 System function structure diagram
The whole system is composed of multiple functional modules. All the functional modules should be listed one by one, and then the functional design should be carried out one by one, so that each module has a corresponding functional design, and then the overall design of the system can be carried out. .
System function structure diagram, as shown in Figure 4-3:
Figure 4-3 Administrator function structure diagram
4.3. Database design
4.3.1 Database entities
The administrator information structure diagram is shown in Figure 4-5:
Figure 4-5 Structural diagram of administrator information entity
User information entity attribute diagram, as shown in Figure 4-6:
Figure 4-6 User information entity attribute diagram
The attribute diagram of the procurement plan entity is shown in Figure 4-7.
Figure 4-7 Procurement plan entity attribute diagram
The attribute diagram of material information management entity is shown in Figure 4-8.
Figure 4-8 Material information management entity attribute diagram
4.3.2 Database Design Table
4. 4 Data Sheet
Convert ER diagram of database conceptual design into relational database. In a relational database, the data relationship is composed of data tables, but the structure of the table is expressed in the fields of the table.
| classification_management |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| classification_management_id |
int |
11 |
no |
primary key |
Category Management ID |
| material_classification |
varchar |
64 |
yes |
Material classification |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| epidemic_data |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| epidemic_data_id |
int |
11 |
no |
primary key |
Epidemic data ID |
| title_name |
varchar |
64 |
yes |
title name |
|
| release_time |
datetime |
0 |
yes |
release time |
|
| data_picture |
varchar |
255 |
yes |
data picture |
|
| details |
text |
0 |
yes |
details |
|
| remark_information |
text |
0 |
yes |
Remarks |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| material_information |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| material_information_id |
int |
11 |
no |
primary key |
material information ID |
| item_no |
varchar |
64 |
yes |
Material number |
|
| material_name |
varchar |
64 |
yes |
Material name |
|
| material_classification |
varchar |
64 |
yes |
Material classification |
|
| material_picture |
varchar |
255 |
yes |
Materials picture |
|
| material_inventory |
int |
11 |
yes |
Material inventory |
|
| storage_location |
text |
0 |
yes |
Storage location |
|
| material_description |
text |
0 |
yes |
Material description |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| operator |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| operator_id |
int |
11 |
no |
primary key |
operator ID |
| full_name |
varchar |
64 |
yes |
Name |
|
| gender |
varchar |
64 |
yes |
gender |
|
| examine_state |
varchar |
16 |
no |
Approval Status |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| user_id |
int |
11 |
no |
User ID |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| outbound_management |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| outbound_management_id |
int |
11 |
no |
primary key |
Outbound Management ID |
| item_no |
varchar |
64 |
yes |
Material number |
|
| material_name |
varchar |
64 |
yes |
Material name |
|
| material_classification |
varchar |
64 |
yes |
Material classification |
|
| operator |
int |
11 |
yes |
Operator |
|
| outbound_quantity |
int |
11 |
yes |
Outbound quantity |
|
| ex_warehouse_remarks |
text |
0 |
yes |
Remarks |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| procurement_plan |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| procurement_plan_id |
int |
11 |
no |
primary key |
Procurement Plan ID |
| material_name |
varchar |
64 |
yes |
Material name |
|
| purchase_quantity |
varchar |
64 |
yes |
Purchase quantity |
|
| purchase_date |
date |
0 |
yes |
purchase date |
|
| operator |
int |
11 |
yes |
Operator |
|
| purchase_contract |
varchar |
255 |
yes |
contract of purchase |
|
| approval_status |
varchar |
64 |
yes |
Approval Status |
|
| approval_reply |
text |
0 |
yes |
approval reply |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| supplier_information |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| supplier_information_id |
int |
11 |
no |
primary key |
Supplier Information ID |
| supplier_name |
varchar |
64 |
yes |
Supplier name |
|
| representative |
varchar |
64 |
yes |
representative |
|
| contact_number |
varchar |
16 |
yes |
contact number |
|
| supplier_address |
text |
0 |
yes |
supplier address |
|
| supplier_description |
text |
0 |
yes |
Supplier description |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| warehousing_management |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| warehousing_management_id |
int |
11 |
no |
primary key |
Inbound Management ID |
| item_no |
varchar |
64 |
yes |
Material number |
|
| material_name |
varchar |
64 |
yes |
Material name |
|
| material_classification |
varchar |
64 |
yes |
Material classification |
|
| operator |
int |
11 |
yes |
Operator |
|
| receipt_quantity |
int |
11 |
yes |
Storage quantity |
|
| warehousing_remarks |
text |
0 |
yes |
Storage remarks |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
5 System detailed design
5.1 Administrator function module
管理员登录，管理员通过输入用户，密码，角色等信息进行系统登录，如图5-1所示。
图5-1管理员登录界面图
管理员登录进入校园防疫管理可以查看管理员：首页、用户管理（管理员、操作员、）更多管理（采购计划、物资信息、分类管理、入库管理、出库管理、供应商信息、公告信息、疫情数据）等内容，如图5-2所示。
图5-2管理员功能界面图
用户管理，在用户管理页面可以查看等索引、用户账号、密码、用户姓名、性别、年龄、联系电话、电子邮箱、身份证号、个人照片等信息，并可根据需要进行修改或删除等操作，如图5-3所示。
图5-3用户管理界面图
采购计划，在采购计划页面可以查看索引、物资名称、采购数量、采购日期、操作人、采购合同等信息，并可根据需要进行修改或删除等操作，如图5-4所示。
图5-4采购计划界面图
物资信息，在物资信息页面可以查看索引、物资编号、物资分类、物资图片、物资库存、存放位置、物资描述等信息，并可根据需要进行修改或删除等操作，如图5-5所示。
图5-5物资信息界面图
入库管理，在入库管理页面可以查看索引、物资名称、物资分类、操作人、入库数量、入库备注等信息，并可根据需要进行修改或删除等操作，如图5-6所示。
图5-6入库管理界面图
公告信息，在公告信息页面可以查看索引、公告标题、发布时间、公告内容、备注信息、创建时间等信息，并可根据需要进行修改或删除等操作，如图5-6所示。
图5-7接种预约界面图
5.2用户后台功能模块
用户注册，在用户注册页面通过填写用户账号、密码、用户姓名、年龄、联系电话、电子邮箱、身份证号、家庭地址等信息完成用户注册，如图5-8所示。
图5-8用户注册界面图
用户登录进入后台可以查看首页、采购计划、物资信息、入库管理、出库管理、供应商信息、公告信息、疫情数据等内容，如图5-9所示。
图5-9用户功能界面图
物资信息，在物资信息页面通过填写物资编号、物资分类、物资图片、物资库存、存放位置、物资描述等信息进行操作，如图5-10所示。
图5-10物资信息界面图
供应商信息管理，在供应商信息管理页面可以查看索引、供应商名称、代表人、联系电话、供应商地址、供应商描述等信息进行操作，如图5-11所示。
图5-11供应商信息界面图
疫情数据管理，在疫情数据管理页面可以查看索引、标题名称、发布时间、数据图片、详细内容、备注信息、创建时间等信息，如图5-12所示。
图5-12接种信息界面图
6 系统测试
6.1系统测试的目的
程序设计不能保证没有错误，这是一个开发过程，在错误或错误的过程中都是难以避免的。虽然这是不可避免的，但我们不能使这些错误始终存在于系统中，错误可能会造成无法估量的后果，如系统崩溃，安全信息泄露，系统无法正常启动等，为了避免这些问题我们需要测试程序，在测试过程中发现问题并纠正它们，从而使系统更长时间稳定成熟。
本章的作用是发现这些问题，并对其进行修改，虽然耗时费力，但对于长期使用而言是非常重要和必要系统的开发。
软件在设计后必须进行测试，调试过程中使用的方法是软件测试方法。在开发新软件时，系统测试是检查软件是否合格的关键步骤，以及是否符合设计目标的参考。测试主要是查看软件中数据的准确性，正确的操作与否，以及操作的结果，还有哪些方面需要改进。
校园防疫管理的实现，对于系统中功能模块的实现及操作都必须通过测试进行来评判系统是否可以准确的实现。在校园防疫管理正式上传使用之前必须做的一步就是系统测试，对于测试发现的错误及时修改处理，保证系统准确无误的供给用户使用。
6.2系统测试方法
在对校园防疫管理进行测试的时候在找到问题的情况下必须在第一时间找到解决问题的办法，不要存在侥幸的心理，这样才能让疫情防控信息管理开发的质量可以过关，并且开发的周期会大大缩短，还有就是在测试时，不要出现重复性的错误，遇到一个错误问题，要将整个校园防疫管理开发所牵扯的该问题都必须一一解决，提高疫情防控信息管理平台的安全性、稳定性。
白盒测试与黑盒测试是测试中比较常用的两种方法。
①结构测试俗称白盒测试：这种测试是在对程序的处理过程与结构都有详尽谅解的前提下，顺从程序内部的逻辑而完成的系统测试，以确定系统中所有的通路都能够遵照设计要求正常工作，不出现任何偏差。
②功能测试又成黑盒测试：主要是针对程序功能能够按照设计正常实现的一种检测，在程序接口处进行，检测程序手法数据是否正常，与外部信息的交换是否完整。
6.3测试过程
在软件的测试过程中，通常测试人员需要针对不同的功能模块设计多种测试用例。通过测试用例能够及时发现代码业务逻辑上是否与真实的业务逻辑相对应，及时发现代码上或逻辑上的缺陷，以此来来完善系统，提高软件产品的质量，使软件具有良好的用户体验。
注册测试用例表如下所示。
表6-1注册测试用例
| 测试性能 |
新用户注册 |
||
| 用例目的 |
测试系统新用户个人信息注册功能的功能和安全性 |
||
| 前提条件 |
进入注册页面填写个人信息 |
||
| 输入条件 |
预期输出 |
实际情况 |
|
| 各项基本信息输入不完整 |
不允许注册，无法点击注册按钮 |
一致 |
|
| 填写已存在的用户名 |
系统显示出提示信息，要求重新填写 |
一致 |
|
| 两次密码输入不一致 |
系统显示出提示信息，要求重新填写 |
一致 |
|
| 填写的各项信息没有符合提示的长度和字符要求 |
系统显示出提示信息，要求重新填写 |
一致 |
|
| 胡乱填写电话号码 |
收不到验证码 |
一致 |
|
| 填写验证码与收到的不一致 |
系统显示提示信息告知用户验证码错误，不予注册 |
一致 |
|
登录测试用例表如下所示。
表6-2登录测试用例
| 测试性能 |
用户或操作员登录系统 |
||
| 用例目的 |
测试用户或操作员登录系统时功能是否正常 |
||
| 前提条件 |
进入用户登录页面或操作员登录页面 |
||
| 输入条件 |
预期输出 |
实际情况 |
|
| 各项信息不予填写，直接点击登陆按钮 |
不允许登录，提示填写账号相关信息 |
一致 |
|
| 填写错误的登录名或密码后点击登录系统 |
提示用户名或密码错误，要求重新填写进行登录 |
一致 |
|
| 填写与验证码信息不一致的信息 |
系统显示出提示信息，表明验证码错误，要求重新填写 |
一致 |
|
6.4 测试结果
经过对一系列测试结果的有效分析，本平台开发系统符合用户的要求和需求。所有的基本功能相对齐全，操作起来简单方便，测试系统性能良好，作为大众化系统使用是比较值得推广宣传的。
结论
本系统通过对java和Mysql数据库的简介，从硬件和软件两反面说明了校园防疫管理的可行性，本文结论及研究成果如下：实现了java与Mysql相结合构建的校园防疫管理，网站可以响应式展示。通过本次校园防疫管理的研究与实现，我感到学海无涯，学习是没有终点的，而且实践出真知，只有多动手才能尽快掌握它，经验对系统的开发非常重要，经验不足，就难免会有许多考虑不周之处。比如要有美观的界面，更完善的功能，才能吸引更多的用户。
由于在此之前对于java知识没有深入了解，所以从一开始就碰到许多困难，例如一开始的页面显示不规范、数据库连接有问题已经无法实现参数的传递等等，不过通过在网上寻找有关资料以及同学的帮助下最后都得到了解决，在此过程中，我不仅学到了很多知识，也提高了自己解决问题的能力，尤其是学会如何从大量的信息中筛选出所需有用的信息，同时我更加深刻的体会到了，虽然书本上的大部分知识都是有价值，正确的，但实际上每个人编程的思路和对数据处理的方法、思想都是不同的，这就要求我们一定要通过实践才能找到解决问题的方案。在此次毕业设计活动中，我不断的提高了自己，也得到了宝贵的经验，我相信这些对我以后的发展都会有很大帮助。
通过这次校园防疫管理的开发，我参考了很多相关系统的例子，取长补短，吸取了其他系统的长处，逐步对该系统进行了完善，但是该系统还是有很多的不足之处，有待以后进一步学习。
实践证明，校园防疫管理有着非常好的发展前景，经过测试运行，系统各项功能都十分完善，界面漂亮，使用方便，操作容易，在技术理论上已经成熟。
致 谢
毕业设计结束的同时也意味着四年的大学生活就要结束了。校园防疫管理的完成以及如何在系统运行过程中实现的更好，这其中付出了很大的努力，这段时光将会终身难忘。
在毕业设计的这一段时间里，离不开导师的细心指导，还有同学们的热情帮助，有时候几个同学在一起讨论系统中的某个功能模块如何实现，如何实现的更好，或是问题没得到有效的解决，就会没有心思做其他的事情，让我们对学习充满了动力。
在毕业设计即将结束之时，首先要感谢我的指导老师，谢谢您在毕业设计和毕业论文中对我的指导。在您的细心指导下我才能快速的掌握系统的相关功能，在您的大力帮助下我才能将课本上的知识与自己的项目结合，真正的做到学以致用。感谢您经常牺牲自己的休息时间，利用其丰富的教学和项目经验对我进行指导。课堂上，您教会我们如何学习、教会我们新的知识，在课下，您又像朋友一样亲切，教会了我很多道理，让我意识到先做人、后做事。感谢所有教过我的老师，为我倾注了大量的心血，正是你们的谆谆教诲、严谨教学才使我能顺利的完成学业，再此向你们表示深深的感谢。感谢大学里教过我的每一位老师，真心祝福您们。
在这里还得感谢我的战友们，也就是同学们对我的大力支持及帮助。正是因为有你们的不断帮助、鼓励，熬夜通宵，不停的调试、测试程序，给我带来了极大的动力，才能最终完成网站的运行。我们在一起交流、谈论的时光，都将是我们在通往未来道路上的宝贵财富。我要深深地感谢你们！
毕业在即，在今后的工作和生活中，我会铭记师长们的教诲、同学们的帮助，继续不懈努力和追求，来报答所有支持和帮助过我的人！
最后，我要向牺牲了休息时间来对本文进行审阅，评议和参与论文答辩的各位老师表示深深的感谢。在此，衷心的谢谢您们！
参考文献
[1]徐佩.新时期计算机软件开发技术的应用及发展趋势[J].农家参谋,2019(08):167.
[2]张帅,崔婀娜,魏立波.互联网+健康在线服务平台的设计与实现[J].科技创新与应用,2019(10):91-92.
[3]谷利国,陈存田,张甲瑞.基于B/S模式的人事教育信息管理系统的分析与设计[J].电脑知识与技术,2019,15(10):58-59.
[4]胥新政,强毅.基于JSP的常用金属材料标准检索平台开发设计[J].制造业自动化,2019,41(03):41-43+69.
[5]王祖维,南淮耀,张英.“互联网+”视域下的高校学生公寓管理系统设计与实现——以沈阳师范大学为例[J].现代商贸工业,2019,40(08):187-188.
[6]廖明华,齐攀.学生职业能力测评管理系统的设计与实现[J].广东交通职业技术学院学报,2019,18(01):48-52.
[7]李冬冬,刘华明,毕学慧,王秀友.旧衣申领系统的设计与实现[J].电脑知识与技术,2019,15(08):47-50.
[8]李庆年.“互联网+”视域下的人才招聘管理系统设计与实现[J].国际公关,2019(03):164-165.
[9]刘婷,彭焕峰,邵淑婷.基于云平台的高校监考管理系统[J].电脑知识与技术,2019,15(07):91-92.
[10]赵丙秀.基于百度AI平台的Web人脸注册和登录系统的实现[J].电脑知识与技术,2019,15(07):114-115.
[11]戴昭颖,尹涛.钢铁行业成本预算系统开发应用实践[J].电子技术与软件工程,2019(04):29-30.
[12]曹灿,刘志刚.基于SSH和Layui的工程科学前沿与实践系统[J].工业控制计算机,2019,32(02):91-92+96.
[13]谢路.基于Web的考务管理系统设计与实现[J].福建电脑,2019,35(01):136-137.
[14]张继东.MySQL数据库基于JSP的访问技术[J/OL].电子技术与软件工程,2017,(15):169(2017-08-03).
[15]韩思凡.Web开发中的JSP与HTML的基础应用[J].科学技术创新,2020(14):71-72.
[16]NastitiAndini,DaehaKim,JongAhnChun.Operationalsoilmoisturemodelingusingamulti-stageapproachbasedonthegeneralizedcomplementaryprinciple[J].AgriculturalWaterManagement,2020,231.
[17]ADTisari,D.Phillips,IWWarmada,Hartono,A.Idrus.40Ar/39ArgeochronologyofthePongkorlowsulfidationepithermalgoldmineralisation,WestJava,Indonesia[J].OreGeologyReviews,2020,119.
[18]FranciscoOrtin,OscarRodriguez-Prieto,NicolasPascual,MiguelGarcia.HeterogeneoustreestructureclassificationtolabelJavaprogrammersaccordingtotheirexpertiselevel[J].FutureGenerationComputerSystems,2020,105.
[19]SatyaKrismatama,IndahRiyantini,IwangGumilar,LantunParadhitaDewanti.SelectivityofFishingGearforScomberomorusguttatus(Bloch&Schneider,1801)CommoditiesinPangandaranFishingGround,WestJava[J].AsianJournalofFisheriesandAquaticResearch,2020.
[20]ZhongXiangfu,PlaAlbert,RaynerSimon.Jasmine:aJavapipelineforisomiRcharacterizationinmiRNA-Seqdata[J].Bioinformatics,2020
Like+Favorite+Follow → private message to receive the source code and database