TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Thus, development of the user documentation should be part of the same
processes as the product life cycle,
and ideally performed in conjunction with development of the software, so
that the software and the user
documentation can be tested, distributed, and maintained together. The
specification of all the documentation,
including on-screen documentation and printed documentation, should be a
part of the development of the
product as a whole, not a separate exercise. Although accurate user
documentation cannot be completed until
the software product has been fully developed, the user documentation and
the product both benefit from
concurrent development.
-----------
I am sitting here imagining what a good technical writer could do to *this*
document to make it usable.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
