Also flow charting in the old sense is often more trouble than it is worth. Data decomposition and object oriented diagramming is more appropriate.
------------------- anecdote alert --------------------------
Way back in the 70's I worked for an insurance company and there was a system written in the past by a then director. This director required all changes to the system be made first to the flow chart and reviewed before a line of code could be changed. The flow chart was in eight 3 inch 3-ring binders. The director had drawn each and every page and could not fathom the idea of the flowcharts getting out of date with the code. What a nightmare project to work on. Few bugs were fixed as trying to understand the flowchart was impossible.
These days most programmers realize that typically any diagramming approach is just the dirty water used to prime the pump. The effort to maintain the diagram is mostly pointless, as the only real accurate documentation is the code.
