The client can better define the high level process of the desired application outcome by creating flow charts themselves. This helps the client understand the system they want and the one we are trying to build. It helps the program designer understand the elements of the project that are most important to the client.

When we are looking at an embedded project, which has just one input and one output there is not a lot to discuss or understand.

However, if we have a remote communications project, with several field inputs and user interface outputs, then we must clearly document the data controls and sequences, which describe how we convert our set of inputs to real world outputs.

After program architecture and user interface requirements have been agreed upon, we can then begin create a flow chart at component or library level.

A flow chart is a pictorial procedural design consisting of three graphical control elements of sequence, selection and repetition. (Of course, this is not a flow chart diagram tutorial)

There are only seven control structures in structured C programming and we usually get to use all of them!

1. Sequence
2. If (Selection)
3. If/else (Selection)
4. Switch (Selection)
5. While (Repetition)
6. Do/While (Repetition)
7. For (Repetition)

Each of these control structures can be graphically represented. When they are joined together using some simple structure programming rules, we create a structured program.

Programs that have been designed with structured programming rules are easier to program, read, test, and debug. Structured programs reduce complexity by limiting the number of design constructs to a predictable limited set of actions.