Note: Show part of the document content and system screenshots. If you need complete videos, codes, articles and installation and debugging environment, please send a private message to the up owner.
4.2 System function module design
The purpose of system function module design is to complete the functions required in the early requirements analysis stage. By designing different functional modules for different users. This system divides users into three roles: administrator, user administrator and user. When different roles log in to the system, they are given different functions. Then, for each type of role, the system functions implemented, the interface displayed and the required The logic is designed to realize the implementation of different system function modules for different users.
In software development, it is not only necessary to ensure users' functional requirements for the system, but also to ensure good interaction between the system and users. Therefore, in the design of the software, functional components are designed with emphasis. From its initial conception, this system is based on meeting the basic needs of prevention and control information management and has universal applicability. In this way, the system will be divided into more small pieces, which can be modified and maintained by managers according to their own needs, and then further subdivided into functional modules according to the different needs of different users.
Based on the modular design concept, the prevention and control information management system has expanded the management module for managers. The prevention and control information management system has designed three types of roles: user, user administrator, and administrator. The overall functional structure of the system is shown in Figure 4.1. Show.
4.4.2 Logic design
This system uses the MySQL database to store data. The specific display part of the main data tables used in the system is as follows.
Table 4.1 Users
Field Name |
type |
length |
primary key |
Field description |
id |
bigint |
primary key |
primary key |
|
addtime |
timestamp |
creation time |
||
yonghuzhanghao |
varchar |
200 |
user account |
|
yonghuxingming |
varchar |
200 |
username |
|
mima |
varchar |
200 |
password |
|
shoujihaoma |
varchar |
200 |
phone number |
|
touxiang |
varchar |
200 |
avatar |
|
xingbie |
varchar |
200 |
gender |
|
youxiang |
varchar |
200 |
|
|
zhuzhi |
varchar |
200 |
address |
Table 4.2 Administrator table
Field Name |
type |
length |
primary key |
Field description |
id |
bigint |
primary key |
primary key |
|
username |
varchar |
100 |
username |
|
password |
varchar |
100 |
password |
|
role |
varchar |
100 |
Role |
|
addtime |
timestamp |
Add time |
Table 4.3 token table
Field Name |
type |
length |
primary key |
Field description |
id |
bigint |
primary key |
primary key |
|
userid |
bigint |
user id |
||
username |
varchar |
100 |
username |
|
tablename |
varchar |
100 |
Table Name |
|
role |
varchar |
100 |
Role |
|
token |
varchar |
200 |
password |
|
addtime |
timestamp |
Add time |
||
expiratedtime |
timestamp |
Expiration |
Table 4.4 Close contacts
Field Name |
type |
length |
primary key |
Field description |
id |
bigint |
primary key |
primary key |
|
addtime |
timestamp |
creation time |
||
yonghuzhanghao |
varchar |
200 |
user account |
|
yonghuxingming |
varchar |
200 |
username |
|
xingbie |
varchar |
200 |
gender |
|
shenfenzheng |
varchar |
200 |
ID card |
|
zhuzhi |
varchar |
200 |
address |
|
jiechulaiyuan |
varchar |
200 |
source of exposure |
|
gelidizhi |
varchar |
200 |
quarantine address |
|
gelikaishiriqi |
date |
Quarantine start date |
||
gengxinshijian |
date |
Update time |
||
xiangqing |
longtext |
4294967295 |
Details |
|
guanlizhanghao |
varchar |
200 |
Manage account |
|
guanlixingming |
varchar |
200 |
Admin name |
Table 4.5 Diagnosis information
Field Name |
type |
length |
primary key |
Field description |
id |
bigint |
primary key |
primary key |
|
addtime |
timestamp |
creation time |
||
quezhenbianhao |
varchar |
200 |
Confirmation number |
|
yonghuzhanghao |
varchar |
200 |
user account |
|
yonghuxingming |
varchar |
200 |
username |
|
xingbie |
varchar |
200 |
gender |
|
shenfenzheng |
varchar |
200 |
ID card |
|
zhuzhi |
varchar |
200 |
address |
|
zhuyuanriqi |
date |
Date of hospitalization |
||
ganranlaiyuan |
varchar |
200 |
Source of infection |
|
xiangqing |
longtext |
4294967295 |
Details |
|
quezhenshijian |
date |
Diagnosis time |
||
guanlizhanghao |
varchar |
200 |
Manage account |
|
guanlixingming |
varchar |
200 |
Admin name |
Table 4.6 Epidemic Announcement
Field Name |
type |
length |
primary key |
Field description |
id |
bigint |
primary key |
primary key |
|
addtime |
timestamp |
creation time |
||
title |
varchar |
200 |
title |
|
introduction |
longtext |
4294967295 |
Introduction |
|
picture |
varchar |
200 |
picture |
|
content |
longtext |
4294967295 |
content |
Chapter 5 System Implementation
5.1 Front desk function module
When any user accesses the prevention and control information management system, they will enter a front-end web page that can be displayed without logging in. This page has functional modules such as home page, epidemic information, vaccination, nucleic acid testing, epidemic announcements, and back-end management. The front page is a display of prevention and control information. You can view epidemic information, vaccination, nucleic acid testing, epidemic announcements and other information at once by sliding the scroll bar. The interface is shown in Figure 5.1.
5.1.1 Epidemic information module
Through this module, you can view the detailed information of the current prevention and control, including confirmed diagnosis, isolation, cure, death and other information, as shown in Figure 5.2.
5.3.5 Epidemic prevention material management
The epidemic prevention material management module is a module required by administrators to manage the distribution of materials. This module contains material classification, material name, material description and other information. This module can add, delete, modify and check the information of epidemic prevention materials, and perform fuzzy queries based on the name of the material during query. The implementation is shown in Figure 5.10.
1.4 Research content of the paper
Chapter 2 Related Technologies
2.1 Introduction to Java technology
2.4 Eclipse development environment
3.1 System feasibility analysis
3.3 Functional requirements analysis
3.4 Non-functional requirements analysis
4.1 Design concepts and principles
4.2 System function module design
Chapter 5 System Implementation
5.1 Front desk function module
5.1.1 Epidemic information module
5.1.3 Nucleic acid detection module
5.1.4 Backend management module
5.2 Administrator function module
5.3.3 Epidemic information management
5.3.5 Epidemic prevention material management
5.3.5 Infection source management
5.4 User administrator function module
5.4.2 Health check-in management
5.4.3 Close contact management
5.4.4 Diagnosis information management