Validating Technical Procedures

["Spreadbury, David C." <David -dot- Spreadbury -at- marconi -dot- com>]

I have been asked to show why validating a hardware or software procedure,
by someone other than the hardware/software engineering team or the writer
who wrote the procedure, before releasing a product is not only good sense
but should be required.

I have searched the Web for articles on validating documentation and have
come up somewhat dry. Several places/articles mentioned that it should be
included in the doc plan, which would be incorporated into the project plan,
but nothing as to the "Why". Common sense and experience has taught me that
it is a requirement, but the boss wants something, probably to 'prove' to
her boss, that it should be considered as a requirement.

<><><><><><><><><><><><><><><><><><>
David C. Spreadbury
Information Developer
Marconi Networks - Access Division
(972)916-4344
David -dot- Spreadbury -at- marconi -dot- com
<><><><><><><><><><><><><><><><><><>


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

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com


---
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.