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. For vehicle management system and other issues, conduct research and analysis on the vehicle management system, and then develop and design the vehicle management system to solve the problem.
The main functional modules of the vehicle management system include system user (administrator, ordinary user) module management (vehicle files, charging information, entry and exit charges, vehicle violations, vehicle maintenance), and adopts an object-oriented development model for software development and hardware development. The setup can well meet the needs of actual use, and has improved the corresponding software setup and program coding work. Mysql is used as the main storage unit of background data, and the SSM framework and Java technology are used to code and develop the business system. All functions of this system have been realized. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyzing various requirements and technical issues of the vehicle management system, proving the necessity and technical feasibility of the system, and then giving a basic introduction to the technical software and design ideas that need to be used to design the system, and finally implementing the vehicle management system and Deployment runs using it.
Keywords: vehicle management system; Java; SSM; MYSQL
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. Conduct research and analysis on vehicle management systems and other issues, and then develop and design a vehicle management system to solve the problem.
The main functional modules of the vehicle management system include system user (administrator, ordinary user) module management (vehicle files, fee information, access fees, vehicle violations, vehicle maintenance), adopting an object-oriented development model for software development and hardware installation, which can well meet the actual needs of use, improve the corresponding software installation and program coding work, Adopting MySQL as the main storage unit for backend data, adopting SSM framework, Java technology, coding and development of business systems, 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 vehicle management system, prove the necessity and technical 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 vehicle management system and deploy it for operation.
Keywords:Vehicle management system; Java； SSM； MYSQL
1.1 Research background and significance
1. 3 Introduction to ssm framework
1. 4 Thesis structure arrangement
Chapter 2 Requirements Analysis of Vehicle Management System
2.1 System feasibility analysis
2.1.1 Technical feasibility analysis
2.1.2 Economic feasibility analysis
2.1.3 Operation feasibility analysis
2.2 System requirements analysis
2.2.1 Functional requirements analysis
2.2.2 Non-functional requirements analysis
Chapter 3 Overall Design of Vehicle Management System
3.1 System function module design
3.2.1 Database conceptual structure design
3.2.2 Database logical structure design
Chapter 4 Design and Implementation of Key Modules 1 7
4. 2 Personal information module
4. 4 System user management module
4. 6 Charge information module
4. 7 entrance and exit charging module
4. 8 Vehicle Maintenance Module
The vehicle management system is the management and deployment of the human, financial, material and other resources involved. With the rapid development of the transportation industry, it has brought great convenience to people's lives. At the same time, various transportation tools In particular, the sharp increase in the number of cars has brought increasingly serious and huge pressure to all aspects of society. For vehicle management within various institutions or corporate units, traditional manual operation methods are gradually unable to meet the current needs of vehicle management due to low efficiency and high error rate due to heavy workload and high intensity. Based on the characteristics of the project needs, focusing on improving vehicle use and management, and combining the characteristics of the vehicles themselves, the management of passing vehicle dispatching is completed, and the vehicle usage dispatching, vehicle information and related personnel information management, usage records, accidents and other information are unified managed. Further improve vehicle management, usage efficiency and safety guarantee, ensure that vehicle status is documented and evidence-based, and realize scientific and automated management of vehicles.
In intelligent management, enterprise vehicle management has become one of the urgent problems to be solved. The arrival of the era of rapid economic development has brought opportunities to the development of enterprises, but at the same time, more and more workloads require the use of more vehicles to facilitate work, which has brought huge pressure to the vehicle management of enterprises. Enterprises must Reasonably arrange the vehicle usage of various subordinate departments and provide real-time vehicle information. Only by doing this can the enterprise run better and maximize the overall work efficiency of the enterprise.
-
- development significance
The vehicle management system is an information management system and a small database system. The vehicle management system integrates knowledge in the vehicle operation field, vehicle management field, database field and other aspects.
Due to the complexity of vehicle information and the numerous procedures of the management system, manual file management in the past is no longer suitable. There are many shortcomings in the file management method: a large amount of information is easy to be lost, ignored, and forgotten; the redundancy of information is extremely large; the security is extremely poor; it is difficult to find; the workload is heavy and the staff is tired.
Vehicle management software replaces manual file management and can avoid or greatly alleviate the above problems. Moreover, computer management has some irreplaceable advantages: some information that needed to be memorized in the past, such as the term of vehicle insurance or the age of the vehicle, can now be queried and managed using computer software; with the popularity of computers, it can also be retrieved at any time Work anywhere, company leaders can also search for required information and check work at home or other places; large storage capacity; good confidentiality; long life, etc. The work efficiency of the enterprise has improved, management has become more convenient, and it will gradually move towards formalization.
-
- Introduction to Ssm 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.
-
- Thesis structure arrangement
The paper will be arranged hierarchically. In addition to the abstract, table of contents, acknowledgments, and literature reference sections, the main text will also analyze the website requirements, elaborate on the general design and implemented functions, and finally list some commissioning records. The paper mainly The architecture is as follows:
Chapter 1 explains the background of the project and the practical significance of development.
Chapter 2 analyzes the feasibility and functional requirements of this system.
Chapter 3 explains the overall design of the project.
Chapter 4 clarifies the implementation of the detailed functions of the vehicle management system, mainly based on the technical functional module functions.
Chapter 5 lists some system debugging and testing records.
Chapter 6 presents the conclusions of the vehicle management system.
The vehicle management system uses the MySQL database for storage and development tools such as IDEA and Tomcat for development, which can bring a lot of convenience to our writing work. The system is developed using the SSM framework, which makes the system more scalable and maintainable, reduces Java configuration code, and simplifies programming code. Currently, the SSM framework is also one of the frameworks chosen by many enterprises.
The development software used in developing the vehicle management system, such as IDEA development tools, Tomcat8.0 server, MySQL5.7 database, Photoshop image processing software, etc., are all open source and free. These environments have been studied systematically in school. You can operate it independently without any additional cost, and the system development tools can be downloaded directly from the Internet, so it is economically feasible.
When designing this project, I referred to many successful cases of similar systems, systematically analyzed their operation interfaces and functions, and combined many cases together to highlight people-oriented and simplified operations, so people with basic computer knowledge can Operate this project. Therefore, there is no problem with operational feasibility.
The design and implementation of the Java-based vehicle management system is to allow users to more conveniently manage some information related to insurance claims . Users can save a lot of time and energy when searching and managing, and effectively reduce unnecessary searches. time. The system is functionally divided into two parts: the ordinary user terminal and the administrator terminal .
System client:
(1) Personal information: Users can update their personal avatar, nickname, mobile phone number and other information by clicking the "Personal Information" button.
(2) Change password: The user clicks 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 twice, the change is successful. , otherwise an error message will be given.
(3) Vehicle file: Click the "Vehicle File" menu to view all vehicle file information in the system. It supports querying vehicle file information through ordinary users or user names. If you want to know the detailed information of a certain vehicle file , click "Details" at the back to enter the details interface;
(4) Charging information: Click on the "Charging Information" menu to view the charging information submitted by yourself. It supports querying the charging information through the charging number or charging title. If you want to know the details of a certain charging information, click on the following "View" will enter the details interface;
(5) Access charges: Click the "Access charges" menu to view all access charges information in the system. It supports querying access charges information through vehicle number or license plate number. If you want to know the detailed information of a certain access charge , click "Details" at the back to enter the details interface;
(6) Vehicle Violation: Click the "Vehicle Violation" menu to view all vehicle violation information in the system. It supports querying vehicle violation information by vehicle model or violation behavior. If you want to know the detailed information of a certain vehicle violation , click "Details" at the back to enter the details interface;
Administrator side:
(1) Login: The administrator can log in through the account and password in the background. The administrator's account and password are set directly in the database. If you forget the password, you can click "Forgot Password" to retrieve the password;
(2) Personal information: The administrator clicks the "Personal Information" button to update the individual's avatar, nickname, mobile phone number and other information.
(3) Modify password: The administrator clicks the "Modify 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, modify it. Successful, otherwise an error message will be given.
(4) System users: Administrators can manage and control all user roles in the system, including administrators and ordinary users. If you need to add a new user, click the "Add" button on the page and enter the above information according to the prompts. User information can be viewed in the corresponding user interface after clicking "Submit". You can click the "Delete" button behind the user to directly delete a user.
(5) Vehicle files: The administrator clicks "Vehicle Files" to display all vehicle files. It supports inputting the vehicle number or license plate number to query the vehicle files. If you want to add a new vehicle file, click the "Add" button and enter Related information can be added by clicking the "Submit" button. At the same time, you can select a certain vehicle file and click "Delete" to delete it. You can also click the "Access Charges", "Vehicle Violation", and "Vehicle Maintenance" buttons at the back to edit the vehicle file. Update and maintain vehicle violation/vehicle maintenance information;
(6) Charging information: The administrator clicks "Charging Information" to display all charging information. It supports querying the charging information through the charging number or charging title. If you want to add new charging information, click the "Add" button and enter Related information can be added by clicking the "Submit" button. At the same time, you can select a certain piece of charging information and click "Delete" to delete it.
(7) Access charges: Click the "Access charges" menu to view all access charges information added in the system. It supports querying access charges information through ordinary users or user names. If you want to add new access charges, click "Add" button, enter the access fee information according to the prompts, click the "Submit" button, the new access fee information will be displayed in the system, and the added access fee information can also be deleted;
(8) Vehicle maintenance: Click the "Vehicle Maintenance" menu to view all vehicle maintenance information added in the system. It supports querying vehicle maintenance information through ordinary users or user names. If you want to add new vehicle maintenance, click "Add" button, enter the vehicle maintenance information according to the prompts, click the "Submit" button, the new vehicle maintenance information will be displayed in the system, and the added vehicle maintenance information can also be deleted;
The non-functional requirements of the vehicle management system include the safety, reliability, performance, scalability, etc. of the self-service vehicle management system . The details can be expressed in the following 3-1 table:
Table 2.1 Vehicle management system non-functional requirements table
| safety |
Mainly refers to the installation of the vehicle management system database, the use of the database and the setting of passwords must comply with regulations. |
| reliability |
Reliability means that the vehicle management system can operate according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for vehicle management systems 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 vehicle management system and operate. |
| maintainability |
The maintainability of vehicle management system development is very important. After testing, there is no problem with maintainability. |
The use case diagram of ordinary user roles in the vehicle management system is shown in Figure 2.1:
Figure 2.1 Common user role use case diagram
The use case diagram of the administrator role in the vehicle management system is shown in Figure 2.2 :
Figure 2.2 Administrator role use case diagram
After analyzing the background, significance and feasibility of project development, the next step is to discuss the functional division of the project and the design of various tables in the project database during specific implementation. In this chapter, a systematic introduction will be made.
The design of the functional module is to create a system architecture based on the specific functions that the system is to implement and how the functions are divided. It is displayed in the form of a module diagram to facilitate us to list and involve the functions . In terms of system functions, the project is divided into two modules: administrator + system user . Each module logs in and corresponds to the corresponding function. The specific function module diagram is shown in Figure 3.1.
Figure 3.1 Function module diagram of vehicle management system
The design of the database carries various data of the system. In a system, all kinds of data require a special container. The database is this container. When establishing the database, it mainly consists of two parts: the design of the database model and the design of each database table. .
The following is the ER entity relationship diagram of the main database tables in the entire vehicle management system.
Figure 3.2 Overall ER relationship diagram of vehicle management system
From the previous ER diagram, you can see that the project requires the creation of many data tables. The following is the relational model of the main database tables in the project:
Table charging_information (charging information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
charging_information_id |
int |
10 |
0 |
N |
Y |
Charge information ID |
|
| 2 |
charge_number |
varchar |
64 |
0 |
Y |
N |
Charge number |
|
| 3 |
charge_title |
varchar |
64 |
0 |
Y |
N |
Charge title |
|
| 4 |
charging_standards |
varchar |
64 |
0 |
Y |
N |
Charges |
|
| 5 |
creator |
varchar |
64 |
0 |
Y |
N |
framer |
|
| 6 |
fee_description |
text |
65535 |
0 |
Y |
N |
Charge description |
|
| 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 entry_and_exit_fees (exit and exit fees)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
entry_and_exit_fees_id |
int |
10 |
0 |
N |
Y |
Entry and exit fee ID |
|
| 2 |
ordinary_users |
int |
10 |
0 |
Y |
N |
0 |
general user |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
vehicle_number |
varchar |
64 |
0 |
Y |
N |
vehicle number |
|
| 5 |
license_plate |
varchar |
64 |
0 |
Y |
N |
License plate number |
|
| 6 |
vehicle_model |
varchar |
64 |
0 |
Y |
N |
Vehicle model |
|
| 7 |
charge_title |
varchar |
64 |
0 |
Y |
N |
Charge title |
|
| 8 |
charging_month |
varchar |
64 |
0 |
Y |
N |
Charge month |
|
| 9 |
charging_standards |
varchar |
64 |
0 |
Y |
N |
Charges |
|
| 10 |
admission_time |
datetime |
19 |
0 |
Y |
N |
Admission time |
|
| 11 |
time_of_appearance |
datetime |
19 |
0 |
Y |
N |
playing time |
|
| 12 |
residence_time |
varchar |
64 |
0 |
Y |
N |
residence time |
|
| 13 |
charging_fees |
varchar |
64 |
0 |
Y |
N |
Fee |
|
| 14 |
fee_type |
varchar |
64 |
0 |
Y |
N |
Charge type |
|
| 15 |
remarks |
text |
65535 |
0 |
Y |
N |
Remarks |
|
| 16 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 17 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 18 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table ordinary_users (ordinary users)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
ordinary_users_id |
int |
10 |
0 |
N |
Y |
Common user ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 3 |
user_gender |
varchar |
64 |
0 |
Y |
N |
User gender |
|
| 4 |
user_age |
varchar |
64 |
0 |
Y |
N |
User age |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 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 vehicle_archives (vehicle archives)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
vehicle_archives_id |
int |
10 |
0 |
N |
Y |
Vehicle file ID |
|
| 2 |
ordinary_users |
int |
10 |
0 |
Y |
N |
0 |
general user |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
user_gender |
varchar |
64 |
0 |
Y |
N |
User gender |
|
| 5 |
users_mobile_phone |
varchar |
64 |
0 |
Y |
N |
User mobile phone |
|
| 6 |
id_number |
varchar |
64 |
0 |
Y |
N |
ID number |
|
| 7 |
distribution_time |
datetime |
19 |
0 |
Y |
N |
Release time |
|
| 8 |
vehicle_number |
varchar |
64 |
0 |
Y |
N |
vehicle number |
|
| 9 |
license_plate |
varchar |
64 |
0 |
Y |
N |
License plate number |
|
| 10 |
vehicle_model |
varchar |
64 |
0 |
Y |
N |
Vehicle model |
|
| 11 |
user_profile |
varchar |
255 |
0 |
Y |
N |
profile picture |
|
| 12 |
remarks |
text |
65535 |
0 |
Y |
N |
Remarks |
|
| 13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table vehicle_maintenance (vehicle maintenance)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
vehicle_maintenance_id |
int |
10 |
0 |
N |
Y |
Vehicle Repair ID |
|
| 2 |
ordinary_users |
int |
10 |
0 |
Y |
N |
0 |
general user |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
vehicle_number |
varchar |
64 |
0 |
Y |
N |
vehicle number |
|
| 5 |
license_plate |
varchar |
64 |
0 |
Y |
N |
License plate number |
|
| 6 |
vehicle_model |
varchar |
64 |
0 |
Y |
N |
Vehicle model |
|
| 7 |
repair_details |
varchar |
64 |
0 |
Y |
N |
Repair details |
|
| 8 |
maintenance_costs |
varchar |
64 |
0 |
Y |
N |
Repair fees |
|
| 9 |
repair_time |
datetime |
19 |
0 |
Y |
N |
Maintenance time |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table vehicle_violation (vehicle violation)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
vehicle_violation_id |
int |
10 |
0 |
N |
Y |
Vehicle Violation ID |
|
| 2 |
ordinary_users |
int |
10 |
0 |
Y |
N |
0 |
general user |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
vehicle_number |
varchar |
64 |
0 |
Y |
N |
vehicle number |
|
| 5 |
license_plate |
varchar |
64 |
0 |
Y |
N |
License plate number |
|
| 6 |
vehicle_model |
varchar |
64 |
0 |
Y |
N |
Vehicle model |
|
| 7 |
violation_of_regulations |
varchar |
64 |
0 |
Y |
N |
Violations |
|
| 8 |
penalty_results |
varchar |
64 |
0 |
Y |
N |
Penalty result |
|
| 9 |
add_time |
datetime |
19 |
0 |
Y |
N |
add time |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
- Chapter 4 Design and Implementation of Key Modules
Administrators and ordinary users enter their account number + password on the login interface and click the "Login" button. The system will match the accounts of the administrator and system users in the user database table. If the account number + password are correct, they will log in to each system user. The user's main management interface, otherwise the corresponding information will be prompted and the user will return to the login interface. The main interface is displayed as shown in Figure 4.1 below.
Figure 4.1 Login interface diagram
The login key code is as follows.
/**
* Log in
* @param data
* @param httpServletRequest
* @return
*/
@PostMapping("login")
public Map<String, Object> login(@RequestBody Map<String, String> data, HttpServletRequest httpServletRequest) {
log.info("[Execute login interface]");
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, "Account or password cannot be empty");
}
if (resultList == null || password == null) {
return error(30000, "Account or password cannot be empty");
}
//Determine whether there is this user
if (resultList.size()<=0){
return error(30000,"User does not exist");
}
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.3所示。
图4.2个人信息界面图
-
- 修改密码模块
管理员和用户点击“修改密码”按钮，可以对登录密码进行更改，首先输入原密码，然后再输入新密码和确认密码，当原密码正确，输入两次新密码一致，则修改成功，否则给出错误提示信息。修改密码界面如下图4.3所示。
图4.3修改密码界面图
-
- 系统用户管理模块
管理员可以对系统中所有的用户角色进行管控，包含了管理员以及普通用户这两种角色，如果需要添加新的用户，点击页面中的“添加”按钮根据提示输入上用户信息，点击“提交”以后在对应的用户界面就可以查看到了，可以点击用户后面的“删除”按钮直接删除某一用户，这里以管理员用户为例。界面如下图4.4所示。
图4.4 系统用户界面图
系统用户关键代码如下所示。
@PostMapping("/set")
@Transactional
public Map<String, Object> set(HttpServletRequest request) throws IOException {
service.update(service.readQuery(request), service.readConfig(request), service.readBody(request.getReader()));
return success(1);
}
-
- 车辆档案模块
点击“车辆档案”会显示出所有的车辆档案信息，支持输入车辆编号或者车牌号码对车辆档案信息进行查询，如果想要添加新的车辆档案信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条车辆档案信息，点击“删除”进行删除，也可以点击后面的“出入收费”“车辆违章”“车辆维修”按钮对车辆档案的出入收费/车辆违章/车辆维修信息进行更新维护。界面如下图4.5所示。
图4.5车辆档案界面图
车辆档案关键代码如下所示。
@RequestMapping("/get_obj")
public Map<String, Object> obj(HttpServletRequest request) {
List resultList = service.selectBaseList(service.select(service.readQuery(request), service.readConfig(request)));
if (resultList.size() > 0) {
JSONObject jsonObject = new JSONObject();
jsonObject.put("obj",resultList.get(0));
return success(jsonObject);
} else {
return success(null);
}
}
-
- 收费信息模块
管理员和用户点击“收费信息”这个按钮可以查看到系统中的收费信息，支持通过收费编号或者收费标题进行查询收费信息，如果想要添加新的收费信息，点击“添加”按钮然后根据提示输入收费信息，点击“提交”后，在收费信息界面就会显示新增的收费信息，可以点击某一收费信息查看收费信息的详情，也可以直接点击“删除”进行删除收费信息。界面如下图4.6所示。
图4.6 收费信息界面图
-
- 出入收费模块
管理员点击“出入收费”会显示出所有的出入收费信息，支持通过普通用户或者用户姓名对出入收费信息进行查询，如果想要添加新的出入收费信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条出入收费信息，点击“删除”进行删除。界面如下图4.7所示。
图4.7出入收费界面图
出入收费逻辑代码如下：
@PostMapping("/set")
@Transactional
public Map<String, Object> set(HttpServletRequest request) throws IOException {
service.update(service.readQuery(request), service.readConfig(request), service.readBody(request.getReader()));
return success(1);
}
-
- 车辆维修模块
管理员点击“车辆维修”会显示出所有的车辆维修信息，支持通过普通用户或者用户姓名对车辆维修信息进行查询，如果想要添加新的车辆维修信息，点击“添加”按钮，输入相关信息，点击“提交”按钮就可以添加了，同时可以选择某一条车辆维修信息，点击“删除”进行删除。界面如下图4.8所示。
图4.8 车辆维修界面图
通过前面章节的介绍，我们可以看到本车辆管理系统已经完成了，但是能不能投入使用还是未知，因为在每个项目正式使用之前必须对开发的项目进行测试，如果不进行测试一旦投入使用可能会出现很多未可知的问题，比如使用人数太多导致系统瘫痪，比如某一功能存在bug信息填写错误等等，这些错误将给使用者带来很多的困扰，甚至造成更大的损失，因此测试是项目投入使用的最后一步，为用户提供一个运行顺畅、完美的项目也就是我们进行最后测试的目的。
用户登录功能测试：
表5.1 用户登录功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 用户登录模块测试 |
用户登录成功的情况 |
点击前登录界面输入账号和密码分别输入admin和admin后点击“登录”按钮。 |
登录成功并调整到用户界面 |
正确 |
车辆维修添加功能测试：
表5.2 车辆维修添加功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 车辆维修添加模块测试 |
车辆维修添加成功的情况 |
在车辆维修的页面中将点击添加，输入维修相关信息，输入正确的信息后然后点击“提交”按钮。 |
提示添加成功 |
正确 |
| 车辆维修添加模块测试 |
车辆维修添加失败的情况 |
在车辆维修页面中不填写的普通用户或者车辆型号，其他信息正常输入“提交”按钮。 |
提示“添加失败，信息不能为空” |
正确 |
查询收费信息功能模块测试：
表5.3 查询收费信息功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 查询通知公告功能测试 |
查询成功的情况 |
在收费信息界面输入普通用户或者收标题进行查询 |
查询成功 |
正确 |
车辆档案添加功能测试：
表5.4 车辆档案添加功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 车辆档案添加模块测试 |
车辆档案添加成功的情况 |
在车辆档案的页面中将点击添加，输入车辆档案相关信息，输入正确的信息后然后点击“提交”按钮。 |
提示添加成功 |
正确 |
| 车辆档案添加模块测试 |
车辆档案添加失败的情况 |
在车辆档案页面中不填写的车辆编号或者车牌号码，其他信息正常输入“提交”按钮。 |
提示“添加失败，信息不能为空” |
正确 |
通过编写车辆管理系统的测试用例，已经检测完毕用户的登录模块、车辆维修添加模块、查询收费信息模块、车辆档案添加模块的功能测试，在对以上功能得测试过程中，发现了系统中的很多漏送并进行了完善，经过多人在线进行测试，系统完全可以正常运行，当然在后期的维护中系统将不断完善。
在开发本车辆管理系统之前我胸有成竹，觉得很简单，但在实际的开发中我发现了自身的很多问题，许多编程思想和方法都还没有掌握牢靠，比如Bootsatrp、Jquery、AJAX 、Spring、SpringMVC、mybeatis等许多Java Web开发技术，通过开发这个车辆管理系统我成长了很多，懂得了做什么事情都要脚踏实地，不能眼高手低，在本次车辆管理系统的开发中我逐渐掌握逐渐熟悉的技术。
本次车辆管理系统的开发中我还学会了例如良好的编程思想和完善的规划思想。在着手编程之前需要罗列出程序框架的大概，脑海中构建出程序的主题框架。做好这一步我们才能胸有成竹的经行开发项目。当设计框架了熟于心之后，需要思考本次编程所需的主要知识点和技术点，并充分学习。如此一来项目的开发才能循序渐进、如丝般顺滑，长久以往就能养成良好的开发习惯。一个程序好不好还要看出的bug多不多，如果在项目完成前做好bug的查验与预防可能发生的事故才能保证程序的稳定长久性运行。如果项目在完工后出现各种问题自己，那么在进入社会后，不仅会给公司团队带来麻烦和增加不必要的工作，还会导致客户流失，公司对自己的评价下降。
在本次项目中我也暴露了诸多问题。对于Java的编程知识有所欠缺，环境配置和算法上出现诸多问题，时常导致项目运行出错，或者目标的实现有问题。或者实现想法时算法未优化，使得代码冗长，程序运行不顺畅。
[1]黎洁霞,甘渐宽,王方会,白玉.基于SSM框架的新型可视化食堂管理系统[J].网络安全技术与应用,2022(08):40-41.
[2]Fu Zhengtang,Dong Peiwu,Ju Yanbing,Gan Zhenkun,Zhu Min. An intelligent green vehicle management system for urban food reliably delivery:A case study of Shanghai, China[J]. Energy,2022,257.
[3]王柯,周祎,纪雯烩.基于SSM框架的IT知识学习交流平台的设计与实现[J].电子制作,2022,30(13):52-57.DOI:10.16589/j.cnki.cn11-3571/tn.2022.13.011.
[4]宋锦华.基于SSM框架的在线教育平台设计与实现[J].电脑编程技巧与维护,2022(05):27-29.DOI:10.16184/j.cnki.comprg.2022.05.048.
[5]殷凤梅,刘冠中.基于SSM框架的网上招聘系统设计与实现[J].长春大学学报,2022,32(04):1-5+62.
[6]彭婷.基于SSM框架的客户关系管理系统的设计与实现[J].信息与电脑(理论版),2022,34(08):137-139.
[7]韩雪娜,李晖.基于RFID技术的食品物流车辆管理系统设计[J].包装与食品机械,2021,39(03):73-77.
[8]程胜.现代车辆管理系统及其维修策略分析[J].时代汽车,2021(12):184-185.
[9]Xinwen Zhang,Siyuan Wen,Rui Wang. Implementation of Vehicle Management System Based on Spring Boot and VUE[C]//.第33届中国控制与决策会议论文集（9）.,2021:519-523.DOI:10.26914/c.cnkihy.2021.028243.
[10]管中华,戚颖.基于人脸识别和RFID技术的智能车辆管理系统[J].科技资讯,2021,19(09):34-38.DOI:10.16661/j.cnki.1672-3791.2104-5042-1225.
[11]史渊源,周辉,于烨,周怡,马国武,吴佳静,马龙.基于Hadoop的车辆管理系统设计与实现[J].湘潭大学学报(自然科学版),2021,43(01):97-106.DOI:10.13715/j.cnki.nsjxu.2021.01.011.
[12]卢玉华,薛斌斌,骆军.车辆管理系统信息安全防护[J].中国科技信息,2020(24):44-45.
[13]Xiaojie Guo,Tingmei Wang*. Design and Implementation of Graduate Information Management System Based on SSM Framework[J]. Journal of Simulation,2020,8(2).
[14]夏琮.车辆管理系统的设计与实现[J].时代汽车,2020(06):18-21.
[15]付召斌,王苹.基于OpenCV的校园车辆管理系统的设计与实现[J].通讯世界,2020,27(02):3-4.
[16]陈欢,陈新泉.基于RFID的小区车辆管理系统设计[J].广西民族大学学报(自然科学版),2020,26(01):82-86.DOI:10.16177/j.cnki.gxmzzk.2020.01.013.
[17]苟坤炎,韩利凯.基于web停车场车辆管理系统的设计与实现[J].电子世界,2019(18):193-194.DOI:10.19353/j.cnki.dzsj.2019.18.105.
[18]韩亮, 智能网联运营车辆管理系统的研究与开发. 四川省,宜宾成电智慧信息系统研究院有限公司,2019-09-26.
[19]梁中阁,徐峰,胡争.基于B/S架构的校园车辆管理系统的设计与实现[J].计算机产品与流通,2019(09):186+212.
[20]Wu Jihong,Wang Junmei,Shi Dongling. Design and Research of University International Cooperation Office Platform Based on SSM Framework[C]//.Proceedings of 2019 International Conference on Virtual Reality and Intelligent Systems (ICVRIS 2019) Volume I.,2019:229-232.DOI:10.26914/c.cnkihy.2019.011418.
致谢
至此论文结束，感谢您的阅读。在此我要特别的感谢我的导师，虽然我在实习期间很忙，论文撰写的时候经常是停停改改，但是我的导师依旧十分的负责，时不时的询问我的任务进展情况，跟进我的论文进度，在指导老师的帮助下，我逐步完成了自己的论文和程序，从导师身上也学习到很多知识和经验，这些知识和经验令我受益匪浅。同时我也从导师身上看到了自己的不足，不论是在技术层面上还是在对待工作的态度上，导师如同明镜一般照出了我的缺点我的不足。此外，我还要感谢在我实习期间在论文和程序上帮助过我的同学和社会人士，此前我对于SSM框架方面的一些知识还不了解，是他们在我编写程序过程中给了我很多的启发和感想，也帮助了我对于程序的调试和检测。没有他们我是不能顺利完成本次毕业设计的。至此，我的毕业设计就花上了一个圆满的句号了。
请关注点赞+私信博主，免费领取项目源码