Re: "use-case based documentation"

Subject: Re: "use-case based documentation"
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 3 Feb 2015 13:05:34 -0800

Why / when vs. how. There's often more than one reason you might
follow the instructions in a particular procedural topic (i.e. more
than one use case per task).

On Tue, Feb 3, 2015 at 11:43 AM, Mike McCallister
<mike -dot- mccallister -at- pkware -dot- com> wrote:
> how does a "use case" differ from what we think of as a "task"?
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

"use-case based documentation": From: Julie Stickler
Re: "use-case based documentation": From: Mike Starr
Re: "use-case based documentation": From: Robert Lauriston
RE: "use-case based documentation": From: Mike McCallister

Previous by Author: Re: "use-case based documentation"
Next by Author: Re: "use-case based documentation"
Previous by Thread: Re: "use-case based documentation"
Next by Thread: Re: "use-case based documentation"

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

Sponsored Ads