|
Think Aloud Protocol
A think-aloud (or thinking aloud) protocol is a method used to gather data in usability testing in product design and development, in psychology and a range of social sciences (e.g., reading, writing, translation research, decision making, and process tracing). Description Think-aloud protocols involve participants thinking aloud as they are performing a set of specified tasks. Participants are asked to say whatever comes into their mind as they complete the task. This might include what they are looking at, thinking, doing, and feeling. This gives observers insight into the participant's cognitive processes (rather than only their final product), to make thought processes as explicit as possible during task performance. In a formal research protocol, all verbalizations are transcribed and then analyzed. In a usability testing context, observers are asked to take notes of what participants say and do, without attempting to interpret their actions and words, and especially noting ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Usability Testing
Usability testing is a technique used in user-centered interaction design to evaluate a product by testing it on users. This can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system. It is more concerned with the design intuitiveness of the product and tested with users who have no prior exposure to it. Such testing is paramount to the success of an end product as a fully functioning application that creates confusion amongst its users will not last for long. This is in contrast with usability inspection methods where experts use different methods to evaluate a user interface without involving users. Usability testing focuses on measuring a human-made product's capacity to meet its intended purposes. Examples of products that commonly benefit from usability testing are food, consumer products, websites or web applications, computer interfaces, documents, and devices. Usability testing measures the usability, or ease of use, ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Psychology
Psychology is the scientific study of mind and behavior. Psychology includes the study of conscious and unconscious phenomena, including feelings and thoughts. It is an academic discipline of immense scope, crossing the boundaries between the natural and social sciences. Psychologists seek an understanding of the emergent properties of brains, linking the discipline to neuroscience. As social scientists, psychologists aim to understand the behavior of individuals and groups.Fernald LD (2008)''Psychology: Six perspectives'' (pp.12–15). Thousand Oaks, CA: Sage Publications.Hockenbury & Hockenbury. Psychology. Worth Publishers, 2010. Ψ (''psi''), the first letter of the Greek word ''psyche'' from which the term psychology is derived (see below), is commonly associated with the science. A professional practitioner or researcher involved in the discipline is called a psychologist. Some psychologists can also be classified as behavioral or cognitive scientists. Some psyc ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Process Tracing
Process tracing is a research method used to develop and test theories. It is generally understood as a "within-case" method to draw inferences on the basis of causal mechanisms. It has been used in social sciences (such as in psychology), as well as in natural sciences. Scholars that use process tracing evaluate the weight of evidence on the basis of the strength of tests (notably straw-in-the-wind tests, hoop tests, smoking gun tests, double decisive tests). As a consequence, what matters is not solely the quantity of observations, but the quality and manner of observations. By using Bayesian probability, it may be possible to make strong causal inferences from a small sliver of data through process tracing. As a result, process tracing is a prominent case study method. Process tracing Process-tracing can be used both for inductive (theory-generating) and deductive (theory-testing) purposes. In terms of theory-testing, the process-tracing method works by presenting the observabl ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Protocol Analysis
Protocol analysis is a psychological research method that elicits verbal reports from research participants. Protocol analysis is used to study thinking in cognitive psychology (Crutcher, 1994), cognitive science (Simon & Kaplan, 1989), and behavior analysis (Austin & Delaney, 1998). It has found further application in the design of surveys and interviews (Sudman, Bradburn & Schwarz, 1996), usability testing (Henderson, Smith, Podd, & Varela-Alvarez, 1995), educational psychology (Pressley & Afflerbach 1995; Renkl, 1997) and design research (Gero & McNeill 1998). See also * Content analysis * Partial concurrent thinking aloud * Think aloud protocol A think-aloud (or thinking aloud) protocol is a method used to gather data in usability testing in product design and development, in psychology and a range of social sciences (e.g., reading, writing, translation research, decision making, and pro ... References * Austin, J., & Delaney, P. F. (1998). Protocol analysis as a tool for ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Comparison Of Usability Evaluation Methods
Usability testing methods aim to evaluate the ease of use of a software product by its users. As existing methods are subjective and open to interpretation, scholars have been studying the efficacy of each method and their adequacy to different subjects, comparing which one may be the most appropriate in fields like e-learning, e-commerce, or mobile applications. See also * Usability inspection * Partial concurrent thinking aloud Partial concurrent thinking aloud (or partial concurrent think-aloud, or PCTA) is a method used to gather data in usability testing with screen reader users. It is a particular kind of think aloud protocol (or TAP) created by Stefano Federici and S ... References {{Reflist External links Exploring two methods of usability testing: concurrent versus retrospective think-aloud protocols Usability Human–computer interaction Computing comparisons ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Partial Concurrent Thinking Aloud
Partial concurrent thinking aloud (or partial concurrent think-aloud, or PCTA) is a method used to gather data in usability testing with screen reader users. It is a particular kind of think aloud protocol (or TAP) created by Stefano Federici and Simone Borsci at the Interuniversity Center for Research on Cognitive Processing in Natural and Artificial Systems of University of Rome "La Sapienza". The partial concurrent thinking aloud is built up in order to create a specific usability assessment technique for blind users, eligible to maintain the advantages of concurrent and retrospective thinking aloud while overcoming their limits. Using PCTA blind users' verbalizations of problems could be more pertinent and comparable to those given by sighted people who use a concurrent protocol. In the usability evaluation with blind people, the retrospective thinking aloud is often adopted as a functional solution to overcome the structural interference due to thinking aloud and hearing the scr ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Protocol Analysis
Protocol analysis is a psychological research method that elicits verbal reports from research participants. Protocol analysis is used to study thinking in cognitive psychology (Crutcher, 1994), cognitive science (Simon & Kaplan, 1989), and behavior analysis (Austin & Delaney, 1998). It has found further application in the design of surveys and interviews (Sudman, Bradburn & Schwarz, 1996), usability testing (Henderson, Smith, Podd, & Varela-Alvarez, 1995), educational psychology (Pressley & Afflerbach 1995; Renkl, 1997) and design research (Gero & McNeill 1998). See also * Content analysis * Partial concurrent thinking aloud * Think aloud protocol A think-aloud (or thinking aloud) protocol is a method used to gather data in usability testing in product design and development, in psychology and a range of social sciences (e.g., reading, writing, translation research, decision making, and pro ... References * Austin, J., & Delaney, P. F. (1998). Protocol analysis as a tool for ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Retrospective Think Aloud
Retrospective think aloud protocol is a technique used in usability, and eye tracking in particular, to gather qualitative information on the user intents and reasoning during a test. It's a form of think aloud protocol A think-aloud (or thinking aloud) protocol is a method used to gather data in usability testing in product design and development, in psychology and a range of social sciences (e.g., reading, writing, translation research, decision making, and proc ... performed ''after'' the user testing session activities, instead of during them. Fairly often the retrospective protocol is stimulated by using a visual reminder such as a video replay. In writing studies, the visual reminder may be the writing produced during the think-aloud session. References * * Human–computer interaction {{Comp-stub ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Rubber Duck Debugging
In software engineering, rubber duck debugging (or rubberducking) is a method of debugging code by articulating a problem in spoken or written natural language. The name is a reference to a story in the book ''The Pragmatic Programmer'' in which a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it, line-by-line, to the duck. p. 95, footnote. Many other terms exist for this technique, often involving different (usually) inanimate objects, or pets such as a dog or a cat. Many programmers have had the experience of explaining a problem to someone else, possibly even to someone who knows nothing about programming, and then hitting upon the solution in the process of explaining the problem. In describing what the code is supposed to do and observing what it actually does, any incongruity between these two becomes apparent.. More generally, teaching a subject forces its evaluation from different perspectives and can provide a deeper und ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Human–computer Interaction
Human–computer interaction (HCI) is research in the design and the use of computer technology, which focuses on the interfaces between people (users) and computers. HCI researchers observe the ways humans interact with computers and design technologies that allow humans to interact with computers in novel ways. A device that allows interaction between human being and a computer is known as a "Human-computer Interface (HCI)". As a field of research, human–computer interaction is situated at the intersection of computer science, behavioral sciences, design, media studies, and several other fields of study. The term was popularized by Stuart K. Card, Allen Newell, and Thomas P. Moran in their 1983 book, ''The Psychology of Human–Computer Interaction.'' The first known use was in 1975 by Carlisle. The term is intended to convey that, unlike other tools with specific and limited uses, computers have many uses which often involve an open-ended dialogue between the user and t ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Testing
Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but not necessarily limited to: * analyzing the product requirements for completeness and correctness in various contexts like industry perspective, business perspective, feasibility and viability of implementation, usability, performance, security, infrastructure considerations, etc. * reviewing the product architecture and the overall design of the product * working with product developers on improvement in coding techniques, design patterns, tests that can be written as part of code based on various techniques like boundary conditions, etc. * executing a program or application with the intent of examining behavior * reviewing the deployment infrastructure a ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
