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:Sample software requirement docs. From:Smokey Lynne L Bare <slbare -at- JUNO -dot- COM> Date:Sat, 19 Dec 1998 01:59:44 -0500
Dear folks,
>
>I finally got our systems development managers to buy into the ISO
>12207guidelines over the outdated MIL STD 498s, which are now cancelled.
> They are in the process of replacing their Database 498 DID with the
>design segment in IEEE/ISO 12207.
>
>What they need now is to see a sample of this type of documentation in
>this format. They have nothing to go by, as there is NO documentation,
I
>mean, no documentation to speak of from the client side. There was no
>concept of a professional technical writer/communicator before I came,
>and now they are all excited about starting with a new compliant
>guideline and creating a true tech. pubs group.
>
> Would it be possible please, if someone would be kind enough to share
>examples of
> a life cycle document. I told the project manager about our great
>listserv, and she has asked if I could post the following to the other
>professional TCs and TWs:
>
>The manager asketh.......
>
>Application development is looking for a sample that has detailed
>requirements, something a programmer can actually program from. This is
>also to be used as an example for the functional people to show where
>they presently are......and where they should really be.
>
>Presently, application development is receiving high-end functional
>requirements vs the needed technical requirements. "This is what I need
>to gather for them."
>
>She thanks you.
>
>Please respond to the e-mail address below. TIA.
>
>Smokey
>
>> Smokey Lynne Bare, C.T.C.
>>
>> Information Architect
>> Technical Communications Specialist
>> Military Systems
>> Defense Supply Center, Columbus
>> 614-692-1305
>>
>> E-mail: Smokey_Bare -at- dscc -dot- dla -dot- mil
>>