>
>However it is much easier to handle documentation when it is separated because it does not require access to the code. Thinkof the team environment where someone else has the code checked out when you are ready to add your documentation. That is all I meant.

Unfortunately, the problem with this is that in many cases it's darn near impossible to document the system (and all of the various business rules) w/o looking at the code. I could run through a form in an app. 20 times and never realize that if I hit ALT-ESC-Z while standing on my head it opens a special edit form. You might know up front what the system is supposed to do, but the docs aren't much use if they document that instead of what the system actually does ;-)