Summary
In the information age of the 21st century, almost any industry is inseparable from computers. It is also very common to use computers in university community management systems. In the past, manual management methods were used to manage college associations, which resulted in problems such as cumbersome management and difficulty in maintenance. Nowadays, computers are used to manage the basic information of college associations, which is more convenient and simpler than manual management, and has the advantages of ease of use. Management, fast search speed, large storage capacity and many other advantages. Using it in the university community management system can not only improve the work efficiency of administrators in the university community management system, but also make the university community management system more scientific and standardized. Under the constant impact of the information age, the combination of university community management systems and computer technology will be a shortcut to improve the level of university community management systems.
The database used in this system is Mysql, which is developed using SSM technology. During the design process, the system code was fully guaranteed to have good readability, practicality, easy scalability, versatility, easy later maintenance, easy operation, and simple page.
关键词：High school company management system, SSM, Mysql
SSM University Association Management System
ABSTRACT
In the era of information technology in the 21st century, almost any industry cannot do without computers, and it is also very common to apply computers to the management system of university associations. In the past, manual management methods were used to manage college associations, which caused problems such as cumbersome management and difficult maintenance. Nowadays, using computers to manage various basic information of college associations is not only convenient and simple compared to manual management, but also has many advantages such as easy management, fast search speed, and large storage capacity. Using it in the university community management system can not only improve the work efficiency of administrators in the university community management system, but also make the university community management system more scientific and standardized. Under the continuous impact of the information age, the combination of university community management system and computer technology will be a shortcut to improve the level of university community management system.
The database used in this system is MySQL, developed using SSM technology. During the design process, the system code has been fully guaranteed to have good readability, practicality, scalability, versatility, ease of later maintenance, easy operation, and concise pages.
Keywords: university community management system, SSM, MySQ
Table of contents
SSM college club management system
SSM University Association Management System
1.1 Background and significance
1.2 Overview of research at home and abroad
Chapter 2 Related Technologies
2.2 Introduction to SSM framework
3.2 System feasibility analysis
3.2.1 Technical feasibility: technical background
3.2.3 Operational feasibility:
3.3 Project design goals and principles
3.4.3 Deletion of information process
4.2 Development process design
4.3 Database design principles
Table access_token (login access duration)
Table article (article: article for content management system)
Table article_type (article classification)
Table association_members (association members)
Table auth (user rights management)
Table community_activities (community activities)
Table community_classification (community classification)
Table community_information (community information)
Table forum_type (forum classification)
Table league_application (League Application)
Table user (user account: used to save user login information)
Table user_group (user group: used for user front-end identity and authentication)
Chapter 5 System Detailed Design
5.1 Administrator function module
Chapter1Chapter Introduction
1.1 Background and significance
As the size of the school continues to expand, the number of club members has increased dramatically, club activities are rich and colorful, and all kinds of information about students have also doubled. Faced with the huge amount of information, it is necessary to develop a community management system to improve the efficiency of community management work. Through such a system, standardized management of information, scientific statistics and quick query can be achieved, thereby reducing the workload of management. Especially in today's era when digital management is prevalent, establishing your own practical management system is of far-reaching significance.
The development of this system first introduces the development background of the community management system, the functions to be completed by the system and the development process, and then explains the connection process to the database when the system is running, the establishment, modification and maintenance of the database, as well as the management and backend of each community Functions and design ideas of basic data settings and other modules.
1.2 Overview of research at home and abroad
A survey of some university websites in first-tier cities such as Beijing, Shanghai, Guangzhou, and Shenzhen found that among the websites visited, most university websites did not have special modules related to student organizations, and some only briefly mentioned them in the news content. It was mentioned that there is a lack of clear community management system part, and there are problems such as too long information update interval, lack of maintenance and inconvenient consumption. Obviously, college clubs lack corresponding club management strategies in terms of information management, and are more at the stage of allowing students to freely develop clubs; this makes the development of clubs unbalanced, or fundamentally exists in name only. Exists frequently. There is no relatively complete student club management module found on most university websites, and some are only briefly mentioned in school news, lacking a clear club management system structure.
There are many types of club management systems abroad, but they mainly focus on single club management. This is mainly because most foreign club members can directly join clubs with a social nature after finishing college. Most clubs do not have a clear subordinate management relationship with the school, but it is relatively timely to update and maintain information on club-related activities.
1.3 Contents of the study
Currently, many people still use traditional paper tools as the main tool for information management, while the application of network technology only plays a supporting role. In terms of awareness of network tools, more traditional office software is still the main tool used by people, while relatively comprehensive and professional community information management software is still not understood or recognized by most people. This topic aims to achieve homepage, website management (carousel chart, bulletin board), content management (forum list, forum classification, community information, information classification), personnel management (administrators, students) through label classification management and other methods. ), module management (club classification, club information, club membership application, club members, club activities), personal management and other system management functions, thus achieving fast Convenient club information inquiry, joining application, club members, club activities, etc.need.
Chapter 2 Related Technologies
2.1 Development Technology
The front-end part of this system is developed based on the MVVM model, using B/S mode, and the back-end part is developed based on Java's SSM framework.
Front-end part: The front-end framework uses the popular progressive JavaScript framework Vue.js. Use Vue-Router and Vuex to realize dynamic routing and global state management, Ajax to realize front-end and back-end communication, Element UI component library to quickly prototype the page, and the project front-end to achieve responsiveness through grid layout, which can be adapted to PC, tablet, mobile phone, etc. Perfect layout display for different screen sizes.
Back-end part: Use SSM as the development framework, and integrate MyBatis, Redis and other related technologies.
2.2 Introduction to SSM framework
The SSM (Spring+SpringMVC+MyBatis) framework set is integrated by the two open source frameworks Spring and MyBatis (SpringMVC is part of Spring). It is often used as a framework for web projects with relatively simple data sources.
1.6.1 Spring
Spring is like a big factory that assembles beans in the entire project. In the configuration file, you can specify the use of specific parameters to call the constructor method of the entity class to instantiate the object. It can also be called the glue in the project.
The core idea of Spring is IoC (Inversion of Control), which means that programmers no longer need to explicitly `new` an object, but let the Spring framework do it all for you.
1.6.2 SpringMVC
SpringMVC intercepts user requests in the project. Its core Servlet, DispatcherServlet, assumes the responsibility of intermediary or front desk, and matches user requests through HandlerMapping to the Controller. The Controller is the specific operation performed in response to the request. SpringMVC is equivalent to struts in the SSH framework.
1.6.3 Mybot
Mybatis is an encapsulation of jdbc, which makes the underlying operations of the database transparent. The operations of mybatis are centered around a sqlSessionFactory instance. Mybatis is associated to the Mapper file of each entity class through the configuration file. The Mapper file is configured with the SQL statement mapping required for each class to the database. Every time you interact with the database, get a sqlSession through sqlSessionFactory, and then execute the sql command.
The page sends a request to the controller, the controller calls the business layer processing logic, the logic layer sends a request to the persistence layer, the persistence layer interacts with the database, and then returns the result to the business layer, the business layer sends the processing logic to the controller, and the controller then Call the view to display the data.
2.3 MVVM pattern
MVVM is the abbreviation of Model-View-ViewModel. It is essentially an improved version of MVC. MVVM abstracts the state and behavior of the View, allowing us to separate the view UI and business logic. Of course, ViewModel has already done these things for us. It can take out the Model data and help handle the business logic involved in the View that needs to display content. Microsoft's WPF brings new technology experiences, such as Silverlight, Audio, Video, 3D, animation..., which leads to software The UI layer is more detailed and customizable. At the same time, at the technical level, WPF also brings new features such as Binding, Dependency Property, Routed Events, Command, DataTemplate, ControlTemplate and so on. The origin of the MVVM (Model-View-ViewModel) framework is the application method that combines the MVP (Model-View-Presenter) mode with WPF. A new type of architectureframework. It is based on the original MVP framework and incorporates the new features of WPF to cope with the increasingly complex needs of users.
2.4 B/S structure
B/S (Browser/Server) is a more trouble-free architecture than its predecessor. It uses Web server to complete data transmission and exchange. You only need to download the browser as the client, and then the work will be "downsized", and there is no need to consider the problem of constantly installing software [9].
2.5 MySQL number set
Mysql's language is unstructured and users can work on data. MySQL has attracted much attention because of its speed, reliability and adaptability. Most people agree that MySQL is the best choice for managing content without the need for transactional processing. And because Mysql's language and structure are relatively simple, but its functions and amount of stored information are very powerful, it has been widely used.
The role of Mysql database in the programming process is very extensive, bringing convenience to users for data query. The application of Mysql database is highly flexible and powerful, so only a small piece of code is needed to implement a certain function, unlike other programs that require writing large pieces of code. Generally speaking, the language of Mysql database is relatively simpler.
Data process analysis is primarily a repository of data storage, which is performed on a computer rather than a real-life repository. Data is stored in a fixed format, not in an unordered manner. The definition is: it has a fixed format for a long time and can be stored in a shared computer memory. Database management mainly includes data storage, modification and addition, and the establishment of data tables. In order to ensure the normal operation of system data, some capable processors can manage it without requiring professional people to handle it. The establishment of the data table can adjust the data in the data table, recombine and reconstruct the data to ensure the security of the data. Due to the powerful functions of the database, the development of this system mainly uses Mysql for data management.
2.6 Vue.js main functions
Vue.js is a progressive framework for building user interfaces. Unlike other heavyweight frameworks, Vue adopts a bottom-up incremental development design. Vue's core library only focuses on the view layer, and is very easy to learn and integrate with other libraries or existing projects. Vue, on the other hand, is fully capable of driving complex single-page applications developed using single-file components and libraries supported by the Vue ecosystem.
The goal of Vue.js is to enable responsivedata bindingand composed view components with the simplest possible API.
Vue.js itself is not a full-featured framework - it only focuses on the view layer. Therefore it is very easy to learn and very easy to integrate with other libraries or existing projects. On the other hand, Vue.js can also power complex single-page applications when used with related tools and supporting libraries.
Chapter 3 System analysis
3.1 Demand analysis
The university club management system is mainly to realize the needs of quick and convenient club information inquiry, club membership application, club membership, club activities and other needs, and to satisfy users more conveniently and quickly, to better store all data information and to provide quick and convenient retrieval functions, which is very important to the system. Each module is determined by making a reasonable analysis considering the user's operability through many of today's developed systems, following the principles of system optimization developed, and after comprehensive investigation and research.
Before any project is developed and researched, it is necessary to conduct a careful analysis of the needs of the R&D system itself. Market research cannot be ignored. The functional needs of users must be determined from actual scenarios to clarify goals and develop the entire system. There is a more accurate positioning. In this chapter, it is necessary to analyze the system performance analysis, business process analysis, and data. The overall interface of the college community management system is simple and the functions are complete.
The feasibility of requirements is the analysis and discussion of what requirements a developed system can achieve. Whether the developed system or website meets the previous requirements. Only in pre-assessment of system development can requirements be completed before system development and implementation. During the development and application of the system, detailed descriptions of technical feasibility, operational feasibility, economic feasibility and legal feasibility proved that these points are feasible.
Analysis of the functions to be realized by the system. For the convenient management of the current network, the system should realize that users can directly view all data information on the platform, and can add, delete or modify university community management system information online according to needs, which can save time. , there is no need to waste time like the traditional method, which is really difficult to meet the various needs of users. Therefore, the development of university community management systems can not only meet the needs of users, but also reduce the original unnecessary workload and greatly improve the work efficiency of administrators.
3.2 System feasibility analysis
3.2.1 Technical Feasibility: Technical Background
This system is developed in the Windows operating system, and the current performance of the PC is already capable of serving as a web server for ordinary websites. The technology used in system development is also owned by itself, and it is also one of the widely used technologies today.
The development environment and configuration of the system can be installed by yourself. The system uses SSM development tools and the relatively mature Mysql database to interact with the system's front-end and back-end data. The database is modified and maintained according to technical language and combined with needs, which can make the website The operation is more stable and secure, thereby completing the development of the website.
(1) Hardware feasibility analysis
The design of system management and information analysis does not have any rigid requirements for the computer used. As long as the computer can be used normally for code writing and page design, it is feasible. The main requirements are for the server. The server to be uploaded after the platform is built is If there are certain requirements, the server must be chosen with relatively high security, and then opening the website must be smooth and cannot be paused for too long; it must be cost-effective and secure.
(2) Software feasibility analysis
The entire system is developed using cloud computing. The advantages of cloud computing are the scalability of traffic and intelligent adjustment based on traffic, ensuring system security and timely backup of data information.
Therefore, we conducted a feasibility study from two aspects and it can be seen that there is no problem in the development of the system.
3.2.2 经济性
The market research and other related management systems conducted before the development of the college community management system are free of charge. They are all through the developers' own efforts. All the work is done by themselves. When encountering problems that are difficult to solve by themselves, Most of the problems are solved through relevant information with the help of classmates and instructors, so the development of the college community management system is completely economically feasible without any expenses.
Using relatively mature technology, the system is developed based on SSM and uses Mysql database. Therefore, the system does not require high human and financial resources to develop and is economically feasible.
3.2.3 Operationalability:
The operability mainly refers to the user experience after the design of the college community management system is completed, and the administrator can manage relevant data information at any time through the system, and both the system and administrator roles can be easily and clearly entered. With its own system interface, functional modules can be operated simply and clearly through the interface navigation menu, which facilitates user information operation needs and administrators to manage data information. For system operation, no professional is required to directly operate and manage the functional modules, so The operability of the system is completely fine. The operation process of this system also uses the interface window to log in, so as long as the operator knows simple computer operations, it is completely fine.
3.3 Project design goals and principles
1. Basic requirements for university community management systems
(1) Functional requirements: Can manage home page, website management (carousel, bulletin board), content management (forum list, forum classification, club information, information classification), personnel management (administrators, students), module management (clubs) Classification, club information, club membership application, club members, club activities), personal management and other system management functions.
(2) Performance: It can be used on different operating systems without errors, so that different types of users can perform expected operations without errors and conveniently after logging into the corresponding interface.
(3) Security and confidentiality requirements: Users must pass the administrator's review before they can enter the system.
(4) Environmental requirements: Supports the use of multiple operating systems such as Windows series and Vista systems.
2. Development goals
The main development goals of the college community management system are as follows:
(1) Realize the systematization, standardization and automation of management system information relationships;
(2) Reduce the workload of maintenance personnel and enable users to control and manage information;
(3) Convenient to query information and manage information, etc.;
(4) Improve the efficiency of problem solving and operator work through network operations;
(5) Considering the diversity of users, the interface and operation are required to be simple and easy to understand.
3. Design principles
This system uses SSM technology and Mysql database development to fully ensure system stability and integrity.
The design ideas for the design and implementation of the university community management system are as follows:
- The operation is simple and convenient, the system interface is safe and good, the page layout is simple and clear, and it is convenient to query club information, application for joining the club, club members, club activities and other related information.
2. Instant visibility: Inquiries and processing of information in the university community management system will be immediately available, thus realizing the system function of “instant release and immediate results”.
3. Complete functions: can manage home page, website management (carousel, bulletin board), content management (forum list, forum classification, community information, information classification), personnel management (administrators, students), module management ( Modification and maintenance operations of club classification, club information, club membership application, club members, club activities), personal management and other functions.
3.4 System process analysis
3.4.1 Operation process
System login flow chart, as shown in the figure:
Figure 3-1 Login flow chart
3.4.2 Add information process
Add an information flow diagram, as shown in the figure:
Figure 3-2 Add information flow chart
3.4.3 Deletion of information process
Delete information flow chart, as shown in the figure:
Figure 3-3 Deletion information flow chart
Chapter4Chapter System Setup
4.1 System Architecture
The structure of University Club Management System is shown in Figure 4-1:
Figure 4-1 System structure
Login system structure diagram, as shown in Figure 4-2:
Figure 4-2 Login structure diagram
The system functional structure diagram is shown in Figure 4-3.
Figure 4-3 System functional structure diagram
4.2Opening flow schedule
The analysis of system process is to adjust and organize the system design plan by investigating the identification, feasibility, operability, system analysis and processing capabilities of the problems involved in the system to ensure that the system can reach the ideal state. These operations require a series of process tests focusing on registration and login to ensure the integrity of the database, thereby controlling the security of information management involved in the system and ensuring the normal conversion of information input and output. Then, complete the drawing work of the flow chart through practical operations.
The development of the university community management system involves analyzing the management modules and the database used by the system, writing code, and testing the system, as shown in Figure 4-4.
Figure 4-4 Development system flow chart
4.3 Database design principles
When learning programming, we all know that database design is based on the system functions that need to be designed. We need to establish a database relational model to store data information, so that when we are in the program, there is no need to add data to the program page, thereby improving the system s efficiency. The database stores a lot of information and can be said to be the core and foundation of the information management system. The database also provides the system with operation modules such as adding, deleting, modifying, and checking, so that the system can quickly find the information it wants instead of in the program code. found in. Each part of the information table in the database is accurately combined, arranged and combined into a data table according to certain relationships.
Planning is divided into several entity information through the functions of the college community management system. The entity information will be explained through the ER diagram. The main entity diagrams of this system are as follows:
(1) Use informationReal bodyPicture, as shown in 4-3:
Picture 4-3 Use informationBody attribute diagram
- The E-R diagram of the system is shown below:
Picture 4-3 Series E-RPicture
4.4 number table
Convert the E-R diagram of the database conceptual design into a relational database. In a relational database, data relationships are composed of data tables, but the structure of the table is represented by the fields of the table.
Table access_token (login access duration)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
token_id |
int |
10 |
0 |
N |
AND |
Temporary access badge ID |
|
| 2 |
token |
varchar |
64 |
0 |
AND |
N |
temporary access badge |
|
| 3 |
info |
text |
65535 |
0 |
AND |
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 article (article: article for content management system)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
article_id |
mediumint |
8 |
0 |
N |
AND |
Article id: [0,8388607] |
|
| 2 |
title |
varchar |
125 |
0 |
N |
AND |
Title: [0,125] is used in the title tag of articles and html |
|
| 3 |
type |
varchar |
64 |
0 |
N |
N |
0 |
Article classification: [0,1000] is used to search for articles of the specified type |
| 4 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of clicks: [0,1000000000] Number of people who visited this article |
| 5 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 6 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 7 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 8 |
source |
varchar |
255 |
0 |
AND |
N |
Source: [0,255] Source of article |
|
| 9 |
url |
varchar |
255 |
0 |
AND |
N |
Source address: [0,255] used to jump to the website where the article was published |
|
| 10 |
tag |
varchar |
255 |
0 |
AND |
N |
Tag: [0,255] is used to mark the relevant content of the article. Multiple tags are separated by spaces. |
|
| 11 |
content |
longtext |
2147483647 |
0 |
AND |
N |
Text: the main content of the article |
|
| 12 |
img |
varchar |
255 |
0 |
AND |
N |
cover picture |
|
| 13 |
description |
text |
65535 |
0 |
AND |
N |
Article description |
Table article_type (article classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
smallint |
5 |
0 |
N |
AND |
Category ID: [0,10000] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
Display order: [0,1000] determines the order in which categories are displayed. |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
Category name: [2,16] |
|
| 4 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 5 |
description |
varchar |
255 |
0 |
AND |
N |
Description: [0,255] describes the role of this classification |
|
| 6 |
icon |
text |
65535 |
0 |
AND |
N |
Category icon: |
|
| 7 |
url |
varchar |
255 |
0 |
AND |
N |
External link address: [0,255] If this category jumps to other websites, set it on the URL |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table association_members (association members)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
association_members_id |
int |
10 |
0 |
N |
AND |
Society member ID |
|
| 2 |
association_number |
varchar |
64 |
0 |
AND |
N |
Society number |
|
| 3 |
association_name |
varchar |
64 |
0 |
AND |
N |
Society name |
|
| 4 |
association_president |
varchar |
64 |
0 |
AND |
N |
President of the society |
|
| 5 |
student |
int |
10 |
0 |
AND |
N |
0 |
student |
| 6 |
student_number |
varchar |
64 |
0 |
AND |
N |
student ID |
|
| 7 |
full_name |
varchar |
64 |
0 |
AND |
N |
Name |
|
| 8 |
gender |
varchar |
64 |
0 |
AND |
N |
gender |
|
| 9 |
class_name |
varchar |
64 |
0 |
AND |
N |
class name |
|
| 10 |
date_of_joining_the_league |
date |
10 |
0 |
AND |
N |
Joining date |
|
| 11 |
association_position |
varchar |
64 |
0 |
AND |
N |
Club positions |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 14 |
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 |
default value |
illustrate |
| 1 |
auth_id |
int |
10 |
0 |
N |
AND |
Authorization ID: |
|
| 2 |
user_group |
varchar |
64 |
0 |
AND |
N |
user group: |
|
| 3 |
mod_name |
varchar |
64 |
0 |
AND |
N |
Module name: |
|
| 4 |
table_name |
varchar |
64 |
0 |
AND |
N |
Table Name: |
|
| 5 |
page_title |
varchar |
255 |
0 |
AND |
N |
page title: |
|
| 6 |
path |
varchar |
255 |
0 |
AND |
N |
Routing path: |
|
| 7 |
position |
varchar |
32 |
0 |
AND |
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 |
Can it be deleted: |
| 11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
Whether it can be modified: |
| 12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to view: |
| 13 |
field_add |
text |
65535 |
0 |
AND |
N |
Add fields: |
|
| 14 |
field_set |
text |
65535 |
0 |
AND |
N |
Modify fields: |
|
| 15 |
field_get |
text |
65535 |
0 |
AND |
N |
Query fields: |
|
| 16 |
table_nav_name |
varchar |
500 |
0 |
AND |
N |
Cross-table navigation name: |
|
| 17 |
table_nav |
varchar |
500 |
0 |
AND |
N |
Cross-table navigation: |
|
| 18 |
option |
text |
65535 |
0 |
AND |
N |
Configuration: |
|
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
table collect (collection)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
collect_id |
int |
10 |
0 |
N |
AND |
Collection ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Collector ID: |
| 3 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
| 4 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
| 5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| 6 |
title |
varchar |
255 |
0 |
AND |
N |
title: |
|
| 7 |
img |
varchar |
255 |
0 |
AND |
N |
Cover: |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table comment (comment)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
comment_id |
int |
10 |
0 |
N |
AND |
Comment ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Commenter ID: |
| 3 |
reply_to_id |
int |
10 |
0 |
N |
N |
0 |
Reply comment ID: empty is 0 |
| 4 |
content |
longtext |
2147483647 |
0 |
AND |
N |
content: |
|
| 5 |
nickname |
varchar |
255 |
0 |
AND |
N |
Nick name: |
|
| 6 |
avatar |
varchar |
255 |
0 |
AND |
N |
Avatar address: [0,255] |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 9 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
| 10 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
| 11 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
Table community_activities (community activities)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
community_activities_id |
int |
10 |
0 |
N |
AND |
Club activity ID |
|
| 2 |
activity_name |
varchar |
64 |
0 |
AND |
N |
Event name |
|
| 3 |
activity_status |
varchar |
64 |
0 |
AND |
N |
Active status |
|
| 4 |
activity_date |
date |
10 |
0 |
AND |
N |
Event date |
|
| 5 |
event_cover |
varchar |
255 |
0 |
AND |
N |
event cover |
|
| 6 |
event_location |
varchar |
64 |
0 |
AND |
N |
Event Location |
|
| 7 |
event_details |
varchar |
64 |
0 |
AND |
N |
Event Details |
|
| 8 |
hits |
int |
10 |
0 |
N |
N |
0 |
Clicks |
| 9 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table community_classification (community classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
community_classification_id |
int |
10 |
0 |
N |
AND |
Community classification ID |
|
| 2 |
association_name |
varchar |
64 |
0 |
AND |
N |
Society type |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table community_information (community information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
community_information_id |
int |
10 |
0 |
N |
AND |
Community information ID |
|
| 2 |
association_number |
varchar |
64 |
0 |
N |
N |
Society number |
|
| 3 |
association_name |
varchar |
64 |
0 |
AND |
N |
Society name |
|
| 4 |
community_type |
varchar |
64 |
0 |
AND |
N |
Society type |
|
| 5 |
club_cover |
varchar |
255 |
0 |
AND |
N |
Club cover |
|
| 6 |
association_president |
varchar |
64 |
0 |
AND |
N |
President of the society |
|
| 7 |
establishment_time |
date |
10 |
0 |
AND |
N |
Founding time |
|
| 8 |
introduction_to_the_association |
longtext |
2147483647 |
0 |
AND |
N |
Society profile |
|
| 9 |
hits |
int |
10 |
0 |
N |
N |
0 |
Clicks |
| 10 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 12 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 13 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
table forum (forum)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
forum_id |
mediumint |
8 |
0 |
N |
AND |
Forum id |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
sort |
| 3 |
user_id |
mediumint |
8 |
0 |
N |
N |
0 |
User ID |
| 4 |
nickname |
varchar |
16 |
0 |
AND |
N |
Nickname: [0,16] |
|
| 5 |
praise_len |
int |
10 |
0 |
AND |
N |
0 |
Number of likes |
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of visits |
| 7 |
title |
varchar |
125 |
0 |
N |
N |
title |
|
| 8 |
keywords |
varchar |
125 |
0 |
AND |
N |
Key words |
|
| 9 |
description |
varchar |
255 |
0 |
AND |
N |
describe |
|
| 10 |
url |
varchar |
255 |
0 |
AND |
N |
Source address |
|
| 11 |
tag |
varchar |
255 |
0 |
AND |
N |
Label |
|
| 12 |
img |
text |
65535 |
0 |
AND |
N |
cover picture |
|
| 13 |
content |
longtext |
2147483647 |
0 |
AND |
N |
text |
|
| 14 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 16 |
avatar |
varchar |
255 |
0 |
AND |
N |
Poster's avatar: |
|
| 17 |
type |
varchar |
64 |
0 |
N |
N |
0 |
Forum classification: [0,1000] is used to search for forum posts of specified types |
Table forum_type (forum classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
smallint |
5 |
0 |
N |
AND |
Category ID: [0,10000] |
|
| 2 |
name |
varchar |
16 |
0 |
N |
N |
Category name: [2,16] |
|
| 3 |
description |
varchar |
255 |
0 |
AND |
N |
Description: [0,255] describes the role of this classification |
|
| 4 |
url |
varchar |
255 |
0 |
AND |
N |
External link address: [0,255] If this category jumps to other websites, set it on the URL |
|
| 5 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 6 |
icon |
varchar |
255 |
0 |
AND |
N |
Category icon: |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table hits (user clicks)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
hits_id |
int |
10 |
0 |
N |
AND |
Like ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Liked by: |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 5 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
Table league_application (League Application)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
league_application_id |
int |
10 |
0 |
N |
AND |
入团申请ID |
|
| 2 |
association_number |
varchar |
64 |
0 |
Y |
N |
社团编号 |
|
| 3 |
association_name |
varchar |
64 |
0 |
Y |
N |
社团名称 |
|
| 4 |
community_type |
varchar |
64 |
0 |
Y |
N |
社团类型 |
|
| 5 |
association_president |
varchar |
64 |
0 |
Y |
N |
社团会长 |
|
| 6 |
student |
int |
10 |
0 |
Y |
N |
0 |
学生 |
| 7 |
student_id |
varchar |
64 |
0 |
Y |
N |
学号 |
|
| 8 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 9 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
| 10 |
class_name |
varchar |
64 |
0 |
Y |
N |
班级名称 |
|
| 11 |
instructor |
varchar |
64 |
0 |
Y |
N |
辅导员 |
|
| 12 |
reasons_for_joining_the_league |
text |
65535 |
0 |
Y |
N |
入团原因 |
|
| 13 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 14 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
| 15 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 16 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 17 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表notice (公告)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
notice_id |
mediumint |
8 |
0 |
N |
Y |
公告id： |
|
| 2 |
title |
varchar |
125 |
0 |
N |
N |
标题： |
|
| 3 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文： |
|
| 4 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表praise (点赞)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
praise_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： |
| 8 |
status |
bit |
1 |
0 |
N |
N |
1 |
点赞状态:1为点赞，0已取消 |
表slides (轮播图)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
slides_id |
int |
10 |
0 |
N |
Y |
轮播图ID： |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
标题： |
|
| 3 |
content |
varchar |
255 |
0 |
Y |
N |
内容： |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
链接： |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
轮播图： |
|
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量： |
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表student (学生)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
student_id |
int |
10 |
0 |
N |
Y |
学生ID |
|
| 2 |
student_number |
varchar |
64 |
0 |
N |
N |
学号 |
|
| 3 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 4 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
| 5 |
name_of_department |
varchar |
64 |
0 |
Y |
N |
院系名称 |
|
| 6 |
class_name |
varchar |
64 |
0 |
Y |
N |
班级名称 |
|
| 7 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 9 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 11 |
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 |
更新时间： |
5.1管理员功能模块
管理员登录，通过填写账号、密码、图片验证，输入完成后选择登录即可进入高校社团管理系统，如图5-1所示。
图5-1管理员登录界面图
管理员登录进入首页后，可以编辑操作首页，网站管理（轮播图，公告栏），内容管理（论坛列表，论坛分类，社团资讯，资讯分类），人员管理（管理员，学生），模块管理（社团分类、社团信息、入团申请、社团成员、社团活动），个人管理等内容，如图5-2所示。
图5-2管理员功能界面图
人员管理，在此页面可以查看用户名、昵称、性别、学号等信息，并可根据需要对个人信息进行添加，编辑，删除或查看详细内容等操作，如图5-3所示。
图5-3人员管理界面图
管理员或社团部长在社团活动管理页面可以对活动内容及其分类进行查询，重置，添加，删除等操作，如图5-4，5-4-1所示。
图5-4社团活动管理界面图
图5-4-1社团活动添加界面图
入团申请，在此管理页面可以对学生入团申请信息进行查询，重置，添加，删除以及审核回复等操作，加入页面可编辑社员的入团日期和社团职位管理，如图5-5，5-5-1所示。
图5-5入团申请界面图
图5-5-1加入审核界面图
网站管理，在此管理页面可以对轮播图和公告进行查询，重置，添加，删除等操作，如图5-6 5-7所示。
图5-6添加轮播图界面图
图5-7添加公告信息界面图
内容管理，管理员在内容管理页面可看到论坛列表+论坛分类+社团资讯+资讯分类这四个子菜单，管理员可根据需要对这四个子菜单进行增删改查等操作，如图5-8所示。
图5-8内容管理界面图
模块管理，管理员在模块管理页面可看到社团信息+社团分类+社团成员+社团活动+入团申请这五个子菜单，管理员可根据需要对这五个子菜单进行增删改查等操作，如图5-9所示。
图5-9模块管理界面图
5.2学生功能模块
用户注册，通过填写账号、密码、昵称、邮箱、手机号、身份等信息，输入完成后选择登录即可进入高校社团管理系统，如图5-10所示。
图5-10用户注册界面图
个人收藏，在此界面可以查看自己收藏的文章等，可进行删除等操作，如图5-11所示。
图5-11个人收藏界面图
交流论坛：学生在交流论坛一栏可查看论坛帖子，并可编辑标题、标签、分类、封面图等内容进行发布帖子，如图5-12 5-13所示。
图5-12交流论坛界面图
图5-13发布帖子界面图
社团资讯：学生在社团资讯页面可查看管理员发布的社团资讯信息，并可对资讯进行点赞、收藏、发表评论等操作，如图5-14所示。
图5-13新闻资讯界面图
社团信息，在此页面可以查看各个社团的详细信息，可以提交入团申请，点赞，评论，收藏等操作，如图5-14，5-15所示。
图5-14社团信息界面图
图5-15申请入团界面图
社团活动，在此页面可以查看推荐的社团活动信息，可进行点赞，评论，收藏等操作，如图5-16，5-17所示。
图5-11社团活动界面图
图5-17活动详情界面图
第6章 系统测试
6.1系统测试的目的
程序设计不能保证没有错误，这是一个开发过程，在错误或错误的过程中都是难以避免的。虽然这是不可避免的，但我们不能使这些错误始终存在于系统中，错误可能会造成无法估量的后果，如系统崩溃，安全信息泄露，系统无法正常启动等，为了避免这些问题，我们需要测试程序，再测试过程中发现问题，并纠正它们，从而使系统更长时间稳定成熟。本章的作用是发现这些问题，并对其进行修改，虽然耗时费力，但对于长期使用而言是非常重要和必要系统的开发。
软件在设计后必须进行测试，调试过程中使用的方法是软件测试方法。在开发新软件时，系统测试是检查软件是否合格的关键步骤，以及是否符合设计目标的参考。测试主要是查看软件中数据的准确性，正确的操作与否，以及操作的结果，还有哪些方面需要改进。
高校社团管理系统的实现，对于系统中功能模块的实现及操作都必须通过测试进行来评判系统是否可以准确的实现。在高校社团管理系统正式上传使用之前必须做的一步就是系统测试，对于测试发现的错误及时修改处理，保证系统准确无误的供给用户使用。
6.2系统测试方法
在对高校社团管理系统进行测试的时候在找到问题的情况下必须在第一时间找到解决问题的办法，不要存在侥幸的心理，这样才能让高校社团管理系统开发的质量可以过关，并且开发的周期会大大缩短，还有就是在测试时，不要出现重复性的错误，遇到一个错误问题，要将整个高校社团管理系统开发所牵扯的该问题都必须一一解决，提高高校社团管理系统平台的安全性、稳定性。
白盒测试与黑盒测试是测试中比较常用的两种方法。
①结构测试俗称白盒测试：这种测试是在对程序的处理过程与结构都有详尽谅解的前提下，顺从程序内部的逻辑而完成的系统测试，以确定系统中所有的通路都能够遵照设计要求正常工作，不出现任何偏差。
②功能测试又成黑盒测试：主要是针对程序功能能够按照设计正常实现的一种检测，在程序接口处进行，检测程序手法数据是否正常，与外部信息的交换是否完整。
6.3功能测试
用户登录测试：
| 模块名称 |
测试用例 |
预期结果 |
实际结果 |
是否通过 |
| 登录模块 |
用户名：admin 密码：123 |
弹出错误提示，提示密码错误 |
弹出错误提示，提示密码错误 |
通过 |
| 登录模块 |
用户名：123 密码：admin |
弹出错误提示，提示用户名错误 |
弹出错误提示，提示用户名错误 |
通过 |
| 登录模块 |
用户名：admin 密码：admin |
管理员登录成功 |
管理员登录成功 |
通过 |
删除分类测试：
| 模块名称 |
测试用例 |
预期结果 |
实际结果 |
是否通过 |
| 删除分类模块 |
分类名：最新通知 |
删除成功、页面自动跳转 |
删除成功、页面自动跳转 |
通过 |
修改密码测试：
| 模块名称 |
测试用例 |
预期结果 |
实际结果 |
是否通过 |
| 修改密码模块 |
原密码：666 新密码：123 确认密码：123 |
弹出错误提示，提示原密码错误 |
弹出错误提示，提示原密码错误 |
通过 |
| 修改密码模块 |
原密码：admin 新密码：123 确认密码：333 |
弹出错误提示，提示确认密码不一致 |
弹出错误提示，提示确认密码不一致 |
通过 |
| 修改密码模块 |
原密码：admin 新密码：123 确认密码：123 |
密码修改成功 |
密码修改成功 |
通过 |
通过对功能的测试，高校社团管理系统的基本功能都是可行的，不管是系统里面的功能，还是界面的设计都是可值得推广宣传的。
此时项目已经完成，即使实施的时间不是很长，但是这个过程中需要准备很长的一段时间去对系统设计开发所实际到的技术进行学习。在学习的过程中，我逐渐认识得到了我自身存在的一些不足。对于一些控制是必要的应用技能，能够理解，整个过程中仅仅是一个掌握了常用的性能和控制方法，我觉得挺容易的。从该系统中，系统的分析和设计的调查数据，并且已经经历了几个月，并努力几个月，该系统已经完成。很显然，该系统仍有很多不成熟，在系统设计过程中有许多技术缺陷存在。在设计的过程中也涉及到了很多自己无法解决的问题，主要通过找专业的网站和论坛来解决这些问题，对于圆满完成我的毕业设计，他们也贡献了很大一部分力量。系统的开发环境和配置都是可以自行安装的，系统使用SSM开发工具，使用比较成熟的Mysql数据库进行对系统前台及后台的数据交互，根据技术语言对数据库，结合需求进行修改维护，可以使得系统运行更具有稳定性和安全性，从而完成实现系统的开发。
在以后的学习及工作中，我将继续努力学习计算机方面的技术，以期在平台开发中可以更好更快的实现需求功能。
高校社团管理系统的完成，如何实现的更好，其中付出的努力是很大的，这段时光将会终身难忘。
首先要感谢我的指导老师，谢谢您在设计和论文中给我的指导。在您的细心指导下我才能快速的掌握系统的相关功能，在您的大力帮助下我才能将课本上的知识与自己的项目结合，真正的做到学以致用。感谢您经常牺牲自己的休息时间，利用其丰富的教学和项目经验对我进行指导。
感谢所有教过我的老师，为我倾注了大量的心血，正是你们的谆谆教诲、严谨教学才使我能顺利的完成学业，再此向你们表示深深的感谢。
感谢我的同学们，对我的大力支持及帮助，正是你们不断的帮助、鼓励，给我带来了极大的动力，最终系统可以顺利的运行。我们在交流、谈论的这段时间,将是我未来的财富，我要深深地感谢你们!
毕业在即，在今后的工作和生活中，我会铭记师长们的教诲、同学们的帮助，继续不懈努力和追求，来报答所有支持和帮助过我的人!。
参考文献
[1]Paul Krill. JavaScript, Java, and Python skills top demand[J]. InfoWorld.com,2023.
[2]López-Fogliani D.E.,Muñoz C.. Right-handed neutrinos, domain walls and tadpoles in the superstring inspired μνSSM[J]. Nuclear Physics, Section B,2023,986.
[3]Paul Krill. AWS Lambda kickstarts Java functions[J]. InfoWorld.com,2022.
[4]任浩然,刘丹,景永强.JAVA在计算机软件开发中的应用研究[J].信息记录材料,2022,23(11):83-85.DOI:10.16009/j.cnki.cn13-1295/tq.2022.11.072.
[5]任鑫梅,刘小英.高校社团管理信息系统的设计与实现[J].电脑知识与技术,2021,17(11):31-32+35.DOI:10.14004/j.cnki.ckt.2021.0923.
[6]符毓晟.高校学生社团管理系统设计与实现[J].电脑知识与技术,2020,16(27):75-78.DOI:10.14004/j.cnki.ckt.2020.2879.
[7]曹光辉.基于Web的高校社团管理系统设计与实现[J].无线互联科技,2020,17(08):38-40.
[8]惠苗,张晓冬.“互联网+”高校社团管理系统的设计与实现[J].萍乡学院学报,2019,36(03):78-83.
[9]张冰,梁致远,田元元,严竞雄.基于Web的高校社团管理系统的设计与实现[J].信息与电脑(理论版),2019(07):109-112.
[10]罗超,王志辉.高校社团管理信息系统的设计与实现[J].信息记录材料,2019,20(04):27-28.DOI:10.16009/j.cnki.cn13-1295/tq.2019.04.011.
[11]周洋,何丽丽.基于B/S模式的高校社团管理系统的研究与设计[J].电脑知识与技术,2018,14(33):84-85+96.DOI:10.14004/j.cnki.ckt.2018.3877.
[12]龚文辉. 高校大学生社团管理平台的设计与实现[D].江西师范大学,2018.
[13]王晓旭.高校社团管理信息系统的构建与设计[J].电子技术与软件工程,2017(14):44.
[14]刘艾侠,上官新梓.高校学生社团管理系统设计初步[J].电脑知识与技术,2017,13(04):56+62.DOI:10.14004/j.cnki.ckt.2017.0360.
[15]彭林,于国龙,宋敏,李飘,陈桃,王宗贵.高校社团管理系统设计与实现[J].物联网技术,2017,7(02):113-114.DOI:10.16667/j.issn.2095-1302.2017.02.034.
[16] Dong Caihua, Liang Minjian, Guo Zhenming. Design and implementation of university community management system [J]. Computers and Telecommunications, 2017(Z1):28-30.DOI:10.15966/j.cnki.dnydx.2017.z1.013.
[17] Zhou Bin, Li Guanjin, Chen Congwen, Li Xiaofeng, Shen Yujia. A university club activity management system and method [P]. Guangdong: CN106056505A, 2016-10-26.
[18] Peng Ke. Analysis of college student association management system [J]. Shanxi Youth, 2016(17):223.
[19] Han Zhi. Design and development of university student association management system [J]. Software Guide, 2016, 15(07):79-81.
[20] Xiao Peng, Zhu Jiewen. Design and implementation of college community management system based on B/S model [J]. Journal of Pingxiang College, 2014, 31(06): 57-59.
To get the project source code for free, please follow ❥ Like, collect and send a private message to the blogger, thank you~