- If your main program requires more than one page, you
probably should be breaking it down into more subroutines. Flowcharts
longer than one page are hard to understand.
- A word to the wise: good programmers use lots of subroutines, whereas bad ones usually don't.
- Use the standard flowchart symbols--they were designed to
make flowcharts easy to read. Also, you want other people to easily
understand your flowcharts.
- Put comments next to flowchart blocks that need additional explanation.
- At points where two arrows come together, assign a label. Then, use this same label in the actual program.
- Make your labels easy to understand. In otherwords, for a portion of a program that calculates an average, use a label such as CalcAverage, rather than something that doesn't give us any clues, such as ROUTINE2.
- When you have arrows going back to a point higher up on a flowchart, make the flow go in a clockwise direction.
- Use Word or a flowcharting program to create your
flowcharts. You'll then be able to move blocks around as needed while
you're figuring out how your program will really work. (Using pencil
and paper for complex flowcharts will drive you batty!)
|