Page 1 of 1

Documentation

Posted: Sun Jun 15, 2008 1:35 pm
by tinker
Documentation

At the outset of a project it is sometimes a mistake to dive straight into writing code blocks, usualy because the structure of the overall task has not been fully thought through.

I think a useful add-on would be the ability to draw Non-Actionable flowcode blocks in order to list and analyse the steps the actual process has to go through.

Ideally, two or three levels of flowcode chart starting from the basic outline and moving towards the decision making elements which the written code will have to process.

This will work as both an aid memoir to the programmer and provide a structure to the project documentation.

George :)