Intelligent classroom attendance system

Abstract

The invention relates to the technical field of smart classroom attendance checking, in particular to a smart classroom attendance checking system, which comprises an application layer used for configuring Spring Boot framework parameters and starting an application service; the service layer is used for recording, counting, predicting and analyzing classroom attendance; the security layer is used for managing user information and configuring roles and resource access permissions for users; the data layer is used for realizing data interaction among the application layer, the service layer, the security layer, the data layer, the log layer, the front-end layer and the database based on a Mapper interface; the log layer is used for recording a pushing result of the attendance message and a system operation log; the front-end layer is used for constructing a user interface and responding to a request of a user; and the database is used for storing data information of the application layer, the service layer, the security layer, the data layer, the log layer and the front-end layer. Through a modern software architecture and an intelligent algorithm, the efficiency and level of the classroom attendance system are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of smart classroom attendance, and in particular to a smart classroom attendance system. Background Art

[0002] Existing classroom attendance systems usually rely on manual operations, which are inefficient and prone to errors. With the development of information technology, it has become a trend to use automated and intelligent means to manage attendance. However, the attendance systems currently on the market have single functions and lack the ability to deeply analyze and predict attendance data. Therefore, the present invention provides an integrated and intelligent smart classroom attendance system to solve the above-mentioned problems in the prior art. At the same time, it improves the accuracy of sign-in, eliminates the occurrence of cheating behaviors such as signing in on behalf of others, and provides corresponding data support for later campus management and teaching construction. Summary of the invention

[0003] The purpose of the present invention is to provide a smart classroom attendance system, which improves the efficiency and level of the classroom attendance system through modern software architecture and intelligent algorithms.

[0004] To achieve the above object, the present invention provides the following solutions:

[0005] A smart classroom attendance system, comprising: an application layer, a service layer, a security layer, a data layer, a log layer, a front-end layer and a database;

[0006] The application layer is used to configure Spring Boot framework parameters and start application services;

[0007] The service layer is used to record, count, predict and analyze classroom attendance;

[0008] The security layer is used to manage user information and configure roles and resource access permissions for users;

[0009] The data layer is used to implement data interaction between the application layer, service layer, security layer, data layer, log layer, front-end layer and the database based on the Mapper interface;

[0010] The log layer is used to record the push results of attendance messages and system operation logs;

[0011] The front-end layer is used to build a user interface and respond to user requests;

[0012] The database is used to store data information of the application layer, service layer, security layer, data layer, log layer, and front-end layer.

[0013] Optionally, the application layer includes an attendance applet module, which is used to process the user's attendance result query and history record management on the WeChat applet side. The attendance applet module uses a first interface to receive a query request and calls a query method in a first implementation class.

[0014] Optionally, the service layer includes an attendance recording module, an attendance statistics module, an attendance prediction module and a classroom behavior analysis module;

[0015] The attendance record module is used to manage and record student course sign-in information to form historical attendance data;

[0016] The attendance statistics module is used to perform statistical analysis on the historical attendance data and obtain statistical results;

[0017] The attendance prediction module is used to predict future attendance based on the statistical results through machine learning technology;

[0018] The classroom behavior analysis module is used to analyze and report the behavior in the classroom.

[0019] Optionally, the attendance record module uses the second interface to record the sign-in information, and calls the second implementation class to save the sign-in record; the attendance statistics module uses the third interface to receive statistical requests, and calls the statistical analysis logic in the third implementation class; the attendance prediction module uses the fourth interface to receive prediction requests, and calls the prediction algorithm in the fourth implementation class; the classroom behavior analysis module uses the fifth interface to receive behavior analysis requests, and calls the behavior analysis logic in the fifth implementation class.

[0020] Optionally, the security layer includes a system user module, a role management module and a resource authority management module;

[0021] The system user module is used to manage user information;

[0022] The role management module is used to configure roles for users and assign resource access permissions;

[0023] The resource authority management module is used to manage system resources and authority allocation.

[0024] Optionally, the system user module uses the sixth interface to receive user management requests and calls the user management logic in the sixth implementation class; the role management module uses the seventh interface to receive role management requests and calls the role management logic in the seventh implementation class; the resource authority management module uses the eighth interface to receive resource management requests and calls the resource management logic in the eighth implementation class.

[0025] Optionally, the Mapper interface in the data layer includes: a resource interface, a course sign-in interface, and a user interface. The resource interface is used to perform database operations for resource authority management, the course sign-in interface is used to perform database operations for course sign-in record management, and the user interface is used to perform database operations for system user management.

[0026] Optionally, the log layer includes a message log module and a system log module;

[0027] The message log module is used to record the results of attendance message push;

[0028] The system log module is used to record system operation logs.

[0029] Optionally, the message log module uses the ninth interface to receive message log recording requests and calls the message log recording logic in the ninth implementation class; the system log module uses the tenth interface to receive system log recording requests; the system log recording logic in the tenth implementation class.

[0030] Optionally, the front-end layer uses a RESTful API to interact with the application layer, service layer, security layer, data layer, log layer and database.

[0031] The beneficial effects of the present invention are:

[0032] The smart classroom attendance system provided by the present invention realizes the full process automated management from data collection, processing, analysis to prediction, and has the following advantages:

[0033] (1) Efficient management: The application layer flexibly and efficiently configures the system's initialization parameters, and the modular design of the service layer enables comprehensive management of classroom attendance.

[0034] (2) Data synchronization: The data layer realizes data synchronization between each module and the school database to ensure the real-time and accuracy of information.

[0035] (3) Safe and reliable: The security layer implements system user authentication and authorization through Apache Shiro to ensure the security of the system.

[0036] (4) Logging: The log layer fully records system operation logs and message push results, facilitating system operation and maintenance and troubleshooting.

[0037] (5) User-friendly: The front-end layer interacts with the back-end through RESTful API to build a friendly user interface and improve user experience.

[0038] In summary, the present invention improves the efficiency and level of the classroom attendance system through modern software architecture and intelligent algorithms, and provides strong support and guarantee for the educational development of the school. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 The present invention is a schematic diagram of the structure of a smart classroom attendance system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0042] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0043] This embodiment provides a smart classroom attendance system. Figure 1 As shown, it includes: application layer, service layer, security layer, data layer, log layer, front-end layer and database;

[0044] The application layer is used to configure Spring Boot framework parameters and start application services;

[0045] The service layer is used to record, count, predict and analyze class attendance;

[0046] The security layer manages user information and configures roles and resource access permissions for users;

[0047] The data layer is used to implement data interaction between the application layer, service layer, security layer, data layer, log layer, front-end layer and database based on the Mapper interface;

[0048] The log layer is used to record the push results of attendance messages and system operation logs;

[0049] The front-end layer is used to build the user interface and respond to user requests;

[0050] The database is used to store data information of the application layer, service layer, security layer, data layer, log layer, and front-end layer.

[0051] This system uses the Spring Boot framework for system development. The system can be quickly started and easily deployed. At the same time, Spring Boot's automatic configuration simplifies the project configuration process. The system's initialization parameters are configured flexibly and efficiently through the application layer; the security layer's security framework Apache Shiro is used to authenticate and authorize users and roles to provide security for the operation of the system; the service layer implements functions such as classroom attendance recording, statistics, prediction and analysis; the data layer implements the school's attendance data interface to obtain student classroom attendance data, and combines the application layer to clean, convert, adapt, and deduplicate the data. Finally, the structured data is loaded into the corresponding structured database for storage to improve the timeliness, openness, and data integration capabilities of data information transmission.

[0052] This system improves the efficiency and level of the classroom attendance system through modern software architecture and intelligent algorithms, providing strong support and guarantee for the school's educational development. The following is a detailed description of each layer:

[0053] (I) Application layer:

[0054] The application layer is implemented using the attendance applet module, which is used to process the user's attendance result query and history management on the WeChat applet. The attendance applet module uses the first interface to receive the query request and calls the query method in the first implementation class. The main functions include:

[0055] (1) Users view real-time attendance information on the WeChat mini program and provide real-time feedback on their check-in status.

[0056] (2) Users can query their historical attendance records and filter them by time, course, etc.

[0057] (3) Display the attendance statistics of the current class.

[0058] The attendance applet module implements the above functions by calling the applet service interface, namely the MiniProgramServiceI interface. The main implementation class of the interface is the applet service implementation class MiniProgramServiceImpl, which is responsible for obtaining relevant attendance data from the database and returning it to the applet end.

[0059] The specific steps of its implementation are: the user initiates an attendance query request on the mini program side; the system receives the request through the MiniProgramServiceI interface and calls the query method in the MiniProgramServiceImpl class; the database access layer obtains the attendance data and returns it to the service layer; after the service layer processes the data, it returns the result to the mini program side and displays it on the user interface. Users can easily view and manage their personal attendance data on the WeChat mini program side, which improves the user experience and convenience of the attendance system.

[0060] (II) Service Layer:

[0061] The service layer includes attendance record module, attendance statistics module, attendance prediction module and classroom behavior analysis module, as follows:

[0062] The attendance record module is used to manage student course attendance information. Its main functions include:

[0063] (1) Record students’ check-in time, location, and status.

[0064] (2) Provide an interface for other modules to query students’ check-in status.

[0065] (3) Support batch processing of check-in data to improve data access efficiency.

[0066] The attendance record module implements the above functions by calling the course sign-in service interface, namely the CourseSignServiceI interface. The main implementation class of the interface is the course sign-in service implementation class CourseSignServiceImpl, which is responsible for processing the sign-in data and storing it in the database.

[0067] The specific steps for its implementation are: students sign in in the classroom through the sign-in device; the system records the sign-in information through the CourseSignServiceI interface; the CourseSignServiceImpl class implements sign-in record preservation and calls the database to store data; an interface is provided for the attendance applet module and the attendance statistics module to call to obtain the sign-in data.

[0068] Through the implementation of this module, real-time recording and query of student sign-in data can be achieved to ensure the accuracy and completeness of the data.

[0069] The attendance statistics module is used to perform statistical analysis on historical attendance data. Its main functions include:

[0070] (1) Statistically analyze students’ attendance data and generate various reports.

[0071] (2) Provide an interface for administrators to query statistical results, supporting multi-dimensional queries such as by course and time period.

[0072] (3) The analysis results are used in the attendance prediction module to provide basic data support.

[0073] The attendance statistics module implements the above functions by calling the attendance statistics service interface, namely the AttendanceStatisticsServiceI interface. The main implementation class of the interface is the attendance statistics service implementation class AttendanceStatisticsServiceImpl, which is responsible for processing the original attendance data and generating statistical reports.

[0074] The specific steps of its implementation are: the system receives statistical requests through the AttendanceStatisticsServiceI interface; the AttendanceStatisticsServiceImpl class implements the statistical analysis logic, calls the database to obtain the original data and processes it; the processed data is returned through the interface for use by other modules and administrators.

[0075] Through the implementation of this module, the system can provide detailed attendance data analysis, help schools and teachers understand students' attendance, and provide data support for teaching management.

[0076] The attendance prediction module is used to predict future attendance through machine learning technology. Its main functions include:

[0077] (1) Use historical attendance data and machine learning algorithms to predict future attendance rates.

[0078] (2) Provide prediction results for administrators and teachers to refer to and help formulate corresponding teaching plans.

[0079] (3) Continuously optimize the prediction model to improve prediction accuracy.

[0080] The attendance prediction module implements the above functions by calling the attendance prediction service interface, namely the AttendancePredictionServiceI interface. The main implementation class of the interface is the attendance prediction service implementation class AttendancePredictionServiceImpl, which is responsible for calling the attendance statistics module to obtain basic data and make predictions.

[0081] The specific steps of its implementation are: the system receives the prediction request through the AttendancePredictionServiceI interface; the AttendancePredictionServiceImpl class implements the prediction algorithm and calls the attendance statistics module to obtain historical data; the prediction algorithm is executed, the prediction result is generated and returned through the interface.

[0082] Through the implementation of this module, the system can make scientific predictions about future attendance, help schools and teachers prepare countermeasures in advance, and optimize the allocation of teaching resources.

[0083] The classroom behavior analysis module is used to analyze and report classroom behavior. Its main functions include:

[0084] (1) Analyze students’ behavior in the classroom and generate behavior analysis reports.

[0085] (2) Provide an interface for administrators and teachers to query analysis results and help improve teaching methods.

[0086] (3) Support multiple behavior analysis models and flexibly configure analysis parameters.

[0087] The classroom behavior analysis module implements the above functions by calling the classroom behavior analysis service interface, namely the ClassroomBehaviorAnalysisServiceI interface. The main implementation class of the interface is the classroom behavior analysis service implementation class ClassroomBehaviorAnalysisServiceImpl, which is responsible for processing behavior data and generating analysis reports.

[0088] The specific steps of its implementation are: the system receives behavior analysis requests through the ClassroomBehaviorAnalysisServiceI interface; the ClassroomBehaviorAnalysisServiceImpl class implements the analysis logic and calls the database to obtain behavior data; the analysis algorithm is executed, a report is generated and returned through the interface.

[0089] Through the implementation of this module, the system can conduct a comprehensive analysis of student behavior in the classroom, provide valuable behavior reports, and help schools and teachers improve teaching strategies and enhance teaching effectiveness.

[0090] (III) Security layer:

[0091] The security layer includes the system user module, role management module and resource authority management module, as follows:

[0092] The system user module is used to manage system users. Its main functions include:

[0093] (1) Manage user information in the system, including user registration, login and permission management.

[0094] (2) Provide an interface for other modules to query and update user information.

[0095] (3) Support multiple user authentication methods to improve system security.

[0096] The system user module implements the above functions by calling the user service interface, namely the UserServiceI interface. The main implementation class of the interface is the user service implementation class UserServiceImpl, which is responsible for processing user data and storing it in the database.

[0097] The specific steps for its implementation are: the system receives user management requests through the UserServiceI interface; the UserServiceImpl class implements the user management logic, calls the database to obtain and update user data; and provides an interface for other modules to call to ensure the consistency and security of user information.

[0098] Through the implementation of this module, the system can effectively manage user information, ensure the security and consistency of user data, and provide a reliable user base for the normal operation of the system.

[0099] The role management module is used to configure system roles and assign resource access permissions. Its main functions include:

[0100] (1) Manage role information in the system, including role creation, deletion, and permission configuration.

[0101] (2) Provide an interface for other modules to query and update role information.

[0102] (3) Support multiple role permission models and flexibly configure permission parameters.

[0103] The role management module implements the above functions by calling the role service interface, namely the RoleServiceI interface. The main implementation class of the interface is the role service implementation class RoleServiceImpl, which is responsible for processing role data and storing it in the database.

[0104] The specific steps for its implementation are: the system receives role management requests through the RoleServiceI interface; the RoleServiceImpl class implements the role management logic, calls the database to obtain and update role data; and provides an interface for other modules to call to ensure the consistency and security of role information.

[0105] Through the implementation of this module, the system can flexibly manage roles and permissions to ensure the security and controllability of system resources.

[0106] The resource authority management module is used to manage system resources and authority allocation. Its main functions include:

[0107] (1) Manage resource information in the system, including resource creation, deletion, and permission allocation.

[0108] (2) Provide an interface for other modules to query and update resource information.

[0109] (3) Support multiple resource permission models and flexibly configure permission parameters.

[0110] The resource authority module implements the above functions by calling the resource service interface, namely the ResourceServiceI interface. The main implementation class of the interface is the resource service implementation class ResourceServiceImpl, which is responsible for processing resource data and storing it in the database.

[0111] The specific steps of its implementation are: the system receives resource management requests through the ResourceServiceI interface; the ResourceServiceImpl class implements the resource management logic, calls the database to obtain and update resource data; and provides an interface for other modules to call to ensure the consistency and security of resource information.

[0112] Through the implementation of this module, the system can efficiently manage resources and permissions, and ensure the rational allocation and safe use of system resources.

[0113] (iv) Data layer:

[0114] The Mapper interfaces provided by the data layer include: resource interface, namely ResourceMapper interface, course sign-in interface, namely CourseSignMapper interface, and user interface, namely UserMapper interface, as follows:

[0115] The ResourceMapper interface is used to perform database operations for resource permission management. This interface defines database operations related to system resources and permissions, such as querying resource lists, obtaining permissions based on roles, adding new resources, updating resource information, deleting resources, etc. Through this interface, operations such as adding, deleting, modifying, and checking resource permissions can be implemented to ensure the accuracy and integrity of system resource and permission management.

[0116] The CourseSignMapper interface is used to perform database operations for course sign-in record management. This interface defines database operations related to student course sign-in information, such as querying sign-in records, counting sign-in status, adding sign-in records, updating sign-in status, etc. Through this interface, accurate management and statistical analysis of course sign-in information can be achieved.

[0117] The UserMapper interface is used to perform database operations for system user management. This interface defines database operations related to system users, such as querying user information, updating user status, adding users, deleting users, etc. Through this interface, comprehensive management of system users can be achieved to ensure the accuracy and security of user data.

[0118] (V) Log layer:

[0119] The log layer records logs through SLF4J and Logback, including message log module and system log module, as follows:

[0120] The message log module is used to record the results of attendance message push. Its main functions include:

[0121] (1) Record the results of various message pushes in the system, including success and failure messages.

[0122] (2) Provide an interface for administrators to query message logs, and support filtering by time, message type, etc.

[0123] (3) Analyze message logs, optimize message push strategies, and improve push success rates.

[0124] The message log module implements the above functions by calling the message log service interface, namely the MessageLogServiceI interface. The main implementation class of the interface is the message log service implementation class MessageLogServiceImpl, which is responsible for processing log data and storing it in the database.

[0125] The specific steps of its implementation are: the system receives log record requests through the MessageLogServiceI interface; the MessageLogServiceImpl class implements the log record logic and calls the database to save log data; an interface is provided for other modules to call to ensure the consistency and traceability of log information.

[0126] Through the implementation of this module, the system can record the results of attendance message push in detail, providing important data support for the operation, maintenance and optimization of the system.

[0127] The system log module is used to record system operation logs. Its main functions include:

[0128] (1) Record various operation logs in the system, including user operations, system events, etc.

[0129] (2) Provide an interface for administrators to query operation logs, and support filtering by time, operation type, etc.

[0130] (3) Analyze operation logs, optimize system operation strategies, and improve system stability and security.

[0131] The system log module implements the above functions by calling the system log service interface, namely the SystemLogServiceI interface. The main implementation class of the interface is the system log service implementation class SystemLogServiceImpl, which is responsible for processing log data and storing it in the database.

[0132] The specific implementation steps are as follows: the system receives log record requests through the SystemLogServiceI interface; the SystemLogServiceImpl class implements the log record logic and calls the database to save log data; an interface is provided for other modules to call to ensure the consistency and traceability of log information.

[0133] Through the implementation of this module, the system can record operation logs in detail, providing important data support for system operation, maintenance and optimization.

[0134] (VI) Front-end layer:

[0135] Design user interfaces using front-end technologies, such as HTML, CSS, and JavaScript, and interact with the back-end through RESTful APIs, which are architectural styles for application program interfaces that use HTTP requests to access or use data.

[0136] Multiple application interfaces are designed in the front-end layer, including attendance statistics interface, attendance prediction interface, system user and role management interface, message log interface, system log interface, etc.

[0137] Attendance Statistics Interface: Statistics are collected by time (this week, this month, this semester, etc.) and object (course, student, teacher, etc.), and displayed in a combination of charts and lists. After specifying the object to be counted (course, teacher or student), users can click Details in the list to view the attendance details of a specific course, teacher or student.

[0138] Attendance prediction interface: Users click the details button of the corresponding course to view the attendance rate forecast of students of the specified course in the past 7 days and the next 7 days.

[0139] System user and role management interface: When the user enters the user list interface, he can view the users created in the current system, modify, delete, and add new users. In addition, the system can search for users by user account, nickname, and user status (such as frozen, locked, normal, etc.). After the user opens the role management interface, he can view the existing roles in the system and perform operations on a certain role. The user can also search for roles by role code, name, or status.

[0140] Message log interface: Users can enter the list interface to check whether the attendance message has been successfully pushed to students. Users can filter the message push results according to student ID, name, date and other conditions.

[0141] System log interface: records the user's operation log in the system. You can add query conditions according to the search bar to retrieve the corresponding log information.

[0142] The embodiments described above are only descriptions of the preferred embodiments of the present invention and are not intended to limit the scope of the present invention. Without departing from the design spirit of the present invention, various modifications and improvements made to the technical solutions of the present invention by ordinary technicians in this field should all fall within the protection scope determined by the claims of the present invention.

Claims

1. A smart classroom attendance system, characterized in that: include: Application layer, service layer, security layer, data layer, log layer, front-end layer and database; The application layer is used to configure Spring Boot framework parameters and start application services; The service layer is used to record, count, predict and analyze classroom attendance; The security layer is used to manage user information and configure roles and resource access permissions for users; The data layer is used to implement data interaction between the application layer, service layer, security layer, data layer, log layer, front-end layer and the database based on the Mapper interface; The log layer is used to record the push results of attendance messages and system operation logs; The front-end layer is used to build a user interface and respond to user requests; The database is used to store data information of the application layer, service layer, security layer, data layer, log layer, and front-end layer.

2. The smart classroom attendance system according to claim 1 is characterized in that: The application layer includes an attendance applet module, which is used to process the user's attendance result query and history record management on the WeChat applet side. The attendance applet module uses a first interface to receive a query request and calls a query method in a first implementation class.

3. The smart classroom attendance system according to claim 1 is characterized in that: The service layer includes an attendance record module, an attendance statistics module, an attendance prediction module and a classroom behavior analysis module; The attendance record module is used to manage and record student course sign-in information to form historical attendance data; The attendance statistics module is used to perform statistical analysis on the historical attendance data and obtain statistical results; The attendance prediction module is used to predict future attendance based on the statistical results through machine learning technology; The classroom behavior analysis module is used to analyze and report the behavior in the classroom.

4. The smart classroom attendance system according to claim 3 is characterized in that: The attendance record module adopts the second interface to record the sign-in information, and calls the second implementation class to save the sign-in record; the attendance statistics module adopts the third interface to receive statistical requests, and calls the statistical analysis logic in the third implementation class; the attendance prediction module adopts the fourth interface to receive prediction requests, and calls the prediction algorithm in the fourth implementation class; the classroom behavior analysis module adopts the fifth interface to receive behavior analysis requests, and calls the behavior analysis logic in the fifth implementation class.

5. The smart classroom attendance system according to claim 1 is characterized in that: The security layer includes a system user module, a role management module and a resource authority management module; The system user module is used to manage user information; The role management module is used to configure roles for users and assign resource access permissions; The resource authority management module is used to manage system resources and authority allocation.

6. The smart classroom attendance system according to claim 5, characterized in that: The system user module uses the sixth interface to receive user management requests and calls the user management logic in the sixth implementation class; the role management module uses the seventh interface to receive role management requests and calls the role management logic in the seventh implementation class; The resource authority management module uses the eighth interface to receive resource management requests and calls the resource management logic in the eighth implementation class.

7. The smart classroom attendance system according to claim 1, characterized in that: The Mapper interface in the data layer includes: a resource interface, a course sign-in interface, and a user interface. The resource interface is used to perform database operations for resource authority management, the course sign-in interface is used to perform database operations for course sign-in record management, and the user interface is used to perform database operations for system user management.

8. The smart classroom attendance system according to claim 1, characterized in that: The log layer includes a message log module and a system log module; The message log module is used to record the results of attendance message push; The system log module is used to record system operation logs.

9. The smart classroom attendance system according to claim 8, characterized in that: The message log module uses the ninth interface to receive message log record requests and calls the message log record logic in the ninth implementation class; the system log module uses the tenth interface to receive system log record requests; the system log record logic in the tenth implementation class.

10. The smart classroom attendance system according to claim 1, characterized in that: The front-end layer uses RESTful API to interact with the application layer, service layer, security layer, data layer, log layer and database.

Images