Random thoughts...
I always think of my test suite as one of my prime sources of documentation. If you've not already got one, write one. Especially since you can't really refactor with any confidence without one.
Personally, I put a good test suite above any other sort of documentation - so I'd do that first (if not already done).
As for "standard languages" UML is probably your best bet. The various UML diagram types probably cover all that you need. The basic state & class diagrams will probably be enough for you.
However, if you're going to be refactoring your code base it doesn't sound like it's going to be worth documenting structures that you are going to change.
If you're writing documentation for "perl" people - consider using POD. It's a nice simple format, and the fact that its usually in close proximity to the code means that it tends to be updated and accurate.
In reply to Re: Algorithm, Flowchart and Refactoring
by adrianh
in thread Algorithm, Flowchart and Refactoring
by artist
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |