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.
Subject:Re: Technical Reviews of On-line Help From:Tom Murrell <trmurrell -at- yahoo -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 19 May 2000 06:10:17 -0700 (PDT)
--- Cathy Arthur <carthur -at- ndigital -dot- com> is about to start an online help
project and wants to know how best to establish the review process for the
documentation.
<mytwocents>
Try doing two separate types of reviews. First, have the SMEs involved in
desktop reviews of the text. These reviews should focus on the technical
accuracy of the information: correctness, completeness, suitability, the same
sorts of things you would focus on with SMEs for other technical documentation.
Once the layout and organization work on the text is done--what information is
accessed from where in the online help--have a desktop/system combined review
to see that information has been properly positioned and allocated for the
various parts of the system, or however it will be accessed. I think this
should be a combination of desktop and system in whatever ratio will help
reviewers understand how the information will be accessible to the user and how
it will be organized.
The third step in this process would be QA testing and review. As the system is
tested, the online documentation should be tested in exactly the same way as
any other part of the system is tested. From a user's perspective, the online
help IS part of the system.
Each step of the way attacks a different part of the documentation development
and system development in a methodical way.