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.
I'd take that to mean that the examples should reflect expected
real-world uses of the software.
For example, if a developer gives me a sample application that has
database table columns named "foo," "bar," and so on, I'll change
those to something like FName, LName, EmployeeID, etc.
On Tue, Feb 3, 2015 at 9:47 AM, Julie Stickler <jstickler -at- gmail -dot- com> wrote:
> One of our Product Managers keeps using the phrase "use-case based
> documentation" as in, that's something she wants the doc team to provide.
> I suspect what she means is task based documentation, but she insists
> that's not what she means.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015
