RE: Business Process Information in a User Guide

["Steve Hudson" <steve -at- wright -dot- com -dot- au>]

Two words - Use Cases. Flesh em out, all the tasks your software is used for
should be represented in its own use case, or a variant.

Steve Hudson
Principal Technical Writer
Wright Technologies (Aus)
steve -at- wright -dot- com -dot- au
(612) 9518-1822
The best way to predict the future... is to create it!



-----Original Message-----
From: Erika Yanovich

Scott, you are so right! Lots of manuals tell you how to use a certain
feature, but they don't tell you why. This is true for hardware as well. I
am trying to change this approach here as much as I can and on the few
things we already did, we got excellent feedback from users. If anyone out
there has experience promoting the task-oriented approach, it would be great
to hear.


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

A landmark hotel, one of America's most beautiful cities, and 
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.  http://ieeepcs.org/2001/

  +++  Miramo -- Database/XML publishing automation.  See us at  +++
  +++  Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion  +++
  +++ More info: http://www.axialinfo.com  http://www.miramo.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.