Glossary: T

Talking Protocol: A technique in usability tests where users are asked to speak their thoughts as they perform a task. Verbalization of the task is quite useful in understanding mistakes that are made and getting ideas for what the causes might be and how the interface could be improved.
Task Analysis: A set of methods for decomposing people's tasks in order to understand the procedures better and to help provide computer support for those tasks. The basic approach is to define the task and its goals and then to list the steps involved.
Task Completion Time: Amount of time it takes a user to perform a computer task from start to finish.
Test: The process of evaluating a system or program by manual or automated means to verify that it meets its required expectations or to identify differences between expected and actual results.
Test Case: A specific set of test data along with inputs, conditions, and expected results for a particular test objective that depicts a complete business or administrative process.
Test Environment: An environment that contains the integral hardware, software, tools, and other support elements needed to conduct a test of logically or physically separate components.
Test Issue: A design flaw exhibited when a business application process is subjected to a test procedure.
Test Objective: An identified set of product features to be measured under specified conditions by comparing actual vs. required behavior.
Test Plan: A formal or informal plan followed to assure the controlled testing of a product using test scripts and/or cases to test a particular situation.
Test Procedure: The formal or informal steps followed to execute a test, usually a written document that allows others to test with a minimum of training.
Test Process Schedule: Document showing the performance order of business processes during tests, so that a monthly processing cycle can be recreated.
Test Script: A set of test cases used to test the predetermined business and/or administrative processes performed within a department, lab, or center.
Test Validity: The degree to which a test accomplishes its specified goal.
Three-Click Rule: Access to any primary feature of a software application or each logical step in a process should require no more than three mouse clicks. Applying this principle can be tricky because a primary feature or logical step is hard to define. Nevertheless, it's a helpful rule of thumb for software development and usability.
Transaction Database: Comprehensive itemization of the processes MIT currently uses in SAP and serves as the foundation for future tests.
Transaction Page: A web page for a user to perform an operation on system data. Create Journal Voucher is a transaction page within the Journal Voucher feature.
Transport Request: An SAP package containing a collection of SAP objects. It is generally used to record and manage changes made to SAP repository objects and to customize settings.