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.
Thanks very much for your information on the telephony dictionary. I will
summarize the information in a separate mail.
I have another question:
My job, which until now has been focussed around standard technical writing
(ie producing software user guides, online help, user training materials) is
undergoing a change in emphasis. As of July I shall be involved in software
requirements definition as my major function. Although I've had some limited
involvement in requirements type work over the past year and a half, this is
the first time that I will be responsible for managing requirements definition
for an entire project.
Does anyone on the list have experience in this field? Do you have any advice.
I'm particularly interested in information on potential pitfalls (and how to
avoid them!), how your technical writing skills helped in this work etc etc.
Reading or other formal information source would also be appreciated. So far
I've looked at the ANSI Standard 'IEEE Guide to Software Requirements
Looking forward to your replies.
Sodalia Trento Italy
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net