179:
encountering human error. Error should be reduced as much as possible in order to avoid frustration or injury. There are two main types of human errors which are categorized as slips and mistakes. Slips are a very common kind of error involving automatic behaviors (i.e. typos, hitting the wrong menu item). When we experience slips, we have the correct goal in mind, but execute the wrong action. Mistakes on the other hand involve conscious deliberation that result in the incorrect conclusion. When we experience mistakes, we have the wrong goal in mind and thereby execute the wrong action.
183:
reverse), they might step on the gas intending to drive, but instead accelerate into a garage wall or another car. In order to avoid modal errors, designers often employ modeless states in which users do not have to choose a mode at all, or they must execute a continuous action while intending to execute a certain mode (i.e. pressing a key continuously in order to activate "lasso" mode in
Photoshop).
101:. In this sense, it is not strictly a design role, and many usability engineers have a background in computer science because of this. Despite this point, its connection to the design trade is absolutely crucial, not least as it delivers the framework by which designers can work so as to be sure that their products will connect properly with their target usership.
296:
This tool is produced by Mind Design
Systems is available freely to federal government employees. According to the official company website this tool consists of two tightly-integrated applications. The first is the UTE Manager, which helps a tester set up test scenarios (tasks) as well as survey and
300:
The second UTE application is the UTE Runner. The UTE Runner presents the test participants with the test scenarios (tasks) as well as any demographic and survey questions. In addition, the UTE Runner tracks the actions of the subject throughout the test including clicks, keystrokes, and scrolling.
31:
to define problems that occur during the use of such a system. Usability
Engineering involves the testing of designs at various stages of the development process, with users or with usability experts. The history of usability engineering in this context dates back to the 1980s. In 1988, authors
182:
Even though slips are the more common type of error, they are no less dangerous. A certain type of slip error, a mode error, can be especially dangerous if a user is executing a high-risk task. For instance, if a user is operating a vehicle and does not realize they are in the wrong mode (i.e.
178:
In usability engineering, it's important target and identify human errors when interacting with the product of interest because if a user is expected to engage with a product, interface, or service in some way, the very introduction of a human in that engagement increases the potential of
256:
There are a variety of online resources that make the job of a usability engineer a little easier. Online tools are only a useful tool, and do not substitute for a complete usability engineering analysis. Some examples of these include:
88:
in the usability engineering lifecycle. Ensuring good usability via this process prevents problems in product adoption after release. Rather than focusing on finding solutions for usability problems—which is the focus of a
125:
are held by some to be a context, efficiency, and satisfaction with which specific users should be able to perform tasks. Advocates of this approach engage in task analysis, then prototype interface design, and
297:
demographic questions. The UTE Manager also compiles the test results and produces customized reports and summary data, which can be used as quantitative measures of usability observations and recommendations.
191:
Usability engineers conduct usability evaluations of existing or proposed interfaces and their findings are fed back to the designer for use in design or redesign. Common usability evaluation methods include:
265:
This is a product of the
National Institute of Standards and Technology. This toolkit is focused on evaluating the HTML of a website versus a wide range of usability guidelines and includes:
727:
309:
This tool is a product of UsableNet.com and implements the section 508 Usability and
Accessibility guidelines as well as the W3C Web Accessibility Initiative Guidelines.
156:. The aim of these guidelines is to facilitate the use of a software application for people with disabilities. Some guidelines for web accessibility are:
734:
521:
Usability
Evaluation and Interface Design: Cognitive Engineering, Intelligent Agents, and Virtual Reality, Volume 1 (Human Factors and Ergonomics)
66:
describes methods to use throughout a product development process—so designers can ensure they take into account the most important barriers to
114:
542:
411:
385:
338:
604:
582:
563:
528:
509:
490:
471:
445:
433:
333:
63:
53:
134:
423:
397:
375:
109:
Usability engineers sometimes work to shape an interface such that it adheres to accepted operational definitions of
278:
Framework for
Logging Usability Data (FLUD) – a file format and parser for representation of user interaction logs
48:, respectively—published material on the subject, isolating the early setting of goals, iterative evaluation, and
142:
694:
272:
Web
Category Analysis Tool (WebCAT) – lets the usability engineer construct and conduct a web category analysis
653:
41:
138:
141:
were also developed by the NIST. Usability.gov, a no-longer maintained website formerly operated by the US
275:
Web
Variable Instrumenter Program (WebVIP) – instruments a website to capture a log of user interaction
110:
597:
The Human-Computer
Interaction Handbook: Fundamentals, Evolving Technologies and Emerging Applications
33:
130:
on those designs. On the basis of such tests, the technology is potentially redesigned if necessary.
37:
556:
Human-Computer Interaction Handbook: Fundamentals, Evolving Technologies, and Emerging Applications
133:
The National Institute of Standards and Technology has collaborated with industry to develop the
686:
269:
Web Static Analyzer Tool (WebSAT) – checks web page HTML against typical usability guidelines
206:
678:
240:
221:
8:
149:
757:
211:
94:
58:
690:
679:
600:
578:
559:
524:
505:
486:
467:
460:
441:
419:
393:
371:
343:
318:
245:
127:
79:
284:
VisVIP Tool – produces a 3D visualization of user navigation paths through a website
145:, provided a tutorial and wide general reference for the design of usable websites.
538:
407:
348:
24:
90:
547:
Usability Engineering: Scenario-Based Development of Human-Computer Interaction
416:
Usability Engineering: Scenario-Based Development of Human-Computer Interaction
163:
The Section 508 government guidelines applicable to all public-sector websites.
751:
454:
323:
201:
153:
166:
The ADA Guidelines for accessibility of state and local government websites.
592:
216:
196:
67:
455:
328:
232:
634:
353:
71:
28:
390:
Making use : scenario-based design of human–computer interactions
122:
84:
49:
20:
56:
is a leader in the field of usability engineering. In his 1993 book
677:
Coakes, Elayne; Willis, Dianne; Lloyd-Jones, Raymond, eds. (2000).
281:
FLUDViz Tool – produces a 2D visualization of a single user session
118:
78:
implementing the product. Nielsen’s work describes how to perform
137:, which serves as a guide for many industry professionals. The
483:
The Usability Engineering Lifecycle: A Practitioner's Handbook
251:
710:
629:
74:, memorability, error-free use, and subjective satisfaction
624:
19:
is a professional discipline that focuses on improving the
619:
291:
135:
Common Industry Specification for Usability – Requirements
537:
406:
152:, encompasses the standards and guidelines of design for
45:
287:
TreeDec – adds navigation aids to the pages of a website
676:
575:
Usability Engineering: Process, Products & Examples
458:; Tara Scanlon; Carolyn Snyder; Terri DeAngelo (1998).
139:
specifications for successful usability in biometrics
591:
681:The new SocioTech : graffiti on the long wall
630:The National Institute of Standards and Technology
459:
23:of interactive systems. It draws on theories from
169:The IBM Guidelines for accessibility of websites.
97:—a usability engineer mainly concentrates on the
749:
115:International Organization for Standardization
711:Usability.gov - Improving the user experience
260:
304:
160:The Web Accessibility Initiative Guidelines.
635:The Web Accessibility Initiative Guidelines
252:Software applications and development tools
104:
572:
370:(2nd ed.). Boston: AP Professional.
499:
312:
52:as key activities. The usability expert
432:
384:
365:
292:The Usability Testing Environment (UTE)
148:Usability, especially with the goal of
750:
480:
462:Web Site Usability: A Designer's Guide
721:
719:
553:
518:
186:
13:
725:
716:
14:
769:
709:General Services Administration,
658:The Interaction Design Foundation
614:
654:"What is Usability Engineering?"
117:approved definitions (see e.g.,
728:"The DESIGN of EVERYDAY THINGS"
392:. Cambridge, Mass.: MIT Press.
359:
143:General Services Administration
111:user requirements documentation
703:
670:
646:
1:
685:. London: Springer. pp.
639:
42:Digital Equipment Corporation
7:
500:Faulkner, Xristine (2000).
10:
774:
713:, accessed 5 November 2022
519:Smith, Michael J. (2001).
261:The Web Metrics Tool Suite
595:; Julie A. Jacko (2007).
573:Leventhal, Laura (2007).
305:The UsableNet Liftmachine
173:
82:and how to use usability
481:Mayhew, Deborah (1999).
366:Nielsen, Jakob (1993).
202:Cognitive task analysis
105:International standards
207:Cognitive walkthroughs
554:Jacko, Julie (2012).
502:Usability Engineering
438:Usability engineering
368:Usability engineering
313:Notable practitioners
222:Heuristic evaluations
59:Usability Engineering
17:Usability engineering
241:Think aloud protocol
95:interaction designer
543:John Millar Carroll
485:. Morgan Kaufmann.
466:. Morgan Kaufmann.
440:. Morgan Kaufmann.
418:. Morgan Kaufmann.
412:John Millar Carroll
150:Universal Usability
113:. For example, the
549:. Morgan Kaufmann.
212:Contextual inquiry
187:Evaluation methods
606:978-0-8058-5870-9
584:978-0-13-157008-5
577:. Prentice Hall.
565:978-1-4398-2943-1
539:Rosson, Mary Beth
530:978-0-8058-3607-3
511:978-0-333-77321-5
492:978-1-55860-561-9
473:978-1-55860-569-5
447:978-0-12-518406-9
408:Rosson, Mary Beth
344:Larry Constantine
246:Usability testing
128:usability testing
765:
742:
741:
739:
733:. Archived from
732:
723:
714:
707:
701:
700:
684:
674:
668:
667:
665:
664:
650:
610:
588:
569:
550:
534:
515:
496:
477:
465:
451:
429:
403:
386:Carroll, John M.
381:
349:Mary Beth Rossen
25:computer science
773:
772:
768:
767:
766:
764:
763:
762:
748:
747:
746:
745:
737:
730:
724:
717:
708:
704:
697:
675:
671:
662:
660:
652:
651:
647:
642:
617:
607:
585:
566:
531:
512:
493:
474:
448:
426:
400:
378:
362:
339:John M. Carroll
315:
307:
294:
263:
254:
189:
176:
107:
80:usability tests
12:
11:
5:
771:
761:
760:
744:
743:
740:on 2022-04-24.
715:
702:
695:
669:
644:
643:
641:
638:
616:
615:External links
613:
612:
611:
605:
589:
583:
570:
564:
551:
535:
529:
516:
510:
497:
491:
478:
472:
452:
446:
434:Nielsen, Jakob
430:
424:
404:
398:
382:
376:
361:
358:
357:
356:
351:
346:
341:
336:
331:
326:
321:
319:Deborah Mayhew
314:
311:
306:
303:
293:
290:
289:
288:
285:
282:
279:
276:
273:
270:
262:
259:
253:
250:
249:
248:
243:
238:
235:
230:
229:Questionnaires
227:
224:
219:
214:
209:
204:
199:
188:
185:
175:
172:
171:
170:
167:
164:
161:
106:
103:
99:research phase
34:John Whiteside
9:
6:
4:
3:
2:
770:
759:
756:
755:
753:
736:
729:
726:Norman, Don.
722:
720:
712:
706:
698:
692:
688:
683:
682:
673:
659:
655:
649:
645:
637:
636:
632:
631:
627:
626:
625:Usability.gov
622:
621:
608:
602:
599:. CRC Press.
598:
594:
593:Sears, Andrew
590:
586:
580:
576:
571:
567:
561:
558:. CRC Press.
557:
552:
548:
544:
540:
536:
532:
526:
523:. CRC Press.
522:
517:
513:
507:
503:
498:
494:
488:
484:
479:
475:
469:
464:
463:
457:
453:
449:
443:
439:
435:
431:
427:
425:1-55860-712-9
421:
417:
413:
409:
405:
401:
399:0-262-03279-1
395:
391:
387:
383:
379:
377:0-12-518405-0
373:
369:
364:
363:
355:
352:
350:
347:
345:
342:
340:
337:
335:
334:Jakob Nielsen
332:
330:
327:
325:
324:Donald Norman
322:
320:
317:
316:
310:
302:
298:
286:
283:
280:
277:
274:
271:
268:
267:
266:
258:
247:
244:
242:
239:
236:
234:
231:
228:
225:
223:
220:
218:
215:
213:
210:
208:
205:
203:
200:
198:
195:
194:
193:
184:
180:
168:
165:
162:
159:
158:
157:
155:
154:accessibility
151:
146:
144:
140:
136:
131:
129:
124:
120:
116:
112:
102:
100:
96:
92:
87:
86:
81:
77:
73:
69:
65:
61:
60:
55:
54:Jakob Nielsen
51:
47:
43:
39:
35:
30:
26:
22:
18:
735:the original
705:
680:
672:
661:. Retrieved
657:
648:
633:
628:
623:
618:
596:
574:
555:
546:
520:
504:. Palgrave.
501:
482:
461:
456:Spool, Jared
437:
415:
389:
367:
360:Bibliography
308:
299:
295:
264:
255:
217:Focus groups
197:Card sorting
190:
181:
177:
147:
132:
108:
98:
83:
75:
68:learnability
57:
38:John Bennett
16:
15:
620:Digital.gov
329:Alan Cooper
233:RITE method
50:prototyping
696:1852330406
663:2023-08-19
640:References
354:Steve Krug
226:Interviews
85:heuristics
72:efficiency
29:psychology
758:Usability
123:usability
121:part 11)
21:usability
752:Category
545:(2002).
436:(1993).
414:(2002).
388:(2000).
119:ISO 9241
237:Surveys
64:Nielsen
693:
689:–125.
603:
581:
562:
527:
508:
489:
470:
444:
422:
396:
374:
174:Errors
76:before
738:(PDF)
731:(PDF)
691:ISBN
601:ISBN
579:ISBN
560:ISBN
525:ISBN
506:ISBN
487:ISBN
468:ISBN
442:ISBN
420:ISBN
394:ISBN
372:ISBN
44:and
40:—of
36:and
27:and
687:119
93:or
46:IBM
754::
718:^
656:.
541:;
410:;
91:UX
70:,
62:,
699:.
666:.
609:.
587:.
568:.
533:.
514:.
495:.
476:.
450:.
428:.
402:.
380:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.