Spending time on the design before coding is essential for complicated projects. I think it does not matter too much exactly what format or technique you use so long as you understand it and are consistent. I often start with a text document which lists the main requirements. If the user interface is significant, I create a list of user inputs to the program and outputs from the program which will be displayed to the user. Then I make a list of tasks which the program must perform.
Then I get another pencil and create a state chart or flow chart or some hybrid of the two.
Then I go back and refine each of these parts. For example beside each front panel control (on the user inputs list) I indicate whether a change in the control will generate an event, whether it needs to be disabled under certain conditions, whether there are other parameters associated with it, and so on. The task list will be expanded to list inputs, outputs, and the basic function of the task. A flow chart per state can be generated. Additional cycles of refinement can be added as needed.
Now, open LV and start coding.
Reviews at various stages should be included as appropriate.
Lynn
