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:Info Mapping-Windows NT Server From:Patrick McCarthy <PTM123 -at- AOL -dot- COM> Date:Sun, 1 Sep 1996 14:40:32 -0400
I have enjoyed the discussion of Info Mapping/Chunking etc. Development
methodologies such as Info Mapping add much value to the documentation
process. Recently, I was asked to develop procedures for system
administrators to configure a particular protocol on a Windows NT server.
procedures had to be developed using Info Mapping methodology.
Generally, I agree with Info Mapping's requirement of seven items in the
short- term memory. However, in the case of Windows NT, I had to throw
idea right out the window (no pun intended). Because Windows NT is a GUI
based network OS, each time I introduced a new window, I had to explain
every entry it contained (customer requirement).
Some windows had up to 12 entries. Between this problem and the fact that
I had to add special notes all the time ( to remind the system
administrator that if
you did item D, make sure items A, B, and C were complete), I felt that
subject matter made Info Mapping difficult.
In the following example, some of the NOTES invoked other procedures
Remote Access Service, installing Windows NT files). Let's see if I
Info Mapping RULE OF SEVEN in the following example:
EXAMPLE: Installing Protocol Drivers on the Windows NT Server (step f)
f. The Chassis and Available Clients dialog box asks you how many
protocol ports you want to configure and who is allowed to dial-in
the NT server. You must provide the following information:
Number of Line Devices: The number of protocol ports to setup
the NT server. Enter a number from 4 to 256. The default value
Enable Protocol Address Authentication: When enabled, allows
NT server to restrict dial-in clients to those specified in the
IP Address window.
Peer Client IP Addresses: Contains the valid IP addresses for
with the protocol address authentication.
Number of Line Devices____ |_| Enable IP Address Authentication
Peer Client IP Addresses ADD
Figure XX. Chassis Configuration and Available Clients window
Make the appropriate selections on the Chassis Configuration and
Available box. Select OK. You will get a dialog box notifying you
Remote Access Service (RAS) will be started in order to setup the
ports (if RAS has already been installed, it will be invoked at this
NOTE: If TCP/IP is not installed on the NT Server, you will get a
prompting you to install it. Specify the correct path for the !386
for Windows NT files.
NOTE: If installing TCP/IP on a server, you must use the Network
window to specify the required protocol for each port.
NOTE: If Remote Access Service is not installed on the NT Server, you
will get a dialog box prompting you to do so.
NOTE: If you are setting up a server, you must specify the static IP
for all RAS connections.
INFO MAPPING EVALUATION: If you consider all the required tasks in this
step, I would say I went over the RULE OF SEVEN by two or three. Mr Horn
would not be happy! Of course, Mr. Horn was not paying the bills on this
ptm123 -at- aol -dot- com
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-