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.
I worked at Raytheon for two years (about 7 years ago). My memory's a bit
fuzzy, but I think that according to Mil. Spec. 2167, there must be one
document that defines what the product "shall" do (requirements) and a
corresponding document that explains what the product "will" do (behavior
Rayfolks use to make lists of the "shalls" when designing the product.
When I was writing the "Detailed Design Document" (or something like that),
the words shall and will were not interchangeable.
Hope this helps. And if anyone out there can add to or correct what I've
said, please do!
Member of Technical Staff - Principal Technical Writer
Burlington, Massachusetts, USA
JTorpie -at- EaselCor -dot- mhs -dot- compuserve -dot- com <-------- new address!