Note: Show part of the document content and system screenshots. If you need complete videos, codes, articles and installation and debugging environment, please send a private message to the up owner.
3.2.1 System use case diagram
There are two main user roles designed in this system: user and administrator.
The use case diagrams of the two roles are shown in Figure 1.
(1) User permissions: change personal information, study courses, and take course exams.
(2) Administrator rights: manage user information, upload study materials, upload exam questions and other functions.
3.2.2 Functional requirements analysis
This system is mainly designed to enable users to study and take exams on the information technology learning website. There are two types of user roles: user and administrator. The following is a use case document description of system functions.
- The user registration form is shown in Table 1.
Table 1 User registration use case description
Use case name |
User registration account |
use case number |
01 |
participants |
user |
event stream |
The user clicks to register on the homepage, enters the necessary information as required, submits it to the server, and completes the registration. |
Preconditions |
none |
Postcondition |
The server saves the user's information to the database and determines whether the registration is successful. |
- The user login table is shown in Table 2.
Table 2 User login use case description
Use case name |
User login website |
use case number |
02 |
participants |
user |
event stream |
The user enters the password of the registered account on the login interface, and the system transfers the information to the database to analyze whether it matches. If the match is successful, the user can log in. |
Preconditions |
The user has registered an account. |
Postcondition |
The user logs in to the website and enters the homepage of the website. |
- Users’ course learning is shown in Table 3
Table 3 Course Learning Use Case Description
Use case name |
course study |
use case number |
03 |
participants |
user |
event stream |
The user clicks on the course information interface and clicks on the corresponding course to view the course information. |
Preconditions |
User login successful |
Postcondition |
Users view course information, download course files and watch videos. |
- Conditional search courses are shown in Table 4
Table 4 Exam test case description
Use case name |
Conditional search courses |
use case number |
04 |
participants |
user |
event stream |
The user enters the query conditions in the condition search bar of the course information interface, clicks the query and submits it to the server. The server extracts corresponding information from the database according to the query conditions. |
Preconditions |
Course related information has been uploaded |
Postcondition |
The queried information is displayed on the user interface |
- The exam tests are shown in Table 5
Table 5 Examination test case description
Use case name |
exam test |
use case number |
05 |
participants |
user |
event stream |
Users click on the exam of the corresponding course on the exam test interface to conduct self-tests. |
Preconditions |
The administrator has uploaded relevant test questions |
Postcondition |
Users enter the exam interface to answer questions |
- Personal information management is shown in Table 6.
Table 6 Personal information management use case description
Use case name |
Personal information management |
use case number |
06 |
participants |
user |
event stream |
Users can enter the personal center to manage information such as password changes and basic information changes. |
Preconditions |
User needs to log in |
Postcondition |
The modified personal information has been updated in the database. |
- Administrator information management is shown in Table 7.
Table 7 Administrator management use case description
Use case name |
Administrator information management |
use case number |
07 |
participants |
administrator |
event stream |
Administrators manage user information, upload course information, upload test questions, and edit campus announcements. |
Preconditions |
Administrator needs to log in |
Postcondition |
Administrators can perform related operations |
3.3 System maintenance analysis
The survival of the system is inseparable from system maintenance, so the importance of system maintenance cannot be ignored. During the entire life cycle of a system, system maintenance costs account for a considerable proportion. In system maintenance work, off-campus interns from the computer department and graduates of computer-related majors usually play an important role. According to statistics, 90% of computer-related software workers around the world are engaged in system maintenance. This shows that system maintenance plays a key role in the survival of the entire system and is a heavy task. System maintenance work covers many aspects, including troubleshooting, software updates, performance optimization, etc. Through timely maintenance, the stable operation of the system can be ensured and the reliability and safety of the system can be improved. In addition, regular maintenance can identify and resolve potential problems, reducing system failures and downtime. To sum up, the importance and heavy tasks of system maintenance are undeniable. As technology continues to advance, system maintenance costs will continue to increase.
System maintenance work is as follows:
(1) Program maintenance: System maintenance is a necessary process, because a series of problems will occur during the use of the system. In addition, users will inevitably find some problems during use. As time goes by, users will also have new needs. Therefore, during system maintenance, in addition to solving known problems, it is also necessary to pay attention to user feedback and changing needs. Timely maintenance and improvements can maintain system stability and reliability while reducing the complexity of maintenance work. If too many problems accumulate, changes to the program will become complicated, increasing the difficulty and workload of maintenance. System maintenance work is ongoing and needs to keep pace with the times. Only through timely maintenance and improvement can the efficient operation of the system and meet the needs of users be ensured. Therefore, the importance of system maintenance cannot be ignored. It is the key to the survival and development of the system.
(2) Database update and maintenance: The project database is an important resource in the project management and decision-making process. However, over time, the data in the database changes and is updated, so regular updates and maintenance of the project database is essential. First determine the update needs and understand what data needs to be updated, when and how often. Clarify user needs and expectations to make informed decisions during the update process.
(3) Maintenance of machines and equipment: In order to ensure the normal operation of the equipment, professionals should be dispatched for daily monitoring and maintenance. This allows timely troubleshooting and ensures that machines and equipment can remain in good working order. Monitoring and maintenance work by professionals is the key to ensuring stable operation of equipment and can improve equipment reliability and efficiency.
4.4.4 Modify information process
When modifying information, the user submits the modified information, and the system will check the information. Information that does not comply with the rules will not be changed. The flow chart is shown in Figure 11.
4.4.5 Deletion of information process
When deleting information, the system will confirm whether to delete the information. After confirmation, the system will update the database in time. The system’s deletion information is shown in Figure 12.
Figure 12 Deletion information flow chart
4.5 System design principles
System design principles include the following points:
(1) Security principle, system design must have security guarantees to avoid leakage of user information and prevent unauthorized intrusions and other issues. The enhancement of these factors is an important aspect that must be prioritized when designing a system.
(2) Principle of easy operability. Ease of operation is a key consideration in system design, aiming to provide users with a good operating experience. Simplified operating steps and one-click operation can improve operating efficiency. User needs should be the core of the design, and problems should be considered from the user's perspective. Take user feedback seriously and make timely responses and improvements. The easy-to-operate design can provide users with a convenient and intuitive experience and improve user satisfaction of the system.
4.6 Database logical design
(1) The configuration file is shown in Table 8 below.
Table 8 Configuration file config
List |
type of data |
Required |
describe |
id |
bigint(20) |
yes |
primary key |
name |
varchar(100) |
yes |
Configuration parameter name |
value |
varchar(100) |
no |
Configuration parameter values |
(2) The test sheet is shown in Table 9 below
Table 9 test paper exampaper
List |
type of data |
Required |
describe |
id |
bigint(20) |
yes |
primary key |
addtime |
timestamp |
yes |
creation time |
name |
varchar(200) |
yes |
Test paper name |
time |
int(11) |
yes |
Exam duration (minutes) |
status |
int(11) |
yes |
test paper status |
(3) The test questions table is shown in Table 10 below
Table 10 exam questions
List |
type of data |
Required |
describe |
id |
bigint(20) |
yes |
primary key |
addtime |
timestamp |
yes |
creation time |
papers |
bigint(20) |
yes |
The test volume id to which it belongs (foreign key) |
papername |
varchar(200) |
yes |
Test paper name |
questionname |
varchar(200) |
yes |
Question name |
options |
longtext |
no |
options, json string |
score |
bigint(20) |
no |
Points |
answer |
varchar(200) |
no |
correct answer |
analysis |
longtext |
no |
Answer analysis |
type |
bigint(20) |
no |
Question type, 0: single-choice question 1: multiple-choice question |
sequence |
bigint(20) |
no |
The test questions are sorted, the larger the value, the higher the rank. |
(4) The examination record table is shown in Table 11 below
Table 11 Exam record table examrecord
List |
type of data |
Required |
describe |
id |
bigint(20) |
yes |
primary key |
addtime |
timestamp |
yes |
creation time |
userid |
bigint(20) |
yes |
user id |
username |
varchar(200) |
no |
username |
papers |
bigint(20) |
yes |
test volume id (foreign key) |
papername |
varchar(200) |
yes |
Test paper name |
questionid |
bigint(20) |
yes |
Question ID (foreign key) |
questionname |
varchar(200) |
yes |
Question name |
options |
longtext |
no |
options, json string |
score |
bigint(20) |
no |
Points |
answer |
varchar(200) |
no |
correct answer |
analysis |
longtext |
no |
Answer analysis |
myscore |
bigint(20) |
yes |
question score |
myanswer |
varchar(200) |
no |
Candidate answers |
id |
bigint(20) |
yes |
primary key |
addtime |
timestamp |
yes |
creation time |
userid |
bigint(20) |
yes |
user id |
5.2.4 Implementation of user examination test module
After the user finishes learning, click on the exam test module to test the learning content. The interface is shown in Figure 18.
Table of contents
1.3 Development purpose and significance
2 Technical introduction to the system
2.2 Introduction to Spring Boot
2.3 Introduction to Vue technology
2.4 Introduction to database technology
3 System analysis of information technology learning website
3.1 System feasibility analysis
3.2 System requirements analysis
3.3 System maintenance analysis
4Information Technology LearningSystem Outline Design
4.1 Brief description of system outline design
4.2 System basic structure design
4.3 Working principle of the system
5Information technology learningSystem's implementation