Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Usability engineering
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{More footnotes needed|date=December 2024}} '''Usability engineering''' is a professional discipline that focuses on improving the [[usability]] of interactive systems. It draws on theories from [[computer science]] and [[psychology]] 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 [https://www.interaction-design.org/literature/author/john-whiteside John Whiteside] and [https://www.interaction-design.org/literature/author/john-bennett John Bennett]—of [[Digital Equipment Corporation]] and [[IBM]], respectively—published material on the subject, isolating the early setting of goals, iterative evaluation, and [[Prototype|prototyping]] as key activities. The usability expert [[Jakob Nielsen (usability consultant)|Jakob Nielsen]] is a leader in the field of usability engineering. In his 1993 book ''[https://www.nngroup.com/books/usability-engineering/ Usability Engineering]'', [[Jakob Nielsen (usability consultant)|Nielsen]] describes methods to use throughout a product development process—so designers can ensure they take into account the most important barriers to [[learnability]], [[efficiency]], memorability, error-free use, and subjective satisfaction ''before'' implementing the product. Nielsen’s work describes how to perform [[Usability testing|usability tests]] and how to use usability ''[[Heuristic|heuristics]]'' 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 [[User experience|UX]] or [[Interaction design|interaction designer]]—a usability engineer mainly concentrates on the ''research phase''. 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.<ref>{{Cite web |title=What is Usability Engineering? |url=https://www.interaction-design.org/literature/topics/usability-engineering |access-date=2023-08-19 |website=The Interaction Design Foundation |language=en}}</ref> == International standards == Usability engineers sometimes work to shape an interface such that it adheres to accepted operational definitions of [[user requirements document]]ation. For example, the [[International Organization for Standardization]] approved definitions (see e.g., [[ISO 9241]] part 11) [[usability]] 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 [[usability testing]] on those designs. On the basis of such tests, the technology is potentially redesigned if necessary.<ref>{{cite book|editor-last1=Coakes|editor-first1=Elayne|editor-last2=Willis|editor-first2=Dianne|editor-first3=Raymond|editor-last3= Lloyd-Jones|title=The new SocioTech : graffiti on the long wall|url=https://archive.org/details/newsociotechgraf00coak|url-access=limited|date=2000|publisher=Springer|location=London |isbn=1852330406|pages=[https://archive.org/details/newsociotechgraf00coak/page/n132 119]–125}}</ref> The National Institute of Standards and Technology has collaborated with industry to develop the [https://www.nist.gov/publications/common-industry-specification-usability-requirements Common Industry Specification for Usability – Requirements], which serves as a guide for many industry professionals.{{Who|date=December 2014}} The [http://zing.ncsl.nist.gov/biousa/docs/Usability_and_Biometrics_final2.pdf specifications for successful usability in biometrics] were also developed by the NIST. Usability.gov, a no-longer maintained website formerly operated by the US [[General Services Administration]],<ref>General Services Administration, [https://www.usability.gov/ Usability.gov - Improving the user experience], accessed 5 November 2022</ref> provided a tutorial and wide general reference for the design of usable websites. Usability, especially with the goal of [[Universal Usability]], encompasses the standards and guidelines of design for [[accessibility]]. The aim of these guidelines is to facilitate the use of a software application for people with disabilities. Some guidelines for web accessibility are: #The Web Accessibility Initiative Guidelines. #The Section 508 government guidelines applicable to all public-sector websites. #The ADA Guidelines for accessibility of state and local government websites. #The IBM Guidelines for accessibility of websites. == Errors == 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 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.<ref name="Kim">{{cite web| url=https://www.sunyoungkim.org/class/old/hci_f18/pdf/The-Design-of-Everyday-Things-Revised-and-Expanded-Edition.pdf | title=The DESIGN of EVERYDAY THINGS | first=Don| last=Norman |archive-url=https://web.archive.org/web/20220424223415/https://www.sunyoungkim.org/class/old/hci_f18/pdf/The-Design-of-Everyday-Things-Revised-and-Expanded-Edition.pdf | archive-date=2022-04-24}}</ref> 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. 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).<ref name="Kim"/> == Evaluation methods == 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: *[[Card sorting]] *[[Task analysis|Cognitive task analysis]] *[[Cognitive walkthrough]]s *[[Contextual inquiry]] *[[Focus groups]] *[[Heuristic evaluation]]s *Interviews *Questionnaires *[[RITE method]] *Surveys *[[Think aloud protocol]] *[[Usability Testing|Usability testing]] == Software applications and development tools == 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: === The Web Metrics Tool Suite === 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: * Web Static Analyzer Tool (WebSAT) – checks web page HTML against typical usability guidelines * Web Category Analysis Tool (WebCAT) – lets the usability engineer construct and conduct a web category analysis * Web Variable Instrumenter Program (WebVIP) – instruments a website to capture a log of user interaction * Framework for Logging Usability Data (FLUD) – a file format and parser for representation of user interaction logs * FLUDViz Tool – produces a 2D visualization of a single user session * VisVIP Tool – produces a 3D visualization of user navigation paths through a website * TreeDec – adds navigation aids to the pages of a website === The Usability Testing Environment (UTE) === 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 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. 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. === The UsableNet Liftmachine === 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. == Notable practitioners == # [[Deborah J. Mayhew|Deborah Mayhew]] # [[Donald Norman]] # [[Alan Cooper (software designer)|Alan Cooper]] # [[Jakob Nielsen (usability consultant)|Jakob Nielsen]] # [[John M. Carroll (information scientist)|John M. Carroll]] # [[Larry Constantine]] # [[Mary Beth Rosson|Mary Beth Rossen]] # [[Steve Krug]] ==Bibliography== #{{cite book|last1=Nielsen|first1=Jakob|title=Usability engineering|date=1993|publisher=AP Professional|location=Boston |isbn=0-12-518405-0|edition=2nd}} #{{cite book|last1=Carroll|first1=John M.|author-link=John M. Carroll (information scientist)|title=Making use : scenario-based design of human–computer interactions|date=2000|publisher=MIT Press|location=Cambridge, Mass. |isbn=0-262-03279-1}} # {{cite book |title=Usability Engineering: Scenario-Based Development of Human-Computer Interaction |last=Rosson |first=Mary Beth |author-link=Mary Beth Rosson |author2=John Millar Carroll|author-link2=John M. Carroll (information scientist) |year=2002 |publisher=Morgan Kaufmann |isbn=1-55860-712-9 }} # {{cite book |title=Usability engineering |last=Nielsen |first=Jakob |author-link=Jakob Nielsen (usability consultant) |year=1993 |publisher=Morgan Kaufmann |isbn=978-0-12-518406-9 }} # {{cite book |title=Web Site Usability: A Designer's Guide |last=Spool |first=Jared |author-link=Jared Spool |author2=Tara Scanlon |author3=Carolyn Snyder |author4=Terri DeAngelo |year=1998 |publisher=Morgan Kaufmann |isbn=978-1-55860-569-5 |url-access=registration |url=https://archive.org/details/websiteusability00spoo }} # {{cite book |title=The Usability Engineering Lifecycle: A Practitioner's Handbook |last=Mayhew |first=Deborah |year=1999 |publisher=Morgan Kaufmann |isbn=978-1-55860-561-9 }} # {{cite book |title=Usability Engineering |last=Faulkner |first=Xristine|date=2000 |publisher=Palgrave |isbn=978-0-333-77321-5 }} # {{cite book |title=Usability Evaluation and Interface Design: Cognitive Engineering, Intelligent Agents, and Virtual Reality, Volume 1 (Human Factors and Ergonomics) |last=Smith |first=Michael J. |year=2001 |publisher=CRC Press |isbn= 978-0-8058-3607-3 }} # {{cite book |title=Usability Engineering: Scenario-Based Development of Human-Computer Interaction |last=Rosson |first=Mary Beth |author-link=Mary Beth Rosson |author2=John Millar Carroll |author-link2=John M. Carroll (information scientist) |year=2002 |publisher=Morgan Kaufmann }} # {{cite book |title=Human-Computer Interaction Handbook: Fundamentals, Evolving Technologies, and Emerging Applications |last=Jacko |first=Julie |year=2012 |publisher=CRC Press |isbn=978-1-4398-2943-1}} # {{cite book |title=Usability Engineering: Process, Products & Examples |last=Leventhal |first=Laura |year=2007 |publisher=Prentice Hall |isbn= 978-0-13-157008-5 }} # {{cite book |title=The Human-Computer Interaction Handbook: Fundamentals, Evolving Technologies and Emerging Applications |last=Sears |first=Andrew |author-link=Andrew Sears |author2=Julie A. Jacko |year=2007 |publisher=CRC Press |isbn=978-0-8058-5870-9}} == External links == [https://www.digital.gov Digital.gov] [http://www.Usability.gov Usability.gov] [http://zing.ncsl.nist.gov/ The National Institute of Standards and Technology] [http://www.w3.org/WAI/intro/wcag.php The Web Accessibility Initiative Guidelines] ==References== {{Reflist}} {{Authority control}} {{DEFAULTSORT:Usability Engineering}} [[Category:Usability]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Authority control
(
edit
)
Template:Cite book
(
edit
)
Template:Cite web
(
edit
)
Template:More footnotes needed
(
edit
)
Template:Reflist
(
edit
)
Template:Who
(
edit
)