run under normal conditions. This information is important both to enable users to plan work activities and to identify systems that run longer or shorter than expected – a sign that typically indicates problems with the run.
9.2.2 User Training User training
may involve equipment use, particularly in the case where, say, a microcomputer is in use and the individual involved is both operator and user. In these cases, user must be instructed first in how to operate the equipment. Questions that seem trivial to the analyst, such as how to turn on a terminal, how to insert a
diskette into a microcomputer, or when it is safe to turnoff equipment without danger of data loss, are significant problems to new users who are not familiar with computers. User training must also instruct individuals in troubleshooting the system, determining whether a problem that arise is caused by the equipment or software or by something they have done in using the system. Including a troubleshooting guide in systems documentation will provide a useful reference long after the training period is over. There is nothing more frustrating than working with a system, encountering a problem, and not being able to determine whether it is the user’s fault or a problem with the system itself. The place to prevent this frustration is during training. Most user training deals with the operation of the system itself. Training in data coding emphasizes the methods to be followed in capturing data form transactions or preparing data needed for decision support activities. For example,
in an accounting system, it maybe important to translate customer names into customer account numbers that are input as part of the accounting transaction. Users must be trained so that they know how to determine the customer account number, that it is four digits in length, and that there are no alphabetic characters in it. Data – handling activities receiving the most attention in user training are adding data (how to store new transactions, editing data (how to change previously stored data, formulating inquiries (finding specific records or getting responses to questions) and deleting records of data. The bulk of systems use involves
this set of activities, so it follows that most training time will be devoted to this area. From time to time, users will have to prepare disks, load paper into printers, or change ribbons on printers. No training program is complete without sometime devoted to systems
maintenance activities. If a microcomputer or data
entry system will use disks, users should be instructed in formatting and testing disks. They should also actually perform ribbon changes, equipment cleaning and other routine maintenance. It is not enough to simply include this information in a manual, even though that is essential for later reference. As the above discussion demonstrates, there are two aspects to user training familiarization with the processing system itself (that is, the equipment used for data entry or processing) and training in using the application (that is, the software that accepts the data,
processes it, and produces the results. Weaknesses in either aspect of training are likely to lead to awkward situation that produce user frustration, errors, or both. Good documentation, although essential, does not replace training. There is no substitute for hands – on – operation of the system while learning its use.
Share with your friends: