Some experiences about software maintenance work
First, you must clear the content of the work, uncertain places should be questioned early, everyone must express their understanding of the work content in one sentence. In addition, the changes not mentioned in the maintenance work are resolutely not allowed to do, and they are doing more.
Second, the time is also necessary to analyze and understand the project business, including the business background of the system, the relationship between the database (table), the business of this module, etc. It is necessary to understand the system from a deeper level to understand the system.
Third, regard the maintenance process of the project as a test process. All places that do not satisfy existing requirements are a bug, we must first catch all bugs (the bugs of the system are bug, developers to catch each module or the BUG of the screen), and then eliminate these bugs. Of course, you can't let go.
Fourth, the processing of the screen is only the surface layer, the key is the flow of data. So for each screen (module), it must be clear: which related tables (or views) should be referenced, which tables are updated.
5. Pay special attention to the input and output of the screen (module).
Sixth, for the revised part must be noticed, each change must be recorded, and the tracking survey can be performed at any time.
7. Maintenance and modification of the screen part should be noted: 1. It is best to investigate before changing the properties of the control, whether the property is set in the original program, if any, you can't just simple The modification attribute on the screen. 2. If the input requirements of the control have changed, all events of the control, the CHECK section of the control, preferably anywhere in the control, see if it is necessary to correct. 3. Focus on the interaction between the control and the module-level variable, the global variable.
8. Maintenance and modification of the report part should be noted: 1. It is important to understand what information can be displayed through this report. User needs to output the report under what circumstances. 2. Special attention is carried out in this report whether or not there is a report script. 3. Do not violate the requirements of the original font, display formats when adding a project.
Nine, it is best to make full use of existing global variables and global functions. Modify and add global variables, and do communication between team members when the global function.
10. Analyze the code specification of the original procedure and make an agreement before the maintenance work (there must be documentation). This agreement is fully compliant with the original system, which is not allowed to start.
