Re: Software Bug Databases

[jlshaeffer -at- aol -dot- com]

 In my experience, only the writer can judge the doc impact. Some things that seem minor to developers can be major in the documentation and the reverse is true, as well. 
I also found it useful to peruse the reported bugs that did not reference the documentation directly, so that I could get "ahead of the curve" and anticipate documentation impacts that non-writers did not consider. It seems like more work, but it saved a lot of rewrite time. 
At least you have access to the bug database and get the documentation bugs written up in it. Some writers aren't even that lucky. Documentation really needs to be part of that system. 

Jim Shaeffer


 







 


________________________________________________________________________
More new features than ever.  Check out the new AOL Mail ! - http://o.aolcdn.com/cdn.webmail.aol.com/mailtour/aol/en-us/text.htm?ncid=aolcmp00050000000003
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.