Methodology for Documenting Existing Code Base
What is the best format/setup for an architecture document? That is, the document that comes out of brainstorming an idea and then finding a technical process in which it will be made. There really isn't much details at this point, just a logical flow of how things will work. Flowcharts are good, I guess, but at certain times, I find that the boxes need a paragraph to explain.
A lot of people have told me about Doxygen, but that's more for documenting code itself (which I will have to do at some point on an existing application).