Documenting the way software actually works WAS: Try selling the sizzle of what you do.

["Sue Ahrenhold" <SAhrenhold -at- IpdSolution -dot- com>]

>>That is never a question.  Documentation documents actual behavior,
>>or else it is fiction.

Way TOO simple an answer for me.

The answer to this question here is:  Well, is it in the bug tracking system?  Will it be fixed before the release?  If it isn't fixed, have we put it in the Known issues section of the Release Notes?
If these are true, then document it the way it's supposed to work.

At many smaller companies, the documentation is also the functional specification.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Buy or upgrade to RoboHelp X3 today and receive the WebHelp
Merge Module for FREE ($299 value). RoboHelp X3's all-new
features include conditional text, completely re-engineered
printed documentation output, Context-sensitive Help Toolkit,
single-source layouts, and more!
Order online today at http://www.ehelp.com/techwr-l


---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.