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.
Tom Murrell
Senior Technical Writer, Alliance Data Systems, Inc.
CAD4A - (614)729-4364
Fax: (614)729-4499 mailto:tmurrell -at- alldata -dot- net
> ----------
> From: Catharine Strauss[SMTP:cstrauss -at- EPICOR -dot- COM]
> Reply To: Catharine Strauss
> Sent: Tuesday, August 24, 1999 3:45 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Documentation requirements
>
> If documentation requirements are resources necessary to create
> documentation, what would you call a requirement that you have specific
> documents in order to perform a procedure?
>
> For example, you can have a procedure that requires to you have certain
> software, certain hardware and a manual. You can organize the
> requirements
> into a bulleted list like so:
>
> * Software requirements
> * Hardware requirements
> * Documentation requirements (??? Doesn't sound right)
>
> What would you recommend as the last entry to make it clear that we aren't
> requiring our users to document their processes, but do require them to
> have
> a set of instructions in front of them to perform the procedure?
>
> Any suggestions will be appreciated.
>
> -Catharine Strauss
>
>
> From ??? -at- ??? Sun Jan 00 00:00:00 0000=
> =
>
>
