1. Every program flowchart starts with a single terminal outline and ends with one or more terminal outlines.
2. The descriptive names that identify data items being used and the operations being performed should be used consistently.
3. The words used inside the outlines should be chosen so that they will have meaning for anyone reading the flowchart.
4. There should be only one flowline into an outline. Any merging flows should brought together on a flowline.
5. Try to leave white space in the flowchart by using connectors instead of flowlines that wander all over the flowchart.

This is a translation program that checks syntax errors from program code that the programmer may violate the rule of any specific language he/she has chosen. And it also tells the programmer what syntax errors were detected and where they are in the program code. Unlike interpreter, the compiler processes the entire program as a unit.

Disk-checking is a reviewing proces in which a representative sample of data is manually processed through an algorithm, flowcharts, pseudocode or coded program to locate logic errors.

Documenting: Preparing a written record of all activities associated with the programming process.

Benefits: 

1. When time comes to change a program, even the programmer who worte it is likely to have difficulty remembering the details of the program unless it has been well documented.
2. If the original programmer is no longer available, it may be virtually impossible to modify the program unless very careful and detailed documentation exists.
3. Without adequate documentation, it may be necessary to rewrite completely a program that must be changed.

A series of refinements after  initial algorithm to make the process more efficient and to include some steps that we had failed to consider in our initial algorithm.