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.
The United States Air Force has a specification that defines COTS
manuals and what they are supposed to contain. It also tells what to
do if they do not contain the required information.In a commercial
environment, it usually means what the company wants it to mean.
Usually they will request a quote for 'COTS'manuals hoping your
definition and theirs is different and that they can get you to agree
to their definition later at no extra cost.
In proposing a system/whatever with COTS documentation, the proposer
should define what will be supplied--the existing doumentation with no
changes at all. Any changes will be grounds to renegotiate the line
item in the CDRL. But it all boils down to who is defining COTS, and
what ax they have to grind at the time.
---Kate Skilton <KNSkilt -at- ACCUSORT -dot- COM> wrote:
> Hello All -
> I was wondering if anyone out there knew if there was any kind of a
> standard set up defining what exactly is contained in COTS
> documentation. Or, is it merely a term used by a company to state what
> is considered standard for them?
> Kate Skilton
> Engineering Technical Writer
> knskilt -at- accusort -dot- com
From ??? -at- ??? Sun Jan 00 00:00:00 0000=
> Send commands to listserv -at- listserv -dot- okstate -dot- edu (e.g., SIGNOFF
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com