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: O&M vs. User vs. System Guide From:Gail Gurman <gail -at- HOMEMAIL -dot- COM> Date:Wed, 17 Jun 1998 11:31:13 -0700
>>>>> "GH" == Gina Hertel <Ghertel -at- ALPHA88 -dot- COM> writes:
GH> What is the difference between...?
GH> 1.) Operations and Maintenance Guide
GH> 2.) User Guide
GH> 3.) System Guide
GH> I'm working on a deliverable right now, and I'm not sure what to call it.
Are there any standards for these things? I've been told to change
the name of a book I've always called a "User's Guide" to make it a
"Reference Guide."
In fact, someone at my company decided that we would have two kinds
of books: Handbooks and Reference Guides. We've agreed that
Handbooks are short books with basic procedures. Reference Guides
have more indepth info.
I wish there were a list of document title terms with definitions of
what each means, but my suspicion is that there is no such thing,
that these things are just decided on a fairly ad hoc basis.
