Various maintenance brings me wealth

 

In the past, I always thought that system maintenance was a very distant and profound task, both yearning and afraid of poor performance. But now I don't want to think so much, just think about how to do it well.

The "maintenance business" begins with Library maintenance. The maintenance of the library is divided into two phases. In the first stage, there is no "Administrator", and there is a direct "conversation" between the group and the group. There are many handover problems, and each task is scattered, inefficient. In the second stage, "please" out of Jiang Qian-lan as the administrator, maintenance logs are obtained from her, reducing the dialogue between groups and also reducing coupling. In terms of tasks, each group completes a task (such as reinstalling the system) in a centralized manner ). Such tasks are relatively concentrated, and the efficiency is much higher. A group and a group are similar to a "pipeline job". Each group only targets a task at a time, with a high focus and high efficiency. It also provides great help for the "online library Maintenance System" that we are currently working on.

 

YH maintenance is the most time-consuming maintenance. However, the gains are also huge. In a big aspect, YH has led me to witness most of the process from development to sales of commercial software to maintenance, in this way, we can understand the practical value of a commercial software.

Maintenance work, communication with customers, found many bugs in the system, unreasonable design, and new user requirements, paving the way for system upgrades. A project system can reflect its value only when it passes the real test of real users. At the same time, user feedback information is also the most useful and valuable. Some maintenance matters during the maintenance process also subverted my thoughts on system maintenance. In general, we will configure the environment required by the software for the user, and the system can operate normally. Most maintenance jobs are non-system errors. I roughly estimated:

The most environmental configuration problems include two aspects: software and hardware. However, thanks to various documents, it also saves me a lot of time. During the maintenance process, the system functions cannot be easily believed. The abnormal shutdown of the computer may result in incorrect time and affect the use of the project system. Therefore, we may need to use both system and network verification.

The new features are added, tested, and upgraded in the later stage, and the precautions for cooperative development are also realized in the code. Note, owner, completion time, function, modifier, modification content, modification time, and so on must be written for each function. In this way, it will be much easier for future maintenance. BS has also learned a lot about website release and deployment. The CS release at the front end and BS management at the back end are all connected to the database through the configuration file, which gives a new understanding of the operation of a system.

YH is made in a short period of time, with less flexibility. Some configuration items can be written into the program. In this way, some new requirements can only be processed by modifying the source code, upgrade. The flexibility of the system is improved. By configuring different items to meet new user needs, the user experience and product loyalty can also be increased.

In general, YH maintenance makes me realize clearly:

①. Effective documents are very important and important.

②. The maintenance work is complicated, but it helps us to understand the requirements. It is most important for the ease of use of system development in the future, and the robustness and reliability will also be improved a lot.

③. The software may not only provide project functions. In order to improve user experience and ease of use of the system, detection functions for the running environment should also be added. For example, "network connection status.

④. Responsible for cooperative development. Cooperative Development, more interfaces, and more persons in charge can reduce the Coupling Degree of communication.

 

Compared with YH, the maintenance of evaluation is quite simple. Because the evaluation is conducted once every six months, the maintenance coefficient is larger. There are very few evaluation documents (of course there are few software problems), which is difficult to maintain. It is necessary to take time to experiment and understand the functions and implementation logic of the system. However, it is very helpful for the concurrent processing capability of evaluation. In evaluation, the method of concurrent processing seems to be to send requests within a certain period of time to the server for centralized processing, rather than processing every request in a timely manner, this greatly saves the system overhead of the server and increases the system response speed.

 

Of course, the wealth maintained is not only that. Some wealth is in front of us. Although we can see it, we still don't get it. We need to continue. Maintenance is a great fortune and needs to be chewed and digested slowly.