Note: Show part of the document content and system screenshots. If you need complete videos, codes, articles and installation and debugging environment, please send a private message to the up owner.
3.3Performance demand analysis
Performance ofthissystemfromeach< /span>Analysis;
1. Comprehensive performance analysis:possibleconfirmation designbeginning daigowa calculation,useexpressivekaliteral Format details person =13>targetperfectionsexuality;
2. Whether the system operationcan be analyzed smoothly: each function has the relationship of writing data andThe code corresponding to is analyzed through requirements analysis and feasibility analysis Display the physical data of the system, ensure the smoothness of its system;
3. Analysis of the system’s interface design: The way the software in the system is processed and analyzed isthroughdifferent codes running, canmake thesystem convenient Operation;
4. Analyze the security of the system:Make each role has different corresponding information. Be sure to use your own name when logging in to the system. If you log in with your account and password, if your account and password are incorrect, your login will fail. After successfully logging in you can operate on your owndata but not < /span> system. the security of the ensuresThis , information to view’s accountOthers
4 System design
4.1 Functional structure
In order to better understand the overall idea of this system, the system is represented in the form of a structural diagram, and the basic functions of the vehicle maintenance system are designed and implemented. The structural diagram is as follows:
4.2 Database design
4.2.1 Database E/R diagram
An ER diagram is a graph composed of specific interrelationships. The E/R diagram can clearly illustrate the interrelationships between entities involved in the system. In the system, for some of the most important or several key entities, as shown in the figure:
(1) The user registration E/R diagram is as follows:
4.2.2 Database table
The design of the database table is as follows:
Each accessory has a unique id as the primary key of the table.The accessory classification table is shown in Table 4.1
Table 4.1 Classification of accessories
Field Name |
type |
length |
Field description |
primary key |
default value |
id |
bigint |
primary key |
primary key |
||
addtime |
timestamp |
creation time |
CURRENT_TIMESTAMP |
||
peijianfenlei |
varchar |
200 |
Accessories classification |
Each fault information has a corresponding description, and the fault information table is shown in Table 4.2.
Table 4.2 Fault information
Field Name |
type |
length |
Field description |
primary key |
default value |
id |
bigint |
primary key |
primary key |
||
addtime |
timestamp |
creation time |
CURRENT_TIMESTAMP |
||
guzhangmingcheng |
varchar |
200 |
Fault name |
||
cheliangmingcheng |
varchar |
200 |
vehicle name |
||
chepaihaoma |
varchar |
200 |
License plate number |
||
cheliangyanse |
varchar |
200 |
vehicle color |
||
yonghuzhanghao |
varchar |
200 |
user account |
||
yonghuxingming |
varchar |
200 |
username |
||
guzhangmiaoshu |
longtext |
4294967295 |
Fault description |
||
jiejueshijian |
date |
Resolution time |
|||
jiejuefangfa |
longtext |
4294967295 |
Solution |
||
yuangongzhanghao |
varchar |
200 |
Employee account |
||
yuangongxingming |
varchar |
200 |
employee's name |
The announcement has a unique id as the subject's primary key, and related instructions. The announcement information table is shown in Table 4.3.
Table 4.3 Announcement information
Field Name |
type |
length |
Field description |
primary key |
default value |
id |
bigint |
primary key |
primary key |
||
addtime |
timestamp |
creation time |
CURRENT_TIMESTAMP |
||
gonggaobiaoti |
varchar |
200 |
Announcement title |
||
fengmian |
varchar |
200 |
cover |
||
faburen |
varchar |
200 |
publisher |
||
gonggaoshijian |
date |
Announcement time |
|||
gonggaoneirong |
longtext |
4294967295 |
Announcement content |
5 system function implementation
After logging in to the system, managers, users and administrators must select roles as required on the login page before entering the operating system, enter their account password and click Login to complete the registration steps, as shown in Figure 5.1.
5.1 Administrator function module
After logging in to the system, the administrator can see the home page, personal management center, user information, personnel management, car information, accident information, inventory information, accessories category management, accessories information, user information, file information, statistical information and other operations , and can complete related operations for each function one by one, as shown in Figure 5.2.
6.2 System testing method
6.2.1 User registration function test
Determine whether the user has successfully registered. As shown in Table 6.1.
Table 6.1 User registration function test cases
serial number |
enter |
expected outcome |
actual results |
Test Results |
1 |
Username: Null Password: Null |
The registered user name can only be in Chinese |
The registered name is only in Chinese |
pass |
2 |
Username 234553 Password: Null |
Prompt password length must be 6-12 characters |
Prompt password length must be 6-12 characters |
pass |
3 |
Username: tzl123 Password: 1ewe56 |
registration success |
registration success |
pass |
4 |
Username: eew3 Password: 121189 |
Prompt username already exists |
Registered member already exists |
pass |
6.2.2 User login function test
Determine whether the user's login is successful. As shown in Table 6.2.
Table 6.2 User login function test cases
serial number |
enter |
expected outcome |
actual results |
Test Results |
1 |
Username: Null Password: Null |
Prompt username or password cannot be empty |
Prompt username or password cannot be empty |
pass |
2 |
Username 154812 Password: Null |
Prompt username or password cannot be empty |
Prompt username or password cannot be empty |
pass |
3 |
Username: zxl123 Password: 12345 |
Prompt that the username or password is inconsistent |
Prompt that the username or password is inconsistent |
pass |
4 |
Username: 2001545 Password: 12345678 |
Prompt that the user does not exist |
Prompt that the user does not exist |
pass |
6.2.3 Personal information modification function test
Whether the user can successfully submit a repair report and whether there is a return prompt when the required information is empty. As shown in Table 6.3.
Table 6.3 Personal information modification function test cases
serial number |
enter |
expected outcome |
actual results |
Test Results |
1 |
Username: ddd |
Successfully modified |
Successfully modified |
pass |
2 |
Mobile number: 12346951111 |
Successfully modified |
Successfully modified |
pass |
3 |
Address: ddd |
Successfully modified |
Successfully modified |
pass |
4 |
Password: ddd |
Successfully modified |
Successfully modified |
pass |
Table of contents
2 Introduction to development technology
2.1 System development platform
2.2 Platform development related technologies
2.2.2 Introduction to mysql database
3.3 Performance requirements analysis
5 system function implementation
5.1 Administrator function module
6.1 Introduction to system testing
6.2.1 User registration function test
6.2.2 User login function test
6.2.3 Personal information modification function test
6.2.4 Post comment function test
6.2.6 Logout user function test
6.2.7 Post message function test