Dave Deitrich
GROUP MEMBERS:
Problem statement:
Existing Automatic Teller Machine (ATM) interfaces are limited in their functionality. There are a number of transactions and services that bank customers obtain from human bank tellers that are not currently addressed by ATM's. Additionally, the rigidity with which banks currently store account information about each customer does not allow users to customize their accounts in ways they see fit.
The functionality of ATM's has remained largely unchanged since their widespread introduction more than 15 years ago. Users insert their card, type in their Personal Identification Number (PIN) on a standard 10-key pad, then use simple text-based menus to select the transaction they prefer. These transactions are usually limited to deposits, withdrawals, and sometimes transfers between two accounts which share the same ATM card and PIN number. Most ATM interfaces include a "Cancel" button that users can use if they make a mistake when entering information. Many types of ATM's also include a "Yes" and "No" button for users to respond to various questions posed by the ATM, typically for confirmation. Some machines also include an "Enter" key, and some machines have a key labeled "More time".
Despite ATM's widespread acceptance, it is interesting to note that there has been no standardization of interfaces across various types of ATM machines. While machines offered by various banks tend to look and act similar, they are often very different in terms of user interaction. Some machines use touch screens, while others do not. Some ATM's have transaction keys flanking either side of the screen, while others do not. Some machines make the "Yes" key functionally equivalent to the "Enter" key, and some machines include both keys with separate functions.
Various interface procedures have survived in these ATM's without justification or improvement, regardless of actual functionality. An example is the "More time" function under various implementations for ATM's. Presumably, the ATM "knows" that you are taking too long to respond or complete a transaction. Prompting the user, "Do you need more time?" is not, however, an appropriate action. If the user has been distracted by his or her checkbook and is busy figuring, then the question could possibly be answered by the "Yes" button to allow the user to complete their task. But what possible meaning could answering "No" have to the system? What are the consequences of not answering at all? What if the user needs additional time to answer the question about needing more time?
Obviously, there are some important limitations and several drawbacks to the existing ATM interaction paradigm. This paradigm was merely functional when introduced in the late 1970's, and at the time, functional was good enough. By today's standards, however, with the increase in computing power, sophistication of users' abilities, and development of graphical user interfaces, the original concept seems lacking and outdated. Our project attempts to create a new ATM interface that widely improves functionality consistent with the needs of today's users.
REPORTS:
EXHIBITS:
COMMENTS:
(I'm pretty sure this doesn't work yet, unfortunately. Please email comments to deitrich@cc.gatech.edu. Thanks much!)
