TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Doc Design and Conventions From:Robert Lauriston <robert -at- lauriston -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Mon, 2 Nov 2009 08:37:27 -0800
A use case is a design exercise. It's a relatively high-level,
abstract description of how to perform a real-world task (defined by
inputs and outputs) using a hypothetical system--in practical terms, a
rough outline of something you could build that you think customers
would pay for. The task is independent of the system.
You might skim Bittner & Spence's "Use Case Modeling" to get a sense
of commonly accepted terminology.
On Mon, Nov 2, 2009 at 7:49 AM, Chris Despopoulos
<despopoulos_chriss -at- yahoo -dot- com> wrote:
...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all?  Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
