Re: Branching...Results

Subject: Re: Branching...Results
From: Richard Mateosian <srm -at- C2 -dot- ORG>
Date: Thu, 20 Jun 1996 08:28:46 -0700

I seem to have missed this thread, but here's my two cents worth.

I think the only good solution to the complexity problem for paper manuals
is to make the user documentation entirely task oriented. There is usually a
reasonably small set of tasks to describe. For each task there is probably a
simple path or set of paths through the maze of menus and options.

For this to work there should be good context sensitive online documentation.

A good example of this approach is Microsoft's user documentation for
Access. It's about 200 pages and covers all the bases. They have other
manuals for application developers. They wrote those in a more traditional
style. ...RM

Richard Mateosian Freelance Technical Writer
srm -at- c2 -dot- org Copyright 1996 Review Editor, IEEE Micro
http://www.c2.org/~srm/ All rights reserved President, Berkeley STC

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net


Previous by Author: Re: how to up...grade?
Next by Author: Re: Quality problem with a contractor--advice needed
Previous by Thread: Branching...Results
Next by Thread: Re: Branching...Results


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

Sponsored Ads


Sponsored Ads