|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| James A. Whittaker, "Software's Invisible Users," IEEE Software, vol. 18, no. 3, pp. 84-88, May/June, 2001. | |||
| BibTex | x | ||
| @article{ 10.1109/52.922730, author = {James A. Whittaker}, title = {Software's Invisible Users}, journal ={IEEE Software}, volume = {18}, number = {3}, issn = {0740-7459}, year = {2001}, pages = {84-88}, doi = {http://doi.ieeecomputersociety.org/10.1109/52.922730}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Software's Invisible Users IS - 3 SN - 0740-7459 SP84 EP88 EPD - 84-88 A1 - James A. Whittaker, PY - 2001 VL - 18 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/52.922730
Developers and testers are comfortable with the idea of receiving input from human users, checking it for validity, and producing output for human users. However, the human user is only part of the equation. Other, invisible software users also submit input and receive output but are less understood and sometimes forgotten altogether. But there is a price to pay for ignoring these invisible users. The first step in proper accounting of these users is to understand their nature and how they can cause software applications to fail.
Citation:
James A. Whittaker, "Software's Invisible Users," IEEE Software, vol. 18, no. 3, pp. 84-88, May-June 2001, doi:10.1109/52.922730
Usage of this product signifies your acceptance of the Terms of Use.

