Re: Screen Dump Question

["Meek, DavidX L" <davidx -dot- l -dot- meek -at- INTEL -dot- COM>]

I haven't followed this thread too closely, so the info below may already
have been posted.

STC's November 1998 issue of Technical Communication (Vol. 45, #4, Fourth
Quarter) had an extensive article covering the use of Screen
Captures/Dumps/etc.  Lief, you might find this useful.  You can contact them
at 703-522-4114.  Or you might try their Web site (sorry, but I don't have
that address handy).

By the way, the STC provides an excellent monthly magazine.

-Dave
(Any statements made above are mine, and mine alone.)


>>Lief Erickson
Subject: Screen Dump Question


This thread has been very interesting. I am a young tech. writer and thus
still can be influenced to be a minimalist or advocate of screens captures
on nearly every page.

I am the lone writer at a software company. My boss would like a screen
shot of nearly every window, screen, dialog/message box - anything the user
might see. Obviously this is overkill. My job is not to capture screens to
place on paper, but to create user documentation.

At the same time our documentation is used as a pre-sales piece. Our
potential customers want to view the documentation to see if our products
solve their problems. They want to do so without having to install the
software, yet they need to have a good understanding of what the software
does. With this in mind, a lot of screen captures help them visualize what
is accomplished using our products. Now, the reviewers at the pre-sales
phase are people writing checks, not users, but the documentation is been
written for users in mind. That means I don't want to put a lot of
unnecessary screen captures in the manual, because they will be working
with the software.

Has anyone had to create a this balance before: pre-sales piece *and* user
manual? If so, how did you handle screen captures? Any advice on how to
handle this?


 From ??? -at- ??? Sun Jan 00 00:00:00 0000=