[thelist] Basic Documentation Questions

[Bill Haenel]

> After writing the
> functional spec (what the program is supposed to do) I start writing in
> detail what processes the program must perform, e.g. (simplistic example):
>
> open database connection
> search for record with title field matching entered text
> if there is a match
> display record
> else
> display error message
> end if
> close database connection
>
> I then break it down into increasing levels of detail, until as McConnell
> says, it's easier to just write the code.

It's really very similar to what I described (outline, flowchart, code)
except that I find that for me personally it's easier to look at a flowchart
and understand how everything, well, flows! I write into the flowchart
objects almost exactly what you have above, then as I need the increasing
levels of detail, they're added to the chart.

This definitely may not be the right way to do it, since I have only methods
that I derived on my own, but so far it's what I've used. I will definitely
check out the book you mentioned.

BH