RE: Rule of thumb for doc time based on development time?

[Chris Gooch <chris -dot- gooch -at- lightworkdesign -dot- com>]

John Posoda wrote:

++
it's probably an
inverse number. By that, I mean that if development spends ALOT of
time on creating a truly inteligent feature with lots of analysis, it
will probably take a short period of time to document it. OTOH, if
they just slap it together, it is going to take MUCH longer to
document it because you have to deal with something that is not
intuitive and needs lots of qualifications.
++


This corresponds with my experience too. Well designed
and put together software is easier to document than
poorly thought out software. Guess which takes less
time to develop?


Christopher Gooch, Technical Author
LightWork Design, Sheffield, UK.
www.lightworkdesign.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author 
content and configure Help in MS Word or any HTML editor. No 
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -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%40infoinfocus.com

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