Describing branches

Subject: Describing branches
From: Marta Cepek <marta -at- M3ISYSTEMS -dot- QC -dot- CA>
Date: Sat, 15 Jun 1996 01:08:49 -0400

> Does anyone out there have other clever ways to lead the user
> through functional branching? I've sought better ways in the
> Journal and in textbooks, but we've yet to find anything that
> isn't just a refinement of these two basic approaches.

*Must* the full branching be described? Perhaps in your paper doc, you can
provide a generic/typical task flow to illustrate the software's intended
functionality, with a proviso that the users' results are affected by their
choices, and may be different from the example. However, your on-line help
should be thorough and context-sensitive for all possibilities.

Marta Cepek
marta -at- m3isystems -dot- qc -dot- ca

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: Screen Capture
Next by Author: Tools|Repair Manual|Remove Automatic TOC Bookmarks
Previous by Thread: Re: Describing branches
Next by Thread: Re: Virus message (Bad information)

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

Sponsored Ads