This fourth and final article in a series about hypertext links and associated design guidelines focuses on learning support and program help links that support users' learning activities and help users understand the operational elements of the program itself. Examples are given from a HyperCard program called Desert Shield. (LRW)

Presents eight humorous ways a consumer can tell whether he has purchased a good or bad microcomputer. (MBR)

Considers three powerful techniques--heuristics, context trees, and search via backward chaining--that a knowledge engineer might employ to develop an expert system to automate performance engineering, i.e., the branch of instructional technology that focuses on the problems of business and industry. (MBR)

Discusses the need for readable, easily accessed user documentation for application software packages and provides suggestions for creating effective user documentation. User characteristics are emphasized, including problems users experience; and recommendations for effective documentation are given, including being task oriented and providing…

Provides directions for conducting a workshop providing technical training in a large organization that links job performances to work processes. Organizational levels of performance are discussed; relationship maps and process maps are explained; and an example of a workshop for a software maintenance environment is presented. (two references)…

Discusses structure, credibility, and use of the Computer Based Training (CBT) Advisor, an expert system designed to help managers make judgements about course selection, system selection, cost/benefits, development effort, and probable success of CBT projects. (MBR)

Discussion of the development of job aids and personal performance tools focuses on self-charting as an effective feedback technique. The use of self-monitoring for various situations is described, the importance of setting goals is discussed, and computer programs developed for self-monitoring are explained. (eight references) (LRW)

Highlights the major differences between software training and reference materials, examines the key features that should be present in both if they are to be effective, and presents a checklist for use in evaluating the documentation that accompanies microcomputer software. (MBR)

Discusses the advantages of using story board techniques to design a course in computer based training, and describes the use of HyperCard to create the story boards directly on the computer screen. The discussion covers HyperCard's software capabilities, programing language, and print features. (CLB)

Discusses the relationship between the problems involved in the creation of expert systems by knowledge engineers, i.e., experts at translating human abilities and knowledge into computer programs, and the major issues dealt with in the planning/analysis phases of instructional development. (MBR)

Describes criteria developed to determine which of three existing computer-based training lessons could be repurposed into a multimedia format. Reasons for repurposing, types of criteria generated to determine the instruction's repurposeability, and lessons learned from the evaluation experience are covered. (Contains 13 references.) (KRN)

Discussion of user-friendly documentation focuses on problems with computer hardware and software documentation, and other forms of instructional manuals, that are poorly written and do not keep the needs of the users in mind. Topics highlighted include target audience analysis and validation and indexes. (LRW)

Purposeful design of feedback during computer-based training development projects is necessary for an instructionally sound product. This paper examines the following aspects of feedback: importance, categories, research findings, different types of instruction, different types of questions, simulations, relationship to motivation, screen design,…

Explains abductive reasoning; compares it to more traditional forms of logic, i.e., deduction and induction; and describes a computerized tutorial called A.R.T. (Abductive Reasoning Tool) that was created to foster abductive reasoning. Implications of using abductive techniques in instructional design are suggested. (Contains 13 references.) (LRW)

Focuses on the first of three stages of the path evaluation procedure for instructional software, performing the preliminary evaluation. The three main steps involved in preliminary evaluation are (1) a program is chosen for evaluation; (2) information is exchanged with the faculty developer; and (3) the instructional designer reviews the software…