Health check-in system for college students based on springboot
Summary
On December 19, 2019, the first case of the new coronavirus occurred in Wuhan, China. Everyone is following the government's call to isolate at home, whether in the city or in a town or village. Check-in system, epidemic prevention and control requires everyone to work together and unite to popularize and educate campus students on the prevention and control of new coronavirus pneumonia, through campus bulletin boards, posting leaflets in corridors, campus radio daily loop broadcasts, campus WeChat groups, etc. In various forms, from the five aspects of personal protection knowledge, campus protection knowledge, protection knowledge when going out to public places, medical knowledge of new coronavirus pneumonia, and medical treatment procedures, targeted epidemic prevention knowledge is popularized to school students. The best way to fully realize the prevention and control of the epidemic is that everyone knows and everyone participates in understanding the horror of the virus, and the best way is to establish and manage the platform information of the campus.
The system adopts Java technology, adopts browser interaction mode for all business modules, selects MySQL as the system database, and selects My eclipse as the development tool to design the system. Basically realized the main functional modules of the college students' health check-in system. The system has administrators, teachers, and students. Administrator: Administrator: home page, user management (administrators, teachers, students) and more management (class management, notice announcements, daily schedule, daily check-in, student leave, student diary, epidemic report). Teachers; Teachers: homepage, student management, notification announcements, daily schedule, daily check-in, student leave, student diary, epidemic report. Students: home page, notice announcement, daily schedule, daily check-in, student leave, student diary, epidemic reporting management, etc.
After testing the system, the program logic and code were improved. At the same time, ensure that all programs in the system can run normally, all functions can be operated, and the system has a good operating experience, achieving a win-win situation for college student health check-in system for student management, teacher management, and government departments.
Keywords: data communication; Java language; data storage
College Students' health punch in system based on springboot
Abstract
The first COVID-19 came to China in December 19, 2019. Everyone is following the government's call to isolate at home. Whether in city or in town or countryside, this has attracted my attention. A closed management system for students' epidemic situation has been designed. The epidemic prevention and control needs concerted efforts of the whole family. The Wuhan campus has carried out the popularization and education of New Coronavirus pneumonia prevention and control through campus bulletin boards. A variety of forms such as flyers, campus circular daily broadcast, campus WeChat group and so on are publicized on the corridor, from the five aspects of personal protection knowledge, campus protection knowledge, knowledge of public places, knowledge of New Coronavirus pneumonia, and medical treatment process, aiming to popularize epidemic prevention knowledge among students at school. The best way to fully realize that everyone knows and participates in the prevention and control of the epidemic and understand the terrible of the virus is to establish the platform information of the campus and manage it.
The system adopts Java technology, adopts the mode of browser interaction for all business modules, selects MySQL as the database of the system, and selects my eclipse as the development tool to design the system. Basically realized the main functional modules of the student epidemic closed management system. The system has administrators, teachers and students. Administrator: Administrator: home page, user management (administrator, teacher, student) and more management (class management, notice and announcement, daily arrangement, daily clock in, student leave, student diary, epidemic reporting). teacher; Teacher: homepage, student management, notice and announcement, daily arrangement, daily clock in, student leave, student diary, epidemic report. student; Home page, notice and announcement, daily arrangement, daily clock in, student leave, student diary, epidemic reporting management, etc.
After testing the system, the program logic and code are improved. At the same time, it ensures that all programs in the system can operate normally and all functions can be operated, and the system has a good operation experience, which realizes the win-win of the closed management system for students, teachers and government departments.
Keywords: data communication; Java language; data storage
Table of contents
Chapter 2 Introduction to Related Technologies
2.5 Introduction to SSM framework
3.1.1 Technical Feasibility Analysis
3.1.2 Economic Feasibility Analysis
3.1.3 Operation Feasibility Analysis
3.2 Analysis of Functional Requirements
4.1 System architecture design
Chapter 5 System Implementation
5.1 Implementation of login module
5.3 Implementation of the administrator subsystem module
5.3.1 Student Management Module
5.3.2 Daily schedule management module
Due to the sudden arrival of the new crown virus, the pressure on the community has increased, and the knowledge of epidemic prevention among students has not been popularized, and students do not know how to deal with it. With the strong support of the government, students in need can be cared for by the campus.
In recent years, with the continuous development of my country's economy, there are more and more management systems for platforms. Each college student health check-in system will also carry out the overall intelligent operation through the computer. The data involved in the function of the college student health check-in system is all related to the data information content of the college student health check-in system and can be managed by students. Staff can select administrators through online processing, which can be assigned through the system. Traditional epidemic prevention methods and information can no longer meet the needs of students. To this end, the university student health check-in system has been developed to provide students with a management based on the university student health check-in system, and at the same time it is convenient for administrators to understand the situation online. Administrators can manage the home page and users (administrators, teachers, students) through the system Management (class management, notice announcement, daily schedule, daily check-in, student leave, student diary, epidemic report) and other detailed operations. The system meets the needs of students for obtaining information from the health check-in system of college students, and the information can be viewed in a timely, accurate and effective manner and work in a systematic, standardized and effective manner.
With the development of society and the advancement of science and technology, Internet technology is becoming more and more popular. The lifestyle of network communication is gradually loved by the broad masses of the people. More and more Internet enthusiasts have begun to meet their basic needs on the Internet, and at the same time gradually enter the daily life of various residents. Internet has many advantages such as convenience, speed, high efficiency and low cost. Therefore, similar to the student health check-in system in colleges and universities, meeting the needs of students for epidemic prevention and control knowledge is not only a way for students to view information at any time, but also improves management efficiency.
This paper first takes the basic problems of the health check-in system process of college students as the research object. Before developing the system, we conducted a detailed investigation and analysis of the existing situation. Finally, we use computer technology to develop a complete and suitable closed management system for college students’ epidemic situation in school. The main advantages of this system are: the system is mainly developed by computer technology, and it is convenient and fast; the system can view students, All information management of teachers.
College student health check-in system is a convenient, fast and practical information service query software. With the continuous popularization of intelligent networks in the global market and the use of various intelligent platforms, the development of the system is related to the daily needs of students in school. As a mainstream intelligent technology development system in China, such software is naturally needed to meet the needs of more students. needs and experiences.
1.3 Research content
The development and implementation of the health check-in system for college students requires the following tasks:
(1) First of all, determine the topic, determine the system to be built, and conduct a preliminary systematic confirmation of the background of the system and some problems currently facing it.
(2) After the system confirmation is completed, the technology used for system development shall be confirmed in combination with the needs of system development. The development of the student health check-in system in this university uses JAVA technology, and the database is used for platform construction and development, and the technology used is confirmed for technical analysis. Whether the technology used can complete the realization of the health check-in system for college students.
(3) Determine the technology used by the system, confirm the student roles divided by the system online, and determine the functional modules to be designed according to the division of student roles. The design of the health check-in system for college students is mainly divided into administrators, teachers, and students. The three roles and the functional modules used are also correspondingly different, but the content realized by the database of the system is interactive. Students and teachers can check the epidemic information according to their own needs at any time, and the administrator can obtain detailed data of all students and teachers. Information, and according to the needs of the first time to deal with solutions.
(4) Design the program and interface after the functional modules of the system are confirmed. The test method finds out the loopholes in the program, and solves the loopholes in the program online. If there is no problem in the test system, the system can be uploaded for formal operation.
The front-end part of the system is developed based on the MVVM model, using the B/S model, and the back-end part is developed based on the Java ssm framework.
Front-end part: The front-end framework adopts the popular progressive JavaScript framework Vue.js. Use Vue-Router and Vuex to achieve dynamic routing and global state management, Ajax to achieve front-end and back-end communication, Element UI component library to make the page quickly prototype, and the front-end of the project realizes responsiveness through grid layout, which can be adapted to PC, tablet, mobile, etc. Perfect layout display for different screen sizes.
Back-end part: use ssm as the development framework, and integrate MyBatis, Redis and other related technologies at the same time.
MVVM is shorthand for Model-View-ViewModel. It's essentially an improved version of MVC. MVVM is to abstract the state and behavior of the View in it, and let us separate the view UI from the business logic. Of course, ViewModel has already done these things for us. It can take out the data of Model and help deal with the business logic involved in View because of the need to display content. Microsoft's WPF brings new technical experience, such as Silverlight, audio , video , 3D , animation ..., which leads to more detailed and customizable software UI layer. At the same time, at the technical level, WPF also brings new features such as Binding, Dependency Property, Routed Events, Command, DataTemplate, and ControlTemplate. The origin of the MVVM (Model-View-ViewModel) framework is a new type of architectural framework developed and evolved from the application of the MVP (Model-View-Presenter) pattern combined with WPF . It is based on the original MVP framework and incorporates the new features of WPF to cope with the increasingly complex needs of customers.
The advancement of science and technology has brought many conveniences to daily life: classroom projectors use virtual imaging technology, digital cameras use photoelectric detection technology, for example, the records of goods entering and leaving warehouses in supermarkets require an information warehouse. This information warehouse is the database, and this time the health check-in system for college students also needs the support of this technology.
The reason for using the MySQL software is that it can be accessed by multiple users, and there are Archives, etc. in it. It will classify the data first, and then store them in tables separately. Such special operations will improve the speed of the data management system itself, allowing the database to be used flexibly. The code of MySQL is public, and allows others to compile and upgrade it twice. This feature can reduce the cost of users, and form a good website system after matching with suitable software. Although it has shortcomings, it is the mainstream application object of users in all aspects.
B/S (Browser/Server) is a more convenient architecture than its predecessor architecture. It uses the Web server to complete the data transfer and exchange. You only need to download the browser as the client, then the work will achieve the effect of "slimming", and there is no need to consider the problem of non-stop installation of software [9].
The SSM (Spring+SpringMVC+MyBatis) framework set is composed of two open source frameworks, Spring and MyBatis (SpringMVC is part of Spring). Often used as a framework for web projects with simpler data sources.
1.6.1 Spring
Spring is like a large factory for assembling beans in the entire project. In the configuration file, you can specify specific parameters to call the constructor 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), that is, programmers are no longer required to explicitly `new` an object, but let the Spring framework do it for you.
1.6.2 SpringMVC
SpringMVC intercepts user requests in the project. Its core Servlet, DispatcherServlet, assumes the role of intermediary or front desk, and matches user requests with the Controller through HandlerMapping. The Controller is the specific operation performed by the corresponding request. SpringMVC is equivalent to struts in the SSH framework.
1.6.3 Mybot
mybatis is an encapsulation of jdbc, which makes the underlying operation of the database transparent. The operations of mybatis revolve around a sqlSessionFactory instance. Mybatis is associated to the Mapper file of each entity class through the configuration file. The Mapper file configures the SQL statement mapping required by 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 to process the logic, the logic layer sends the request to the persistence layer, the persistence layer interacts with the database, and 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.
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.
The development environment and configuration of the system can be installed by yourself. The system is developed using the ssm framework, and the relatively mature Mysql database is used to interact with the relevant data between the foreground and the background of the system. The database is modified and maintained according to the technical language and combined with the requirements. It can make the system operation more stable and safe, so as to complete the development of the realization system.
The so-called technical feasibility refers to whether the functions planned in the early stage can be satisfied within a limited time. Whether there will be problems that cannot be solved in the development and design. Whether the completed project can be well applied, if there are shortcomings, whether there is great difficulty in later maintenance. After evaluating the system, it was determined that existing technology could achieve the goals. Using java technology to realize dynamic pages, embedding low-dependency design patterns, flexible databases, and stable servers, the operating efficiency of the entire system is greatly improved. It can be seen that achieving the goal at the technical level is not a nonsense.
Most of the tools used in the project are currently popular open source and free, so in the early stage of development, the funds used for the project will be greatly reduced, and the development of the software will not be affected by the funds during the project start-up period, so It is still economically feasible. Try to use the least cost to meet the needs of users. Save funds for labor costs and equipment costs. It will go further and further on the road of paperless and high efficiency.
The operation of this system to realize the function is very simple. The common configuration of ordinary computers can run this software, and as long as you have a rough understanding of the basic common sense of computer use, you can use this software smoothly. The computer has the ability to connect to the Internet and can access the system normally. It does not require the operator to have any superb ability. It only needs to understand the business process and operate correctly according to professional knowledge. Therefore, the health check-in system for college students is feasible. .
Before system development and design, you should make a preliminary idea of the functions, know what sections the management system has, what functions each section has, whether the overall design meets the needs of users, and then conduct a detailed analysis and summary of the developed system functions , so as to design a complete system and implement it. Communication analysis of users and developers to achieve the best understanding and make the system function to the best.
The function diagram of the student background is shown below.
Figure 3-1 Functional Diagram of Student Background
The function diagram of the administrator background is as follows.
Figure 3-2 Administrator use case diagram
The teacher background function diagram is shown below.
Figure 3-3 Teacher background function diagram
After analyzing the requirements of the health check-in system for college students, the whole system is mainly divided into three parts: administrators, teachers and students, and the functions of the branches under each module are different. Describe the function as follows:
Student Module:
Account login authentication.
Manage profile information, modify modifiable information items.
Daily arrangements (health check-in, leave, diary) add and query the records of existing arrangements.
Teacher Module:
Personal data management, modify and delete your own information.
Adding and querying students, querying daily arrangements, querying health check-in, querying and reviewing leave management, querying and deleting diary management, querying notices, and viewing diary statistics.
Admin module:
System user management, management and adding and deleting administrators, you can set login permissions, or delete all user accounts.
Teacher management, adding specific information of teachers and querying teachers can also delete teachers.
Notification management, adding the functions of publishing announcements, querying announcements and deleting announcements.
Student management, querying student information, also has the function of modifying and deleting.
Daily arrangement management, query the information of student arrangements, and also have the function of modifying and deleting.
Health check-in management, query the information of students' check-in, and also have the function of modifying and deleting.
Leave management, query the information of students asking for leave, and also have the function of modifying and deleting.
Diary management, query the student diary information, also has the function of modifying and deleting.
Journal statistics, query statistics view.
System management, system backup function.
Non-Functional Requirements Analysis
There are many non-functional requirements of the system, such as performance requirements, maximum number of users that can be carried, stability, and usability requirements. The analysis of this system takes into account the requirement of ease of use, because the system is used by people, so it is necessary to fully consider the user experience from the user's point of view, so that the system is easy to understand, easy to use and easy to operate.
The zero-level data flow chart includes modules such as login, user function, and retrieval maintenance. The data used in the login module stores user account documents, and the storage required by the user function module is the data file of each user function module. The retrieval maintenance uses the above Data documents are retrieved by keywords.
The zero-level data flow diagram of the system is shown in the figure below.
Figure 3-2 System data flow diagram (zero layer)
The first-level data flow chart is a refinement of the zero-level data flow chart, subdividing login into filling in login data and improving data, and subdividing user functions into basic user functions and main user functions.
The layer-by-layer data flow diagram of the system is shown in the figure below.
Figure 3-3 System data flow diagram (one layer)
At present, the main data access method of the B/S system is: the user can enter the system through the browser page, and the system can automatically process the request sent by the user to the server. The processing request is carried out in the background of the system. Perform corresponding operations on the page, and you can see the processing results delivered by the server. The health check-in system for college students is mainly divided into a three-layer architecture design of view-model-control. In the view layer, it mainly operates the data fed back and displayed from the server to the client. In the model layer, it mainly deals with related business logic, data integration, etc., and the final control layer is between the view and the model. It is to adjust the relationship between the two layers and finally implement the data transmission.
The system architecture diagram is shown in the figure below.
Figure 4-1 System architecture diagram
The purpose of system design is to analyze all the functional structures included in the system, and make preparations for developers to design, develop and implement the system. After the preliminary demand investigation, analysis and sorting, the determined overall demand mainly includes multiple modules, namely: system user management, teacher management, notice announcement management, class management, student management, daily schedule original management, health check-in management , Leave management, diary management, diary statistics, data backup. The overall role of the system is divided into three parts, one is the student, the other is the teacher, and the last is the administrator. The distribution of permissions is also obvious. In addition to browsing information, ordinary users also have the ability to query and manage their own account information, modify teacher information, query daily arrangements, check health check-ins, ask for leave, query diaries, query notifications, and query diary statistics. and other permissions; the administrator is the highest authority owner.
The functional structure diagram of the system is shown in the figure below.
Figure 4-2 System function structure diagram
User Management Module
This module is designed for all users to log in. For example, ordinary users such as student users can only perform their own common function operations (such as personal information modification) after logging in. Administrators and super administrators have different permissions after logging in. Administrators cannot Beyond authority. The super administrator can manage the data of the entire system, mainly the user's login authority and the user's operation authority in the system after login.
Daily schedule module
There is a one-to-many relationship between students and arrangements. According to the daily arrangement, the arrangement data is transferred to the system data. The operator is the teacher user, and then generates a daily arrangement list. Students can view the personal historical arrangement list and delete on the right of each data. and edit button to complete the corresponding delete and update functions.
Health check-in module
Students come to record such as check-in data, click the check-in button, fill in the check-in personal status information data to be entered in turn, click the submit button for the physical status information, submit the data to the database, and then swipe the check-in data page, there are delete and edit buttons on the right of each data , to complete the corresponding delete and update functions.
leave module
Students enter the leave data, click the leave input button, fill in the leave information data to be entered in turn, click the submit button, submit the data to the database, and then refresh the leave data page, there are delete and edit buttons on the right of each data to complete the corresponding deletion and update functions.
diary module
Students click on the diary management menu, click Add Diary, and add mood. After the diary content is submitted successfully, the announcement data page is refreshed, and the new data is successfully loaded into the page.
For a system to be developed, ER diagrams allow others to understand the transactions of the system and the relationships between them faster and easier. According to the conclusions drawn in the system analysis stage, it is determined that there are multiple entities in the college student health check-in system, which are daily arrangements, health check-in, leave, diary, students, and teachers.
The overall ER diagram of the system is shown in the figure below.
Figure 4-4 System overall ER diagram
Administrator (admin id, username, password, permissions)
Teacher management (teacher ID, password, teacher name, gender, ID card, phone number, title, teaching assistant course, photo)
Notification Announcement (Title, Content, Attachments, Publisher)
Student management (student number, password, name, gender, ID card, phone number, department, class, photo, teacher ID, adding time) modify and delete details.
Daily schedule management (student ID, student name, class, department, teacher ID add time) modify and delete details.
Health check-in management (student ID, student name, class, department, teacher ID, personal status, physical status, current address, adding time) modify and delete details.
Leave management (leave request number, leave type, leave start time, leave end time, whether to leave school, relevant certificates, student number, name, class, department, teacher job number, adding time,) modify and delete details.
Diary management (student number, student name, class, department, teacher ID, mood, adding time) modify and delete details.
The logical structure of the database is to describe the ER diagram in the database with specific fields. Use fields and data type descriptions to materialize object characteristics, and finally form a database table structure with certain logical relationships. Part of the data structure table required by the college student health check-in system is shown in the following table.
| class_management |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| class_management_id |
int |
11 |
no |
primary key |
Class Management ID |
| class_name |
varchar |
64 |
yes |
class name |
|
| headmaster |
varchar |
64 |
yes |
head teacher |
|
| contact_number |
varchar |
64 |
yes |
contact number |
|
| class_size |
int |
11 |
yes |
class size |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| daily_schedule |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| daily_schedule_id |
int |
11 |
no |
primary key |
daily schedule id |
| student_number |
int |
11 |
yes |
student ID |
|
| student_name |
varchar |
64 |
yes |
student name |
|
| teacher_job_number |
int |
11 |
yes |
Teacher ID |
|
| teacher_name |
varchar |
64 |
yes |
teacher name |
|
| class_name |
varchar |
64 |
yes |
class name |
|
| record_date |
date |
0 |
yes |
record date |
|
| schedule |
text |
0 |
yes |
Schedule |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| epidemic_reporting |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| epidemic_reporting_id |
int |
11 |
no |
primary key |
Epidemic report ID |
| student_number |
int |
11 |
yes |
student ID |
|
| student_name |
varchar |
64 |
yes |
student name |
|
| teacher_job_number |
int |
11 |
yes |
Teacher ID |
|
| teacher_name |
varchar |
64 |
yes |
teacher name |
|
| class_name |
varchar |
64 |
yes |
class name |
|
| report_type |
varchar |
64 |
yes |
reporting type |
|
| nucleic_acid_results |
varchar |
64 |
yes |
nucleic acid results |
|
| detection_time |
datetime |
0 |
yes |
detection time |
|
| health_code |
varchar |
255 |
yes |
health code |
|
| remarks |
text |
0 |
yes |
Remark |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| notice_announcement |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| notice_announcement_id |
int |
11 |
no |
primary key |
Notification Bulletin ID |
| title |
varchar |
64 |
yes |
title |
|
| relevant_attachments |
varchar |
255 |
yes |
Relevant attachments |
|
| publisher |
varchar |
64 |
yes |
publisher |
|
| release_date |
date |
0 |
yes |
release date |
|
| content |
text |
0 |
yes |
content |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| punch_in_every_day |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| punch_in_every_day_id |
int |
11 |
no |
primary key |
Daily punch ID |
| student_number |
int |
11 |
yes |
student ID |
|
| student_name |
varchar |
64 |
yes |
student name |
|
| teacher_job_number |
int |
11 |
yes |
Teacher ID |
|
| teacher_name |
varchar |
64 |
yes |
teacher name |
|
| class_name |
varchar |
64 |
yes |
class name |
|
| record_date |
date |
0 |
yes |
record date |
|
| today_temperature |
varchar |
64 |
yes |
body temperature today |
|
| physical_state |
varchar |
64 |
yes |
body condition |
|
| punch_in_address |
varchar |
64 |
yes |
Punch address |
|
| health_code |
varchar |
255 |
yes |
health code |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| student |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| student_id |
int |
11 |
no |
primary key |
student ID |
| student_number |
varchar |
64 |
yes |
student ID |
|
| student_name |
varchar |
64 |
yes |
student name |
|
| class_name |
varchar |
64 |
yes |
class name |
|
| teacher_job_number |
int |
11 |
yes |
Teacher ID |
|
| teacher_name |
varchar |
64 |
yes |
teacher name |
|
| 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 |
|
| student_diary |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| student_diary_id |
int |
11 |
no |
primary key |
Student Diary ID |
| student_number |
int |
11 |
yes |
student ID |
|
| student_name |
varchar |
64 |
yes |
student name |
|
| teacher_job_number |
int |
11 |
yes |
Teacher ID |
|
| teacher_name |
varchar |
64 |
yes |
teacher name |
|
| class_name |
varchar |
64 |
yes |
class name |
|
| mood |
varchar |
64 |
yes |
Feeling |
|
| date |
date |
0 |
yes |
date |
|
| content |
longtext |
0 |
yes |
content |
|
| recommend |
int |
11 |
no |
Intelligent Recommendation |
|
| create_time |
datetime |
0 |
no |
creation time |
|
| update_time |
timestamp |
0 |
no |
update time |
|
| students_ask_for_leave |
|||||
| Field Name |
type |
length |
not null |
primary key |
field description |
| students_ask_for_leave_id |
int |
11 |
no |
primary key |
Student Leave ID |
| student_number |
int |
11 |
yes |
student ID |
|
| student_name |
varchar |
64 |
yes |
student name |
|
| teacher_job_number |
int |
11 |
yes |
Teacher ID |
|
| teacher_name |
varchar |
64 |
yes |
teacher name |
|
| class_name |
varchar |
64 |
yes |
class name |
|
| leave_type |
varchar |
64 |
yes |
leave type |
|
| leave_days |
int |
11 |
yes |
days off |
|
| start_time |
datetime |
0 |
是 |
开始时间 |
|
| end_time |
datetime |
0 |
是 |
结束时间 |
|
| relevant_vouchers |
varchar |
255 |
是 |
相关凭证 |
|
| reason_for_leave |
text |
0 |
是 |
请假原因 |
|
| examine_state |
varchar |
16 |
否 |
审核状态 |
|
| examine_reply |
varchar |
255 |
是 |
审核回复 |
|
| recommend |
int |
11 |
否 |
智能推荐 |
|
| create_time |
datetime |
0 |
否 |
创建时间 |
|
| update_time |
timestamp |
0 |
否 |
更新时间 |
|
| teacher |
|||||
| 字段名称 |
类型 |
长度 |
不是null |
主键 |
字段说明 |
| teacher_id |
int |
11 |
否 |
主键 |
教师ID |
| teacher_job_number |
varchar |
64 |
否 |
教师工号 |
|
| teacher_name |
varchar |
64 |
是 |
教师姓名 |
|
| examine_state |
varchar |
16 |
否 |
审核状态 |
|
| recommend |
int |
11 |
否 |
智能推荐 |
|
| user_id |
int |
11 |
否 |
用户ID |
|
| create_time |
datetime |
0 |
否 |
创建时间 |
|
| update_time |
timestamp |
0 |
否 |
更新时间 |
|
系统的登录窗口是用户的入口，用户只有在登录成功后才可以进入访问。通过在登录提交表单，后台处理判断是否为合法用户，进行页面跳转，进入系统中去。
登录合法性判断过程：用户输入账号和密码后，系统首先确定输入输入数据合法性，然后在login.jsp页面发送登录请求，调用src下的mainctrl类的dopost方法来验证。
用户登录模块的IPO如下所示：
输入：用户名和密码。
处理：
1）检测用户输入的账号、密码是否正确及在数据库已对应存在。
2）从数据库中提取记录，并储存在本地的session中（timeout默认=30min）。
3）根据用户名，将其显示在系统首页上。
输出：是否成功的信息。
登录流程图如下所示。
图5-1登录流程图
系统登录界面如下所示。
图5-2系统登录界面
5.2.1 用户首页模块
系统呈现出一种简洁大方的首页：界面简约、鳞次栉比，用户能轻车熟路的使用。出于对系统使用群体广泛的顾虑，应有良好性能的后台。
如下图所示为系统的首页界面。
图5-3系统首页界面
5.2.2每日安排模块
每日安排学生编辑学号、教师工号、教师姓名、班级名称、学生账号、学生姓名、记录日期等内容，并可根据需要进行修改、删除等操作。如图5-4所示。
图5-4每日安排界面图
5.2.3每日打卡模块
每日打卡学生编辑学号、教师工号、教师姓名、班级名称、学生账号、学生姓名、记录日期、今日体温等内容，并可根据需要进行修改、删除等操作。如图5-5所示。
图5-5每日打卡录入界面如图
5.2.4学生请假模块
学生请假学生编辑学号、教师工号、教师姓名、班级名称、学生账号、学生姓名、请假类型、请假天数等内容，并可根据需要进行修改、删除等操作。如图5-6所示。
图5-6学生请假申请界面
5.3管理员子系统模块的实现
5.3.1学生管理模块
学生在yhzhgl查看学生信息，先使用sql语句查询出所有学生表的数据，然后调用PageManager.getPages(url,4,sql, request )，返回一个ArrayList的对象，在for循环里，使用jsp得到每个ArrayList对象的数据，在jsp页面中解析ArrayList对象，得到其各个键值对的值。
学生管理界面如下图所示。
图5-7学生管理界面
5.3.2每日安排管理模块
添加安排信息时，输入必填字段后，表现层的KechengController接受传过来的安排信息参数，再调用KechengController类的addKecheng方法，经过KechengService业务层到KechengMapper持久层的处理，完成对整个添加安排信息的操作。addKecheng方法也和用户管理中的addUser方法类似，同时做添加和修改工作。
修改安排信息时，选择需要修改的安排进行修改，调用KechengController控制器的editKecheng方法，拿到该安排原本的信息并显示到页面，管理员再对需要修改的安排信息字段进行修改，完成后调用addKecheng方法，调用业务层的updateByKey方法，更新数据库的安排信息表的数据。
每日安排管理流程图如下所示。
图5-8每日安排管理流程图
每日安排界面如下图所示。
图5-9每日安排添加界面
5.3.3每日打卡模块
每日打卡页面可查看学号、教师工号、教师姓名、班级名称、学生账号、学生姓名、记录日期、今日体温等内容，并可根据需要进行修改、删除等操作
图5-10每日打卡界面
5.3.4教师管理模块
删除教师时，选择需要删除的教师进行删除，把主键的uId传到JiaoshiController控制器，再调用控制器的deleteJiaoshi方法，数据经过JiaoshiService业务层解析和处理，请求JiaoshiMapper持久层调用deleteByPrimaryKey方法操作数据库将教师数据从数据库中删除。
查找教师时，输入需要查找的教师名，调用getData方法获取所有数据并且进行分页，把获取到的所有数据显示到视图上，这时候只需要用脚本方法便能快速查找，不涉及对数据库操作。
教师管理流程图如下所示。
图5-11教师管理流程图
教师添加界面如下图所示。
图5-12教师添加界面
在对该系统进行完详细设计和编码之后，就要对高校学生健康打卡系统的程序进行测试，检测程序是否运行无误，反复进行测试和修改，使之最后成为完整的软件，满足用户的需求，实现预期的功能。
在软件的测试过程中，通常测试人员需要针对不同的功能模块设计多种测试用例。通过测试用例能够及时发现代码业务逻辑上是否与真实的业务逻辑相对应，及时发现代码上或逻辑上的缺陷，以此来来完善系统，提高软件产品的质量，使软件具有良好的用户体验。
登录测试用例表如下所示。
表6-1登录测试用例
| 测试性能 |
用户或操作员登录系统 |
||
| 用例目的 |
测试用户或操作员登录系统时功能是否正常 |
||
| 前提条件 |
进入用户登录页面或操作员登录页面 |
||
| 输入条件 |
预期输出 |
实际情况 |
|
| 各项信息不予填写，直接点击登陆按钮 |
不允许登录，提示填写账号相关信息 |
一致 |
|
| 填写错误的登录名或密码后点击登录系统 |
提示用户名或密码错误，要求重新填写进行登录 |
一致 |
|
| 填写与验证码信息不一致的信息 |
系统显示出提示信息，表明验证码错误，要求重新填写 |
一致 |
|
每日安排测试用例表如下所示。
表6-2课程成绩测试用例
| 测试性能 |
用户进行成绩课程的操作 |
||
| 用例目的 |
测试用户进行安排操作时，系统的功能是否正常 |
||
| 前提条件 |
用户进入安排详情页，该每日安排能够被成功 |
||
| 输入条件 |
预期输出 |
实际情况 |
|
| 用户未登录，点击成绩按钮 |
跳转至登录页面，提示用户先进性登录 |
一致 |
|
| 正常的登录用户，点击成绩按钮 |
系统弹出提示框，提示用户成绩成功，同时该课程的状态更改为已成绩状态 |
一致 |
|
请假管理测试用例表如下所示。
表6-3课程管理测试用例
| 测试性能 |
请假管理相关信息管理功能 |
||
| 用例目的 |
测试系统后台操作员对请假管理相关信息进行管理的功能是否正常 |
||
| 前提条件 |
登录系统后台进入相关管理页面 |
||
| 输入条件 |
预期输出 |
实际情况 |
|
| 普通操作员登录，点击进入课程相关信息管理的页面 |
提示非超级用户，权限不够，无法进行相关页面删除 |
一致 |
|
| 超级操作员登入，删除某个已被删除的请假 |
提示该请假删除失败 |
一致 |
|
| 点击增加请假按钮 |
页面正常跳转 |
一致 |
|
| 增加请假是，填写已存在的课程编号 |
提示该编号已存在 |
一致 |
|
经过对此系统的测试，得出该系统足以满足用户日常需求，在功能项目和操作等方面也能满足操作员对于其他用户的管理。但是，还有很多功能有待添加，这个系统仅能满足大部分的需求，还需要对此系统的功能更进一步的完善，这样使用起来才能更加的完美。
通过这次大学生防疫封校管理系统的开发，我参考了很多相关系统的例子，取长补短，吸取了其他系统的长处，逐步对该系统进行了完善，但是该系统还是有很多的不足之处，有待以后进一步学习。
实践证明，大学生防疫封校管理系统有着非常好的发展前景，经过测试运行，系统各项功能都十分完善，界面简洁，使用方便，操作容易，在技术理论上已经成熟。
通过大学生防疫封校管理系统的开发，本人巩固了之前学过的知识，如今将平时所学到的知识融合在设计中，在设计过程中，做了很多的准备，首先，在数据库系统的设计过程中，尤其是在数据库的工作原理、工作特点，对其深刻的讨论，与此同时，对于小型站点来说，最好服务器的选择，其次，利用所学的知识点分析所做的系统，并在此基础上设计。
目前本系统已经上线，正在试运行阶段，用户反馈良好，基本完成用户所需，试运行过程中没有出现阻断性问题，有一些不足和小问题也及时予以修正，系统上线后，为了保证数据的安全性，对系统进行了备份操作，系统备份是每两个月备份一次，数据库备份为每周备份一次，系统部署在租赁的云平台服务器中。
本次系统上线成功后，得到了用户的高度认可，但是在功能上和性能上还需做进一步的研究处理，使其有更高的性能和更好的用户体验。
系统在以后的升级过程中，需要解决一系列用户所提出的问题，例如打印过程中如何避免浏览器的兼容性问题，大量用户访问时，如何保持较高的响应速度，在系统今后的升级过程中将着重解决这些安全性问题。
参考文献
[1]李秋萍,彭辉.高校新冠疫情集中医学观察的防控策略与思考——以中国药科大学为例[J].江苏科技信息,2021,38(36):28-31+35.
[2]金振娅. 全力做好“两节”期间疫情防控[N]. 光明日报,2021-12-30(008).DOI:10.28273/n.cnki.ngmrb.2021.006554.
[3]李雅琴.Java编程语言的优势及其应用实践研究[J].互联网周刊,2021(24):60-62.
[4]徐欢,凌骏.防疫封校期间校园学生活动的组织开展研究——以某职业院校学生读书会活动为例[J].武汉冶金管理干部学院学报,2021,31(04):17-20+23.
[5]韩冰,刘翠焕,黄振华,张波,陈明珠,张潇.人工智能时代下“Java程序设计”课程教学改革[J].科技风,2021(33):98-100.DOI:10.19392/j.cnki.1671-7341.202133033.
[6]丁海洋,王昊翔,姚全珠.基于MVVM框架的汽车销售管理系统设计与实现[J].电子制作,2021(22):55-56+8.DOI:10.16589/j.cnki.cn11-3571/tn.2021.22.019.
[7]杨涛,陈维. 中文版COVID-19恐怖症量表在疫情封校期间的信效度检验[C]//第二十三届全国心理学学术会议摘要集（下）.,2021:302.DOI:10.26914/c.cnkihy.2021.039964.
[8]苏文强,刘紫阳,苗玉恒.基于SSM的缺陷管理系统设计与实现[J].大众科技,2021,23(10):4-6+10.
[9]王伟,常庆丽,吴朝霞.基于SSM+Vue的精准帮扶系统研究与实现[J].河南科技,2021,40(27):12-14.
[10]胡开华,张玉静,陈明禄,何文鑫.基于Vue.js的Web应用开发教学案例设计与实现[J].信息与电脑(理论版),2021,33(18):91-94.
[11]喻佳,吴丹新.基于SSM的Web快速开发框架[J].电脑编程技巧与维护,2021(09):31-33.DOI:10.16184/j.cnki.comprg.2021.09.013.
[12]巢晟盛.基于SSM微服务架构下前后端分离的MVVM模型浅析[J].电脑知识与技术,2021,17(23):128-129+141.DOI:10.14004/j.cnki.ckt.2021.2412.
[13]赵志威,张生月,蒋应举,屠晓光.基于SSM的高新技术企业创新能力评价平台设计与实现[J].现代信息科技,2021,5(15):40-42.DOI:10.19850/j.cnki.2096-4706.2021.15.011.
[14]霍鹏宇.后疫情时期“高校封校”下的体育教育思考[J].当代体育科技,2021,11(20):71-73.DOI:10.16655/j.cnki.2095-2813.2010-1579-3836.
[15]方生.基于“Vue.js”前端框架技术的研究[J].电脑知识与技术,2021,17(19):59-60+64.DOI:10.14004/j.cnki.ckt.2021.1863.
[16]宋馨来,张海涛.基于前后端分离和Spring Security的用户登录功能的设计与实现[J].科技创新与应用,2021,11(18):19-21+24.
[17]Dang Tran Khanh,Huy Ta Manh,Dang Ly Hoang,Le Hoang Nguyen. An Elastic Data Conversion Framework: A Case Study for MySQL and MongoDB[J]. SN Computer Science,2021,2(4):
[18]马忠强,牟聪瑞,刘磊.新冠疫情封校期间不同体育运动对航海类学生负面情绪调节自我效能感的中介作用[J].高教学刊,2021,7(14):1-6+11.
[19]Dan Roscigno. Bring Elastic Observability to your Java application[J]. InfoWorld.com,2020:
[20]Benymol Jose,Sajimon Abraham. Performance analysis of NoSQL and relational databases with MongoDB and MySQL[J]. Materials Today: Proceedings,2020,24(Pt 3):
致谢
光阴似箭，一晃大学生活即将过去了。一直以严谨的态度和积极的热情投身于学习和工作中，虽然有竞争，也有泪水，但是通过我不断学习和奋斗不断的完善自己，不仅很好的完成了我的学业而且也让我的各方面得到了发展，取得了很大的进步。
University life is coming to an end, although there are many regrets, but we have to say goodbye after all. Looking back on the study and life of the university, there are tears and sweat. During this period, I strictly demanded myself. With my strong pursuit of knowledge, I worked hard, studied hard, had a correct attitude, clear goals, firmly mastered some professional knowledge and skills, and integrated theory with practice. In addition to the study of professional knowledge, I continue to expand my knowledge and acquire new knowledge in different ways from different fields. Strive to become a college student who is qualified in all aspects.
This graduation project is the longest and most labor-intensive project I have completed alone. Fortunately, during the process of completing my graduation project, there were many classmates and teachers who helped me. Over the course of several months of development, I ran into countless issues, large and small. It is my roommate and teacher, constantly helping and encouraging.
My instructor, even though he was very busy with his work, was still able to promptly reply to the question emails we sent, and took time to give us offline tutoring. Point out our design mistakes, logic errors and study planning problems. It can be said that without the help of the tutor, my graduation project will fall into a dead end. It is the tutor who pointed out the maze for me, like a street lamp in the fog, pointing out the direction for me!
Get the source code of the project for free, please pay attention to like + private chat