Since the 1920s, computers have appeared crazily in people's lives and work, becoming a good helper for people's lives and work. Computers have penetrated into every household. Online offices and online teaching have replaced the traditional manual record management methods. , using computers to work does not have to be limited to a fixed time and a fixed location, and cross-regional communication can be easily achieved through computer systems. With the popularization of higher education, the number of students has continued to increase. Recently, due to the impact of the epidemic, traditional query and management of student information has become increasingly inconvenient, and manual query management has also reduced work efficiency and increased the number of teachers. and the workload of the school, and it is not convenient for students to make inquiries, so a student information management system was developed.
This system is developed with practical application as the background. Through the system administrator, the system administrator can conduct unified management of all students, teachers and other personnel as well as some student management, assignment tasks, task completion, check-in, teacher-student communication and other data information related to students. , to facilitate the retention of data. Teachers and students can register and then log in to the system to query and manage information such as assigned tasks, completed tasks, check-ins, and communication between teachers and students. In general, the front-end of the system is displayed through Java pages, the back-end uses the SSM framework, and the database uses the currently popular open source relational database MYSQL. This system uses the currently popular vue.js in the front-end technology to make the page display more neat and beautiful.
Keywords: student information management; Java; SSM; MYSQL
Since the 1920s, computers have appeared crazily in people's life and work, becoming a good helper for people's life and work. Computers have penetrated into every household. Network office and network teaching have replaced the traditional manual record management. Using computers to work can not be limited to fixed time and location, and cross regional communication can be easily realized through the computer system. With the popularization of higher education, the number of students is also increasing. Recently, due to the impact of the epidemic, the traditional query management of student information is becoming more and more inconvenient, and the manual query management also reduces the work efficiency, increases the workload of teachers and schools, and is not convenient for students to query. Therefore, the student information management system is developed.
This system takes practical application as the development background. Through the system administrator, all students, teachers and other personnel as well as some data information related to students such as student management, task assignment, task completion, clock in and sign in, and teacher-student communication can be managed uniformly to facilitate the retention of data. Teachers and students can register and log in to the system to query and manage the information about task assignment, task completion, clock in and communication between teachers and students. In general, the foreground of the system is displayed through Java pages, the background uses the SSM framework, and the database uses the popular open-source relational database MYSQL. This system uses the current popular vue.js in the foreground technology to make the page more neat and beautiful.
Keywords: Student information management; Java； SSM； MYSQL
1.1 Topic selection background
1.2 Significance of the research topic
1.3 Thesis structure arrangement
Chapter 2 Requirements Analysis of Student Information Management System
2.1 System feasibility analysis
2.1.1 Technical feasibility analysis
2.1.2 Economic feasibility analysis
2.1.3 Operation feasibility analysis
2.2 System requirements analysis
2.2.1 Functional requirements analysis
2.2.2 Non-functional requirements analysis
Chapter 3 Overall Design of Student Information Management System
3.1 System function module design
3.2.1 Database conceptual structure design
3.2.2 Database logical structure design
Chapter 4 Design and Implementation of Key Modules 1 7
4. 8 Teacher-student exchange management module
Today, with the rapid economic development in the 21st century, various office auxiliary software has become popular in various industries, such as enterprise ERP software, family financial management software, education student status management software, etc., have been highly praised by users. For education As far as careers are concerned, most schools have developed a lot of web management systems for students and teachers to conduct online learning and management, such as student status systems, examination systems, etc. Through these systems, data maintenance, students and their related information can be conveniently maintained. Information management, and its current application in teaching involves politics, economy, culture and other fields.
Generally speaking, the current education is no longer dominated by the traditional teaching form of a single teacher facing a group of students. Instead, diversified teaching in the form of various auxiliary teaching forms has become the mainstream on the original basis. This kind of The change is precisely because after the computer network is combined with education, it is determined by the many advantages of online teaching in the form of the Internet. The student information management system studied in this topic is mainly based on computer network technology. In terms of student information management, various functions have been designed and implemented. The implemented system has three parts: administrators, teachers and students. It mainly includes three functions: teaching administrator subsystem, teacher subsystem and student subsystem, realizing functions such as student management, teacher management, assignment management, task completion management, check-in management, teacher-student communication management, etc.
Student information management system is an important part of school business development and is valued by more and more schools. On the one hand, for most schools, the student information management system helps them better query and manage student-related information; on the other hand, students can view courses, course selections, and results online, which will attract more students Use, diversified choices and a completely transparent process in the management process can gain user recognition and increase user stickiness. Through the student information management system, students can complete student-related information queries on the system without going to each teacher's office or academic affairs office to query, enabling users to query student information without leaving home.
This article will design a student information management system for schools based on SSM. In accordance with the user-needs-centered concept and with the goal of meeting user needs in an all-round, high-quality, and efficient manner, we will provide schools with a more powerful student information management system. Incorporating computer information technology into the important technical aspects of the student information management system can not only improve the efficiency of student information management and reduce the workload of administrators, but also make it easier for students to check tasks, conduct teacher-student exchanges, check in, and sign in, etc., which is very important for the future of the school. The impact of developments and improvements is far-reaching. School administrators can manage all information online, and the degree of rationalization of its internal structure directly affects the school administrator's final decision. Therefore, sufficient information and fast and convenient management methods are necessary for a student information management system.
The paper will be arranged hierarchically. In addition to the abstract, table of contents, acknowledgments, and literature reference sections, the main text will also analyze the website requirements, elaborate on the general design and implemented functions, and finally list some commissioning records. The paper mainly The architecture is as follows:
Chapter 1 explains the background of the project and the practical significance of development.
Chapter 2 analyzes the feasibility and functional requirements of this system.
Chapter 3 explains the overall design of the project.
Chapter 4 clarifies the implementation of the detailed functions of the student information management system, mainly based on the technical functional module functions.
Chapter 5 lists some system debugging and testing records.
Chapter 6 introduces the conclusion of the student information management system.
- Chapter 2 Requirements Analysis of Student Information Management System
The student information management system uses the mysql database for storage and development tools such as IDEA and Tomcat for development, which can bring a lot of convenience to our writing work. The system is developed using the SSM framework, which makes the system more scalable and maintainable, reduces Java configuration code, and simplifies programming code. Currently, the SSM framework is also one of the frameworks chosen by many enterprises.
The development software used in developing the student information management system, such as IDEA development tools, Tomcat8.0 server, MySQL5.7 database, Photoshop image processing software, etc., are all open source and free, and these environments have been systematically studied in the school . , you can operate it independently without any additional cost, and the system development tools can be downloaded directly from the Internet, so it is economically feasible.
When designing this project, I referred to many successful cases of similar systems, systematically analyzed their operation interfaces and functions, and combined many cases together to highlight people-oriented and simplified operations, so people with basic computer knowledge can Operate this project. Therefore, there is no problem with operational feasibility.
The design and implementation of the student information management system is to allow school users to more conveniently manage some information related to students . Users can save a lot of time and energy when searching and managing, and effectively reduce unnecessary search time. The system is functionally divided into three parts: student end , teacher end and administrator end.
Student side:
(1) Registration and login: When students want to query and manage the functions implemented in the system , they must log in to the system. If they do not have an account, on the login interface, click the "Register" button to jump to In the registration interface, fill in the registration information according to the prompts, add and submit, the student's information is added to the database, and then enter the filled in account number and password to log in ;
(2) Personal information: After logging in, students can modify their personal information and the password for their account login;
(3) Student information: After clicking the "Student Management" button, you will view all student information in the system. It supports querying student information by student number or student name or class name. If you want to know the detailed information of a certain student, click The subsequent "View" will enter the details interface;
(4) Assigned task information: Click the "Assigned task information" menu to view your own task information. It supports querying task information by student number. If you want to know the details of an assigned task, click " Details" will enter the details interface;
(5) Complete the task: Click the "Complete Task Information" button to view all completed task information. It supports querying the completed task information through the class name or student name;
(6) Check-in: Click the "Punch-in" button to view all the check-in information submitted by you. You can check the check-in information by student name or class name or student number. If you want to add new check-in information, click "Add" button and then enter the check-in information according to the prompts. After clicking "Submit", the newly added student check-in information will be displayed on the student check-in interface. You can click on a certain check-in information to view the details of the check-in information;
(7) Teacher-student communication: Click on the "Teacher-Student Communication" menu to view all queried teacher-student communication information in the system. It supports querying teacher-student communication information by title. If you want to know about a certain teacher-student communication For detailed information, click "Details" at the back to enter the details interface;
Teacher side:
(1) Registration and login: When teachers want to query and manage the functions implemented in the system , they must log in to the system. If they do not have an account, on the login interface, click the "Register" button to jump to In the registration interface, fill in the registration information according to the prompts, add and submit, the teacher 's information will be added to the database, and then enter the filled in account number and password to log in ;
(2) Personal information: After logging in, teachers can modify their personal information and the password for their account login;
(3) Student information: After clicking the "Student Management" button, you will view all student information in the system. It supports querying student information by student number or student name or class name. If you want to know the detailed information of a certain student, click The subsequent "View" will enter the details interface;
(4) Assigned task information: Click the "Assigned task information" menu to view your own task information. It supports querying task information by student number. If you want to know the details of an assigned task, click " Details" will enter the details interface;
(5) Punch-in and sign-in information: Click the "Punch-in and Sign-in Information" button to view the sign-in information that you choose to clock in. You can query the clock-in and sign-in information by class name or student name. If you want to know the details of a certain sign-in, click The subsequent "View" will enter the details interface;
(6) Teacher-student communication: Click the "Teacher-Student Communication" button to view the teacher-student communication you have queried. It supports querying the communication information by class name or student name, and you can delete the queried communication information;
Administrator side:
(1) Personal information: After logging in, managers can modify their personal information and the password for their account login;
(2) User management: Administrators can manage and control all user roles in the system, including administrators, students, and teachers. If you need to add a new user, click the "Add" button on the page and enter according to the prompts. Go to the user information and click "Submit" to view it on the corresponding user interface. You can click the "Delete" button behind the user to directly delete a user.
(3) Student management: Click the "Student Management" button to view all student information in the system. It supports querying student information by student name or class name or student number. If you want to add new student information, click "Add" " button and then enter the student information according to the prompts. After clicking "Submit", the newly added student information will be displayed on the student information interface. You can click on a certain student information to view the details of the student information, or you can directly click "Delete" to delete the student. information;
(4) Assign tasks: Click the "Assign tasks" button to view all assigned task information. It supports querying assigned task information by class name or student name. If you want to know the details of a certain task, click " View" will enter the details interface;
(5) Complete the task: Click the "Complete Task" button to view all completed task information. It supports querying the completed task information by the student's name or class name or student number. You can add, delete, and view the completed task information of the student. Details of the task information;
(6) Punch-in and sign-in: Click the "Punch-in and sign-in" button to view the clock-in and sign-in information of all students. It supports querying the clock-in and sign-in information through the class name or student name, and the added clock-in and sign-in can be deleted at the same time;
(7) Teacher-student communication: Click the menu "Teacher-student communication information" to view all the communication information added in the system. It supports querying the teacher-student communication information by title. If you want to add a new teacher-student communication, click "Add" button, enter the teacher-student communication information according to the prompts, click the "Submit" button, the new communication information will be displayed in the system, and the added teacher-student communication information can also be deleted;
The non-functional requirements of the student information management system include the security, reliability, performance, scalability, etc. of the self-service student information management system . The details can be expressed in the following 3-1 table:
Table 2.1 Non-functional requirements table for student information management system
| safety |
Mainly refers to the installation of the student information management system database, the use of the database and the setting of passwords must comply with standards. |
| reliability |
Reliability means that the student information management system can install and operate according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for the student information management system to occupy the market, so it is best to have good performance. |
| Scalability |
For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system. |
| Ease of use |
Users only need to follow the page display content of the student information management system and operate. |
| maintainability |
The maintainability of student information management system development is very important. After testing, there is no problem with maintainability. |
The use case diagram of the student role in the student information management system is shown in Figure 2.1:
Figure 2.1 Student role use case diagram
The use case diagram of the teacher role in the student information management system is shown in Figure 2.2:
Figure 2.2 Teacher role use case diagram
The use case diagram of the administrator role in the student information management system is shown in Figure 2.3:
Figure 2.3 Administrator role use case diagram
After analyzing the background, significance and feasibility of project development, the next step is to discuss the functional division of the project and the design of various tables in the project database during specific implementation. In this chapter, a systematic introduction will be made.
The design of the functional module is to create a system architecture based on the specific functions that the system is to implement and how the functions are divided. It is displayed in the form of a module diagram to facilitate us to list and involve the functions . In terms of system functions, the project is divided into three modules: administrator + teacher + student. Each module logs in and corresponds to the corresponding function. The specific function module diagram is shown in Figure 3.1.
Figure 3.1 Function module diagram of student information management system
The design of the database carries various data of the system. In a system, all kinds of data require a special container. The database is this container. When establishing the database, it mainly consists of two parts: the design of the database model and the design of each database table. .
The following is the total ER entity relationship diagram of the main database tables in the entire student information management system.
Figure 3.2 Overall ER relationship diagram of student information management system
From the previous ER diagram, you can see that the project requires the creation of many data tables. The following is the relational model of the main database tables in the project:
(1) The table teacher entity is used to store the teacher number, teacher name, gender, etc. in the teacher information;
Table 3.1 Teacher information teacher table
| name |
type |
length |
not null |
primary key |
Comment |
| teacher_id |
int |
11 |
yes |
yes |
Teacher ID |
| teacher_no |
varchar |
64 |
yes |
no |
Teacher number |
| teacher_name |
varchar |
64 |
no |
no |
Teacher name |
| gender |
varchar |
64 |
no |
no |
gender |
| examine_state |
varchar |
16 |
yes |
no |
Approval Status |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| user_id |
int |
11 |
yes |
no |
User ID |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
Update time |
(2) The table system_students entity is used to store student names, class names, gender, student numbers, etc. in student information;
Table 3.2 Student information system_students table
| name |
type |
length |
not null |
primary key |
Comment |
| system_students_id |
int |
11 |
yes |
yes |
System student ID |
| student_id |
varchar |
64 |
no |
no |
student number |
| gender |
varchar |
64 |
no |
no |
gender |
| student_name |
varchar |
64 |
no |
no |
student name |
| class_name |
varchar |
64 |
no |
no |
class name |
| examine_state |
varchar |
16 |
yes |
no |
Approval Status |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| user_id |
int |
11 |
yes |
no |
User ID |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
Update time |
(3) The table complete_the_task entity is used to store the task number, student number, student name, class name, teacher name, task name, dispatch time, completion file, completion notes, etc. in the completed task information;
Table 3.3 Complete task information complete_the_task table
| name |
type |
length |
not null |
primary key |
Comment |
| complete_the_task_id |
int |
11 |
yes |
yes |
Complete task ID |
| task_no |
varchar |
64 |
yes |
no |
Task number |
| student_id |
int |
11 |
no |
no |
student number |
| student_name |
varchar |
64 |
no |
no |
student name |
| class_name |
varchar |
64 |
no |
no |
class name |
| teacher_no |
int |
11 |
no |
no |
Teacher number |
| teacher_name |
varchar |
64 |
no |
no |
Teacher name |
| task_name |
varchar |
64 |
no |
no |
mission name |
| dispatch_time |
varchar |
64 |
no |
no |
Dispatch time |
| complete_file |
varchar |
255 |
no |
no |
Complete document |
| complete_remarks |
varchar |
64 |
no |
no |
Complete notes |
| examine_state |
varchar |
16 |
yes |
no |
Approval Status |
| examine_reply |
varchar |
16 |
no |
no |
moderation reply |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
Update time |
(4) The table communication_between_teachers_and_students entity is used to store the student number, student name, class name, teacher number, teacher name, communication content, etc. in the communication information between teachers and students;
Table 3.4 Communication_between_teachers_and_students table
| name |
type |
length |
not null |
primary key |
Comment |
| communication_between_teachers_and_students_id |
int |
11 |
yes |
yes |
Teacher-student exchange ID |
| student_id |
int |
11 |
no |
no |
student number |
| student_name |
varchar |
64 |
no |
no |
student name |
| class_name |
varchar |
64 |
no |
no |
class name |
| teacher_no |
int |
11 |
no |
no |
Teacher number |
| teacher_name |
varchar |
64 |
no |
no |
Teacher name |
| communication_content |
longtext |
0 |
no |
no |
Communication content |
| examine_state |
varchar |
16 |
yes |
no |
Approval Status |
| examine_reply |
varchar |
16 |
no |
no |
moderation reply |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
Update time |
（5）表clock_in实体用来存放系统中学生的打卡签到信息，包含了管理序号、学生编号、学生姓名、班级名称、教师编号、教师姓名等；
表3.5打卡签到信息clock_in表
| 名称 |
类型 |
长度 |
不是null |
主键 |
注释 |
| clock_in_id |
int |
11 |
是 |
是 |
打卡签到ID |
| management_no |
varchar |
64 |
否 |
否 |
管理序号 |
| student_id |
int |
11 |
否 |
否 |
学生编号 |
| student_name |
varchar |
64 |
否 |
否 |
学生姓名 |
| class_name |
varchar |
64 |
否 |
否 |
班级名称 |
| teacher_no |
int |
11 |
否 |
否 |
教师编号 |
| teacher_name |
varchar |
64 |
否 |
否 |
教师姓名 |
| examine_state |
varchar |
16 |
是 |
否 |
审核状态 |
| examine_reply |
varchar |
16 |
否 |
否 |
审核回复 |
| recommend |
int |
11 |
是 |
否 |
智能推荐 |
| user_id |
int |
11 |
是 |
否 |
用户ID |
| create_time |
datetime |
0 |
是 |
否 |
创建时间 |
| update_time |
timestamp |
0 |
是 |
否 |
更新时间 |
（6）表student_management学生信息实体用来存放系统中学生的信息，包含了管理序号、学生编号、学生姓名、班级名称、教师编号、教师姓名、学生档案、记录日期、限制次数等；
表3.6学生管理信息student_management表
| 名称 |
类型 |
长度 |
不是null |
主键 |
注释 |
| student_management_id |
int |
11 |
是 |
是 |
学生管理ID |
| management_no |
varchar |
64 |
否 |
否 |
管理序号 |
| student_id |
int |
11 |
否 |
否 |
学生编号 |
| student_name |
varchar |
64 |
否 |
否 |
学生姓名 |
| class_name |
varchar |
64 |
否 |
否 |
班级名称 |
| teacher_no |
int |
11 |
否 |
否 |
教师编号 |
| teacher_name |
varchar |
64 |
否 |
否 |
教师姓名 |
| student_files |
varchar |
255 |
否 |
否 |
学生档案 |
| record_date |
date |
0 |
否 |
否 |
记录日期 |
| recommend |
int |
11 |
是 |
否 |
智能推荐 |
| limit_times |
int |
8 |
是 |
否 |
限制次数 |
| limit_type |
tinyint |
2 |
是 |
否 |
限制次数类型1 |
| create_time |
datetime |
0 |
是 |
否 |
创建时间 |
| update_time |
timestamp |
0 |
是 |
否 |
更新时间 |
管理员、教师和学生在登录界面输入账号+密码，点击“登录”按钮，系统在用户数据库表中会对管理员、教师和学生的账号进行匹配，账号+密码正确的话，就会登录到系统中各个用户的主管理界面，否则提示对应的信息，返回到登录的界面，其主界面展示如下图4.1所示。
图4.1 登录界面图
登录关键代码如下所示。
/**
* 登录
* @param data
* @param httpServletRequest
* @return
*/
@PostMapping("login")
public Map<String, Object> login(@RequestBody Map<String, String> data, HttpServletRequest httpServletRequest) {
log.info("[执行登录接口]");
String username = data.get("username");
String email = data.get("email");
String phone = data.get("phone");
String password = data.get("password");
List resultList = null;
QueryWrapper wrapper = new QueryWrapper<User>();
Map<String, String> map = new HashMap<>();
if(username != null && "".equals(username) == false){
map.put("username", username);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(email != null && "".equals(email) == false){
map.put("email", email);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(phone != null && "".equals(phone) == false){
map.put("phone", phone);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}else{
return error(30000, "账号或密码不能为空");
}
if (resultList == null || password == null) {
return error(30000, "账号或密码不能为空");
}
//判断是否有这个用户
if (resultList.size()<=0){
return error(30000,"用户不存在");
}
User byUsername = (User) resultList.get(0);
Map<String, String> groupMap = new HashMap<>();
groupMap.put("name",byUsername.getUserGroup());
List groupList = userGroupService.selectBaseList(userGroupService.select(groupMap, new HashMap<>()));
if (groupList.size()<1){
return error(30000,"用户组不存在");
}
UserGroup userGroup = (UserGroup) groupList.get(0);
//查询用户审核状态
if (!StringUtils.isEmpty(userGroup.getSourceTable())){
String res = service.selectExamineState(userGroup.getSourceTable(),byUsername.getUserId());
if (res==null){
return error(30000,"用户不存在");
}
if (!res.equals("已通过")){
return error(30000,"该用户审核未通过");
}
}
//查询用户状态
if (byUsername.getState()!=1){
return error(30000,"用户非可用状态，不能登录");
}
String md5password = service.encryption(password);
if (byUsername.getPassword().equals(md5password)) {
// 存储Token到数据库
AccessToken accessToken = new AccessToken();
accessToken.setToken(UUID.randomUUID().toString().replaceAll("-", ""));
accessToken.setUser_id(byUsername.getUserId());
tokenService.save(accessToken);
// 返回用户信息
JSONObject user = JSONObject.parseObject(JSONObject.toJSONString(byUsername));
user.put("token", accessToken.getToken());
JSONObject ret = new JSONObject();
ret.put("obj",user);
return success(ret);
} else {
return error(30000, "账号或密码不正确");
}
}
public String select(Map<String,String> query,Map<String,String> config){
StringBuffer sql = new StringBuffer("select ");
sql.append(config.get(FindConfig.FIELD) == null || "".equals(config.get(FindConfig.FIELD)) ? "*" : config.get(FindConfig.FIELD)).append(" ");
sql.append("from ").append("`").append(table).append("`").append(toWhereSql(query, "0".equals(config.get(FindConfig.LIKE))));
if (config.get(FindConfig.GROUP_BY) != null && !"".equals(config.get(FindConfig.GROUP_BY))){
sql.append("group by ").append(config.get(FindConfig.GROUP_BY)).append(" ");
}
if (config.get(FindConfig.ORDER_BY) != null && !"".equals(config.get(FindConfig.ORDER_BY))){
sql.append("order by ").append(config.get(FindConfig.ORDER_BY)).append(" ");
}
if (config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE))){
int page = config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE)) ? Integer.parseInt(config.get(FindConfig.PAGE)) : 1;
int limit = config.get(FindConfig.SIZE) != null && !"".equals(config.get(FindConfig.SIZE)) ? Integer.parseInt(config.get(FindConfig.SIZE)) : 10;
sql.append(" limit ").append( (page-1)*limit ).append(" , ").append(limit);
}
log.info("[{}] - 查询操作，sql: {}",table,sql);
return sql.toString();
}
public List selectBaseList(String select) {
List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);
List<E> list = new ArrayList<>();
for (Map<String,Object> map:mapList) {
list.add(JSON.parseObject(JSON.toJSONString(map),eClass));
}
return list;
}
注册模块满足教师和学生两部分，当学生和教师想要进行学生相关信息的查询管理的时候，就必须进行登录，如果没有账号的话，在登录界面，点击“注册”按钮就会跳转到注册的界面，根据提示填写好注册信息，添加提交，注册的信息在数据库中就添加完成了，然后再输入填写好的账号和密码进行登录，其主界面展示如下图4.1所示。
图4.2 注册界面图
注册关键代码如下所示。
/**
* 注册
* @return
*/
@PostMapping("register")
public Map<String, Object> signUp(HttpServletRequest request) throws IOException {
// 查询用户
Map<String, String> query = new HashMap<>();
Map<String,Object> map = service.readBody(request.getReader());
query.put("username",String.valueOf(map.get("username")));
List list = service.selectBaseList(service.select(query, new HashMap<>()));
if (list.size()>0){
return error(30000, "用户已存在");
}
map.put("password",service.encryption(String.valueOf(map.get("password"))));
service.insert(map);
return success(1);
}
public Map<String,Object> readBody(BufferedReader reader){
BufferedReader br = null;
StringBuilder sb = new StringBuilder("");
try{
br = reader;
String str;
while ((str = br.readLine()) != null){
sb.append(str);
}
br.close();
String json = sb.toString();
return JSONObject.parseObject(json, Map.class);
}catch (IOException e){
e.printStackTrace();
}finally{
if (null != br){
try{
br.close();
}catch (IOException e){
e.printStackTrace();
}
}
}
return null;
}
public void insert(Map<String,Object> body){
E entity = JSON.parseObject(JSON.toJSONString(body),eClass);
baseMapper.insert(entity);
log.info("[{}] - 插入操作：{}",entity);
}
管理员可以对系统中所有的用户角色进行管控，包含了管理员、学生以及教师这三种角色，如果需要添加新的用户，点击页面中的“添加”按钮根据提示输入上用户信息，点击“提交”以后在对应的用户界面就可以查看到了，可以点击用户后面的“删除”按钮直接删除某一用户，这里以教师用户为例。界面如下图4.3所示。
图4.3 用户管理界面图
用户管理关键代码如下所示。
/**
* 用户组：用于用户前端身份和鉴权(UserGroup)表实体类
*
* @author xxx
*@since 202X-XX-XX
*/
@TableName("user_group")
@Data
@EqualsAndHashCode(callSuper = false)
public class UserGroup implements Serializable {
private static final long serialVersionUID = 968356951391304707L;
/**
* 用户组ID：[0,8388607]
*/
@TableId(value = "group_id", type = IdType.AUTO)
private Integer groupId;
/**
* 显示顺序：[0,1000]
*/
@TableField(value = "display")
private Integer display;
/**
* 名称：[0,16]
*/
@TableField(value = "name")
private String name;
/**
* 描述：[0,255]描述该用户组的特点或权限范围
*/
@TableField(value = "description")
private String description;
/**
* 来源表：
*/
@TableField(value = "source_table")
private String sourceTable;
/**
* 来源字段：
*/
@TableField(value = "source_field")
private String sourceField;
/**
* 注册位置:
*/
@TableField(value = "register")
private String register;
/**
* 创建时间:
*/
@TableField(value = "create_time")
private Timestamp createTime;
/**
* 更新时间:
*/
@TableField(value = "update_time")
private Timestamp updateTime;
}
/**
* 所在用户组：[0,32767]决定用户身份和权限
*/
@TableField(value = "user_group")
private String userGroup;
/**
* 用户组：用于用户前端身份和鉴权(UserGroup)表控制层
*
*/
@RestController
@RequestMapping("user_group")
public class UserGroupController extends BaseController<UserGroup, UserGroupService> {
/**
* 服务对象
*/
@Autowired
public UserGroupController(UserGroupService service) {
setService(service);
}
}
-
- 学生管理模块
管理员和学生点击“学生信息”这个按钮可以查看到系统中的学生信息，支持通过学生姓名或者班级名称或者学生档案进行查询学生信息，如果想要添加新的学生信息，点击“添加”按钮然后根据提示输入学生信息，点击“提交”后，在学生管理界面就会显示新增的学生信息，可以点击某一学生信息查看学生信息的详情，也可以直接点击“删除”进行删除学生信息。界面如下图4.4所示。
图4.4 学生管理界面图
学生管理关键代码如下所示。
@RequestMapping("/get_list")
public Map<String, Object> getList(HttpServletRequest request) {
Map<String, Object> map = service.selectToPage(service.readQuery(request), service.readConfig(request));
return success(map);
}
-
- 分配任务模块
点击“分配任务”这个菜单，可以查看到系统中所有查询的分配任务信息，支持通过任务编号对任务信息进行查询，如果想要了解某一任务的详细信息，点击后面的“详情”会进入详情界面，学生和管理员如果想要选择某一分配任务，点击“任务”按钮，根据提示填写对应的信息，点击“提交”按钮，信息没有错误在数据库就会提交成功。界面如下图4.5所示。
图4.5 分配任务界面图
分配任务管理关键代码如下所示。
@PostMapping("/set")
@Transactional
public Map<String, Object> set(HttpServletRequest request) throws IOException {
service.update(service.readQuery(request), service.readConfig(request), service.readBody(request.getReader()));
return success(1);
}
-
- 完成任务模块
学生点击“完成任务信息”这个按钮可以查看到自己提交的完成任务信息，支持通过班级名称或者学生姓名进行查询完成任务信息，如果想要了解某一完成任务的详细信息，点击后面的“查看”会进入详情界面，也支持对自己选择的完成任务进行删除；教师和管理员可以对学生提交的完成任务进行查询，选择某一完成任务，点击后面的“任务”按钮，根据提示输入对应的信息，点击“提交”后，完成任务就录入成功了。界面如下图4.6所示。
图4.6 完成任务界面图
-
- 打卡签到模块
学生点击“打卡签到”这个按钮可以查看到自己所有打卡签到信息，支持通过班级名称或者学生姓名进行查询打卡签到信息，管理员和教师可以对所打卡签到信息进行删除。界面如下图4.7所示。
图4.7 打卡签到界面图
打卡签到管理关键代码：
@RequestMapping("/get_obj")
public Map<String, Object> obj(HttpServletRequest request) {
List resultList = service.selectBaseList(service.select(service.readQuery(request), service.readConfig(request)));
if (resultList.size() > 0) {
JSONObject jsonObject = new JSONObject();
jsonObject.put("obj",resultList.get(0));
return success(jsonObject);
} else {
return success(null);
}
}
-
- 师生交流管理模块
点击“师生交流”这个菜单，可以查看到系统中所有添加的师生交流信息，支持通过标题对师生交流信息进行查询，只有管理员用户可以添加新的师生交流内容，点击“添加”按钮，根据提示输入师生交流信息，点击“提交”按钮，新的师生交流信息就在系统中显示出来了，也可以对添加的师生交流信息进行删除。界面如下图4.8所示。
图4.8 师生交流界面图
通过前面章节的介绍，我们可以看到本学生信息管理系统已经完成了，但是能不能投入使用还是未知，因为在每个项目正式使用之前必须对开发的项目进行测试，如果不进行测试一旦投入使用可能会出现很多未可知的问题，比如使用人数太多导致系统瘫痪，比如某一功能存在bug信息填写错误等等，这些错误将给使用者带来很多的困扰，甚至造成更大的损失，因此测试是项目投入使用的最后一步，为用户提供一个运行顺畅、完美的项目也就是我们进行最后测试的目的。
用户登录功能测试：
表5.1 用户登录功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 用户登录模块测试 |
用户登录成功的情况 |
点击前登录界面输入账号和密码分别输入admin和admin后点击“登录”按钮。 |
登录成功并调整到用户界面 |
正确 |
学生信息添加功能测试：
表5.2 学生信息添加功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 学生添加模块测试 |
学生添加成功的情况 |
在学生的页面中将点击添加，输入学生关信息，输入正确的信息后然后点击“提交”按钮。 |
提示添加成功 |
正确 |
| 学生添加模块测试 |
学生添加失败的情况 |
在学生页面中不填写的体温、健康码信息，其他信息正常输入“提交”按钮。 |
提示“添加失败，信息不能为空” |
正确 |
查询打卡签到信息功能模块测试：
表5.3 查询打卡签到信息功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 查询打卡签到信息功能测试 |
查询成功的情况 |
在打卡签到界面输入班级名称或者学生姓名进行查询 |
查询成功 |
正确 |
师生交流信息添加功能测试：
表5.4 师生交流添加功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 师生交流添加模块测试 |
师生交流添加成功的情况 |
在师生交流的页面中将点击添加，输入课程相关信息，输入正确的信息后然后点击“提交”按钮。 |
提示添加成功 |
正确 |
| 师生交流添加模块测试 |
师生交流添加失败的情况 |
在师生交流页面中不填写的请假时间，其他信息正常输入“提交”按钮。 |
提示“添加失败，信息不能为空” |
正确 |
通过编写学生信息管理系统的测试用例，已经检测完毕用户的登录模块、学生信息添加模块、查询打卡签到模块、师生交流添加模块的功能测试，在对以上功能得测试过程中，发现了系统中的很多漏送并进行了完善，经过多人在线进行测试，系统完全可以正常运行，当然在后期的维护中系统将不断完善。
在开发本学生信息管理系统之前我胸有成竹，觉得很简单，但在实际的开发中我发现了自身的很多问题，许多编程思想和方法都还没有掌握牢靠，比如Bootsatrp、Jquery、AJAX 、Spring、SpringMVC、mybeatis等许多Java Web开发技术，通过开发这个学生信息管理系统我成长了很多，懂得了做什么事情都要脚踏实地，不能眼高手低，在本次学生信息管理系统的开发中我逐渐掌握逐渐熟悉的技术。
本次学生信息管理系统的开发中我还学会了例如良好的编程思想和完善的规划思想。在着手编程之前需要罗列出程序框架的大概，脑海中构建出程序的主题框架。做好这一步我们才能胸有成竹的经行开发项目。当设计框架了熟于心之后，需要思考本次编程所需的主要知识点和技术点，并充分学习。如此一来项目的开发才能循序渐进、如丝般顺滑，长久以往就能养成良好的开发习惯。一个程序好不好还要看出的bug多不多，如果在项目完成前做好bug的查验与预防可能发生的事故才能保证程序的稳定长久性运行。如果项目在完工后出现各种问题自己，那么在进入社会后，不仅会给公司团队带来麻烦和增加不必要的工作，还会导致客户流失，公司对自己的评价下降。
在本次项目中我也暴露了诸多问题。对于Java的编程知识有所欠缺，环境配置和算法上出现诸多问题，时常导致项目运行出错，或者目标的实现有问题。或者实现想法时算法未优化，使得代码冗长，程序运行不顺畅。
- 杨一帆.服务于MySQL数据库的在线监测系统设计[J].自动化技术与应用,2022,41(10):179-182.
- 谢霜.基于Java技术的网络管理体系结构的应用[J].网络安全技术与应用,2022(10):14-15.
[3]王强.基于B/S架构的高校学生信息管理系统设计[J].电子技术与软件工程,2022(17):195-198.
[4]储宝龙.基于B/S结构的中职学校学生管理信息系统的设计[J].现代信息科技,2022,6(16):36-38+42.
[5]郑戟明,董云朝,柳青.MySQL数据库数据导入导出方法的探讨[J].电脑知识与技术,2022,18(22):24-25.
[6]杨迎.Java技术在嵌入式系统中的作用探讨[J].无线互联科技,2022,19(14):96-98.
[7]徐晓.基于Java技术的微信公众号自定义菜单的研究[J].电脑知识与技术,2022,18(21):111-112.DOI:10.14004/j.cnki.ckt.2022.1249.
[8]王莉莉.基于Web的学生信息管理系统设计与实现[J].信息记录材料,2022,23(07):154-158.
[9]童浩卓.基于Spring Cloud框架的分布式学生信息管理系统设计[J].信息技术与信息化,2022(04):69-72.
[10]Yang Mingfeng,Wang Jianying. The Security of Student Information Management System Based upon Blockchain[J]. Journal of Electrical and Computer Engineering,2022,2022.
[11]夏寅,吴郑红,陈群,金薇婕.上海市基础教育学生信息管理系统建设及应用实践[J].教育传播与技术,2022(02):74-78.
[12]金翠荣.学生信息管理系统开发与设计[J].电脑编程技巧与维护,2022(03):65-67.DOI:10.16184/j.cnki.comprg.2022.03.029.
[13]金晶. 一种基于计算机的学生信息管理系统[P]. 辽宁省：CN215117566U,2021-12-10.
[14]Feng Shuo,Zhan Ling,Zhao Hong. Construction and Realization of University Student Information Management System Based on Big Data Technology[J]. Journal of Physics: Conference Series,2021,1992(4).
[15]Yin XueHong. Construction of Student Information Management System Based on Data Mining and Clustering Algorithm[J]. COMPLEXITY,2021,2021.
[16]江金娜. 高校成人教育学生信息管理系统的分析与设计[D].广东工业大学,2019.DOI:10.27029/d.cnki.ggdgu.2019.000729.
[17]左丹. 高校学生信息管理系统需求分析和评价体系设计[C]//.人文学术：过程与方法.,2016:116-122.
致谢
至此论文结束，感谢您的阅读。在此我要特别的感谢我的导师，虽然我在实习期间很忙，论文撰写的时候经常是停停改改，但是我的导师依旧十分的负责，时不时的询问我的任务进展情况，跟进我的论文进度，在指导老师的帮助下，我逐步完成了自己的论文和程序，从导师身上也学习到很多知识和经验，这些知识和经验令我受益匪浅。同时我也从导师身上看到了自己的不足，不论是在技术层面上还是在对待工作的态度上，导师如同明镜一般照出了我的缺点我的不足。此外，我还要感谢在我实习期间在论文和程序上帮助过我的同学和社会人士，此前我对于SSM框架方面的一些知识还不了解，是他们在我编写程序过程中给了我很多的启发和感想，也帮助了我对于程序的调试和检测。没有他们我是不能顺利完成本次毕业设计的。至此，我的毕业设计就花上了一个圆满的句号了。
请关注点赞+私信博主，免费领取项目源码