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.
Re: When to use screen shots (was: screen dumps in books)
Subject:Re: When to use screen shots (was: screen dumps in books) From:Michele Marques <mmarques -at- CMS400 -dot- COM> Date:Fri, 22 Jan 1999 09:25:50 -0500
I use many screen shots (basically, every screen of user input except for the
simplest dialog boxes, and any complex information display screens). I realize
that some of the minimalists would scream and cry at this, but I have two
(hopefully good) reasons:
#1: I am documenting software for use in manufacturing plants. While some
people are computer literate, many people only learn enough to enter the data
required on their screens. One of our trainers even went to a client where many
people had never even seen a keyboard before.
#2: Some of our customers are in an industry where their customers require
certain management procedures, including having every item on every screen
documented - which some of our customers interpret to mean they need a
screenshot of every screen.
