目录
1.3 Paper structure arrangement
Chapter 2 Requirements Analysis of Payroll Management System
2.1 Lineage feasibility analysis
2.1.1 Technical feasibility analysis
2.1.2 Economic Feasibility Analysis
2.1.3 Legal Feasibility Analysis
2.1.4 Operational Feasibility Analysis
2.2 System functional requirements analysis
2.3 Systematic Requirements Analysis
2.5.2 Modification number postponement process
Chapter 3 Overall Design of Payroll Management System
3.1 System function module design
3.2.1 Database conceptual structure design
Chapter 4 Design and Implementation of Key Modules
4.5 Technical information interface
4.6 Kokin information interface
4.7 Position management interface
4.8 Personal information interface
Payroll management system
Required Required
Today, with the development of information technology, all industries are bound to implement information management, especially companies with a large number of employees. If management is only done manually, it will waste huge wealth for the company. The management of corporate wages is a tedious task. , including calculations in various aspects such as attendance, leave, performance, business trips, etc. Only when the company's salary management is in place can the operational efficiency of the entire enterprise be improved. In terms of salary management, traditional management is through paper records or stand-alone software. For management, paper records are easy to lose and difficult to save. In the management of stand-alone software, employees have no way to participate and can only manage personnel, which can no longer meet the needs of the development of the times. Therefore, various information on corporate wages must be managed. Management, design and development of this web version of the payroll management system.
This salary management system uses JAVA language, is based on the Springboot framework and is developed and implemented using the MYSQL database. It is functionally divided into two parts: employees and administrators, which allows users to view their salary information and attendance information through the system; administrators can also Manage employees, positions, employee attendance and wages through the system, provide services for corporate payroll management, and meet the corporate needs for payroll management.
Keywords: Salary management; JAVA language; Springboot; MYSQL
Wage management system
Abstract
Today, with the development of information technology, each industry will realize information management, especially the enterprise with many personnel, if only by manual management, it will waste a huge amount of wealth to the enterprise, enterprise salary management is a tedious salary, including attendance, leave, performance, business trips and other aspects of calculation, only the enterprise salary management in place, In terms of salary management, traditional management is managed by paper records or stand-alone software. Paper records are easy to be lost and not easy to be saved. In stand-alone software management, employees have no way to participate, but can only manage personnel, which cannot meet the needs of the development of The Times. Therefore, for the enterprise wage information management, the design and development of the webpage version of the wage management system.
The salary management system uses JAVA language, based on Springboot framework and the use of MYSQL database development, in the function of staff and administrator two parts, to meet the user through the system to view their own salary information, attendance information; Administrators can also manage employees, positions, attendance and wages through the system, providing services for the enterprise's wage management and meeting the enterprise's demand for wage management.
Key words: Wage management; JAVA language; Springboot; MYSQL
At present, computer information technology has entered everyone's life, ranging from enterprise ERP management to family financial management. Various management software can be found everywhere. Currently, in many enterprises, salary management is used The form-structured salary management system is relatively simple to operate and is widely used by managers. The disadvantage is that it can only be managed by managers and individual employees cannot participate. Today, with more and more employees, the management of wages has become increasingly difficult. The requirements are also constantly increasing. Many companies have implemented manual attendance. If traditional management methods are still used, various information entry will waste a lot of resources. Moreover, in terms of employees' personal attendance and salary inquiries, employees have to go to the office by themselves. /The financial office conducts inquiries in the form of lookup tables, which is not conducive to the development of the enterprise. Therefore, combined with the current popularization and application of B/S technology, a salary management system based on B/S is designed and developed, which can solve the above problems well and allow employees to Active participation in the system not only improves the enthusiasm of employees, but also reduces the work intensity of administrators, improves work efficiency, and is of great significance to the operation of the enterprise.
The first generation of salary management systems was produced in the late 1960s. At that time, some large enterprises were faced with a large amount of data in the calculation and payment of employee wages, and it was time-consuming and labor-intensive to rely solely on users to perform calculations manually. And it is easy to make mistakes. At that time, computer information technology had been put into practical use. Therefore, in order to solve the needs of enterprises in salary calculation and payment, the salary management system was produced. However, because of the limited information technology conditions at that time, the companies using it were very There are few, and the functions can only complete simple salary calculations. In the late 1970s, with the rapid development of computer information technology, the gradual popularization of computers, and the updating of computer development tools and database technology, conditions were provided for the emergence of the second-generation salary management system. On the basis of the first generation system, salary management and attendance management have been improved, and salary analysis can be automatically generated. However, this generation system has not been developed according to actual enterprise needs for salary management. It is improved on the basis of , so its functions are not comprehensive enough.
The 1990s ushered in the reform of the salary management system. Due to the competitive needs of the market, companies began to consider how to attract and retain talents. Talents are the core of the company, how to improve employee motivation, and how to achieve unified management and improvement of employees. The management level of enterprises has made enterprises have better requirements for salary management, so the third generation salary management system has been produced. During this period, there has been a qualitative improvement in both hardware technology and software, which has provided wages The management system provides better development conditions. The third-generation salary management system is designed and developed from an enterprise's perspective on salary management. It combines some salary-related data for unified management, allowing managers to use one system. It can improve multiple operations and get rid of the previous heavy work. At the same time, it can also involve users and directly link their own interests to the system, mobilize the enthusiasm of employees, reduce the cost of enterprise management, and improve the efficiency of management.
The paper will be organized hierarchically. In addition to the abstract, acknowledgments, and literature references, the main text will also analyze the system requirements, describe the general design and implemented functions, and finally list some debugging records. The main structure of the paper is as follows:
Chapter 1 explains the background of the project, the current status of developing this system, and the chapter arrangement of the paper.
Chapter 2 analyzes the specific requirements of the system.
Chapter 3 explains the system design, which covers functional design and database design.
Chapter 4 clarifies the implementation of each functional module of the salary management system and displays it in the form of pictures and texts.
Chapter 5 lists some system debugging and testing records.
Chapter 6 introduces the conclusion of the payroll management system.
Requirements analysis is the first thing to do before developing a system. If a system is not worth developing or violates relevant laws and regulations, the developed system will be worthless. Therefore, before development, we must first analyze the system requirements. Analyze whether system development is feasible. If so, then analyze the company's salary management needs in detail, analyze the functions of the system, and analyze the performance of the system.
Technical feasibility mainly considers whether the development language, database, etc. used when developing the salary management system is feasible. This salary management system chooses JAVA as the language, and uses the Springboot framework and MYSQL database. These technologies are currently very mature. Moreover, the JAVA language not only supports process-oriented, but also supports object-oriented, so it will be more flexible when used, and there is no problem in technology selection.
The main considerations for economic feasibility are cost and benefit. From a cost perspective, JAVA, Springboot, MYSQL, Photoshop, etc. used in the development process can be downloaded through online searches without any fees. The cost of development is almost non-existent; from In terms of benefits, the completion of the payroll management system can provide support for corporate payroll management, reduce corporate costs, and improve management efficiency, so there is no problem economically.
The main legal consideration is whether the development of the system is illegal. The salary management system developed strictly complies with the "Computer Software Protection Regulations of the People's Republic of China", the "Copyright Law of the People's Republic of China" and other laws and regulations. The development of the system can bring benefits to the enterprise. There is no illegality and therefore it is legally possible.
In terms of operation, the main consideration is whether it is simple and feasible for users to use and for managers to manage. Whether users without any computer foundation can use it. The developed salary management system is designed with the concept of being simple and easy to learn. When users enter the system There will be fixed navigation buttons at the end, and the operation can be completed as long as you can read the words. In addition, the administrator only needs to add, delete, modify and check the management, so it is feasible in operation.
Generally speaking, the developed payroll management system has no problem in terms of feasibility and is worthy of development, and other completions are of great significance to the development of the enterprise.
The development of the salary management system is mainly to solve the problems of both hands, improve efficiency, and contribute to the development of the enterprise. Therefore, in terms of system functions, we must first proceed from the perspective of enterprise management, and then proceed from the perspective of employees to ensure that each user can be satisfied. Therefore, in terms of functions, it mainly plans the administrators and employees of the enterprise, and realizes the major functions of login, administrator, employee user, salary information, attendance information, and position management.
(1) Login: The administrator's account is designed directly in the database. The administrator can directly enter the username + password when entering the system's login interface, and then after completing the puzzle sliding verification, click "Login" to log in. The employee's account It is added directly by the administrator. Employees can also log in through the user name and password, and then complete the puzzle sliding verification.
(2) Home page: After the administrator succeeds, he will view the salary information statistics and attendance information statistics in the system in the form of analysis charts on the home page interface;
(3) Administrator: The administrator clicks the "System User" menu and orders the "Administrator" button to view the enterprise's administrator users. If you want to fill in a new administrator, click the "Add" button on the right and enter Click the "Submit" button to submit account, password and other information. It also supports editing, deleting and querying existing administrators;
(4) Employee users: The administrator clicks the "System Users" menu and orders the "Employee Users" button to view all employee users of the company. If you want to fill in a new employee, click the "Add" button on the right and enter the account number , password, nickname, mobile phone number, email and other information, click the "Submit" button to submit. It also supports editing, deleting and querying existing employees;
(5) Salary information: The administrator clicks the "Module Management" menu and orders the "Salary Information" button to view the salary information of all employees of the company. If you want to fill in a new salary, click the "Add" button on the right, and then Select an employee, enter the employee's name, basic salary, salary explanation, fine amount, actual salary, and salary time information, and click the "Submit" button to submit. It also supports editing, deleting, and querying existing salary information; employees You can view your salary information by calling the "Salary Information" button.
(6) Attendance information: The administrator clicks the "Module Management" menu and orders the "Attendance Information" button to view the attendance information of all employees of the enterprise. If you want to fill in new attendance information, click the "Add" button on the right. Then select the employee, enter the employee's name, attendance date, attendance status, attendance notes, workload and other information, and click the "Submit" button to submit. It also supports editing, deletion and query of the existing attendance information; the employee's phone number is "Attendance" Information" button to view your own attendance information.
(7) Position management: The administrator clicks the "Module Management" menu and orders the "Position Management" button to view all positions in the company. If you want to fill in new position information, click the "Add" button on the right, and then enter the position Number, position name, position category, recruitment position, academic requirements, professional requirements and other information, click the "Submit" button to submit. It also supports editing, deletion and query of existing position information.
(8) Personal information: Administrators and employees can update their personal avatar, nickname, mobile phone number and other information by clicking the "Personal Information" button.
(9) Change password: Administrators and employees can change the login password by clicking the "Change Password" button. First enter the original password, then enter the new password and confirm the password. When the original password is correct, enter the new password twice and it will be consistent. If the modification is successful, otherwise an error message will be given.
The performance requirements analysis of the payroll management system mainly analyzes the security of the payroll management system (whether it will leak employees' personal information), the reliability (whether the user can display information based on actual operations when operating), and the performance. How is it (whether the operation is smooth), how is the scalability (can the functions continue to be expanded), etc. The details can be expressed in the following 2.1 table:
Table2.1 Non-functional requirements table for payroll management system
| safety |
Mainly refers tothe installation of the payroll management system database. The use of the database and the password setting must comply with the standards. |
| reliability |
Reliability means thatthe payroll management system can operate according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for affectingpayroll management 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 ofSalary Management System and they will be fine. |
| maintainability |
Salary management systemThe maintainability of development is very important. After testing, there is no problem with maintainability |
The employee role functions in the payroll management system include login, salary information, attendance information, personal information, password modification, and exit. The employee use case diagram is shown in Figure 2.1:
Figure 2.1 Employee role use case diagram
The administrator role function in the salary management system includes the functions of login, administrator, employee user, salary information, attendance information, position management, personal information, password change, and exit. The use case diagram of the administrator is shown in Figure 2.2:
Figure 2.2 Administrator role use case diagram
All users (administrators and employees) in the system can add data. Figure 2.3 shows the process of adding data.
Figure 2.3 Add data flow chart
No one is perfect, everyone makes mistakes sometimes. If the information is wrong when entering the system information, you can edit the data in the system. Figure 2.4 shows the process of modifying data.
Figure 2.4 Modify data flow chart
Some expired data often appear in the system, such as employee resignations, etc. Then these data can be deleted directly. Figure 2.5 is the flow chart when deleting data.
Figure 2.5 Deletion data flow chart
After analyzing the feasibility and functions of the system, the next step is to design the system specifically. Through feasibility analysis, we conclude that the system is worth developing. Through functional analysis, we can determine what functions the system has specifically implemented, and then complete it according to the functional requirements. This chapter introduces the functional design of the system from two aspects: functional modules and the database of the system.
Through the functional requirements analysis in the previous chapter, the functional structure diagram of this salary management system can be obtained. Figure 3.1 is the functional module diagram of the salary management system.
Figure 3.1 Function module diagram of salary management system
The design of the database is the foundation of a system. No matter what the system is, no matter how beautiful the interface design is, if it is not supported by a powerful database, it will not be able to run. When designing the database, we first analyze the database and then develop a conceptual model. Design, and finally create database tables, as shown below.
When designing the database conceptual model, the E-R entity diagram is generally used for display. The entity diagram can display all the field names in the database table. The main database E-R model diagram in this payroll management system is shown in the figure below.
Figure 3.2 Attendance information E-R relationship diagram
Figure 3.3 Employee information E-R relationship diagram
Figure 3.4 Position information E-R relationship diagram
Figure 3.5 Salary information E-R relationship diagram
Figure 3.6 User information E-R relationship diagram
In the database table, we will see the system's table name, primary key, foreign key and other information. We associate each table through the primary key and foreign key of the database table, and then display it in the interface. The main database of this payroll management system The table is as follows:
(1) The table check_work_attendance attendance information entity is used to store the attendance information submitted by the administrator. The fields include attendance personnel, employee names, attendance dates, attendance status, attendance notes, workload, etc. Users can view their own attendance information;
Table 3.1 Attendance information check_work_attendance table
| List |
type of data |
length |
Is it available? |
Comment |
| check_work_attendance_id |
int |
10 |
no |
Attendance information ID |
| attendance_personnel |
int |
10 |
yes |
Attendance staff |
| employee_name |
varchar |
64 |
yes |
employee's name |
| attendance_date |
date |
10 |
yes |
Attendance date |
| attendance_status |
varchar |
64 |
yes |
Attendance status |
| attendance_remarks |
text |
65535 |
yes |
Attendance notes |
| workload |
int |
10 |
yes |
workload |
| recommend |
int |
10 |
yes |
Intelligent Recommendation |
| create_time |
datetime |
19 |
yes |
creation time |
| update_time |
timestamp |
19 |
yes |
Update time |
(2) The table employee_user employee entity is used to store employee information added by the administrator. Employees can log in through their account number and password;
Table 3.2 Employee information employee_user table
| List |
type of data |
length |
Is it available? |
Comment |
| employee_user_id |
int |
10 |
no |
Employee User ID |
| employee_name |
varchar |
64 |
yes |
employee's name |
| employee_gender |
varchar |
64 |
yes |
Employee gender |
| employee_age |
int |
10 |
yes |
Employee age |
| employee_department |
varchar |
64 |
yes |
Staff department |
| examine_state |
varchar |
16 |
yes |
Approval Status |
| recommend |
int |
10 |
yes |
Intelligent Recommendation |
| user_id |
int |
10 |
yes |
User ID |
| create_time |
datetime |
19 |
yes |
creation time |
| update_time |
timestamp |
19 |
yes |
Update time |
(3) The table post_management position management entity is used to store position information added by the administrator. The fields include position number, position name, position category, recruitment position, academic requirements, professional requirements, experience requirements, etc.;
Table 3.3 Post management post_management table
| List |
type of data |
length |
Is it available? |
Comment |
| post_management_id |
int |
10 |
no |
Position management ID |
| post_no |
varchar |
64 |
Position number |
|
| position_name |
varchar |
64 |
Position Title |
|
| position_category |
varchar |
64 |
yes |
Job category |
| recruitment_position |
varchar |
64 |
yes |
Recruitment positions |
| educational_requirements |
varchar |
64 |
yes |
Academic requirements |
| professional_requirements |
varchar |
64 |
yes |
Professional requirements |
| experience_requirements |
varchar |
64 |
yes |
Experience required |
| number_of_posts |
varchar |
64 |
yes |
Number of positions |
| work_location |
varchar |
64 |
yes |
work place |
| position_details |
text |
65535 |
yes |
Job details |
| recommend |
int |
10 |
yes |
Intelligent Recommendation |
| create_time |
datetime |
19 |
yes |
creation time |
| update_time |
timestamp |
19 |
yes |
Update time |
(4) The table salary_information salary entity is used to store the salary information added by the administrator in the system so that employees can view their own salaries;
Table 3.4 Salary information salary_information table
| List |
type of data |
length |
Is it available? |
Comment |
| salary_information_id |
int |
10 |
no |
Salary information ID |
| employee_user |
int |
10 |
yes |
employee user |
| employee_name |
varchar |
64 |
yes |
employee's name |
| base_pay |
varchar |
64 |
yes |
Basic wage |
| salary_bonus |
varchar |
64 |
yes |
salary bonus |
| amount_of_penalty |
varchar |
64 |
yes |
penalty |
| net_salary |
varchar |
64 |
yes |
actual wages |
| pay_time |
date |
10 |
yes |
pay time |
| recommend |
int |
10 |
yes |
Intelligent Recommendation |
| create_time |
datetime |
19 |
yes |
creation time |
| update_time |
timestamp |
19 |
yes |
Update time |
(5) The table user user entity is used to store the user ID, account status, user group, last login time, mobile phone number, mobile phone authentication, etc. added by the administrator for administrators and employees to log in;
Table 3.5 User information user table
| List |
type of data |
length |
Is it available? |
Comment |
| user_id |
mediumint |
8 |
no |
User ID |
| state |
smallint |
5 |
yes |
Account Status |
| user_group |
varchar |
32 |
yes |
User group |
| login_time |
timestamp |
19 |
yes |
Last Login Time |
| phone |
varchar |
11 |
yes |
phone number |
| phone_state |
smallint |
5 |
yes |
Mobile phone authentication |
| username |
varchar |
16 |
yes |
username |
| nickname |
varchar |
16 |
yes |
Nick name |
| password |
varchar |
64 |
yes |
password |
| |
varchar |
64 |
yes |
|
| email_state |
smallint |
5 |
yes |
Email authentication |
| avatar |
varchar |
255 |
yes |
Avatar address |
| create_time |
timestamp |
19 |
yes |
creation time |
- Chapter 4 Design and Implementation of Key Modules
- RegisterInterface
The administrator's account is directly designed in the database. When the administrator enters the login interface of the system, he can directly enter the user name + password, and then after completing the puzzle sliding verification, click "Login" to log in. The employee's account is directly provided by the administrator. If added, employees can also log in through username and password, and then complete the puzzle sliding verification; the main interface is shown in Figure 4.1 below.
Figure 4.1 Login interface diagram
After the administrator succeeds, he will view the salary information statistics and attendance information statistics in the system in the form of analysis charts on the homepage interface. The interface is shown in Figure 4.2 below.
Figure 4.2 Home page interface diagram
The administrator clicks the "System User" menu and clicks the "Administrator" button to view the enterprise's administrator users. If you want to fill in a new administrator, click the "Add" button on the right, and then enter the account number, password and other information. Click the "Submit" button to submit. It also supports editing, deleting and querying existing administrators. The interface is shown in Figure 4.3 below.
Figure 4.3 Administrator interface diagram
The administrator clicks the "System User" menu and orders the "Employee User" button to view all employee users of the enterprise. If you want to fill in a new employee, click the "Add" button on the right, and then enter the account number, password, nickname, and mobile phone Number, email and other information, click the "Submit" button to submit. It also supports editing, deleting and querying existing employees. The employee user interface is shown in Figure 4.4 below, and the employee user management interface is shown in Figure 4.5 below.
Figure 4.4 Add employee user interface diagram
Figure 4.5 Employee user interface diagram
The administrator clicks the "Module Management" menu and orders the "Salary Information" button to view the salary information of all employees of the company. If you want to fill in a new salary, click the "Add" button on the right, then select the employee and enter the employee's name. , basic salary, salary explanation, fine amount, actual salary, salary time information, click the "Submit" button to submit. It also supports editing, deletion and query of existing salary information; employee phone "Salary Information" button You can view your salary information. The salary information interface is shown in Figure 4.6 and Figure 4.7 below.
Figure 4.6 Salary information interface diagram (administrator)
Figure 4.7 Salary information interface diagram (employees)
The administrator clicks the "Module Management" menu and orders the "Attendance Information" button to view the attendance information of all employees of the enterprise. If you want to fill in new attendance information, click the "Add" button on the right, then select the employee and enter the employee Click the "Submit" button to submit information such as name, attendance date, attendance status, attendance notes, and workload. It also supports editing, deletion, and query of existing attendance information; employees can view their own information by calling the "Attendance Information" button Attendance information. The attendance information interface is shown in Figure 4.8 and Figure 4.9 below.
Figure 4.8 Attendance information interface diagram (administrator)
Figure 4.9 Attendance information interface diagram (employee)
The administrator clicks the "Module Management" menu and orders the "Position Management" button to view all positions in the company. If he wants to fill in new position information, click the "Add" button on the right, and then enter the position number, position name, and position Click the "Submit" button to submit information such as categories, recruitment positions, academic requirements, professional requirements, etc. It also supports editing, deleting and querying existing position information. The position management interface is shown in Figure 4.10 below.
Figure 4.10 Position management interface diagram
Administrators and employees can click the "Personal Information" button to update their personal avatar, nickname, mobile phone number and other information; the personal information interface is shown in Figure 4.11 below.
Figure 4.11 Personal information interface diagram
Administrators and employees can click the "Change Password" button to change the login password. First enter the original password, then enter the new password and confirm the password. When the original password is correct and the new password is consistent after entering it twice, the change is successful. Otherwise, An error message appears. The password modification interface is shown in Figure 4.12 below.
Figure 4.12 Password modification interface diagram
At this point, the development of the system is basically completed. Next, we analyze the system's experiments and results to ensure that the system can operate normally and then be put into use. The detection method for the system's experiments and result analysis is to test the system. Testing is the system In the last step of completion, the system that has not been tested cannot be put into use, otherwise it will cause losses if a bug occurs. Below we analyze the testing method and the test use cases, and finally give the system test results.
There are two types of system testing, one is black box testing and the other is white box testing. Black box testing is generally called functional testing. We also call it requirements testing. In the process of black box testing In , we don’t know its development principle. We are just testing the system as a user. We mainly rely on our previous testing experience to take some critical values and then test them through test cases. This testing method It is the fastest way to find problems. Secondly, we can find some representative data and conduct use case testing on the system. The commonly used testing tools in the black box testing process are winrunner and AutoRunner; white box testing is called result testing. , that is, logic-driven testing. In the process of white-box testing, we mainly test based on the principles of system development. We mainly test as a developer whether the code has completed its specific functions and the specific implementation. Is the path correct? Of course, this testing method is time-consuming and laborious, because each function has more than one running path. By testing the running path in the program, we can detect whether there are bugs in the developed code and whether it has achieved expectations. Commonly used testing tools during white-box testing are Jcontract, C++ Test, and CodeWizard.
Functional test of login module:
Table 5.1 Login module function test table
| test name |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 登录模块测试 |
登录成功的情况 |
使用者可以通过浏览器进入到工资管理系统登录界面，输入用户名：admin和密码admin，完成滑动拼图验证后，点击“登录”按钮。 |
成功登录到管理员管理的界面 |
正确 |
| 登录模块测试 |
登录失败的情况 |
使用者可以通过浏览器进入到工资管理系统登录界面，输入用户名：admin和密码111，完成滑动拼图验证后，点击“登录”按钮。 |
系统提示“用户名和密码不匹配” |
正确 |
员工用户信息添加功能测试：
表5.2 员工用户信息添加功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 员工用户添加模块测试 |
员工用户添加成功的情况 |
管理员在“系统用户”菜单中点击“员工用户”会显示出所有的员工用户信息，点击“添加”按钮，输入账号、密码、昵称、手机号码、邮箱等，输入正确的信息后，点击“提交”按钮。 |
提示添加成功 |
正确 |
| 员工用户添加模块测试 |
员工用户添加失败的情况 |
管理员在“系统用户”菜单中点击“员工用户”会显示出所有的员工用户信息，点击“添加”按钮，不输入账号，其他信息正常填写后，点击“提交”按钮。 |
提示“添加失败，账号不能为空” |
正确 |
查询考勤信息功能模块测试：
表5.3 查询考勤信息功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 查询考勤信息功能测试 |
查询成功的情况 |
员工在菜单栏中点击“考勤信息”，然后互出现自己的考勤信息 |
查询成功 |
正确 |
工资信息添加功能模块测试：
表5.4 添加工资信息功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 工资信息添加模块测试 |
工资信息添加成功的情况 |
管理员在“模块管理”菜单中点击“工资信息”会显示出所有的员工的工资信息，点击“添加”按钮，选择员工，输入员工姓名、基本工资、工资讲解、罚款金额、实发工资、发薪时间信息，输入正确的信息后，点击“提交”按钮。 |
提示添加成功 |
正确 |
| 工资信息添加模块测试 |
工资信息添加失败的情况 |
管理员在“模块管理”菜单中点击“工资信息”会显示出所有的员工的工资信息，点击“添加”按钮，不选择员工，其他信息正常填写后，点击“提交”按钮。 |
提示“添加失败，员工不能为空” |
正确 |
在本章节对工资管理系统进行了黑白盒测试，并对系统中的部分功能进行了用例分析，能够发现系统还是比较稳定的，系统的所有功能基本可以实现，能够满足管理员和员工对工资信息的查询、管理的需求。通过测试可以看出在系统的运行过程中，其功能完整，对于输入的错误信息，能够把错误信息提示出来，方便用户操作的时候发现自己输入的信息哪里有错误，进而进行改正，而且系统界面都设有导航栏，操作非常便捷，不需要对使用者进行任何培训，对于企业来说是一个很有价值的系统。
经过了几个月的努力，本工资管理系统终于完成了，虽然在校期间也开发过一些小型的系统，但是都是在老师的讲解以及辅助下完成的，没有经历过开发之前的需求分析、系统分析，都是直接从系统设计开始的，因此本次开发的工资管理系统对我意义重大。
在开发系统最初，首先对各个企业工资管理方面的需求进行调研，了解对于企业来说，开发的系统需要实现哪些功能才能满足企业的管理需求，对需求进行分析；其次选择自己比较熟悉的JAVA语言，MYSQL数据库，使用Springboot框架来设计开发，通过知网库、学校图书馆等地方查阅、学习这些技术，掌握编程的思想和方法，然后就是对系统进行分析，从系统开发的可行性、系统实现的功能、系统应该具备的性能以及系统的操作流程方面，对系统进行全方位的分析，确定系统的最终功能，从而对系统的功能和数据库进行设计，最后就是系统的实现以及对实现的功能的测试，确保系统能够稳定的运行。
在开发的过程中暴露出了自己的很多问题，比如前期的准备还是不够充分，不能完全掌握其操作流程；在开发过程中对JAVA的编程掌握的还不够熟练以及对系统的环境配置上还存在很多问题，经常会导致项目在运行的时候出现错误。学无止境，通过一边查阅资料一边向导师请教，慢慢的解决了这些问题，在以后的学习、工作者我会更加严谨，通过本项目的开发，我将会收益终生！
参考文献
[1]李萱然. 高校人事工资管理系统的优化与实现[J]. 2021.
[2]李兆琪. 基于MySQL数据库服务器创建企业工资管理系统[J]. 赤峰学院学报:自然科学版, 2021, 37(11):2.
[3]杨真懿. 探究人事与工资管理系统在工作中的运用[J]. 前卫, 2022(14):3.
[4]王丹丹, 杨飞亮. 工资管理系统的设计[J]. 沧州师范学院学报, 2022(1).
[5]凌择马. 计算机软件开发中JAVA编程语言及其实际应用研究[J]. 智能城市应用, 2021, 4(3):94.
[6]王昊欣, 姜学东. JAVA编程语言在计算机软件开发中的应用[J]. 电子技术与软件工程, 2022(1):4.
[7]李雅琴. Java编程语言的优势及其应用实践研究[J]. 互联网周刊, 2021, 000(024):60-62.
[8]张泽陆. 计算机软件开发技术在JAVA编程语言的应用[J]. 工程技术发展, 2022, 3(5):78-80.
[9]蒋治学.JSP技术及其在动态网页开发中的应用分析[J].浙江水利水电学院学报,2020,32(02):75-77.
[10]刘小飞,李明杰.基于JSP和Servlet架构的新闻频道系统[J].电脑知识与技术,2020,16(12):82-83.
[11]曾晰，舒坚。基于JSP的养老院管理信息系统的设计与实现[J].信息通信，2019,（09）：122-124.
[12]费扬，杜庆治。基于JSP的大学城外卖网的设计与实现[J].软件，2020,38（07）：92-96.
[13]潘杨占胜.JSP中文乱码问题的探讨与解决方法[J].福建电脑,2020,36(04):36-41.
[14]翁春荣. 浅谈JSP的网络数据库连接技术及运用[J]. 网络安全技术与应用, 2021, 000(008):51-52.
[15]欧阳桂秀. 基于Java和MySQL的数据库管理系统的设计与实现[J]. 信息记录材料, 2022, 23(9):3.
[16] Huang J . Online Booking Laboratory Management System[J]. Springer, Cham, 2021.
[17]Pande M . Impact Of Covid 19 On Java Web Frameworks Software Market Effects, Aftermath And Forecast To 2026. 2021.
[18]Dusan Teodorovic,Panta Ludc.An intelligent driver location system for smart parking[J].The MISSuper Strategies Conference, 2020: 26-29.
[19] Gwenael Le Bodic. Mobile messaging technologies and services SMS EMS and MMS .New York: J.Wiley, 2020.
致 谢
“致谢”意味着论文的结束，也意味着自己的毕业设计顺利完成，同时也代表了自己的大学生涯即将结束，我即将要离开自己敬爱的老师和亲爱的同学们，在这里我首先要感谢的就是所有的老师，“春满江山绿满园，桃李争春露笑颜，东西南北春常在，唯有师恩留心间”，他们无论在我的学业还是在我的生活上付出了所有，对我谆谆教诲；其次我要感谢我的指导老师，他在我的整个毕业设计当中起着引导作用，每当我有困难的时候，他总会第一时间帮助我，引导我进行解决问题，而不是直接告诉我答案，“授人以鱼不如授人以渔”，指导老师的这种做法让我受益终生，同时我也从指导老师身上学习到了许多的开发技巧以及检验，这对我今后的开发起着十分重要的作用；再次，我需要感谢我的同学、室友，他们不仅仅在毕业设计上给我许多帮助意见，在大学同窗四年，他们给过我的帮助太多了，我对他们有太多的不舍，无法用言语表示，我相信在以后的人生道路上只要想到他们，我心里就会很温暖，这种友情是任何感情替代不了的；最后我还要感谢家人，感谢自己，感谢家人对我的支持，感谢自己在学业上的坚持，我相信我以后的道路会越来越好。
免费领取项目源码，请关注点赞+私聊