RE: Writing a product functional spec AFTER the product is built

Subject: RE: Writing a product functional spec AFTER the product is built
From: Heather Anderson <Heather -dot- Anderson -at- cubrc -dot- org>
To: Tara English-Sweeney <tens00 -at- gmail -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 29 Jun 2010 09:42:21 -0400

I've worked on validation documents after the system was already completed and in use (and by that, I mean requirements documents, testing plans, etc.) and right now I'm working on a user guide for a system that's been completed for some time.

I wish people would use a SDLC but a lot of times they don't seem to do so, or the writing for the system/product is an afterthought.

One of my favorite examples is years ago when I was working for the State Department. We were using Doc-to-Help. The manual for it? Not finished. There were yellow highlights and comments that said, "fill this in." I pretty much had to teach myself via trial and error.

So it definitely happens, even with big companies.

~ Heather

-----Original Message-----
From: techwr-l-bounces+heather -dot- anderson=cubrc -dot- org -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+heather -dot- anderson=cubrc -dot- org -at- lists -dot- techwr-l -dot- com] On Behalf Of Tara English-Sweeney
Sent: Sunday, June 27, 2010 10:34 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Writing a product functional spec AFTER the product is built

Hello. I am wondering how often technical writers have been asked to write a
product functional specification after a product has been built. I have been
working feverishly on one. The goal is for it to be used as a sales tool and
even more importantly, to ensure that customers have a clear definition of
the the features and functions (via use cases) so there is no
misinterpretation.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Gain access to everything you need to create and publish information
through multiple channels. Your choice of authoring (and import)
formats with virtually any output. Try Doc-To-Help free for 30-days.
http://www.doctohelp.com/


---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


Follow-Ups:

References:
Writing a product functional spec AFTER the product is built: From: Tara English-Sweeney

Previous by Author: RE: GoDaddy Phishing
Next by Author: RE: Writing a product functional spec AFTER the product is built
Previous by Thread: Re: Writing a product functional spec AFTER the product is built
Next by Thread: RE: Writing a product functional spec AFTER the product is built


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

Sponsored Ads


Sponsored Ads