Introduction:

With the development of society, all walks of life are taking advantage of the information age. The superiority and popularization of computer make it necessary to develop all kinds of information system. College graduates employment management system, the main modules include home page, personal center, student management, counselor management, enterprise management, recruitment information management, apply for information management, graduate destination management, employment knowledge management, system management and other functions. The system administrator is mainly for the safe and effective storage and management of all kinds of information, but also can manage the system and update maintenance operations, and has the corresponding operation rights on the background. In order to realize the various functions of college graduates employment management system, it needs the strong support of background database. The administrator verifies the registration information, collects the information, and thus obtains the association information and so on the large amount of data by the database management. In this paper, the database server uses Mysql as the background database, so that the Web and database are closely linked. In the design process, the system code is fully guaranteed to be readable, practical, easy to expand, universal, easy to maintain, easy to operate and simple page characteristics. The development of the system to obtain college graduates employment management system information can be more convenient and fast, but also make college graduates employment management system management information become more systematic, ordered. The system interface is friendly and easy to operate.

Project design:

College graduates employment management system is based on Web service mode, which is a model structure suitable for Internet environment. As long as users can connect to the Internet, they can use this system in no time or place. College graduates employment management system working principle diagram, as shown

Figure System working principle diagram

System architecture diagram belongs to the system design stage, system architecture diagram is only a product of this stage, the overall architecture of the system determines the mode of the whole system, is the foundation of the system. The overall structure design of employment management system for college graduates

Function screenshots:

System home page: Home page can view the home page, enterprise, recruitment information, employment knowledge, announcement information, personal center, background management and other information for detailed operation

Login and registration: administrator, student, instructor and enterprise four roles, can simply enter their own system interface, through the interface navigation menu can simply operate the functional module, convenient user information operation requirements and administrator management data information

Company Information:

Company Details:

Recruitment information: in the recruitment information page, you can view the enterprise name, enterprise account, post name, working place, working time, salary, recruitment number, contact information, click times, job requirements, enterprise introduction and other information

Recruitment Information details:

Recruitment information company introduction

The user fills in the application information: the administrator or the enterprise receives the application information for review, after review, the user can see it

Interview after the login of enterprise account is approved:

Student users view job information

Employment Knowledge: On the employment knowledge page, you can view titles, categories, pictures, related materials, videos and other information

In employment knowledge you can download files and watch videos.

As well as review of comments and document content

Offline information session:

Announcement Information:

Announcement Details:

Personal Center:

Administrator background management: the administrator login into the system, you can to see all of the information, you can view the home page, personal center, student management, imperfect management, enterprise management, information management, information management, applying for graduate recruitment to management, employment, knowledge management, system management, etc., and can also carry on the corresponding operation management

Enterprise management: On the enterprise management page, you can modify or delete indexes, enterprise accounts, enterprise names, enterprise addresses, responsible persons, contact information, email addresses, enterprise pictures, and attachments

Job Information:

 

Job Information:

Graduation Destination:

Employment Knowledge:

Offline information session:

Management of system announcements and rote charts:

​​

Code implementation:



/** * Job information * back-end interface *@author 
 * @email 
 * @dateThe 2022-03-05 23:00:18 * /
@RestController
@RequestMapping("/zhaopinxinxi")
public class ZhaopinxinxiController {
    @Autowired
    private ZhaopinxinxiService zhaopinxinxiService;
    


    /** * Back-end list */
    @RequestMapping("/page")
    public R page(@RequestParam Map<String, Object> params,ZhaopinxinxiEntity zhaopinxinxi,
		HttpServletRequest request){
		String tableName = request.getSession().getAttribute("tableName").toString();
		if(tableName.equals("qiye")) {
			zhaopinxinxi.setQiyezhanghao((String)request.getSession().getAttribute("username"));
		}
        EntityWrapper<ZhaopinxinxiEntity> ew = new EntityWrapper<ZhaopinxinxiEntity>();
		PageUtils page = zhaopinxinxiService.queryPage(params, MPUtil.sort(MPUtil.between(MPUtil.likeOrEq(ew, zhaopinxinxi), params), params));

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

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

	 /** * query */
    @RequestMapping("/query")
    public R query(ZhaopinxinxiEntity zhaopinxinxi){
        EntityWrapper< ZhaopinxinxiEntity> ew = new EntityWrapper< ZhaopinxinxiEntity>();
 		ew.allEq(MPUtil.allEQMapPre( zhaopinxinxi, "zhaopinxinxi")); 
		ZhaopinxinxiView zhaopinxinxiView =  zhaopinxinxiService.selectView(ew);
		return R.ok("Recruitment information query succeeded").put("data", zhaopinxinxiView);
    }
	
    /** ** */
    @RequestMapping("/info/{id}")
    public R info(@PathVariable("id") Long id){
        ZhaopinxinxiEntity zhaopinxinxi = zhaopinxinxiService.selectById(id);
		zhaopinxinxi.setClicknum(zhaopinxinxi.getClicknum()+1);
		zhaopinxinxiService.updateById(zhaopinxinxi);
        return R.ok().put("data", zhaopinxinxi);
    }

    /** * Front-end details */
	@IgnoreAuth
    @RequestMapping("/detail/{id}")
    public R detail(@PathVariable("id") Long id){
        ZhaopinxinxiEntity zhaopinxinxi = zhaopinxinxiService.selectById(id);
		zhaopinxinxi.setClicknum(zhaopinxinxi.getClicknum()+1);
		zhaopinxinxiService.updateById(zhaopinxinxi);
        return R.ok().put("data", zhaopinxinxi);
    }
    



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

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

    /** * delete */
    @RequestMapping("/delete")
    public R delete(@RequestBody Long[] ids){
        zhaopinxinxiService.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<ZhaopinxinxiEntity> wrapper = new EntityWrapper<ZhaopinxinxiEntity>();
		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("qiye")) {
			wrapper.eq("qiyezhanghao", (String)request.getSession().getAttribute("username"));
		}

		int count = zhaopinxinxiService.selectCount(wrapper);
		return R.ok().put("count", count); }}Copy the code

Database design:

Transform the e-R diagram of database conceptual design into a relational database. In a relational database, data relationships consist of data tables, but the structure of the table is expressed in the fields of the table.

Table 4-1: Enterprises
The field names type The length of the Fields that
id bigint A primary key
addtime timestamp Creation time
qiyezhanghao varchar 200 Corporate account
mima varchar 200 password
qiyemingcheng varchar 200 An enterprise name
qiyedizhi varchar 200 Business address
fuzeren varchar 200 head
lianxifangshi varchar 200 contact
youxiang varchar 200 email
qiyetupian varchar 200 Enterprise image
qiyezizhi varchar 200 Enterprise qualification
yingyexukezheng varchar 200 Business license
sfsh varchar 200 Whether the audit
shhf longtext 4294967295 Review the reply

​​

Table: Bulletin information
The field names type The length of the Fields that
id bigint A primary key
addtime timestamp Creation time
title varchar 200 The title
introduction longtext 4294967295 Introduction to the
picture varchar 200 The picture
content longtext 4294967295 content

Table: Employment knowledge
The field names type The length of the Fields that
id bigint A primary key
addtime timestamp Creation time
biaoti varchar 200 The title
fenlei varchar 200 classification
tupian varchar 200 The picture
xiangguanziliao varchar 200 The relevant data
shipin varchar 200 video
wenzhangneirong longtext 4294967295 The article content

Table: Counsellor
The field names type The length of the Fields that
id bigint A primary key
addtime timestamp Creation time
fudaoyuangonghao varchar 200 Instructor id
mima varchar 200 password
fudaoyuanxingming varchar 200 Counselor’s Name
xingbie varchar 200 gender
lianxidianhua varchar 200 Contact phone number
jiaoshiyouxiang varchar 200 Teachers’ email

Table: Recruitment information
The field names type The length of the Fields that
id bigint A primary key
addtime timestamp Creation time
qiyemingcheng varchar 200 An enterprise name
qiyezhanghao varchar 200 Corporate account
qiyetupian varchar 200 Enterprise image
gangweimingcheng varchar 200 Post the name
shangbandidian varchar 200 work
shangbanshijian varchar 200 Go to work time
xinzidaiyu int salary
zhaopinrenshu int hiring
lianxifangshi varchar 200 contact
qiyejieshao longtext 4294967295 Companies to introduce
renzhiyaoqiu longtext 4294967295 Job specification
sfsh varchar 200 Whether the audit
shhf longtext 4294967295 Review the reply
clicknum int Click on the number of times

Table: Configuration files
The field names type The length of the Fields that
id bigint A primary key
name varchar 100 Configuration Parameter Name
value varchar 100 Setting Parameter Values

Form: Application information
The field names type The length of the Fields that
id bigint A primary key
addtime timestamp Creation time
qiyemingcheng varchar 200 An enterprise name
gangweimingcheng varchar 200 Post the name
xinzidaiyu varchar 200 salary
qiyezhanghao varchar 200 Corporate account
xueshengzhanghao varchar 200 Student account
xueshengxingming varchar 200 The student’s name
lianxifangshi varchar 200 contact
jianlitoudi varchar 200 A resume
yingpinriqi datetime To apply for the date
sfsh varchar 200 Whether the audit
shhf longtext 4294967295 Review the reply

Thesis Reference:

Pick to

1 System Overview

1.1 an overview of the

1.2 Significance of the project

1.3 Main Contents

2 System development environment

2.1 Spring Boot Framework

2.2 JAVA introduction

2.3 Access database implementation method

2.4 Two connection modes of the MySQL database

2.5 MySql Database

3 Demand Analysis

3.1 Technical feasibility: Technical background

3.2 Economic Feasibility

3.3 Operation Feasibility

3.4 System design rules

3.5 System flow and logic

4. System outline design

4.1 an overview of the

4.2 System Architecture

4.3. Database design

4.3.1 Database Entities

4.3.2 Database design table

5 System Design 5 System design

5.1 System Function Modules

5.2 Administrator Function Modules

5.3 Enterprise Function Modules

5.4 Instructor function modules

5.5 Functional modules for students

6 System Test

6.1 Purpose of system Test

6.2 System test method

6.3 Test Results

conclusion

Thank you

reference