Software Maintenance of Engineering

In the previous blog, I gave you some basics of software testing, and this time the theme is software maintenance.

After software development is delivered to the user, it enters the software run/maintenance phase. After that, the job is to ensure that the software works in a very long period of time, so that the maintenance of the software becomes essential.

Modifications to software products during the software run/maintenance phase are maintained. The reasons for the requirements for maintenance are varied and are summed up in 3 ways:

(1) Correcting some potential bugs or design flaws that are exposed in a particular use environment;

(2) Because of changes in the data environment during the use of the software (such as a change in transaction code) or when the processing environment changes (such as the installation of new hardware or the OS), the software needs to be modified to accommodate this change;

(3) Users and data processors often make improvements to existing functions, add new functionality, and improve overall performance requirements, in order to meet these requirements, need to modify the software to incorporate these requirements into the software.

Then we understand the need for software maintenance, and how to do it. What are the methods. Below I still use a mind map to you to summarize the software maintenance of some basic things:

You can see that the content of the graph may be relatively small, but the time spent in software maintenance is the largest in the lifetime of the software, about 70% or so, so the software maintenance work is also important. Of course, as with software testing, the level of software maintenance personnel is also a large part of the factors from experience, theoretical learning must be tested with practice, because practice is the only standard to test the truth.