Introduction:
Traditional community management is carried out in the offline entity. Due to the differences in community structure, users need to go offline for actual experience, which has great space and time constraints. With the increasing popularity of community groups, their performance and module transparency, more and more people have begun to join online communities for various reasons, and the traditional community management model has been unable to meet the needs of people. The emergence of the Internet has brought about the rapid development of the network again, and people’s life has undergone earth-shaking changes. People can enjoy the convenience brought by the Internet anytime and anywhere. All the needs in life and work can be realized on the Internet, such as learning, joining and so on. That is to say, the network has become the most direct, the most convenient, the most relaxed access.
In today’s world, the Rapid development of the Internet now, how to use the Internet to create a simpler and more efficient life, this is our first discussion. The need for community information management related websites, on the one hand, so that the administrator can timely update and information management of community management information, can easily obtain the circulation of various community information. On the other hand, users can use the Internet to view information related to community management more intuitively. Compared with the traditional community information car, the way of user joining is easier, and the operation of the system is more accurate. This is a potential trend, which may effectively speed up the popularization of community management.
Functional design:
The main development objectives of community management are as follows:
(1) Users can view the latest club information and relevant information in real time;
(2) Users can compare the information of various associations and choose the associations they are more satisfied with;
(3) Users can exchange their experience of joining the club through leaving messages;
(4) administrators can facilitate the management of the front desk web page information in the background;
Log in to the system structure diagram, as shown in the figure:
System structure diagram, as shown in the figure:
Function screenshots:
Client:
User login: Users can log in and register, multi-role login, and only one administrator. Ordinary users can view the home page, personal center, community member management, activity registration management, my collection management and other operations
User home page: through the system to view the front desk community information, community news, community activities, feedback, my personal information
Club Information:
In the club page, you can view the club number, club name, type, picture, club purpose, date of establishment, club address, contact number, email, etc. You can apply for joining and comment on the detailed operation
The application for joining the club and the maintenance staff of the club can be approved or not approved
Club news:
Club news details page can also be collection and comment operations
Message feedback: Users can leave messages on the message feedback page, and the administrator and the person in charge of the community will reply and other detailed operations
Personal center: my personal center, in the personal center, my favorites page can view the user name, password, name, gender, profile picture, mobile phone, email, ID card and other details to delete, modify, etc
Background for common users:
Club staff background:
The main functions are: home page, personal center, community information management, community news management, user consulting management, community activities management, community member management, community funds management, activity registration management
Club administrators can review the application or registration of club activities
Super administrator Background:
Super administrator in addition to some audit, other functions are basic, can view all information. Home page, personal center, user management, association responsible person management, association information management, association classification management, association news management, user consulting management, association activity management, association member management, association funds management, activity registration management, message board management, system management, etc
User management:
Club management:
Club news management:
Club funds:
Message board Replies:
System rotation diagram, etc
Code implementation:
/** * back end interface *@author
* @email
* @dateThe 2022-11-26 08:47:15 * /
@RestController
@RequestMapping("/shetuanhuodong")
public class ShetuanhuodongController {
@Autowired
private ShetuanhuodongService shetuanhuodongService;
/** * Back-end list */
@RequestMapping("/page")
public R page(@RequestParam Map<String, Object> params,ShetuanhuodongEntity shetuanhuodong, HttpServletRequest request){
String tableName = request.getSession().getAttribute("tableName").toString();
if(tableName.equals("shetuanfuzeren")) {
shetuanhuodong.setShetuanbianhao((String)request.getSession().getAttribute("username"));
}
EntityWrapper<ShetuanhuodongEntity> ew = new EntityWrapper<ShetuanhuodongEntity>();
PageUtils page = shetuanhuodongService.queryPage(params, MPUtil.sort(MPUtil.between(MPUtil.likeOrEq(ew, shetuanhuodong), params), params));
return R.ok().put("data", page);
}
/**
* 前端列表
*/
@IgnoreAuth
@RequestMapping("/list")
public R list(@RequestParam Map<String, Object> params,ShetuanhuodongEntity shetuanhuodong, HttpServletRequest request){
EntityWrapper<ShetuanhuodongEntity> ew = new EntityWrapper<ShetuanhuodongEntity>();
PageUtils page = shetuanhuodongService.queryPage(params, MPUtil.sort(MPUtil.between(MPUtil.likeOrEq(ew, shetuanhuodong), params), params));
return R.ok().put("data", page);
}
/** * list */
@RequestMapping("/lists")
public R list( ShetuanhuodongEntity shetuanhuodong){
EntityWrapper<ShetuanhuodongEntity> ew = new EntityWrapper<ShetuanhuodongEntity>();
ew.allEq(MPUtil.allEQMapPre( shetuanhuodong, "shetuanhuodong"));
return R.ok().put("data", shetuanhuodongService.selectListView(ew));
}
/** * query */
@RequestMapping("/query")
public R query(ShetuanhuodongEntity shetuanhuodong){
EntityWrapper< ShetuanhuodongEntity> ew = new EntityWrapper< ShetuanhuodongEntity>();
ew.allEq(MPUtil.allEQMapPre( shetuanhuodong, "shetuanhuodong"));
ShetuanhuodongView shetuanhuodongView = shetuanhuodongService.selectView(ew);
return R.ok("Check club activity success").put("data", shetuanhuodongView);
}
/** ** */
@RequestMapping("/info/{id}")
public R info(@PathVariable("id") String id){
ShetuanhuodongEntity shetuanhuodong = shetuanhuodongService.selectById(id);
return R.ok().put("data", shetuanhuodong);
}
/** * Front-end details */
@IgnoreAuth
@RequestMapping("/detail/{id}")
public R detail(@PathVariable("id") String id){
ShetuanhuodongEntity shetuanhuodong = shetuanhuodongService.selectById(id);
return R.ok().put("data", shetuanhuodong);
}
/** * The backend saves */
@RequestMapping("/save")
public R save(@RequestBody ShetuanhuodongEntity shetuanhuodong, HttpServletRequest request){
shetuanhuodong.setId(new Date().getTime()+new Double(Math.floor(Math.random()*1000)).longValue());
//ValidatorUtils.validateEntity(shetuanhuodong);
shetuanhuodongService.insert(shetuanhuodong);
return R.ok();
}
/**
* 前端保存
*/
@RequestMapping("/add")
public R add(@RequestBody ShetuanhuodongEntity shetuanhuodong, HttpServletRequest request){
shetuanhuodong.setId(new Date().getTime()+new Double(Math.floor(Math.random()*1000)).longValue());
//ValidatorUtils.validateEntity(shetuanhuodong);
shetuanhuodongService.insert(shetuanhuodong);
return R.ok();
}
/** * modify */
@RequestMapping("/update")
public R update(@RequestBody ShetuanhuodongEntity shetuanhuodong, HttpServletRequest request){
//ValidatorUtils.validateEntity(shetuanhuodong);
shetuanhuodongService.updateById(shetuanhuodong);// All updates
return R.ok();
}
/** * delete */
@RequestMapping("/delete")
public R delete(@RequestBody Long[] ids){
shetuanhuodongService.deleteBatchIds(Arrays.asList(ids));
return R.ok();
}
/** * remind interface */
@RequestMapping("/remind/{columnName}/{type}")
public R remindCount(@PathVariable("columnName") String columnName, HttpServletRequest request,
@PathVariable("type") String type,@RequestParam Map<String, Object> map) {
map.put("column", columnName);
map.put("type", type);
if(type.equals("2")) {
SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd");
Calendar c = Calendar.getInstance();
Date remindStartDate = null;
Date remindEndDate = null;
if(map.get("remindstart")! =null) {
Integer remindStart = Integer.parseInt(map.get("remindstart").toString());
c.setTime(new Date());
c.add(Calendar.DAY_OF_MONTH,remindStart);
remindStartDate = c.getTime();
map.put("remindstart", sdf.format(remindStartDate));
}
if(map.get("remindend")! =null) {
Integer remindEnd = Integer.parseInt(map.get("remindend").toString());
c.setTime(new Date());
c.add(Calendar.DAY_OF_MONTH,remindEnd);
remindEndDate = c.getTime();
map.put("remindend", sdf.format(remindEndDate));
}
}
Wrapper<ShetuanhuodongEntity> wrapper = new EntityWrapper<ShetuanhuodongEntity>();
if(map.get("remindstart")! =null) {
wrapper.ge(columnName, map.get("remindstart"));
}
if(map.get("remindend")! =null) {
wrapper.le(columnName, map.get("remindend"));
}
String tableName = request.getSession().getAttribute("tableName").toString();
if(tableName.equals("shetuanfuzeren")) {
wrapper.eq("shetuanbianhao", (String)request.getSession().getAttribute("username"));
}
int count = shetuanhuodongService.selectCount(wrapper);
return R.ok().put("count", count); }}Copy the code
Data design:
The function of database is to store and manage all the data in the system. All data can be stored in the database for the convenience of users. And all the data in the database should also have certain participatory, any system can be used for some data, but also should keep certain independence, each data in the database has a strong security, deposit can be very good to the database, no identity verification is unable to view and use of these data. The design of the database needs to make clear the connection between each entity. The e-R figure of the system is as follows:
The administrator entity stores management information package accounts, passwords, verification codes, and role attributes. Figure 4-5 shows the attributes of the administrator.
Figure Entity attribute diagram of administrator information
User information mainly includes user name, password, name, gender, profile picture, mobile phone, email, ID card and other attributes, as shown in the figure
Figure User information entity attribute diagram
The attributes of the entity managed by the person in charge of the community mainly include the community number, password, name, community name, gender, profile picture, contact phone number, phone mailbox, ID card and other attributes. The entity attribute diagram of the community leader is shown in the figure.
Figure the attribute diagram of the entity managed by the person in charge of the community
Thesis Reference:
Pick to* * * *
Abstract* * * *
Preface to Chapter 1* * * *
1.1 Research Background
1.2 Research Status
1.3 System development objectives
Chapter 2 Technology and principle* * * *
2.1 the JSP is introduced
2.2 JAVA technology
2.3 MySQL Database
2.4 B/S structure
2.5 introduce SSM
Chapter 3 Demand analysis* * * *
3.1 Requirement Analysis
3.2 System feasibility analysis
3.3 Project design objectives and principles
3.4 System process analysis
Chapter 4 Architecture design* * * *
4.1 System Architecture
4.2 Database entity design
4.3 Database table design
Chapter 5 system implementation* * * *
5.1 Function Modules of the Administrator
5.2 Functional module of the club leader
5.3 Front and Back User Function Modules
Chapter 6 system test* * * *
6.1 Test Purpose
6.2 Test Method
6.3 Functional Testing
6.4 Test Conclusions
Chapter 7 concludes* * * *
reference* * * *
Thanks * * * *
Make a friend:
Thumb up, collection, attention, comment, view 👇 🏻 👇 🏻 👇 🏻 home page contact 👇 🏻 👇 🏻 👇 🏻
Clocked articles updated 226/365 days