User documentation as product specs?

Subject: User documentation as product specs?
From: Frank Watson <watson -at- NENE -dot- CMS-STL -dot- COM>
Date: Thu, 18 Apr 1996 10:34:56 CST6CDT

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


Previous by Author: Re: GMT or Universal Time?
Next by Author: Re: Address fields
Previous by Thread: Re: DTP and Writing
Next by Thread: Re: User documentation as product specs?


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads