Glossary - UReturn to Glossary home
Significant difficulty or expense that would be incurred to adjust the normal work environment, method, or circumstances for an individual with a disability.
A graphical visualization language that consists of a series of symbols and connectors used to create process flow diagrams.
The address of a web page.
The address of a web page.
A separately testable element specified in the design of a computer software component. Also, a software component that is not subdivided into other components.
Testing of individual hardware or software units or groups of related units.
A serial computer interface that allows connection of up to 127 devices.
An interview that consists of very general questions and no predetermined plan for the flow of the conversation. See also interview.
A combination of uppercase and lowercase letters.
All capital letters. See also lowercase.
The principle that information and software should be easy to access, understand, remember, and use.
A document that defines the scope of work required to make information or software easy to access, understand, remember, and use.
Research conducted to determine whether information or software is easy to access, understand, remember, and use.
Testing, under real-world or controlled conditions, that evaluates whether information or software is easy to access, understand, remember, and use.
The customary way in which a language is spoken or written.
The specification of tests that are conducted from the end-user perspective; that is, using software as an end-user would in conducting their daily activities.
An economically and programmatically separate component of a capital project that provides a measurable performance outcome for which the benefits exceed the costs, even if no further funding is appropriated.
The ultimate customer for the product; the people who will actually use the product.
Testing performed to obtain confirmation by the customer or a subject-matter expert that the system, modification, or addition meets mutually agreed-upon requirements.
A formal product evaluation performed by a customer as a condition of acceptance or purchase.
Identification of user requirements for a product. Also called audience analysis.
Techniques and technologies to facilitate software usage; for example, online help, tool tips, wizards, and printed documentation.
A project document that provides an overall perspective of the types of user documentation needed to support the project, along with the priority and timing of each document in the release cycle. TEMPLATE
All aspects of the user's interaction with an organization, product, or service.
The ease of learning a computer, software application, or system.
All of the elements of an interface, including interaction, layout, sound, text, and visual design. See also graphical user interface.
The process of coordinating all the elements of an interface, including interaction, layout, sound, text, and visual design, to achieve the best possible interaction for users.
Identifying and defining users’ roles, wants, and needs to develop clear, complete, and concise system requirements and to enhance usability.
A process that focuses on cognitive factors (for example, perception and problem solving) as they relate to people’s interactions with a product.
A document that contains all essential information the user needs to make full use of a product. The manual includes a description of the system functions and capabilities, contingencies and alternate modes of operation, and step-by-step procedures for system access and use.Return to Glossary home