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.
Writing software requirements; document change control
Subject:Writing software requirements; document change control From:Peggy Thompson <Peggy_Thompson -at- CCMAIL -dot- OSTI -dot- GOV> Date:Wed, 18 May 1994 11:26:00 -0400
--Boundary (ID dpWEm6aYqZE1nATdBs9FRg)
Content-type: TEXT/PLAIN; CHARSET=IBM437
Content-description: Text_1
Hi. Do any of you out there have experience writing requirements
documents for software development? Can you give me any hints,
point me to references?
Also, to what extent do you all--all of you--practice formal
document change control; i.e., placing your documents
under--booms of thunder, please--Configuration Management?
