Re: Preparation for a phone screen interview

[Tom Storer <tstorer_tw -at- yahoo -dot- com>]

Diane Evans suggests the following as documents
required at the various stages of a software
development lifecycle:

<1. Vision and Scope document [...]
<
<2. Validation Plan [...]
<
<3. Functional Requirements Specification [...]
<
<4. System Development Specification [...]
<
<5. Test Plan [...]
<
<6. Qualification Document [...]
<
<7. User Documents [...]
<
<8. Change Requests [...]
<
<9. When the system is no longer needed, a document 
<should be permanently filed which explains why the 
<system is no longer needed and what should be done 
<with any of the left-over data. 

This sounds right based on the way things go where I
work, but I'd be curious to know how many of you are
involved in all these stages. At our office, the doc
department works almost exclusively on number 7, user
documents. On an informal basis, we contribute our
language expertise to number 3, functional
specifications, but that depends solely on how the
author of the specification feels about it. I should
note that I work in a French company where all except
user documents are "owned" by French managers or
engineers writing in their own inimitable brand of
English, so when we are asked to give a hand, it's
mostly just to make sure the grammar is correct.

How do doc departments typically work out the division
of responsibilities between professional writers and
the subject-matter experts who provide the content of,
for example, functional or technical specifications,
if the writers are actually creating the document?

Thanks,

Tom

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 today and receive a $100 mail in rebate and a FREE
WebHelp Merge Module for merging multiple Help systems on any desktop
or server. Order online today at http://www.ehelp.com/techwr-l

A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.