程序规范方法（Procedure specification method）.docVIP

程序规范方法（Procedure specification method） 1. procedures should be modular, easy to disassemble or increase. 2. to use RAM or IO, you must first define and reuse, avoid direct reference. If you need to adjust in the future, just change the definition section. 3., the same or similar program segments should be implemented by subroutines. If the stack and other resources are limited and subroutines cannot be used, then macros should be used to implement them, After that, we need to change the time, so long as we change the point, we dont need to change one. 4. write programs should have sufficient notes, documentation, flow charts, schematics. Easy to recall the memories of the past. 5. every time you modify the program, you should update the relevant notes, documentation, flowcharts and schematics simultaneously. So you cant change it next time. 6., the details of each process change should be documented in detail to form a history. 7., the version should be retained after each change. Instead of overwriting the original file. 8. all design proposals should be properly classified, archived, backed up and conditionally optimized to be made into discs. Avoid long periods of age lost due to viruses or hard disk damage. 9. important parameters of the program, such as the first address of the communication, and the ID should be variables that can be modified; ; Procedure flow: Program backup File name adjustment; Program name specification; Register and flag name specification; Program testing; Deleting unwanted files and programs; Adjust the layout of the program in the file; the main program is on, and the external program is in front; The place where the program needs attention; the input and output of the program; Merge and extract, write new subroutines; Revision of new program version; Modify by text record; ; C language package: Put all the definitions of the corresponding hardware in the header file; The rest of the definitions based on the definition are placed in th