Human-Computer Interaction in an Address-Indexed Information System
This presentation will describe the process by which the interface was designed for an information system that's accessed by means of an address. An address-indexed system is used when service is being established for a specific address and there is no account number to use to access records associated with the address. It is necessary to verify that the address is accurate and to know what service or facilities already exist there. The system I'm going to describe is for the telephone company but it could as easily serve the needs of any company or organization which provides service and equipment at specific addresses such as the gas company, cable television company, or a municipal government. The design of this system posed some special human-computer interaction problems. Access to records by means of an address is not as straightforward as access by means of an account number or even a customer name. Addresses are highly variable. In some communities the same street may be known by more than one name and both may be acceptable to the Post Office. In rural areas there are frequently no house numbers and often there are not even street names. One approach to handling address variability is to provide prompting and to design a highly interactive system. Another approach is to create some type of standardization and attempt to impose it on your users. Our design provides both and both will be described. Naturally, the interface had to be designed within a set of constraints. The system was to be on a single centralized large mainframe computer. It would be used by service representatives who would be talking to customers on the telephone at the same time they were accessing the system. We needed fast response time. During busy hours during peak periods of the month there might be thousands of service representatives accessing the system at the same time. There are many components of end user response time. Transaction volume is one of them. This meant that in designing this interactive system we had to keep the number of transactions down, that is, minimize the number of interactions. This presentation will describe how these problems have been resolved in the five years that this system has been evolving. Examples of the challenges and oddities we've encountered will be drawn from our experiences in mechanizing rural addresses and multi-family residences. The process described includes some prototyping, experimentation where possible, and a lot of trial and error with frequent field evaluations. The process also includes a lot of teamwork between the software designers and the human factors designers.