Re: Documentation requirements

Subject: Re: Documentation requirements
From: Catharine Strauss <cstrauss -at- EPICOR -dot- COM>
Date: Tue, 24 Aug 1999 15:24:46 -0500

Thanks for all the speedy suggestions.

We decided to go with Instructional Requirements.

I know it seems vague, but it gave us the idea that we could also make
specific classes mandatory as well.

I live with the hope that spending 45 minutes teaching the user is more
fruitful than spending 20 minutes three times a month fixing what they
messed up. <sigh>

-Catharine Strauss

-----Original Message-----
From: Catharine Strauss [mailto:cstrauss -at- EPICOR -dot- COM]
Sent: Tuesday, August 24, 1999 2:45 PM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Documentation requirements

If documentation requirements are resources necessary to create
documentation, what would you call a requirement that you have specific
documents in order to perform a procedure?

For example, you can have a procedure that requires to you have certain
software, certain hardware and a manual. You can organize the requirements
into a bulleted list like so:

* Software requirements
* Hardware requirements
* Documentation requirements (??? Doesn't sound right)

What would you recommend as the last entry to make it clear that we aren't
requiring our users to document their processes, but do require them to have
a set of instructions in front of them to perform the procedure?

Any suggestions will be appreciated.

-Catharine Strauss

From ??? -at- ??? Sun Jan 00 00:00:00 0000=

From ??? -at- ??? Sun Jan 00 00:00:00 0000=


Previous by Author: Documentation requirements
Next by Author: telecommuting info request
Previous by Thread: Re: Documentation requirements
Next by Thread: Re: Documentation requirements


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


Sponsored Ads