Humanized Input: Techniques for Reliable Keyed Input |
From inside the book
Results 1-3 of 31
Page 22
... Users need not be kept in Limbo , waiting to discover if their transaction is acceptable , only to be disappointed after a long delay . In some But faster ain't necessarily better . systems , the users have adapted to the batching ...
... Users need not be kept in Limbo , waiting to discover if their transaction is acceptable , only to be disappointed after a long delay . In some But faster ain't necessarily better . systems , the users have adapted to the batching ...
Page 216
... users who were concerned with the aspect it protected . Other users didn't even know of its exist- ence , but could be told if they expressed anxiety-- and even given the current number so they might be able to figure out if someone had ...
... users who were concerned with the aspect it protected . Other users didn't even know of its exist- ence , but could be told if they expressed anxiety-- and even given the current number so they might be able to figure out if someone had ...
Page 219
... user has the right to know why the computer is shouting ERROR at him , and not have to make unin- formed guesses . Users have the right to be respected for their knowledge of the real world , and the right to adjust the standards set on ...
... user has the right to know why the computer is shouting ERROR at him , and not have to make unin- formed guesses . Users have the right to be respected for their knowledge of the real world , and the right to adjust the standards set on ...
Contents
HOW INPUTS ARE DESIGNED | 1 |
DEFAULT MESSAGES | 25 |
Design Assumptions | 32 |
Copyright | |
9 other sections not shown
Other editions - View all
Common terms and phrases
accept actual adjust alternative application approach Artificial Intelligence assumptions ation automatic batch blank characters check digit checkword COBOL consider cost data bank data entry default option delimiter detection and correction dozen duplicate edit eliminate equifinality error detection error rate estimate example explicit extra feedback field Figure fixed-field form-filling formal grammar FORTRAN frequency Gilb handling hardware human identifier ilities input design input systems instance interaction job control language keying keypunch keystrokes letters limit check machines mean method natural on-line operator order quantities pattern PL/C PL/I positional possible problem procedure punch punch card reason record reduce redundancy reliability repetition require scheme secondary storage self-checking sequence simple simulation situation Snark source document storage system design techniques telephone number tolerance Tom Gilb transaction update users variation verification Weinberg words zip code Zipf's Law