1. 2 Paper structure and chapter arrangement
2 System analysis of teacher and student honor management system
2.2.2 Data modification process
3 Overall design of teacher and student honor management system
3.1 System architecture design
3.2 System function module design
3.2.1 Overall functional module design
3.2.3 Honor information management module design
3.2.4 Design of teacher honor management module
3.3.1 Database conceptual structure design
3.3.2 Database logical structure design
4 Detailed design and implementation of teacher and student honor management system
Honor management is part of the school's work, and the previous manual operations are very inconvenient for future maintenance and use. The developed teacher-student honor management system is a management software specially used to register and collect statistics on the honor information of school staff (including students). It is developed based on PHP and Thinkphp frameworks and can provide a cross-platform and cross-system system for school students and staff. digital management services. The school can easily review this part of the information through this platform during semester assessment or promotion, and it provides a blueprint for subsequent use. With this system, the school honor information of teachers and students can be queried at any time, which not only facilitates the management of the school, but also greatly improves work efficiency. At the same time, school managers can easily query and summarize, and the school website can also link to the data in this system to display the school's latest honors in a timely manner.
Keywords : teacher and student honor management; PHP; MySQL; Thinkphp framework
Abstract
Honor management is a part of the school's work. The previous manual operation is very inconvenient for future maintenance and use. The developed honor management system for teachers and students is a management software specially used to register and count the honor information of school faculty (including students). It is developed based on PHP and Thinkphp framework, and can provide a cross-platform and cross-system digital management service for school students and faculty. The school can easily review this part of information through this platform during the semester's assessment or promotion, and provide a blueprint for subsequent use. With this system, the honor information of teachers and students can be queried at any time, which not only facilitates the management of the school, but also greatly improves the work efficiency. At the same time, school administrators can easily query and summarize, and the school website can also link the data of the system to display the latest honor of the school in time.
Keywords: Honor management of teachers and students; PHP； MySQL； Thinkphp framework
1Introduction _
1.1 Research background and significance
Today in the 21st century, with the vigorous development of Internet technology, especially the development of network technology and database technology, great changes have taken place in the way people work and live. The application of network technology makes it possible to communicate, exchange and share information between computers, and the widespread application of database technology provides people with massive data storage, data analysis, information retrieval and other functions, so that work can be performed more efficiently.
In our country, education has an important and far-reaching impact on the country's prosperity. Once it became an important industry in the country, with the deepening of reform and opening up and the further development of the market economy, education has received strong support from the country and society based on the unique national conditions of our country. All walks of life attach great importance to it, which has led to the rapid development of the education industry in the direction of standardization and modernization. However, compared with developed countries, the level and application of information digitization in my country's education industry is still relatively low. It only developed earlier in large and medium-sized cities. Only in relatively large colleges and universities are computers actually used for large-scale operations, which improves work efficiency in all aspects and achieves good social and economic benefits. However, some emerging and smaller schools do not yet fully possess this function. Therefore, it can be seen that with the rapid development of education in our country, the application of information technology will become more extensive and in-depth, leading to a gradual transition to information digitization.
In our country, various digital management systems in major educational institutions and schools are not a new topic, but some units do not have any digital management systems at all, and almost all work is still done manually. In particular, the honor management of students and faculty in schools is very little. The honor management of student teachers and schools is all done manually. In many cases, notifications are sent to faculty and staff to hand in only when they are collected and used, and some faculty and staff No notification was received, which caused great inconvenience to the management staff. Today, with the rapid advancement of computer technology, this management method appears to be very backward, extremely inefficient, very costly, and extremely error-prone. With the development of society, digitalization is an inevitable trend in social process. School management can only exert its value if it is fast, accurate and precise.
Therefore, using machines to replace part of human work is an inevitable historical development trend. Unit leaders must pay attention and support to truly change from manual operations to computer-based digital systems. Manual operations will be replaced by computers.
1. 2 Paper structure and chapter arrangement
The paper will be organized hierarchically. In addition to the abstract, acknowledgments and literature reference section, the main text will also analyze the website requirements, describe the general design and implemented functions, and finally list some debugging records. The main structure of the paper is as follows:
Chapter 1: Introduction. The first chapter mainly introduces the background of the project research, the significance of system development and the research content and main work of this article.
Chapter 2: System requirements analysis. Chapter 2 mainly conducts demand analysis from the aspects of users and functions of the system.
Chapter 3: System Design. Chapter 3 mainly carries out functional design of the system framework, system function modules and database.
Chapter 4: System implementation. Chapter 4 mainly introduces the system framework construction and the implementation of the system interface.
Chapter 5: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions.
2 System analysis of teacher and student honor management system
System analysis is a prerequisite for developing a project. Through system analysis, the basic needs of the main users of the system can be well understood, and this is also the reason for the development of the project. Then, a feasibility analysis is performed on the system development, which usually includes technical feasibility, economic feasibility, etc. The feasibility analysis is also an analysis from the overall perspective of the project. Then the specific requirements of the project are analyzed. The analysis method is generally implemented through the user's use case diagram. The following is a detailed introduction.
2.1 Feasibility analysis
Economic feasibility here only represents the operation and maintenance costs of the website, and development costs are not considered here.
At present, the number of information management systems under this model is increasing day by day. Online query and management of teacher and student honor-related information has become popular and popular. The number of users is on the rise. When the number of users becomes huge, the operation and maintenance costs can be covered by advertising fees. Fill, including development costs.
So there is no problem with economic feasibility.
(2) Operational feasibility:
The design of this project refers to several cases of website development under this mode, analyzes their operation interfaces, and combines many cases to highlight people-oriented simplified operations, so people with basic computer knowledge can operate this project.
Therefore, there is no problem with operational feasibility.
(3) Technical feasibility:
Technical feasibility refers to the feasibility of building a framework, as well as the system's adaptability to technological upgrading when better technologies emerge, and the development time and cost ratio.
The existing PHP language can cater to the construction of all e-commerce systems, and the scalability of system technology equipment can be promoted by the resource advantages of the Thinkphp architecture. I used the compiler eclipse+PHP+mysql to run the entire program.
In summary, there is no problem with the technical feasibility.
(4) Legal feasibility:
From a developer's perspective, the Thinkphp framework is open source and free online, and will not cause any legal disputes regarding intellectual property rights.
From a user perspective, as long as contraband is no longer sold on the system, treaties and agreements are made with the system, and illegal payments are eliminated.
In summary, there is no problem with the legal feasibility.
The business process uses some specific symbols and lines to demonstrate the user's process when using the system. When performing system analysis, the business process can help developers better understand the business, discover errors, and improve the system.
After the user successfully logs in to the system , the user can add data. The number of the added data is specific and generated by the system. The user cannot fill it in at will. Except for the number, the user fills in other added information by himself. The filled-in information is verified by the system and is legal. If it passes, it will show that the data has been added successfully. If it is passed, it will not be added successfully. Figure 2-1 shows the process of adding data.
Figure 2-1 Data addition flow chart
2.2.2 Data modification process
The process of data modification is similar to the process of data addition described above, as shown in Figure 2-2 .
Figure 2-2 Data modification flow chart
If there is some useless data in the system , the relevant managers can also delete the data. Figure 2-3 is the flow chart for data deletion.
Figure 2-3 Data deletion flow chart
According to the roles of the teacher-student honor management system, I divided it into three parts: student, teacher module and administrator module.
Student/teacher management module:
(1) Registration and login: Visitors can enter the system at any time and browse the information in the system. However, if they want to make an outpatient appointment, they must have an account in this system. If they do not have an account, they can register as a member user to perform related operations. At the same time, users can also control personal information and operation information through the "My" button.
(2) Announcement table: After logging in, students/teachers can click on the announcement table to view announcement information, etc.
(3) Student Honors: Students/teachers click the "Student Honors" menu button to view various honor information of school students and then search for a certain student.
(3) Teacher Honors: Students/teachers can click the "Teacher Honors" menu button to view various honor information of school teachers and then search for a certain teacher.
Administrator management module:
(1) User management: Administrators can maintain and manage teacher/student users.
(2) Announcement management: Administrators can publish announcement forms for teacher/student users to view.
(3) Honor information management: Administrators can publish honor project information, etc. in the system.
(4) Category management: You can add, delete, modify, and check honor categories.
(5) Student honor management: Administrators maintain and manage student honor information.
(6) Teacher honor management: The administrator maintains and manages teacher honor information.
The non-functional requirements of the teacher-student honor management system include the security, reliability, performance, scalability, etc. of the teacher-student honor management system. The details can be expressed in the following 3-1 table:
Table 2-1 Non-functional requirements table for teacher and student honor management system
| safety |
It mainly refers to the installation of the teacher-student honor management system database. The use of the database and the setting of passwords must comply with the standards. |
| reliability |
Reliability means that the teacher-student honor management system can be operated according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for the teacher-student honor 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 teacher and student honor management system and operate. |
| maintainability |
The maintainability of the development of the teacher-student honor management system is very important. After testing, there is no problem with the maintainability. |
2.4 System use case analysis
Through the analysis of 2.3 functions, the use case diagram of this teacher-student honor management system is obtained:
Figure 2-4 is a use case demonstration of the teacher/student role.
Figure 2-4 Teacher/student role use case diagram of teacher-student honor management system
Figure 2-5 shows the use case of the administrator role.
Figure 2-5 Use case diagram of administrator role in teacher-student honor management system
This chapter mainly determines the functions to be realized by the entire teacher-student honor management system through feasibility analysis, process analysis, functional requirements analysis, and system use case analysis of the teacher-student honor management system. At the same time, it also provides standards for code implementation and testing of the teacher-student honor management system.
3 Overall design of teacher and student honor management system
The main content discussed in this chapter includes the functional module design and database system design of the teacher and student honor management system.
3.1 System architecture design
This teacher and student honor management system is divided into three layers in structure: presentation layer (UI), business logic layer (BLL) and data layer (DL).
Figure 3-1 System architecture design diagram of teacher and student honor management system
Presentation layer (UI): Also known as the UI layer, it mainly completes the UI interaction function of the teacher and student honor management system. A good UI can improve the user experience and enhance the user's comfort when using the teacher and student honor management system. . The UI interface design must also adapt to different versions of teacher and student honor management systems and different size resolutions to achieve good compatibility. The UI interaction function requirements are reasonable, and users must obtain consistent interaction results when performing interactive operations. This requires the presentation layer to be well connected with the business logic layer.
Business Logic Layer (BLL): Mainly completes the data processing function of this teacher and student honor management system. The data transmitted by the user from the presentation layer is processed by the business logic layer and delivered to the data layer. The data read by the system from the data layer is processed by the business logic layer and delivered to the presentation layer.
Data layer (DL): Since the data of the teacher and student honor management system is placed in the mysql database on the server side, the parts that belong to the service layer can be directly integrated into the business logic layer, so there is only the database in the data layer, which is mainly completed The data storage and management functions of this teacher and student honor management system.
3.2 System function module design
3.2.1 Overall functional module design
In the previous chapter, the functional requirements and non-functional requirements of the system were mainly analyzed, and the use cases in this teacher-student honor management system were analyzed based on the requirements. Then the next step is to start designing the architecture, main functions and database of this teacher and student honor management system. The teacher-student honor management system is derived based on the needs analysis in the previous chapter. Its overall design module diagram is shown in Figure 3-2.
Figure 3-2 Function module diagram of teacher and student honor management system
3.2.2 User module design
Users of this system include administrators, teachers/students. The functions of the three user modules are basically the same. The user module structure diagram is taken as an example for analysis, as shown below:
Figure 3-3 User module structure diagram
3.2.3 Honor information management module design
The teacher and student honor management system can add, delete, modify and check honor information. The specific structure diagram is as follows:
Figure 3-4 Honor information module structure diagram
3.2.4 Design of teacher honor management module
In the teacher-student honor management system, users can query teacher honor information online , etc. Its module function structure, the specific structure diagram is as follows:
Figure 3-5 Teacher Honors Module Structure Diagram
Database design generally includes three major processes: demand analysis, conceptual model design, and database table creation. The demand analysis has been explained in the previous chapter, and the conceptual model design has two parts: conceptual model and logical structure design.
3.3.1 Database conceptual structure design
The following is the main ER entity relationship diagram of the main database tables in the entire teacher-student honor management system.
Figure 3-6 Overall ER relationship diagram of the teacher-student honor management system
3.3.2 Database logical structure design
From the total ER relationship diagram in the teacher-student honor management system in the previous section, it can be concluded that a total of many data tables need to be created. Here I mainly list several major database table structure designs.
Table access_token (login access duration)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
Defaults |
illustrate |
| 1 |
token_id |
int |
10 |
0 |
N |
Y |
Temporary access badge ID |
|
| 2 |
token |
varchar |
64 |
0 |
Y |
N |
temporary access badge |
|
| 3 |
info |
text |
65535 |
0 |
Y |
N |
||
| 4 |
maxage |
int |
10 |
0 |
N |
N |
2 |
Maximum lifespan: Default 2 hours |
| 5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
user ID: |
Table announcement_information (announcement information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
Defaults |
illustrate |
| 1 |
announcement_information_id |
int |
10 |
0 |
N |
Y |
Announcement information ID |
|
| 2 |
announcement_no |
varchar |
64 |
0 |
Y |
N |
Bulletin No. |
|
| 3 |
announcement_title |
varchar |
64 |
0 |
Y |
N |
Announcement title |
|
| 4 |
publisher |
varchar |
64 |
0 |
Y |
N |
publisher |
|
| 5 |
release_date |
date |
10 |
0 |
Y |
N |
release date |
|
| 6 |
announcement_content |
text |
65535 |
0 |
Y |
N |
Announcement content |
|
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table auth (user rights management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
Defaults |
illustrate |
| 1 |
auth_id |
int |
10 |
0 |
N |
Y |
Authorization ID: |
|
| 2 |
user_group |
varchar |
64 |
0 |
Y |
N |
user group: |
|
| 3 |
mod_name |
varchar |
64 |
0 |
Y |
N |
Module name: |
|
| 4 |
table_name |
varchar |
64 |
0 |
Y |
N |
Table Name: |
|
| 5 |
page_title |
varchar |
255 |
0 |
Y |
N |
page title: |
|
| 6 |
path |
varchar |
255 |
0 |
Y |
N |
Routing path: |
|
| 7 |
position |
varchar |
32 |
0 |
Y |
N |
Location: |
|
| 8 |
mode |
varchar |
32 |
0 |
N |
N |
_blank |
Jump method: |
| 9 |
add |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to add: |
| 10 |
of the |
tinyint |
3 |
0 |
N |
N |
1 |
是否可删除： |
| 11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
是否可修改： |
| 12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
是否可查看： |
| 13 |
field_add |
varchar |
500 |
0 |
Y |
N |
添加字段： |
|
| 14 |
field_set |
varchar |
500 |
0 |
Y |
N |
修改字段： |
|
| 15 |
field_get |
varchar |
500 |
0 |
Y |
N |
查询字段： |
|
| 16 |
table_nav_name |
varchar |
500 |
0 |
Y |
N |
跨表导航名称： |
|
| 17 |
table_nav |
varchar |
500 |
0 |
Y |
N |
跨表导航： |
|
| 18 |
option |
text |
65535 |
0 |
Y |
N |
配置： |
|
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表category_management (类别管理)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
category_management_id |
int |
10 |
0 |
N |
Y |
类别管理ID |
|
| 2 |
honor_category |
varchar |
64 |
0 |
Y |
N |
荣誉类别 |
|
| 3 |
category_description |
text |
65535 |
0 |
Y |
N |
类别描述 |
|
| 4 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 5 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表hits (用户点击)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hits_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
表honorary_information (荣誉信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
honorary_information_id |
int |
10 |
0 |
N |
Y |
荣誉信息ID |
|
| 2 |
title_name |
varchar |
64 |
0 |
Y |
N |
标题名称 |
|
| 3 |
statistical_name |
varchar |
64 |
0 |
Y |
N |
统计名称 |
|
| 4 |
number_of_honors |
int |
10 |
0 |
Y |
N |
0 |
荣誉数量 |
| 5 |
remarks |
text |
65535 |
0 |
Y |
N |
备注信息 |
|
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表honors_of_teachers (教师荣誉)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
honors_of_teachers_id |
int |
10 |
0 |
N |
Y |
教师荣誉ID |
|
| 2 |
honor_category |
varchar |
64 |
0 |
Y |
N |
荣誉类别 |
|
| 3 |
honor_level |
varchar |
64 |
0 |
Y |
N |
荣誉等级 |
|
| 4 |
award_date |
date |
10 |
0 |
Y |
N |
获奖日期 |
|
| 5 |
teacher_information |
int |
10 |
0 |
Y |
N |
0 |
教师信息 |
| 6 |
teachers_name |
varchar |
64 |
0 |
Y |
N |
教师姓名 |
|
| 7 |
college_name |
varchar |
64 |
0 |
Y |
N |
学院名称 |
|
| 8 |
class_name |
varchar |
64 |
0 |
Y |
N |
班级名称 |
|
| 9 |
major_name |
varchar |
64 |
0 |
Y |
N |
专业名称 |
|
| 10 |
honorary_introduction |
text |
65535 |
0 |
Y |
N |
荣誉介绍 |
|
| 11 |
remarks |
text |
65535 |
0 |
Y |
N |
备注信息 |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表student_honors (学生荣誉)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
student_honors_id |
int |
10 |
0 |
N |
Y |
学生荣誉ID |
|
| 2 |
honor_category |
varchar |
64 |
0 |
Y |
N |
荣誉类别 |
|
| 3 |
honor_level |
varchar |
64 |
0 |
Y |
N |
荣誉等级 |
|
| 4 |
award_date |
date |
10 |
0 |
Y |
N |
获奖日期 |
|
| 5 |
student_information |
int |
10 |
0 |
Y |
N |
0 |
学生信息 |
| 6 |
student_name |
varchar |
64 |
0 |
Y |
N |
学生姓名 |
|
| 7 |
college_name |
varchar |
64 |
0 |
Y |
N |
学院名称 |
|
| 8 |
class_name |
varchar |
64 |
0 |
Y |
N |
班级名称 |
|
| 9 |
major_name |
varchar |
64 |
0 |
Y |
N |
专业名称 |
|
| 10 |
honorary_introduction |
text |
65535 |
0 |
Y |
N |
荣誉介绍 |
|
| 11 |
remarks |
text |
65535 |
0 |
Y |
N |
备注信息 |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表student_users (学生用户)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
student_users_id |
int |
10 |
0 |
N |
Y |
学生用户ID |
|
| 2 |
student_name |
varchar |
64 |
0 |
Y |
N |
学生姓名 |
|
| 3 |
student_gender |
varchar |
64 |
0 |
Y |
N |
学生性别 |
|
| 4 |
student_id |
varchar |
64 |
0 |
N |
N |
学生学号 |
|
| 5 |
college_name |
varchar |
64 |
0 |
Y |
N |
学院名称 |
|
| 6 |
class_name |
varchar |
64 |
0 |
Y |
N |
班级名称 |
|
| 7 |
major_name |
varchar |
64 |
0 |
Y |
N |
专业名称 |
|
| 8 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 10 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表teacher_user (教师用户)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
teacher_user_id |
int |
10 |
0 |
N |
Y |
教师用户ID |
|
| 2 |
teachers_name |
varchar |
64 |
0 |
Y |
N |
教师姓名 |
|
| 3 |
gender_of_teachers |
varchar |
64 |
0 |
Y |
N |
教师性别 |
|
| 4 |
teacher_id |
varchar |
64 |
0 |
N |
N |
教师工号 |
|
| 5 |
college_name |
varchar |
64 |
0 |
Y |
N |
学院名称 |
|
| 6 |
class_name |
varchar |
64 |
0 |
Y |
N |
班级名称 |
|
| 7 |
major_name |
varchar |
64 |
0 |
Y |
N |
专业名称 |
|
| 8 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 10 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表upload (文件上传)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
upload_id |
int |
10 |
0 |
N |
Y |
上传ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
文件名 |
|
| 3 |
path |
varchar |
255 |
0 |
Y |
N |
访问路径 |
|
| 4 |
file |
varchar |
255 |
0 |
Y |
N |
文件路径 |
|
| 5 |
display |
varchar |
255 |
0 |
Y |
N |
显示顺序 |
|
| 6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
父级ID |
| 7 |
dir |
varchar |
255 |
0 |
Y |
N |
文件夹 |
|
| 8 |
type |
varchar |
32 |
0 |
Y |
N |
文件类型 |
表user (用户账户：用于保存用户登录信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
user_id |
mediumint |
8 |
0 |
N |
Y |
用户ID：[0,8388607]用户获取其他与用户相关的数据 |
|
| 2 |
state |
smallint |
5 |
0 |
N |
N |
1 |
账户状态：[0,10](1可用|2异常|3已冻结|4已注销) |
| 3 |
user_group |
varchar |
32 |
0 |
Y |
N |
所在用户组：[0,32767]决定用户身份和权限 |
|
| 4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
上次登录时间： |
| 5 |
phone |
varchar |
11 |
0 |
Y |
N |
手机号码：[0,11]用户的手机号码，用于找回密码时或登录时 |
|
| 6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
手机认证：[0,1](0未认证|1审核中|2已认证) |
| 7 |
username |
varchar |
16 |
0 |
N |
N |
用户名：[0,16]用户登录时所用的账户名称 |
|
| 8 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称：[0,16] |
|
| 9 |
password |
varchar |
64 |
0 |
N |
N |
密码：[0,32]用户登录所需的密码，由6-16位数字或英文组成 |
|
| 10 |
|
varchar |
64 |
0 |
Y |
N |
邮箱：[0,64]用户的邮箱，用于找回密码时或登录时 |
|
| 11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
邮箱认证：[0,1](0未认证|1审核中|2已认证) |
| 12 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
表user_group (用户组：用于用户前端身份和鉴权)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
用户组ID：[0,8388607] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
显示顺序：[0,1000] |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
名称：[0,16] |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]描述该用户组的特点或权限范围 |
|
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
注册位置: |
| 9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
整个师生荣誉管理系统的需求分析主要对系统总体架构以及功能模块的设计，通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。
4 师生荣誉管理系统详细设计与实现
师生荣誉管理系统的详细设计与实现主要是根据前面的师生荣誉管理系统的需求分析和师生荣誉管理系统的总体设计来设计页面并实现业务逻辑。主要从师生荣誉管理系统界面实现、业务逻辑实现这两部分进行介绍。
4.1用户功能模块
4.1.1 教师首页界面
当进入师生荣誉管理系统的时候，系统以上中下的布局进行展示，首先映入眼帘的是系统的导航栏，下面是公告信息，再往下是各种各样的系统信息，其主界面展示如下图4-1所示。
图4-1 教师首页界面图
首页的逻辑代码如下所示。
public function upload()
{
//上传文件目录获取
$month = date('Ym', time());
$data = 'file';//文件域
$path = 'upload/file/' . $month . "/";//上传文件保存位置
$allow_ext = explode(",", "jpg,jpeg,png,jfif,bmp,gif,ico,xls,xlsx,AVI,mov,rmvb,rm,FLV,mp4,3GP");
if ($_FILES) {
$file = $_FILES[$data];
$rst = [];
if (!empty($file['name'])) {
$file_type = explode('.', $file['name']);
$ext = end($file_type); //获取文件的格式
$ext = strtolower($ext);
if (!in_array($ext, $allow_ext)) {
$rst['error']['code'] = 30000;
$rst['message'] = '只能上传jpg,jpeg,png,jfif,bmp,gif,ico,xls,xlsx,AVI,mov,rmvb,rm,FLV,mp4,3GP类型文件';
} else {
if (!is_dir($path))//判断目录是否存在
{
mkdir($path, 0777, true);//如果目录不存在则创建目录
};
$name = date('YmdHis') . '_' . rand(10000, 99999) . '.' . $ext;
$save_rst = move_uploaded_file($file['tmp_name'], $path . $name);
if ($save_rst !== false) {
// $rst['code'] = 1;
$rst['result']['url'] = 'http://'.$_SERVER['HTTP_HOST'].'/'.$path . $name;
// $rst['ext'] = $ext;
} else {
$rst['error']['code'] = 30000;
$rst['error']['message'] = '文件上传失败';
}
}
} else {
$rst['error']['code'] = 30000;
$rst['error']['message'] = '未选择文件';
}
} else {
$rst['error']['code'] = 30000;
$rst['error']['message'] = '未获取到文件';
}
return json_encode($rst);
}
4.1.2 教师登录界面
当教师输入完整的自己的账户名和密码信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到师生荣誉管理系统的首页中；否则将会提示相应错误信息，教师登录界面如下图4-2所示。
图4-2教师登录界面图
教师登录的逻辑代码如下所示。
public function login()
{
if (Request::isPost()) {
$request = Request::param();
$result = $this->validate($request, $this->validate);
if (true !== $result) {
// 验证失败 输出错误信息
$data['error'] = 30000;
$data['message'] = $result;
} else {
$request['password'] = md5($request['password']);
$result = $this->model->login($request, $this->table);
$data = $result;
}
} else {
$data['error'] = 30000;
$data['message'] = "field的值不能为空！";
}
return json_encode($data);
}
public function login($request=[],$table_name = ''){
$username = $request['username'];
$password = $request['password'];
$bol = $this->where(['username'=>$username])->find();
if ($bol){
$password = md5($password);
if ($request['password']==$bol['password']) {
//添加token信息
$access_token['create_time'] = date('Y-m-d H:i:s');
$access_token['update_time'] = date('Y-m-d H:i:s');
$access_token['info'] = json_encode($bol);
// $access_token['info'] = $bol;
$access_token['token'] = md5(date('Y-m-d H:i:s'));
$bol_token = Db::name('AccessToken')->insert($access_token);
if ($bol_token){
$data['obj'] = $bol;
$data['obj']['token'] = $access_token['token'];
return ['result' => $data];
}else{
return ['error' => ['code' => 5000, 'message' => '登录失败,token生成失败']];
}
} else {
return ['error' => ['code' => 5000, 'message' => '登录失败,密码不正确']];
}
}else{
return ['error' => ['code' => 5000, 'message' => '登录失败,账号不存在']];
}
}
4.1.3公告信息界面
当点击导航栏上的“公告信息”的时候，就会进入对应的界面查看公告信息，公告信息界面如下图4-3所示。
图4-3公告信息界面图
公告信息的逻辑代码如下所示。
public function sum()
{
$request = Request::param();
if (isset($request['field'])) {
if (!empty($request['field'])) {
$result = $this->model->sum_field($request, $this->table, $this->table_id);
$data = $result;
} else {
$data['error']['code'] = 30000;
$data['error']['message'] = "field的值不能为空！";
}
} else {
$data['error']['code'] = 30000;
$data['error']['message'] = "field的值不能为空！";
}
return json_encode($data);
}
4.1.4 教师荣誉界面
教师登录系统后可以点击“教师荣誉”菜单，对自己的荣誉信息进行查看了解等，教师荣誉界面如下图4-4所示。
图4-4教师荣誉界面图
教师荣誉的逻辑代码如下：
public function sum_group()
{
$request = Request::param();
if (isset($request['groupby']) && isset($request['field'])) {
if (!empty($request['groupby']) && !empty($request['field'])) {
$result = $this->model->sum_group($request, $this->table, $this->table_id);
$data = $result;
} else {
$data['error']['code'] = 30000;
$data['error']['message'] = "groupby或者field的值不能为空！";
}
} else {
$data['error']['code'] = 30000;
$data['error']['message'] = "groupby或者field的值不能为空！";
}
return json_encode($data);
}
4.1.5 学生荣誉界面
教师点击“学生荣誉”菜单，可以查看搜索学生荣誉信息，学生荣誉展示页面如图4-5所示。
图4-5 学生荣誉界面图
学生荣誉界面逻辑代码如下：
{
if (Request::isPost()) {
$request = Request::param();
$request['create_time'] = isset($request['create_time']) ? $request['create_time'] : date('Y-m-d H:i:s');
$request['update_time'] = isset($request['update_time']) ? $request['update_time'] : date('Y-m-d H:i:s');
$result = $this->validate($request, $this->validate);
if (true !== $result) {
// 验证失败 输出错误信息
$data['error'] = 30000;
$data['message'] = $result;
} else {
if($this->table == 'user'){
$request['password'] = md5($request['password']);
}
$res = $this->add_before($request, $this->table, $this->table_id);
if($res['code'] == 200){
$result = $this->model->add($request, $this->table, $this->table_id);
$this->add_after($this->table);
$data = $result;
}else{
$data['error'] = $res;
}
}
} else {
$data['error']['code'] = 30000;
$data['error']['message'] = "field的值不能为空！";
}
return json_encode($data);
}
4.2管理员功能模块
4.2.1 荣誉信息管理界面
师生荣誉管理系统中的管理人员在“荣誉信息”这一菜单中是可以对荣誉信息（标题名称、统计名称、荣誉数量、备注信息）进行增删改查操作等。界面如下图4-6所示。
图4-6荣誉信息管理界面图
荣誉信息管理界面逻辑代码如下：
public function get_obj()
{
$request = Request::param();
$result = $this->model->get_obj($request, $this->table, $this->table_id, $this->table_id);
$data['result'] = $result;
return json_encode($data);
}
4.2.2 用户管理界面
师生荣誉管理系统中的管理人员在“教师管理”这一菜单是中可以对注册的教师管理员进行管控，这里以教师管理为例。界面如下图4-7所示。
图4-7教师管理界面图
教师管理界面关键代码如下：
public function count()
{
$request = Request::param();
$result = $this->model->list_count($request, $this->table, $this->table_id);
$data['result'] = $result;
return json_encode($data);
}
4.2.3 教师荣誉管理界面
师生荣誉管理系统中的管理人员在“教师荣誉管理”这一菜单中是可以对教师荣誉信息进行上传发布，界面如下图4-8所示。
图4-8教师荣誉管理界面图
教师荣誉管理界面逻辑代码如下：
public function get_list()
{
$request = Request::param();
$result['list'] = $this->model->get_list($request, $this->table, $this->table_id);
$result['count'] = $this->model->list_count($request, $this->table, $this->table_id);
$data['result'] = $result;
return json_encode($data);
}
4.2.4 学生荣誉管理界面
师生荣誉管理系统中的管理人员在“学生荣誉管理”这一菜单下是可以对学生荣誉信息进行添加发布，其管理界面如下图4-9所示。
图4-9学生荣誉管理界面图
学生荣誉管理界面逻辑代码如下：
public function set()
{
if (Request::isPost()) {
$get = Request::get();
$where = [];
foreach($get as $k => $g){
//过滤参数中的页码信息
if($k != 'page' && $k != 'size'){
$where[$k] = $g;
}
}
$request = Request::post();
if($this->table != 'user'){
$request['update_time'] = isset($request['update_time']) ? $request['update_time'] : date('Y-m-d H:i:s');
}
$result = $this->validate($request, $this->validate);
if (true !== $result) {
// 验证失败 输出错误信息
$data['error'] = 30000;
$data['message'] = $result;
} else {
$result = $this->model->set($request, $this->table, $this->table_id, $where);
$data = $result;
}
} else {
$data['error']['code'] = 30000;
$data['error']['message'] = "field的值不能为空！";
}
return json_encode($data);
}
5系统测试
5.1 系统测试用例
系统测试包括：教师/学生登录功能测试、荣誉信息功能测试、学生荣誉添加、教师荣誉添加、密码修改功能测试，如表5-1、5-2、5-3、5-4、5-5所示：
表5-1 教师/学生登录功能测试表
| 用例名称 |
教师/学生登录系统 |
| 目的 |
测试教师/学生通过正确的教师/学生名和密码可否登录功能 |
| 前提 |
未登录的情况下 |
| 测试流程 |
1) 进入登录页面 2) 输入正确的教师/学生名和密码 |
| 预期结果 |
教师/学生名和密码正确的时候，跳转到登录成功界面，反之则显示错误信息，提示重新输入 |
| 实际结果 |
实际结果与预期结果一致 |
荣誉信息查看功能测试：
表5-2 荣誉信息查看功能测试表
| 用例名称 |
荣誉信息查看 |
| 目的 |
测试荣誉信息查看功能 |
| 前提 |
教师登录 |
| 测试流程 |
点击荣誉信息 |
| 预期结果 |
可以查看到所有荣誉信息信息 |
| 实际结果 |
实际结果与预期结果一致 |
管理员添加学生荣誉界面测试：
表5-3 管理员添加学生荣誉界面测试表
| 用例名称 |
学生荣誉添加测试用例 |
||
| 目的 |
测试学生荣誉添加功能 |
||
| 前提 |
管理员用户正常登录情况下 |
||
| 测试流程 |
1）管理员点击学生荣誉，然后点击添加后并填写信息。 2）点击进行提交。 |
||
| 预期结果 |
提交以后，页面首页会显示新的学生荣誉信息 |
||
| 实际结果 |
实际结果与预期结果一致 |
||
| 实际结果 |
实际结果与预期结果一致 |
||
管理员添加教师荣誉界面测试：
表5-4 管理员添加教师荣誉界面测试表
| 用例名称 |
教师荣誉添加测试用例 |
||
| 目的 |
测试教师荣誉添加功能 |
||
| 前提 |
管理员用户正常登录情况下 |
||
| 测试流程 |
1）管理员点击教师荣誉，然后点击添加后并填写信息。 2）点击进行提交。 |
||
| 预期结果 |
提交以后，页面首页会显示新的教师荣誉信息 |
||
| 实际结果 |
实际结果与预期结果一致 |
||
| 实际结果 |
实际结果与预期结果一致 |
||
密码修改搜索功能测试：
表5-5 密码修改功能测试表
| 用例名称 |
密码修改测试用例 |
| 目的 |
测试管理员密码修改功能 |
| 前提 |
管理员用户正常登录情况下 |
| 测试流程 |
1）管理员密码修改并完成填写。 2）点击进行提交。 |
| 预期结果 |
使用新的密码可以登录 |
| 实际结果 |
实际结果与预期结果一致 |
通过编写师生荣誉管理系统的测试用例，已经检测完毕用户登录功能测试、荣誉信息功能、学生荣誉、教师荣誉、密码修改功能测试，通过这4大模块为师生荣誉管理系统的后期推广运营提供了强力的技术支撑。
此时项目已经完成，即使实施的时间不是很长，但是这个过程中需要准备很长的一段时间去对系统设计开发所实际到的技术进行学习。在学习的过程中，我逐渐认识得到了我自身存在的一些不足。对于一些控制是必要的应用技能，能够理解，整个过程中仅仅是一个掌握了常用的性能和控制方法，我觉得挺容易的。从该系统中，系统的分析和设计的调查数据，并且已经经历了几个月，并努力几个月，该系统已经完成。很显然，该系统仍有很多不成熟，在系统设计过程中有许多技术缺陷存在。在设计的过程中也涉及到了很多自己无法解决的问题，主要通过找专业的网站和论坛来解决这些问题，对于圆满完成我的毕业设计，他们也贡献了很大一部分力量。系统的开发环境和配置都是可以自行安装的，系统使用PHP开发语言，使用比较成熟的Mysql数据库进行对系统前台及后台的数据交互，根据技术语言对数据库，结合需求进行修改维护，可以使得系统运行更具有稳定性和安全性，从而完成实现系统的开发。
系统投入运行时，各功能均运行正常。系统的每个界面的操作符合常规逻辑，对使用者来说操作简单，界面友好。整个系统的各个功能设计合理，体现了人性化。
求职招聘系统的主要特点有：
（1）简单大方，易于操作的 Web 页面；
（2）利用 Ajax 技术使页面进行无刷新更新；
（3）根据用户的浏览和搜索记录，用户可以浏览管理员发布的荣誉列表信息；
（4）有良好的安全性和可扩展性，增强了系统的可靠性，使系统保持持久的生命力。
由于时间限制和本人能力条件有限，该系统还存在一些不足，今后也会出现许多新的开发技术，未来还可以对系统做出如下改进：
（1）优化系统页面，使页面更加美观且方便操作；
（2）优化搜索功能，提供多条件选择查询搜索；
（3）进一步提高系统的安全性，使系统更加健壮；
（4）优化数据和代码，提升软件效率，方便系统维护和扩展。
[1]朱明亮.浅析ERP信息管理系统在企业中的应用[J].中国管理信息化,2022,25(22):107-109.
[2]罗玮.计算机数据库在信息管理系统中的应用探究[J].科技创新与生产力,2022(08):64-66.
[3]金焘.实施信息管理系统集成技术要点浅析[J].信息化建设,2022(06):62.
[4]劳飞,单杰.数据库技术在信息管理系统中的应用[J].集成电路应用,2022,39(01):130-131.
[5]万全.大数据在信息管理系统中的应用[J].中国新通信,2021,23(24):85-86.
[6]王斌,李鸿飞,陈思宇.信息管理系统中计算机通信技术的应用探讨[J].长江信息通信,2021,34(10):130-132.
[7]王悦.计算机信息管理系统设计与应用探究[J].大众标准化,2021(17):20-22.
[8]孟凡波.基于高校学生管理的信息管理系统设计与实现[J].电子技术与软件工程,2021(17):169-170.
[9]王炽.高校档案信息管理系统与OA系统的合成研究[J].兰台内外,2021(23):7-9.
[10]王丹丹.PHP网站安全及加密技术对策[J].无线互联科技,2020,17(23):28-29.
[11]张文豪. 基于PHP的通用开发框架研究与实现[D].广东工业大学,2020.
[12]朱飞,刘曼琳.PHP语言中mysql与mysqli应用浅析[J].数字技术与应用,2020,38(07):38-41.
[13]景广军,郝墨轩.基于PHP语言开发的站址导航系统[J].信息与电脑(理论版),2020,32(08):88-92.
[14]黄昌平.基于php语言分析计算机编程的发展前景[J].数码世界,2019(04):46.
[15]吴琛.浅谈基于PHP的网站开发类课程教学研究[J].福建电脑,2018,34(11):173-174.
[16]李春阳. 泉州经贸学院学生管理信息系统的研究与分析[D].云南大学,2018.
[17]唐小明. 宜春学院学生奖罚系统的研究与分析[D].云南大学,2018.
[18]张美江.荣誉档案信息管理系统开发与利用的研究[J].电子技术与软件工程,2018(02):109-110.
逝者如斯夫，不舍昼夜。转眼间，大学生会员活便已经接近尾声，人面对着离别与结束，总是充满着不舍与茫然，我亦如此，仍记得那年秋天，我迫不及待的提前一天到了学校，面对学校巍峨的大门，我心里充满了期待：这里，就是我新生活的起点吗？那天，阳光明媚，学校的欢迎仪式很热烈，我面对着一个个对着我微笑的同学，仿佛一缕缕阳光透过胸口照进了我心里，同时，在那天我认识可爱的室友，我们携手共同度过了这难忘的两年。如今，我望着这篇论文的致谢，不禁又要问自己：现在，我们就要说再见了吗？
感慨莫名，不知所言。遥想当初刚来学校的时候，心里总是想着工科学校会过于板正，会缺乏一些柔情，当时心里甚至有一点点排斥，但是随着我对学校的慢慢认识与了解，我才认识到了她的美丽，她的柔情，并且慢慢的喜欢上了这个校园，但是时间太快了，快到我还没有好好体会她的美丽便要离开了，但是她带给我的回忆，永远不会离开我，也许真正离开那天我的眼里会满含泪水，我不是因为难过，我只是想将她的样子映在我的泪水里，刻在我的心里。最后，感谢我的老师们，是你们教授了我们知识与做人的道理；感谢我的室友们，是你们陪伴了我如此之久；感谢每位关心与支持我的人。
少年，追风赶月莫停留，平荒尽处是春山。
请关注点赞+私信博主，免费领取项目源码