Search

A common scenario in both manufacturing and human-computer interaction is that of people linking independently-designed systems. People receive output from one system, modify it and then input it into the next system in the process. In computer systems, manual data entry tasks introduce the possibility of both human errors and delays. With increased automation and integration of computer systems, many of these human links can be eliminated. Removing the human link between independently-designed systems does not remove the user from the system network. Rather, it places the user in the role of exception processing, controlling, monitoring and responding to the overall network of systems. This new role brings with it the requirement for an expansion of user knowledge to include a complete understanding of the system network and skills for technical problem solving. It further requires that the system's design include appropriate means of notifying exception processors, a system administrator and management of system status and production volume. The appropriate combination of these components will make a substantial contribution toward the development of a successful integrated computer system.

This paper addresses the changing role of the human factors professional in the design of integrated computer systems for telecommunications engineering. Specifically, with the advent of such software, the human-computer interface is at times replaced by a computer-computer interface. With humans removed from the direct processing function, should human factors designers be removed from the design function as well? Our experience has shown that there is in fact a continuing need for our expertise, as long as humans remain in the process in any role. With the changing roles of our users, however, the focus of our efforts should change. The quality and utility of an automated computer system will be optimized by the early and persistent involvement of human factors designers in task analysis, user identification, function allocation, system design, user education and quality assurance.

Gould's (1987) iterative design principle was applied to the design and development of a large, complex interface. Specific challenges we faced in implementing his recommended design approach included the sheer volume of panels in the interface, communication across the design team, excess baggage stemming from the previous interface, management of design changes, and translation into multiple languages. Our methods of facing those challenges are documented, and the lessons we learned in the process are detailed.

In the present paper it is argued that there are two major purposes of instruction for skill acquisition. The first is to insure that the consistent components of the skill are identified by the trainee. The second purpose is to provide many correct executions of (or exposures to) these consistent components. A brief review of the laboratory research supporting the above statements is provided. The concept of consistent component training is described, and a preliminary application of the non-laboratory approach is outlined. Guidelines are discussed for specifying consistent trainable components of a skill or task.

In the present paper, the distinction between consistent and varied mapping typically found in the visual search laboratory is described and assessed. The meaningfulness of the CM/VM distinction in relation to complex industrial tasks is experimentally evaluated. It is concluded that automatic and controlled processing theory could potentially make a significant contribution to the development of enhanced training programs in industry.