Table of contents
1. 4 Paper structure and chapter arrangement 2
2 System analysis of convenient e-government system
2.2.2Data modification process _ _
3 Overall design of convenient e-government system
3.1 System architecture design
3.2 System function module design
3.2.1 Overall functional module design
3.2.3 Comment management module design
3.3.1 Database conceptual structure design
3.3.2 Database logical structure design
4 Detailed design and implementation of convenient e-government system
4.1.2 User registration interface
4.1.5 Online service interface
4.1.7 Convenient service interface
4. 2 Administrator function module
4. 2.1 Carousel chart management interface
4. 2.2 System user management interface
4. 2.3 Laws and regulations management interface
4.2.4 Government information management interface
4.2.5 Government affairs disclosure management interface
4.2.6 Volunteer deployment management interface
In the information society, there is a need for targeted ways to obtain information, but the expansion of the ways is basically the direction that people strive for. Due to deviations in the perspective, people can often obtain different types of information, which is also the most difficult to overcome with technology. subject. In view of the problems such as the convenient e-government system, we conduct research and analysis on the convenient e-government system, and then develop and design the convenient e-government system to solve the problems.
The main functional modules of the convenient e-government system include regional situation, laws and regulations, government information, government disclosure, online services, convenient services, leadership information, leadership mailbox, email management, complaint suggestions, and complaint classification, and adopt an object-oriented development model. The development of software and the establishment of hardware can well meet the needs of actual use. The corresponding software establishment and program coding work have been improved. MySQL is used as the main storage unit of background data, and the SSM framework, JAVA technology, and Ajax technology are used. Carry out coding and development of business systems and realize all functions of this system. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyze the various needs and technical issues of the convenient e-government system, prove the necessity and technical feasibility of the system, and then give a basic introduction to the technical software and design ideas that need to be used in the design system, and finally realize the convenient e-government System and deployment operations use it.
Keywords : SSM technology; MYSQL; convenient e-government system
Abstract
In the information society, there is a need for targeted information acquisition channels, but the expansion of channels is basically the direction of people's efforts. Due to the deviation in perspective, people often can obtain different types of information, which is also the most difficult topic for technology to overcome. Research and analyze the convenience e-government system and other issues, and then develop and design the convenience e-government system to solve the problems.
The main functional modules of the convenient e-government system include regional information, laws and regulations, government information, government openness, online services, convenient services, leadership information, leadership mailbox, email management, complaint suggestions, and complaint classification. The object-oriented development model is adopted for software development and hardware installation, which can effectively meet the actual needs of use and improve the corresponding software installation and program coding work, Adopting MySQL as the main storage unit for backend data, using SSM framework, JAVA technology, and Ajax technology for business system coding and development, all functions of this system have been achieved. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyze the various requirements and technical issues of the convenient e-government system, prove the necessity and feasibility of the system, and then provide a basic introduction to the technical software and design ideas required for designing the system. Finally, implement the convenient e-government system and deploy it for operation.
Keywords:SSM technology; MYSQL； Convenient e-government system
1 Introduction
1.1 Research significance
In recent years, with the rapid development of the Internet, especially since the outbreak of the new coronavirus pneumonia, many management departments have moved their government affairs halls to online platforms and successively launched various convenient e-government services, bringing great convenience to people's production and life. With the continuous promotion of e-government across the country, it also reflects the problems existing in this field, such as unsmooth process design, lack of effective integration, lack of unified planning, poor user experience, etc., which requires the design of e-government At the same time, the system pays more attention to the selection and construction of software frameworks to improve software reusability, and is required to replace the bloated and inefficient development model of traditional EJB, and at the same time adapt to the requirements of increasingly complex Internet application development, allowing electronic While accelerating the development of government affairs, it also promotes the development of the digital economy and assists in the construction of smart cities.
1.2 Research methods
First, through engine search or relevant literature, we learned about the background of the system development and the significance of designing the system, and collected user demand information. Secondly, in terms of development tools, it was finally decided to use the ssm platform to design and develop this system, with MySQL as the tool for designing the database. That is, the user interface is implemented using Java language and connected with the database to achieve complete communication functions. After that, the general functional modules of the system are designed. It is mainly analyzed from the perspective of convenience for system users and system administrators to clarify the functions that the system should have. The final step is to test the system, discover existing problems and find solutions through use case testing. Utilize the existing development platform, combine the knowledge you have learned, and complete the design with the guidance of the teacher to ensure the usability and practicality of the system.
1.3SSM 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.8.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.8.2 SpringMVC
SpringMVC intercepts user requests in the project. Its core Servlet, DispatcherServlet, assumes the responsibilities of intermediary or front desk, and matches user requests to the Controller through HandlerMapping. The Controller is the specific operation performed in response to the request. SpringMVC is equivalent to struts in the SSH framework.
1.8.3 mybatis
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.
1.4Vue.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 implement responsive data binding and composed view components through 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.
1.5 Paper structure and chapter arrangement
The paper will be organized hierarchically. In addition to the abstract, acknowledgments, and literature references, the main text will also analyze the website requirements, describe the general design and implemented functions, and finally list some debugging records. The main structure of the paper is as follows:
Chapter One Introduction. The first chapter mainly introduces the background of the project research, the current situation of system development and the research content and main work of this article.
Chapter 2: System requirements analysis. Chapter 2 mainly conducts demand analysis from the aspects of users and functions of the system.
Chapter 3: System Design. Chapter 3 mainly carries out functional design of the system framework, system function modules and database.
Chapter 4: System implementation. Chapter 4 mainly introduces the system framework construction and the implementation of the system interface.
Chapter 5: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions.
2 Analysis of convenient e-government system
System analysis is a prerequisite for developing a project. Through system analysis, the basic needs of the main users of the system can be well understood, and this is also the reason for the development of the project. Then, a feasibility analysis is performed on the system development, which usually includes technical feasibility, economic feasibility, etc. The feasibility analysis is also an analysis from the overall perspective of the project. Then the specific requirements of the project are analyzed. The analysis method is generally implemented through the user's use case diagram. The following is a detailed introduction.
2.1 Feasibility analysis
Most of the tools used in the project are currently popular open source and free, so in the early stage of development, the funds used for the project will be greatly reduced, and the development of the software will not be affected by funds during the project startup period, so It is still economically feasible. Try to meet the needs of users with the least amount of money. Save money on labor costs and equipment costs. We will go further and further on the road of paperlessness and high efficiency.
So there is no problem with economic feasibility.
(2) Operational feasibility:
The design of this project refers to several cases of website development under this mode, analyzes their operation interfaces, and combines many cases to highlight people-oriented simplified operations, so people with basic computer knowledge can operate this project.
Therefore, there is no problem with operational feasibility.
(3) Technical feasibility:
Technical feasibility refers to the feasibility of building a framework, as well as the system's adaptability to technological upgrading when better technologies emerge, and the development time and cost ratio.
Existing Java technology can cater to the construction of all e-commerce systems. When developing this convenient e-government system, I used Java+MYSQL to run the overall program.
In summary, there is no problem with the technical feasibility.
(4) Legal feasibility:
From a developer's perspective, Java and MYSQL are open source and free online, and there will be no legal disputes regarding intellectual property rights.
From a user perspective, as long as contraband is no longer sold on the system, treaties and agreements are made with the system, and illegal payments are eliminated.
In summary, there is no problem with the legal feasibility.
The business process uses some specific symbols and lines to demonstrate the user's process when using the system. When performing system analysis, the business process can help developers better understand the business, discover errors, and improve the system.
After the user successfully logs in to the system , he or she can add data. The number of the added data is specific and generated by the system. The user cannot fill it in at will. Except for the number, the user fills in other added information by himself. The filled-in information is verified by the system and is legal. If it passes, it will show that the data has been added successfully. If it is passed, it will not be added successfully. Figure 2-1 shows the process of adding data.
Figure 2-1 Data addition flow chart
2.2.2 Data modification process
The process of data modification is similar to the process of data addition described above, as shown in Figure 2-2 .
Figure 2-2 Data modification flow chart
If there is some useless data in the system , the relevant managers can also delete the data. Figure 2-3 is the flow chart for data deletion.
Figure 2-3 Data deletion flow chart
2.3 System function analysis
According to the role of the convenient e-government system, I divided it into two parts: registered users and administrator management.
Registered user management module:
(1) User registration and login: The user registers as a registered user and logs in to the convenient e-government system; the user adds, deletes, modifies and checks personal information, such as personal information and password changes.
( 2 ) Bulletin Board : We will see the " Bulletin Board " menu on the homepage navigation bar . After we click to enter, we will see the bulletin board posted by all administrators in the background ;
( 3 ) News : On the homepage navigation bar, we will see the " News " menu. After we click to enter, we will see the news information released by all administrators in the background, and we can edit the news we like. Like it, if you want to find this information faster next time, you can also add it to favorites and comments;
(4) My Account: When the user clicks the "My" button in the upper right corner, a submenu will appear. Clicking "My Account" can set and manage personal information, passwords for logging into the system, and information collected by oneself;
(5) Online services: When the user clicks the "Online Services" menu button, all online services published by the administrator in the background will be displayed. Online services can be searched by keywords. Select the required online services and click to enter. Detailed introduction interface for online services. In the detailed interface, you can view the name of the online services, release date, department name, form attachments, review cycle and other information, and you can also perform service operations;
(6) Service: When the user wants to perform service on the online service details interface, click the "Service" button below, and it will jump to the service information filling interface. Enter the service information according to the interface prompts, click the "Submit" button, and the service will be completed. finished;
(7) Convenient services: When the user clicks the "Convenient Services" menu button, all the convenient services released by the administrator in the background will be displayed. It supports searching for convenient services by keywords. Select the required convenient services and click to enter. Detailed introduction interface of convenience services. In the detailed interface, you can view the service name, contact number, contact address, remarks and other information of the convenience services;
Administrator management module:
(1) Login: The administrator's account is directly set in the data table and does not require registration;
(2) Carousel image/bulletin board management: Administrators can add, delete, modify and check the carousel image + bulletin board displayed at the front desk of the system to facilitate users to view.
(3) System User: When you click the "System User" menu, two submenus will appear: Registered User + Administrator, and you can add, delete, modify and check these two modules;
(4) Resource management: When the administrator clicks the "Resource Management" menu, the two submenus of news list + news classification will be displayed. The administrator can update and maintain the functions involved in these two departments to better serve front-end users. ;
(5) Module management: When you click the " Module " menu, there will be regional situation + laws and regulations + government affairs information + government affairs disclosure + convenient services + convenient services + leadership information + leadership mailbox + email management + complaints and suggestions + For the eleven sub-menus of complaint classification , the administrator can add, delete, modify and check these eleven modules;
2.3.2 Non-functional analysis
The non-functional requirements of the convenience e-government system include the security, reliability, performance, scalability, etc. of the convenience e-government system. The details can be expressed in the following 3-1 table:
Table 3-1 Non-functional requirements table of convenient e-government system
| safety |
It mainly refers to the installation of the database of the convenience e-government system. The use of the database and the setting of passwords must comply with the standards. |
| reliability |
Reliability means that the convenient e-government system can be operated according to the user's instructions. After testing, the reliability is more than 90%. |
| performance |
Performance is a necessary condition for a convenient e-government system to occupy the market, so it is best to have good performance. |
| Scalability |
For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system. |
| Ease of use |
Users only need to follow the page display content of the convenient e-government system and operate. |
| maintainability |
Maintainability is very important in the development of convenient e-government systems. After testing, there is no problem with maintainability. |
2.4 System use case analysis
Through the analysis of 2.3 functions, the use case diagram of this convenient e-government system is obtained:
An example of registering user roles is shown in Figure 2-3.
Figure 2-3 Convenience e-government system registered user role use case diagram
The administrator in the web backend management maintains all data information in the entire convenient e-government system. An example of the administrator role is shown in Figure 2-4.
figure 2-4 Convenience e-government system administrator role use case diagram
This chapter mainly determines the functions to be realized by the entire convenient e-government system through feasibility analysis, process analysis, functional requirement analysis, and system use case analysis of the convenient e-government system. At the same time, it also provides standards for code implementation and testing of convenient e-government systems.
3 Overall design of convenient e-government system
The main contents discussed in this chapter include the functional module design and database system design of the convenient e-government system.
3.1 System architecture design
This convenient e-government system is divided into three layers in architecture: presentation layer (UI), business logic layer (BLL) and data layer (DL).
Figure 3-1 System architecture design diagram of the convenience e-government system
Presentation layer (UI): Also known as the UI layer, it mainly completes the UI interaction function of this convenient e-government system. A good UI can improve the user experience and enhance the user's comfort when using this convenient e-government system. The interface design of the UI must also adapt to different versions of convenient e-government systems and different size resolutions to achieve good compatibility. The UI interaction function requirements are reasonable, and users must obtain consistent interaction results when performing interactive operations. This requires the presentation layer to be well connected with the business logic layer.
Business Logic Layer (BLL): Mainly completes the data processing function of this convenient e-government system. The data transmitted by the user from the presentation layer is processed by the business logic layer and delivered to the data layer. The data read by the system from the data layer is processed by the business logic layer and delivered to the presentation layer.
Data layer (DL): Since the data of this convenient e-government system is placed in the mysql database on the server side, the parts that belong to the service layer can be directly integrated into the business logic layer, so there is only the database in the data layer, which mainly completes this Data storage and management functions of convenient e-government systems.
3.2 System function module design
3.2.1 Overall functional module design
In the previous chapter, the functional requirements and non-functional requirements of the system were mainly analyzed, and the use cases in this convenient e-government system were analyzed based on the requirements. Then the next step is to start designing the architecture, main functions and database of this convenient e-government system. The convenient e-government system is derived based on the demand analysis in the previous chapter, and its overall design module diagram is shown in Figure 3-2.
Figure 3-2 Functional module diagram of the convenient e-government system
3.2.2 User module design
The backend manager can add, delete, modify and check the users registered in the frontend. The user module structure diagram is as follows:
Figure 3-3 User module structure diagram
3.2.3 Comment management module design
The convenient e-government system is an open platform for communication. Users can communicate on the platform to increase the interaction between users. But at the same time, in order to better standardize the content of comments and give administrators the function of deleting inappropriate comments, a comment management module needs to be specially designed. The specific structure diagram is as follows:
Figure 3-4 Structure diagram of comment module
Database design generally includes three major processes: demand analysis, conceptual model design, and database table creation. The demand analysis has been explained in the previous chapter, and the conceptual model design has two parts: conceptual model and logical structure design.
3.3.1 Database conceptual structure design
The following is the ER entity relationship diagram of the main database tables in the entire convenient e-government system.
Figure 3-6 General ER relationship diagram of the convenient e-government system
3.3.2 Database logical structure design
From the total ER relationship diagram in the convenient e-government system in the previous section, it can be concluded that a total of many data tables need to be created. Here I mainly list several major database table structure designs.
Table complaint_classification (complaint classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
complaint_classification_id |
int |
10 |
0 |
N |
Y |
Complaint category ID |
|
| 2 |
complaint_type |
varchar |
64 |
0 |
Y |
N |
Complaint 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 complaint_suggestions (complaints and suggestions)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
complaint_suggestions_id |
int |
10 |
0 |
N |
Y |
Complaint suggestion ID |
|
| 2 |
date_of_complaint |
date |
10 |
0 |
Y |
N |
date of complaint |
|
| 3 |
complaint_title |
varchar |
64 |
0 |
Y |
N |
Complaint title |
|
| 4 |
complaint_type |
varchar |
64 |
0 |
Y |
N |
Complaint type |
|
| 5 |
complaint_content |
text |
65535 |
0 |
Y |
N |
Complaints |
|
| 6 |
complaint_user |
int |
10 |
0 |
Y |
N |
0 |
Complaint user |
| 7 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 8 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
moderation reply |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table convenient_services (convenient services)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
convenient_services_id |
int |
10 |
0 |
N |
Y |
Convenience service ID |
|
| 2 |
service_name |
varchar |
64 |
0 |
Y |
N |
service name |
|
| 3 |
contact_number |
varchar |
64 |
0 |
Y |
N |
contact number |
|
| 4 |
contact_address |
varchar |
64 |
0 |
Y |
N |
contact address |
|
| 5 |
remarks |
varchar |
64 |
0 |
Y |
N |
Remarks |
|
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table government_information (government information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
government_information_id |
int |
10 |
0 |
N |
Y |
Government information ID |
|
| 2 |
title_content |
varchar |
64 |
0 |
Y |
N |
title content |
|
| 3 |
release_date |
date |
10 |
0 |
Y |
N |
release date |
|
| 4 |
government_affairs_description |
varchar |
64 |
0 |
Y |
N |
Description of government affairs |
|
| 5 |
government_cover |
varchar |
255 |
0 |
Y |
N |
Government cover |
|
| 6 |
government_details |
longtext |
2147483647 |
0 |
Y |
N |
Government details |
|
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table laws_and_regulations (laws and regulations)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
laws_and_regulations_id |
int |
10 |
0 |
N |
Y |
Laws and regulations ID |
|
| 2 |
regulatory_name |
varchar |
64 |
0 |
Y |
N |
Regulation name |
|
| 3 |
effectiveness_level |
varchar |
64 |
0 |
Y |
N |
Effectiveness level |
|
| 4 |
formulating_authority |
varchar |
64 |
0 |
Y |
N |
Establishing authority |
|
| 5 |
timeliness |
varchar |
64 |
0 |
Y |
N |
Timeliness |
|
| 6 |
implementation_date |
date |
10 |
0 |
Y |
N |
Implementation date |
|
| 7 |
publication_date |
date |
10 |
0 |
Y |
N |
Announcement date |
|
| 8 |
details |
longtext |
2147483647 |
0 |
Y |
N |
Details |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
表leaders_mailbox (领导信箱)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
leaders_mailbox_id |
int |
10 |
0 |
N |
Y |
领导信箱ID |
|
| 2 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 3 |
post |
varchar |
64 |
0 |
Y |
N |
职务 |
|
| 4 |
head_portrait |
varchar |
255 |
0 |
Y |
N |
头像 |
|
| 5 |
mailbox |
varchar |
125 |
0 |
Y |
N |
邮箱 |
|
| 6 |
brief_introduction |
text |
65535 |
0 |
Y |
N |
简介 |
|
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表mail_management (邮件管理)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
mail_management_id |
int |
10 |
0 |
N |
Y |
邮件管理ID |
|
| 2 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 3 |
post |
varchar |
64 |
0 |
Y |
N |
职务 |
|
| 4 |
mailbox |
varchar |
64 |
0 |
Y |
N |
邮箱 |
|
| 5 |
sending_user |
int |
10 |
0 |
Y |
N |
0 |
发件用户 |
| 6 |
date_of_shipment |
date |
10 |
0 |
Y |
N |
发件日期 |
|
| 7 |
sending_content |
text |
65535 |
0 |
Y |
N |
发件内容 |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 10 |
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 |
更新时间： |
表online_services (网上办事)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
online_services_id |
int |
10 |
0 |
N |
Y |
网上办事ID |
|
| 2 |
item_name |
varchar |
64 |
0 |
Y |
N |
事项名称 |
|
| 3 |
department_name |
varchar |
64 |
0 |
Y |
N |
部门名称 |
|
| 4 |
release_date |
date |
10 |
0 |
Y |
N |
发布日期 |
|
| 5 |
audit_cycle |
varchar |
64 |
0 |
Y |
N |
审核周期 |
|
| 6 |
table_attachment |
varchar |
255 |
0 |
Y |
N |
表格附件 |
|
| 7 |
matters_needing_attention |
text |
65535 |
0 |
Y |
N |
注意事项 |
|
| 8 |
process_flow |
text |
65535 |
0 |
Y |
N |
办事流程 |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 11 |
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已取消 |
表publicity_of_government_affairs (政务公开)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
publicity_of_government_affairs_id |
int |
10 |
0 |
N |
Y |
政务公开ID |
|
| 2 |
title_content |
varchar |
64 |
0 |
Y |
N |
标题内容 |
|
| 3 |
public_type |
varchar |
64 |
0 |
Y |
N |
公开类型 |
|
| 4 |
release_date |
date |
10 |
0 |
Y |
N |
发布日期 |
|
| 5 |
government_affairs_description |
varchar |
64 |
0 |
Y |
N |
政务描述 |
|
| 6 |
government_cover |
varchar |
255 |
0 |
Y |
N |
政务封面 |
|
| 7 |
government_details |
longtext |
2147483647 |
0 |
Y |
N |
政务详情 |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表regional_overview (地区概况)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
regional_overview_id |
int |
10 |
0 |
N |
Y |
地区概况ID |
|
| 2 |
region_name |
varchar |
64 |
0 |
Y |
N |
地区名称 |
|
| 3 |
release_date |
date |
10 |
0 |
Y |
N |
发布日期 |
|
| 4 |
regional_overview |
text |
65535 |
0 |
Y |
N |
地区概况 |
|
| 5 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 6 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 7 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表registered_users (注册用户)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
registered_users_id |
int |
10 |
0 |
N |
Y |
注册用户ID |
|
| 2 |
full_name |
varchar |
64 |
0 |
Y |
N |
姓名 |
|
| 3 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
| 4 |
id |
varchar |
255 |
0 |
Y |
N |
身份证 |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表service_management (办事管理)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
service_management_id |
int |
10 |
0 |
N |
Y |
办事管理ID |
|
| 2 |
item_name |
varchar |
64 |
0 |
Y |
N |
事项名称 |
|
| 3 |
department_name |
varchar |
64 |
0 |
Y |
N |
部门名称 |
|
| 4 |
application_date |
date |
10 |
0 |
Y |
N |
申请日期 |
|
| 5 |
service_users |
int |
10 |
0 |
Y |
N |
0 |
办事用户 |
| 6 |
service_attachment |
varchar |
255 |
0 |
Y |
N |
办事附件 |
|
| 7 |
progress_of_work |
varchar |
64 |
0 |
Y |
N |
办事进度 |
|
| 8 |
remarks |
varchar |
64 |
0 |
Y |
N |
备注信息 |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表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 |
更新时间： |
3.4本章小结
整个便民电子政务系统的需求分析主要对系统总体架构以及功能模块的设计，通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。
4 便民电子政务系统详细设计与实现
便民电子政务系统的详细设计与实现主要是根据前面的便民电子政务系统的需求分析和便民电子政务系统的总体设计来设计页面并实现业务逻辑。主要从便民电子政务系统界面实现、业务逻辑实现这两部分进行介绍。
4.1用户功能模块
4.1.1 前台首页界面
当进入便民电子政务系统的时候，首先映入眼帘的是系统的导航栏，下面是轮播图以及公告，其主界面展示如下图4-1所示。
图4-1 前台首页界面图
4.1.2 用户注册界面
不是便民电子政务系统中正式用户的是可以在线进行注册的，如果你没有本便民电子政务系统的账号的话，添加“注册”，当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号等后再点击“注册”按钮后将会先验证输入的有没有空数据，再次验证密码和确认密码是否是一样的，最后验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可用户注册成功。其用用户注册界面展示如下图4-2所示。
图4-2 前台用户注册界面图
注册逻辑关键代码如下所示。
* 注册
* @return
*/
@PostMapping("register")
public Map<String, Object> signUp(HttpServletRequest request) throws IOException {
// 查询用户
Map<String, String> query = new HashMap<>();
Map<String,Object> map = service.readBody(request.getReader());
query.put("username",String.valueOf(map.get("username")));
List list = service.selectBaseList(service.select(query, new HashMap<>()));
if (list.size()>0){
return error(30000, "用户已存在");
}
map.put("password",service.encryption(String.valueOf(map.get("password"))));
service.insert(map);
return success(1);
}
public Map<String,Object> readBody(BufferedReader reader){
BufferedReader br = null;
StringBuilder sb = new StringBuilder("");
try{
br = reader;
String str;
while ((str = br.readLine()) != null){
sb.append(str);
}
br.close();
String json = sb.toString();
return JSONObject.parseObject(json, Map.class);
}catch (IOException e){
e.printStackTrace();
}finally{
if (null != br){
try{
br.close();
}catch (IOException e){
e.printStackTrace();
}
}
}
return null;
}
public void insert(Map<String,Object> body){
E entity = JSON.parseObject(JSON.toJSONString(body),eClass);
baseMapper.insert(entity);
log.info("[{}] - 插入操作：{}",entity);
}
4.1.3 用户登录界面
便民电子政务系统中的前台上注册后的用户是可以通过自己的账户名和密码进行登录的，当用户输入完整的自己的账户名和密码信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到便民电子政务系统的首页中；否则将会提示相应错误信息，用户登录界面如下图4-3所示。
图4-3用户登录界面图
登录系统主要代码如下。
* 登录
* @param data
* @param httpServletRequest
* @return
*/
@PostMapping("login")
public Map<String, Object> login(@RequestBody Map<String, String> data, HttpServletRequest httpServletRequest) {
log.info("[执行登录接口]");
String username = data.get("username");
String email = data.get("email");
String phone = data.get("phone");
String password = data.get("password");
List resultList = null;
QueryWrapper wrapper = new QueryWrapper<User>();
Map<String, String> map = new HashMap<>();
if(username != null && "".equals(username) == false){
map.put("username", username);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(email != null && "".equals(email) == false){
map.put("email", email);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(phone != null && "".equals(phone) == false){
map.put("phone", phone);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}else{
return error(30000, "账号或密码不能为空");
}
if (resultList == null || password == null) {
return error(30000, "账号或密码不能为空");
}
//判断是否有这个用户
if (resultList.size()<=0){
return error(30000,"用户不存在");
}
User byUsername = (User) resultList.get(0);
Map<String, String> groupMap = new HashMap<>();
groupMap.put("name",byUsername.getUserGroup());
List groupList = userGroupService.selectBaseList(userGroupService.select(groupMap, new HashMap<>()));
if (groupList.size()<1){
return error(30000,"用户组不存在");
}
UserGroup userGroup = (UserGroup) groupList.get(0);
//查询用户审核状态
if (!StringUtils.isEmpty(userGroup.getSourceTable())){
String res = service.selectExamineState(userGroup.getSourceTable(),byUsername.getUserId());
if (res==null){
return error(30000,"用户不存在");
}
if (!res.equals("已通过")){
return error(30000,"该用户审核未通过");
}
}
//查询用户状态
if (byUsername.getState()!=1){
return error(30000,"用户非可用状态，不能登录");
}
String md5password = service.encryption(password);
if (byUsername.getPassword().equals(md5password)) {
// 存储Token到数据库
AccessToken accessToken = new AccessToken();
accessToken.setToken(UUID.randomUUID().toString().replaceAll("-", ""));
accessToken.setUser_id(byUsername.getUserId());
tokenService.save(accessToken);
// 返回用户信息
JSONObject user = JSONObject.parseObject(JSONObject.toJSONString(byUsername));
user.put("token", accessToken.getToken());
JSONObject ret = new JSONObject();
ret.put("obj",user);
return success(ret);
} else {
return error(30000, "账号或密码不正确");
}
}
public String select(Map<String,String> query,Map<String,String> config){
StringBuffer sql = new StringBuffer("select ");
sql.append(config.get(FindConfig.FIELD) == null || "".equals(config.get(FindConfig.FIELD)) ? "*" : config.get(FindConfig.FIELD)).append(" ");
sql.append("from ").append("`").append(table).append("`").append(toWhereSql(query, "0".equals(config.get(FindConfig.LIKE))));
if (config.get(FindConfig.GROUP_BY) != null && !"".equals(config.get(FindConfig.GROUP_BY))){
sql.append("group by ").append(config.get(FindConfig.GROUP_BY)).append(" ");
}
if (config.get(FindConfig.ORDER_BY) != null && !"".equals(config.get(FindConfig.ORDER_BY))){
sql.append("order by ").append(config.get(FindConfig.ORDER_BY)).append(" ");
}
if (config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE))){
int page = config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE)) ? Integer.parseInt(config.get(FindConfig.PAGE)) : 1;
int limit = config.get(FindConfig.SIZE) != null && !"".equals(config.get(FindConfig.SIZE)) ? Integer.parseInt(config.get(FindConfig.SIZE)) : 10;
sql.append(" limit ").append( (page-1)*limit ).append(" , ").append(limit);
}
log.info("[{}] - 查询操作，sql: {}",table,sql);
return sql.toString();
}
public List selectBaseList(String select) {
List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);
List<E> list = new ArrayList<>();
for (Map<String,Object> map:mapList) {
list.add(JSON.parseObject(JSON.toJSONString(map),eClass));
}
return list;
}
4.1.4 新闻动态界面
当访客点击便民电子政务系统中导航栏上的“新闻动态”后将会进入到该“新闻动态”列表的界面，然后选择想要看的新闻动态信息，点击进入到详细界面，在详细界面可以收藏+赞+评论等操作，新闻动态界面如下图4-4所示。
图4-4新闻动态界面图
4.1.5 网上办事界面
当用户点击“网上办事”这一菜单按钮，会显示管理员在后台发布的所有的网上办事信息，支持通过关键词对网上办事进行搜索，选择需要的网上办事点击可以进入到网上办事详细的介绍界面，在详细界面可以查看到网上办事的事项名称、发布日期、表格附件、办事流程、部门名称、审核周期等信息，同时可以进行办事操作，网上办事界面如下图4-5所示。
图4-5网上办事界面图
4.1.6办事界面
当用户在网上办事详情界面想要进行办事，点击下方的“办事”按钮，就会跳转到办事信息填写界面，根据界面提示输入办事信息，点击“提交”按钮，办事就完成了，办事界面如下图4-6所示。
图4-6办事界面图
4.1.7便民服务界面
当用户点击“便民服务”这一菜单按钮，会显示管理员在后台发布的所有的便民服务信息，支持通过关键词对便民服务进行搜索，选择需要的便民服务点击可以进入到便民服务详细的介绍界面，在详细界面可以查看到便民服务的服务名称、联系地址、联系电话、备注信息等信息，便民服务界面如下图4-7所示。
图4-7便民服务界面图
4.2管理员功能模块
4.2.1 轮播图管理界面
管理员点击“轮播图管理”这一菜单会显示轮播图这个子菜单，管理员可以对前台展示的轮播图进行设置，界面如下图4-8所示。
图4-8轮播图管理界面图
4.2.2系统用户管理界面
管理员点击“系统用户”这一菜单会显示管理员和注册用户这两个子菜单，管理员可以对这两个角色的信息进行增删改查操作。界面如下图4-9所示。
图4-9系统用户管理界面图
系统用户管理关键代码如下所示。
public List selectBaseList(String select) {
List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);
List<E> list = new ArrayList<>();
for (Map<String,Object> map:mapList) {
list.add(JSON.parseObject(JSON.toJSONString(map),eClass));
}
return list;
}
4.2.3法律法规管理界面
管理员点击“法律法规”会显示出所有的法律法规信息，支持通过法律名称或者效力位阶对法律法规信息进行查询，如果想要添加新的法律法规信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条法律法规信息，点击“删除”进行删除。界面如下图4-10所示。
图4-10法律法规管理界面图
法律法规管理关键代码如下所示。
@RequestMapping(value = "/del")
@Transactional
public Map<String, Object> del(HttpServletRequest request) {
service.delete(service.readQuery(request), service.readConfig(request));
return success(1);
}
4.2.4政务信息管理界面
管理员点击“政务信息”会显示出所有的政务信息，支持通过标题内容或者发布日期对政务信息进行查询，如果想要添加新的政务信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条政务信息，点击“删除”进行删除。界面如下图4-11所示。
4.2.5政务公开管理界面
管理员点击“政务公开”会显示出所有的政务公开信息，支持通过标题内容或者公开类型对政务公开信息进行查询，如果想要添加新的政务公开信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条政务公开信息，点击“删除”进行删除。界面如下图4-12所示。
图4-12政务公开管理界面图
5系统测试
系统开发到了最后一个阶段那就是系统测试，系统测试对软件的开发其实是非常有必要的。因为没什么系统一经开发出来就可能会尽善尽美，再厉害的系统开发工程师也会在系统开发的时候出现纰漏，系统测试能够较好的改正一些bug，为后期系统的维护性提供很好的支持。通过系统测试，开发人员也可以建立自己对系统的信心，为后期的系统版本的跟新提供支持。
系统测试包括：用户登录功能测试、便民服务展示功能测试、便民服务添加、便民服务搜索、密码修改功能测试，如表5-1、5-2、5-3、5-4、5-5所示：
表5-1 用户登录功能测试表
| 用例名称 |
用户登录系统 |
| 目的 |
测试用户通过正确的用户名和密码可否登录功能 |
| 前提 |
未登录的情况下 |
| 测试流程 |
1) 进入登录页面 2) 输入正确的用户名和密码 |
| 预期结果 |
用户名和密码正确的时候，跳转到登录成功界面，反之则显示错误信息，提示重新输入 |
| 实际结果 |
实际结果与预期结果一致 |
便民服务查看功能测试：
表5-2 便民服务查看功能测试表
| 用例名称 |
便民服务查看 |
| 目的 |
测试便民服务查看功能 |
| 前提 |
用户登录 |
| 测试流程 |
点击便民服务列表 |
| 预期结果 |
可以查看到所有便民服务 |
| 实际结果 |
实际结果与预期结果一致 |
管理员添加便民服务界面测试：
表5-3 管理员添加便民服务界面测试表
| 用例名称 |
便民服务发布测试用例 |
| 目的 |
测试便民服务发布功能 |
| 前提 |
用户正常登录情况下 |
| 测试流程 |
1）用户点击便民服务管理就，然后点击添加后并填写信息。 2）点击进行提交。 |
| 预期结果 |
提交以后，页面首页会显示新的便民服务 |
| 实际结果 |
实际结果与预期结果一致 |
便民服务搜索功能测试：
表5-4便民服务搜索功能测试表
| 用例名称 |
便民服务搜索测试 |
| 目的 |
测试便民服务搜索功能 |
| 前提 |
无 |
| 测试流程 |
1）在搜索框填入搜索关键字。 2）点击搜索按钮。 |
| 预期结果 |
页面显示包含有搜索关键字的便民服务 |
| 实际结果 |
实际结果与预期结果一致 |
密码修改功能测试：
表5-5 密码修改功能测试表
| 用例名称 |
密码修改测试用例 |
| 目的 |
测试管理员密码修改功能 |
| 前提 |
管理员用户正常登录情况下 |
| 测试流程 |
1）管理员密码修改并完成填写。 2）点击进行提交。 |
| 预期结果 |
使用新的密码可以登录 |
| 实际结果 |
实际结果与预期结果一致 |
通过编写便民电子政务系统的测试用例，已经检测完毕用户登录模块、便民服务查看模块、便民服务添加模块、便民服务搜索模块、密码修改功能测试，通过这5大模块为便民电子政务系统的后期推广运营提供了强力的技术支撑。
At this point, the convenient e-government system has been completed. A lot of preparations were made before development. During the design and development process of this system, I read and studied a lot of literature, from which I also gained a lot of valuable methods and design ideas. I have a lot of confidence in the system. The development of the system also played a very important role. The system development technologies were all familiar to me, such as Web, Java technology, and MYSQL. These technologies were learned in previous studies, and many of the design ideas and methods were It is an experience gained from continuous learning in the past. In fact, the workload is still relatively large for us, but it is precisely because of the previous accumulation and preparation that we can successfully complete this project. From this point of view, accumulating experience and doing Being prepared is very important.
Of course, the design and implementation of this system would also be inseparable from the help of teachers and classmates. It is precisely because of their guidance and help that I was able to successfully complete this system within expectations. At the same time, I also learned a lot during this process. This system also has areas that need improvement. However, due to the shallow professional knowledge, it cannot be perfect. I hope that I will have the opportunity to put it into real use in the future.
[1] Wu Peng, Li Peixue. Research on the design of teaching office supplies management information system in higher vocational colleges based on SSM framework [J]. Light Industry Science and Technology, 2023, 39(01):99-101.
[2] Liu Mingliang, Huang Jianjun. Research on security risks and strategies of e-government systems based on cloud computing [J]. Journal of Hanjiang Normal University, 2022, 42(06): 83-87.DOI: 10.19575/j.cnki.cn42- 1892/g4.2022.06.020.
[3] Chang Wanlun, Tan Shuchen, Qu Xiaoe, Tian Zhao. Design and implementation of a secondary college teaching and research information sharing system based on the SSM framework [J]. Computer Knowledge and Technology, 2022, 18(34): 39- 41.DOI:10.14004/j.cnki.ckt.2022.2208.
[4] Zhao Jing. Enterprise compliance management system based on SSM+VUE framework [J]. Digital Communications World, 2022(11):17-19.
[5] Chu Chunyan. Application of information security technology in e-government systems [J]. Digital Communications World, 2022(09):112-114.
[6] Xie Yongji. Research on incentive design of e-government system outsourcing based on knowledge services [J]. Chinese Market, 2022(27):185-187.DOI:10.13939/j.cnki.zgsc.2022.27.185.
[7]Zheng Hongying. A Study on the Design of English Speaking Examination System Based on SSM Framework[J]. Journal of Sensors,2022,2022.
[8] Fang Siyi. Analysis of office system security strategies of e-government networks [J]. Electronic Technology, 2022, 51(06): 262-263.
[9] Cui Wei, Kang Licheng, Sun Jiaqing, Tang Limin. Optimization of government affairs processes in the maritime department’s e-government system [J]. Water Transport Management, 2022, 44(04): 8-11+16.DOI: 10.13340/j.jsm.2022.04 .004.
[10] He Yida. Research on auditing of e-government information systems[D]. Guangdong University of Finance and Economics, 2021.DOI:10.27734/d.cnki.ggdsx.2021.000358.
[11] Ding Songwan. Full life cycle management and control to ensure efficient operation of e-government[N]. Government Procurement Information, 2020-08-03(003).DOI:10.38293/n.cnki.nzfcg.2020.000814.
[12]. Design and Implementation of ERP System Based on SSM Framework[J]. ,2020,440(5).
[13]Ping Wanxin,Chen Yuankun,Hou Xiaoyan. Design of Campus Bicycle Rental Management System Based on SSM Framework[J]. Journal of Physics: Conference Series,2019,1314.
[14] Yin Xuehua. Analysis of problems and countermeasures in the development of e-government and convenience services in Urumqi [J]. Think Tank Times, 2018(46):284-285.
[15] Yang Haibo. Research on the Construction of Proposal Management Subsystem Based on E-Government System[C]//Tianjin Electronics Society, Tianjin Instrumentation Society. The 32nd China (Tianjin) 2018'IT, Network, Information Technology , Electronics, Instrumentation Innovation Academic Conference Proceedings. The 32nd China (Tianjin) 2018'IT, 2018: 71-74.
[16] Wang Duo, Zhou Meijuan. A brief discussion on how to accelerate the construction of the "Internet + Government Services" platform in Hebei Province [J]. Statistics and Management, 2017(02):120-121.DOI:10.16722/j.issn.1674- 537X.2017.02.042.
Thanks
The deceased is like a man who never gives up day and night. In the blink of an eye, the life of a registered user has come to an end. Facing parting and the end, people are always full of reluctance and confusion. I am also the same. I still remember that autumn, I couldn’t wait to arrive at school one day early, facing the school Looking at the majestic gate, I was full of expectations: Is this the starting point of my new life? That day, the sun was shining brightly, and the school's welcome ceremony was very warm. I faced my classmates who were smiling at me, as if rays of sunshine shone through my chest into my heart. At the same time, I met my lovely roommate that day, and we joined hands. We spent these two unforgettable two years together. Now, as I look at the acknowledgments of this paper, I can’t help but ask myself: Are we saying goodbye now?
I feel inexplicable and don't know what to say. I remember when I first came to school, I always thought that the engineering school would be too rigid and lack some tenderness. At that time, I was even a little bit repelled. But as I slowly got to know and understand the school, I realized that Her beauty, her tenderness, and I slowly fell in love with this campus, but time passed so quickly that I had to leave before I could fully appreciate her beauty, but the memories she brought to me will never be forgotten. If she leaves me, maybe my eyes will be filled with tears on the day she truly leaves. It’s not because I’m sad, I just want her image to be reflected in my tears and engraved in my heart. Finally, I would like to thank my teachers for teaching us knowledge and principles of life; thank you to my roommates for staying with me for so long; thank you to everyone who cares and supports me.
Young man, chase the wind and the moon without stopping. Wherever there is plain wasteland, there are spring mountains.
Please follow and like + privately message the blogger to receive the project source code for free