Re: Validating Technical Procedures

[Andrew Plato <intrepid_es -at- yahoo -dot- com>]

"Spreadbury, David C." wrote...
 
> 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.

It really honks my duck when pointy-haired bosses ask you to validate
something with objective study that is just plain-ol common sense. You
write instructions - duh - validate them. Its not like your asking them to
change their entire development lifecycle. 

Try checking out programming / project management resources. I don't know
of any offhand, but I know I read a "how to manage software projects" book
about 5 years ago that said all documented instructions should be
validated by QA. 

Good luck

---------------------------------
Andrew Plato
President / Principal Consultant
Anitian Corporation
(503) 644-5656 office
(503) 201-0821 cell
http://www.anitian.com
Yahoo Messenger: Anitian
---------------------------------

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.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.