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: What is a Technical Specifications document? From:Scott Wahl <swahl -at- BRIDGEWATERSYS -dot- COM> Date:Mon, 22 Feb 1999 12:12:27 -0500
Cassandra,
A technical spec should be written by a developer. Technical specs should
always be internal documents, to define and clarify development work. The spec
also should relate this work to customer or product management requirements.
A technical spec should never go to a customer. If a customer document is
required, then the job should go to you, as a technical writer.
Scott
--
Scott Wahl
Customer Documentation and Training
Bridgewater Systems Corporation
(613) 591-6655 x.2579
"Parker, Cassandra M. (EXCH)" wrote:
> Hi everyone,
>
> I'm trying to find out how to write a Technical Specifications document.
>
> Is it usually written by a Tech Writer or the Programmer of an application?
> There is a little debate about this subject in my immediate department.
>
> I welcome your views and comments.
>
> Thanks,
> <><><><><><><><><><><><><><><><>
> Cassandra Parker
> Information Services - Tampa, FL
> Applications Delivery - QA
> (813) 829-6560
> <><><><><><><><><><><><><><><><>
