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

程序规范方法（Program specification method） 1. procedures should be modular, easy to remove or add. 2. the use of RAM or IO, you must define and use, avoid direct reference. The future need to be adjusted, as long as the modified definition part well. 3. the same or similar program should use the subroutine to achieve, if the stack resource limitations, can not use the subroutine, you should use macros to implement, This will need to change, as long as the change of a point, need not change a piece. 4. written procedures should have enough notes, documentation, flow chart, principle diagram. For later can quickly evoke memories of the past. 5. every time to modify the program, should be synchronized update related notes, documentation, flow chart, principle diagram. So next time when the change is not on the number. 6. detailed records of each program should modify the details of the formation of a historical record. 7. after each change version should be preserved. Instead of overwriting the original file. 8. of all the design scheme should be properly classified backup, the best conditions for cd. To avoid falling older due to a virus or the hard disk is damaged and lost. 9. important parameters such as the communication program in the first address, ID should be able to change the variable; ; Program finishing process: Backup program File name adjustment; The name of the program code; Register and sign name specification; Test program; Delete the useless files and programs; Adjust the layout in the program file; in the main program, the program in front of foreign; Specify the procedures need to pay attention to where the output and input of the program; Merge and write a new extraction subroutine; The new version of the program to modify; Modify the text record; ; C language program packet: All the corresponding hardware will be defined in header files; Based on the definition of the definition of the remaining in place in the main file; This call is only need to modif