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 have been lurking for several months, and have found this list to be
a great resource. Now, it is time to ask for more direct advice and
feedback.
The medical software company I work for is planning to make a change
in the way it handles product specifications. The intent will be to
develop a draft of the user documentation first, which will become the
specifications around which the software engineers will develop
functionality and user interfaces.
Have any of you had experience with this approach? What have been the
advantages and disadvantages? Problems? Success stories? Any
suggestions about how to best implement this approach?
Feel free to E-mail me directly, unless you feel an ongoing
discussion would be of interest to the entire list. If I receive
enough responses, I will summarize them to the list.
-Frank Watson-
watson -at- cms-stl -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
