​

Introduction:

With the rapid development of society, the influence of computer is comprehensive and deep. The continuous improvement of school management level, the daily life of middle school students on campus epidemic prevention and control requirements are also increasing, the number of students is constantly increasing, making the development of campus epidemic prevention and control system become necessary and urgent. The campus epidemic prevention and control system mainly uses computers to increase students’ choices through the information management required by the campus epidemic prevention and control system, and also facilitates the timely inquiry, modification and understanding of students’ information. The campus epidemic prevention and control system brings more convenience to students. The system works with database management system software to meet students’ needs. The application of computer technology in modern management makes computer become an important tool for people to apply modern technology. It can effectively solve the problem of convenient and comprehensive access to information and improve efficiency.

Functional design:

Technical feasibility: technical background

The enterprise website is developed in the Windows operating system, and the performance of the CURRENT PC has been competent for the web server of ordinary websites. The technology used in system development is also its own, but also one of the widely used technology.

System development environment and the configuration can be installed on its own, the system USES Java development tools, the use of more mature Mysql database on the system at the front desk and the background of data interaction, database according to the technical language, and combining with the demand for modified maintenance, can make site operation has more stability and security, so as to complete realization of website development.

(1) Hardware feasibility analysis

Campus epidemic prevention and control system design for the use of computer and information analysis has no rigid requirements, the computer as long as can normal use of the preparation of the code and the page design is feasible, mainly some requirements for the server, for completing platform to upload server there is a requirement, the server must choose security is higher, Then in the open site must be smooth, can not pause too long; High cost performance; High security.

(2) Software feasibility analysis

The development of the whole system uses cloud computing, traffic scalability and intelligent adjustment based on traffic. The advantages of cloud computing are the scalability 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 we can see that the development of the system is not a problem.

Economic viability

Epidemic prevention and control system development on campus before doing market research and other related management system, there is no any fees, by developers own efforts, all work is hands-on, in they are difficult to solve the problems, mostly with the help of classmates and instructors for the solution of the relevant information, Therefore, the development of campus epidemic prevention and control system is completely feasible economically, without any cost.

Using more mature technology, the system is based on Java development, using Mysql database. So the system in the development of manpower, financial requirements are not high, with economic feasibility.

Operation feasibility:

Operability is mainly to the campus after completion of the epidemic prevention and control system design, the use of the student experience, as well as the administrator can through the system management related data information at any time, and two user roles for administrators, students, can be simple and clear into their system interface, through the interface the navigation menu can be simple and clear operation function module, Convenient for the operation of students’ information needs and scenic spots information management data information, for the operation of the system, do not need professionals can directly carry out the operation and management of functional modules, so the operability of the system is completely possible. The operation process of this system is to use the interface window to log in, so the operator as long as the simple computer operation can be completely.

Structure chart of campus epidemic Prevention and control System:

​

Function screenshots:

User home page: Through the content list, users can obtain the homepage, access registration, epidemic knowledge, forum information, epidemic announcement, personal center, background management, customer service and other information operation content, as shown in the figure

​

Login and registration: Students can enter the campus epidemic prevention and control system by filling in student ID, password, student name, gender, profile picture, major, class, address province, city, county, mobile phone, email and other information. Students can log in through student ID and password

​​

Access registration: Access registration title, login type, registration time, remarks, student NUMBER, student name, gender, profile picture, real-time temperature, mobile phone, class, major, review reply, review status, review and other information can be obtained through the access registration management content list for details, modification, deletion or view

​

Epidemic knowledge: Information such as title, classification, pictures, videos and release date can be obtained from the epidemic knowledge content list for detailed, modified, deleted or viewed operations

​​

Forum communication: you can view, publish posts and other operations through the forum information list

​

Release Details:​

Epidemic Announcement:

​

​

User background management:

​

Administrator background management:

Administrator Homepage: Administrators enter the campus epidemic prevention and control system to view the personal center, nucleic acid test management, temperature state management, student management, student status management, leave application management, access registration management, epidemic knowledge management, forum management, system management and operation

Student management: Obtain the scenic spot student number, password, student name, gender, profile picture, major, class, address province, city, county, mobile phone, email and other information from the student management content list for details, modification, deletion or viewing operations

​

Nucleic acid testing:

​

Student Status:

​

​

Leave management: Through the leave application management content list, you can obtain the application number, application title, vacation days, trip city, route city, application date and other information for details, modification, deletion or view operations

​

Epidemic knowledge: Information such as title, classification, pictures, videos and release date can be obtained from the epidemic knowledge content list for detailed, modified, deleted or viewed operations

​

Forum and rote chart: The administrator can view the epidemic bulletin/customer service management/rote chart on the system management page, upload pictures, add, delete, modify, view, and maintain the entire system, as shown in Figure 5-8

​

Code implementation:

​




/** * Temperature state * back-end interface *@author 
 * @email 
 * @dateThe 2022-01-10 10:02:51 * /
@RestController
@RequestMapping("/tiwenzhuangtai")
public class TiwenzhuangtaiController {
    @Autowired
    private TiwenzhuangtaiService tiwenzhuangtaiService;
    


    /** * Back-end list */
    @RequestMapping("/page")
    public R page(@RequestParam Map<String, Object> params,TiwenzhuangtaiEntity tiwenzhuangtai, HttpServletRequest request){
        EntityWrapper<TiwenzhuangtaiEntity> ew = new EntityWrapper<TiwenzhuangtaiEntity>();
		PageUtils page = tiwenzhuangtaiService.queryPage(params, MPUtil.sort(MPUtil.between(MPUtil.likeOrEq(ew, tiwenzhuangtai), params), params));

        return R.ok().put("data", page);
    }
    
    /**
     * 前端列表
     */
    @RequestMapping("/list")
    public R list(@RequestParam Map<String, Object> params,TiwenzhuangtaiEntity tiwenzhuangtai, HttpServletRequest request){
        EntityWrapper<TiwenzhuangtaiEntity> ew = new EntityWrapper<TiwenzhuangtaiEntity>();
		PageUtils page = tiwenzhuangtaiService.queryPage(params, MPUtil.sort(MPUtil.between(MPUtil.likeOrEq(ew, tiwenzhuangtai), params), params));
        return R.ok().put("data", page);
    }

	/** * list */
    @RequestMapping("/lists")
    public R list( TiwenzhuangtaiEntity tiwenzhuangtai){
       	EntityWrapper<TiwenzhuangtaiEntity> ew = new EntityWrapper<TiwenzhuangtaiEntity>();
      	ew.allEq(MPUtil.allEQMapPre( tiwenzhuangtai, "tiwenzhuangtai")); 
        return R.ok().put("data", tiwenzhuangtaiService.selectListView(ew));
    }

	 /** * query */
    @RequestMapping("/query")
    public R query(TiwenzhuangtaiEntity tiwenzhuangtai){
        EntityWrapper< TiwenzhuangtaiEntity> ew = new EntityWrapper< TiwenzhuangtaiEntity>();
 		ew.allEq(MPUtil.allEQMapPre( tiwenzhuangtai, "tiwenzhuangtai")); 
		TiwenzhuangtaiView tiwenzhuangtaiView =  tiwenzhuangtaiService.selectView(ew);
		return R.ok("Temperature status query succeeded").put("data", tiwenzhuangtaiView);
    }
	
    /** ** */
    @RequestMapping("/info/{id}")
    public R info(@PathVariable("id") String id){
        TiwenzhuangtaiEntity tiwenzhuangtai = tiwenzhuangtaiService.selectById(id);
        return R.ok().put("data", tiwenzhuangtai);
    }

    /** * Front-end details */
    @RequestMapping("/detail/{id}")
    public R detail(@PathVariable("id") String id){
        TiwenzhuangtaiEntity tiwenzhuangtai = tiwenzhuangtaiService.selectById(id);
        return R.ok().put("data", tiwenzhuangtai);
    }
    



    /** * The backend saves */
    @RequestMapping("/save")
    public R save(@RequestBody TiwenzhuangtaiEntity tiwenzhuangtai, HttpServletRequest request){
    	tiwenzhuangtai.setId(new Date().getTime()+new Double(Math.floor(Math.random()*1000)).longValue());
    	//ValidatorUtils.validateEntity(tiwenzhuangtai);
        tiwenzhuangtaiService.insert(tiwenzhuangtai);
        return R.ok();
    }
    
    /**
     * 前端保存
     */
    @RequestMapping("/add")
    public R add(@RequestBody TiwenzhuangtaiEntity tiwenzhuangtai, HttpServletRequest request){
    	tiwenzhuangtai.setId(new Date().getTime()+new Double(Math.floor(Math.random()*1000)).longValue());
    	//ValidatorUtils.validateEntity(tiwenzhuangtai);
        tiwenzhuangtaiService.insert(tiwenzhuangtai);
        return R.ok();
    }

    /** * modify */
    @RequestMapping("/update")
    public R update(@RequestBody TiwenzhuangtaiEntity tiwenzhuangtai, HttpServletRequest request){
        //ValidatorUtils.validateEntity(tiwenzhuangtai);
        tiwenzhuangtaiService.updateById(tiwenzhuangtai);// All updates
        return R.ok();
    }
    

    /** * delete */
    @RequestMapping("/delete")
    public R delete(@RequestBody Long[] ids){
        tiwenzhuangtaiService.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<TiwenzhuangtaiEntity> wrapper = new EntityWrapper<TiwenzhuangtaiEntity>();
		if(map.get("remindstart")! =null) {
			wrapper.ge(columnName, map.get("remindstart"));
		}
		if(map.get("remindend")! =null) {
			wrapper.le(columnName, map.get("remindend"));
		}


		int count = tiwenzhuangtaiService.selectCount(wrapper);
		return R.ok().put("count", count); }}Copy the code
@Configuration
public class InterceptorConfig extends WebMvcConfigurationSupport{
	
	@Bean
    public AuthorizationInterceptor getAuthorizationInterceptor(a) {
        return new AuthorizationInterceptor();
    }
	
	@Override
    public void addInterceptors(InterceptorRegistry registry) {
        registry.addInterceptor(getAuthorizationInterceptor()).addPathPatterns("/ * *").excludePathPatterns("/static/**");
        super.addInterceptors(registry);
	}
	
	/ * * * 2.0 configuration springboot WebMvcConfigurationSupport, leads to the default configuration is covered, static resource needs to be rewritten to allow access to * / addResourceHandlers method
	@Override
    public void addResourceHandlers(ResourceHandlerRegistry registry) {
		registry.addResourceHandler("/ * *")
        .addResourceLocations("classpath:/resources/")
        .addResourceLocations("classpath:/static/")
        .addResourceLocations("classpath:/admin/")
        .addResourceLocations("classpath:/front/")
        .addResourceLocations("classpath:/public/");
		super.addResourceHandlers(registry); }}Copy the code

​

Data design:

Database table is an important part of the database, in fact, the database is only a framework, database table is the essence of the database, the system database table is as follows: ALLUsers table:
The serial number The field names The field type The size of the
1 id Int 4
2 username 150
3 pwd 150
4 cx 150
5 addtime DateTime 8

Churudengji table:
The serial number The field names The field type The size of the
1 id Int 4
2 addtime 150
3 dengjibiaoti 150
4 dengjileixing DateTime 8
5 dengjineirong 150
6 dengjishijian DateTime 8
7 beizhu 150
8 xuehao DateTime 8
9 xueshengxingming 150
10 xingbie DateTime 8
11 touxiang 150
12 shishitiwen DateTime 8
13 shouji
14 banji DateTime 8
15 zhuanye
16 sfsh DateTime 150
17 shhf

Xiujiashenqing table:
The serial number The field names The field type The size of the
1 id Int 4
2 addtime 150
3 shenqingbianhao 150
4 shenqingbiaoti DateTime 8
5 shenqingneirong 150
6 xiujiatianshu DateTime 8
7 xingchengchengshi 150
8 tujingchengshi DateTime 8
9 shenqingriqi 150
10 beizhu DateTime 8
11 xuehao 150
12 xueshengxingming DateTime 8
13 touxiang DateTime 8
14 zhuanye 150
15 banji DateTime 8
16 shouji 150
17 sfsh DateTime 8
18 shhf 150

Xuesheng table:
The serial number The field names The field type The size of the
1 id Int 4
2 addtime 150
4 xuehao 150
5 mima 150
6 xueshengxingming DateTime 8
7 xingbie
8 touxiang DateTime 8
9 zhuanye
10 banji DateTime 8
11 zhuzhishengfen
12 shiji DateTime 8
13 xianqu DateTime 8
14 shouji DateTime 8
15 youxiang DateTime 8

Thesis Reference:

Pick to * * * *

ABSTRACT****

Record the * * * *

Chapter 1 Introduction ****

1.1 Background and significance

1.2 Research overview at home and abroad

1.3 Research content

Chapter 2 Related technology ****

2.1 JAVA introduction

2.2 MyEclipse development environment

2.3 Tomcat Server

2.4 MySQL Database

2.5 Spring Boot Framework

Chapter 3 System analysis ****

3.1 Requirement Analysis

3.2 System feasibility analysis

3.2.1 Technical Feasibility: Technical background

3.2.2 Economic feasibility

3.2.3 Operation Feasibility:

3.3 Project design objectives and principles

3.4 System process analysis

3.4.1 Operation process

3.4.2 Process for Adding Information

3.4.3 Process for Deleting Information

Chapter 4 System design ****

4.1 System Architecture

4.2 Development process design

4.3 Principles of Database design

4.4 the data table

Chapter 5 Detailed system design ****

5.1 Function Modules of the Administrator

5.2 Students front and background function modules

Chapter 6 System testing ****

6.1 Purpose of system Test

6.2 System test method

6.3 Functional Testing

Conclusion * * * *

Thanks * * * *

reference

Full source code:

Like, like, follow, comment, check out 👇🏻👇🏻👇🏻 👇🏻👇🏻👇🏻

Clocked articles updated 243/365 days

​