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: Help with a term From:Tony Chung <tonyc -at- tonychung -dot- ca> To:"Weissman, Jessica" <WeissmanJ -at- abacustech -dot- com> Date:Mon, 23 Apr 2012 08:39:29 -0700
On 2012-04-23, at 7:51 AM, "Weissman, Jessica" <WeissmanJ -at- abacustech -dot- com> wrote:
> For this document and the project it defines, it is vital to avoid confusion with the paper forms that the app is supposed to replace with a more flexible data entry process. I have been told to reserve the term "form" for the legacy paper forms. Otherwise I would turn to "form" as the obvious choice.
> The doc includes upfront sections discussing the goal of eliminating paper forms and the distinction between separate processes that the separate forms represented.
So, the paper forms are used for manual data entry, and the computer
based form process replaces the paper.
Your internal audience needs to know the difference between entering
information on paper based forms, which is consistently inflexible,
and the computer based forms which could change the screens offered to
the user based on the given answers.
It sounds like an exercise in responsive web design. When I wrote this
into our own internal forms requirements document, I called it a
"context-adaptable form".
-Tony
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
