Software Engineering Glossary

Software Engineering Glossary

"T" Glossary Content

Press the "Letter" button to view the glossary contents for that specific letter.

Other topics within the glossary:

tailor	To modify a process, standard, or procedure to better match process or product requirements.
target computer	The computer on which delivered software is intended to operate. Contrast with: host compute.
target language	The language in which the output from a machine-aided translation process is represented. For example, the language output by an assembler or compiler. Syn: object language. Contrast with: source language.
target machine	The computer on which a program is intended to execute. Contrast with: host machine (1). A computer being emulated by another computer. Contrast with: host machine (2).
target program	See: object program.
task	A sequence of instructions treated as a basic unit of work by the supervisory program of an operating system. In software design, a software component that can operate in parallel with other software components. A well-defined unit of work in the software process that provides management with a visible checkpoint into the status of the project. Tasks have readiness criteria (preconditions) and completion criteria (postconditions). Contrast with: activity.
task kick-off meeting	A meeting held at the beginning of a task of a project for the purpose of preparing the individuals involved to perform the activities of that task effectively.
task leader	The leader of a technical team for a specific task, who has technical responsibility and provides technical direction to the staff working on the task.
Task List	A window that shows all running applications and that enables you to switch between them. You can open Task List by choosing Switch To from the Control menu or by pressing CTRL+ESC.
taxonomy	A scheme that partitions a body of knowledge and defines the relationships among the pieces. It is used for classifying and understanding the body of knowledge.
team	A collection of people, often drawn from diverse but related groups, assigned to perform a well-defined function for an organization or a project. Team members may be part-time participants of the team and have other primary responsibilities.
technical management	The application of technical and administrative resources to plan, organize, and control engineering functions.
technical requirements	Those requirements that describe what the software must do and its operational constraints. Examples of technical requirements include functional, performance, interface, and quality requirements.
technical standard	A standard that describes the characteristics of applying accumulated technical or management skills and methods in the creation of a product or performing a service.
techniques	Technical and managerial procedures that aid in the evaluation and improvement of the software development process.
technology	The application of science and/or engineering in accomplishing some particular result.
temporal cohesion	A type of cohesion in which the tasks performed by a software module are all required at a particular phase of program execution; for example, a module containing all of a program's initialization tasks. Contrast with: coincidental cohesion; communicational cohesion; functional cohesion; logical cohesion; procedural cohesion; sequential cohesion.
termination construct	A program construct that results in a halt or exit.
test	An activity in which a system or component is executed under specified conditions, the results are observed or recorded, and an evaluation is made of some aspect of the system or component. To conduct an activity as in (1). A set of one or more test cases. A set of one or more test procedures. A set of one or more test cases and procedures.
test bed	An environment containing the hardware, instrumentation, simulators, software tools, and other support elements need to conduct a test.
test case	A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Documentation specifying inputs, predicted results, and a set of execution conditions for a test item. See also: test case generator; test case specification.
test case generator	A software tool that accepts as input source code, test criteria, specifications, or data structure definitions; uses these inputs to generate test input data; and, sometimes, determines expected results. Syn: test data generator; test generator.
test case specification	A document that specifies the test inputs, execution conditions, and predicted results for an item to be tested. Syn: test description; test specification. See also: test incident report; test item transmittal report; test log, test plan; test procedure; test report.
test coverage	The degree to which a given test or set of tests addresses all specified requirements for a given system or component.
test criteria	The criteria that a system or component must meet in order to pass a given test. See also: acceptance criteria; pass-fail criteria.
test data generator	See: test case generator.
test description	See: test case specification.
test design	Documentation specifying the details of the test approach for a software feature or combination of software features and identifying the associated tests.
test documentation	Documentation describing plans for, or results of, the testing of a system or component. Types include test case specification, test incident report, test log, test plan, test procedure, test report.
test driver	A software module used to invoke a module under test and, often, provide test inputs, control and monitor execution, and report test results. Syn: test harness.
test generator	See: test case generator.
test harness.	See: test driver.
test incident report	A document that describes an event that occurred during testing which requires further investigation. See also: test case specification; test item transmittal report; test log; test plan; test procedure; test report.
test item	A software item which is an object of testing.
test item transmittal report	A document that identifies one or more items submitted for testing. It contains current status and location information. See also: test case specification; test incident report; test log; test plan; test procedure; test report.
test log	A chronological record of all relevant details about the execution of a test. See also: test case specification; test incident report; test item transmittal report; test plan; test procedure; test report
test objective	An identified set of software features to be measured under specified conditions by comparing actual behavior with the required behavior described in the software documentation.
test phase	The period of time in the software life cycle during which the components of a software product are evaluated and integrated, and the software product is evaluated to determine whether or not requirements have been satisfied.
test plan	A document describing the scope, approach, resources, and schedule of intended test activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. A document that describes the technical and management approach to be followed for testing a system or component. Typical contents identify the items to be tested, tasks to be performed, responsibilities, schedules, and required resources for the testing activity. See also: test case specification; test incident report; test item transmittal report; test log, test procedure; test report
test procedure	Detailed instructions for the set-up, execution, and evaluation of results for a given test case. A document containing a set of associated instructions as in (1). Documentation specifying a sequence of actions for the execution of a test. Syn: test procedure specification; test script. See also: test case specification; test incident report; test item transmittal report; test log test plan; test report.
test procedure specification	See: test procedure.
test readiness review (TRR)	A review conducted to evaluate preliminary test results for one or more configuration items; to verify that the test procedures for each configuration item are complete, comply with test plans and descriptions, and satisfy test requirements; and to verify that a project is prepared to proceed to formal testing of the configuration items. A review as in (1) for any hardware or software component. Contrast with: code review; formal qualification review; design review; requirements review.
test repeatability	An attribute of a test, indicating that the same results are produced each time the test is conducted.
test report	A document that describes the conduct and results of the testing carried out for a system or component. Syn: test summary report. See also: test case specification; test incident report; test item transmittal report; test log; test plan; test procedure.
test script	See: test procedure.
test set architecture	The nested relationships between sets of test cases that directly reflect the hierarchic decomposition of the test objectives.
test specification	See: test case specification.
test summary report	A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items. See also: test case specification; test incident report; test item transmittal report; test log; test plan; test procedure; test report.
test unit	A set of one or more computer program modules together with associated control data (for example, tables), usage procedures, and operating procedures that satisfy the following conditions: (a) All modules are from a single computer program; (b) At least one of the new or changed modules in the set has not completed the unit test; (c) The set of modules together with its associated data and procedures are the sole object of a testing process.
testability	(1) The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met. (2) The degree to which a requirement is stated in terms that permit establishment of test criteria and performance of tests to determine whether those criteria have been met.
testability	The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met. The degree to which a requirement is stated in terms that permit establishment of test criteria and performance of tests to determine whether those criteria have been met.
testing	The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs) and to evaluate the features of the software items. See also: acceptance testing; benchmark; checkout; component testing, development testing; dynamic analysis; formal testing; functional testing; informal testing; integration testing, interface testing loopback testing, mutation testing operational testing, performance testing, qualification testing; regression testing; stress testing; structural testing; system testing; unit testing.
text box	In a dialog box, a box in which you type information needed to carry out a command. The text box may be blank or may contain text when the dialog box opens.
text editor	A computer program, often part of a word processing system, that allows a user to enter, alter, and view text. Syn: editor.
text file	A file containing only letters, numbers, and symbols. A text file contains no formatting information, except possibly for linefeeds and carriage returns. A text file is an ASCII file.
text-file transfer	A method for transferring files from Terminal to a remote computer. With this method, files are transferred as ASCII files with few formatting characters, such as linefeeds and carriage returns. All font-formatting information is removed.
text-only	An ASCII file that contains no formatting.
think time	The elapsed time between the end of a prompt or message generated by an interactive system and the beginning of a human user's response. See also: port-toport time; response time; turnaround time.
third generation language (3GL)	See: high order language.
thrashing	A state in which a computer system is expending most or all of its resources on overhead operations, such as swapping data between main and auxiliary storage, rather than on intended computing functions.
three-address instruction	A computer instruction that contains three address fields. For example, an instruction to add the contents of locations A and B, and place the results in location C. Contrast with: one-address instruction; two-address instruction; four-address instruction; zero-address instruction.
three-plus-one address instruction	A computer instruction that contains four address fields, the fourth containing the address of the instruction to be executed next. For example, an instruction to add the contents of locations A and B, place the results in location C, then execute the instruction at location D. Contrast with: one-plus-one address instruction; two-plus-one address instruction; four-plus-one address instruction.
throughput	The amount of work that can be performed by a computer system or component in a given period of time; for example, number of jobs per day. See also: turnaround time; workload model.
tier chart	See: call graph.
time out	A condition that occurs when a predetermined amount of time elapses without the occurrence of an expected event. For example, the condition that causes termination of an on-line process if no user input is received within a specified period of time. To experience the condition in (1).
time sharing	A mode of operation that permits two or more users to execute computer programs concurrently on the same computer system by interleaving the execution of their program. Note: Time sharing may be implemented by time slicing, priority-based interrupts, or other scheduling methods
time slice	The amount of processor time allocated to an application, usually measured in milliseconds.
time slicing	A mode of operation in which two or more processes are each assigned a small, fixed amount of continuous processing time on the same processor, and the processes execute in a round-robin manner, each for its allotted time, until all are completed.
timeout	If a device is not performing a task, the amount of time the computer should wait before detecting it has an error.
timing	The process of estimating or measuring the amount of execution time required for a software system or component. Contrast with: sizing.
timing analyzer	A software tool that estimates or measures the execution time of a computer program or portion of a computer program, either by summing the execution times of the instructions along specified paths or by inserting probes at specified points in the program and measuring the execution time between probes.
title bar	The horizontal bar (at the top of a window) that contains the title of the window or dialog box. On many windows, the title bar also contains the Control-menu box and the Maximize and Minimize buttons.
toolbar	A line of shortcut buttons usually located directly below the menu bar. For example, in File Manager, the toolbar includes buttons to connect to a shared directory and share a local directory. Not all windows have a toolbar.
top-down	Pertaining to an activity that starts with the highest level component of a hierarchy and proceeds through progressively lower levels; for example, top-down design; top-down testing. Contrast with: bottom-up. See also: critical piece first.
topic	Information in the Help window. A Help topic usually begins with a title and contains information about a particular task, command, or dialog box.
total correctness	In proof of correctness, a designation indicating that a program's output assertions follow logically from its input assertions and processing steps, and that, in addition, the program terminates under all specified input conditions. Contrast with: partial correctness.
trace	A record of the execution of a computer program, showing the sequence of instructions executed, the names and values of variables, or both. Types include execution trace, retrospective trace, subroutine trace, symbolic trace, variable trace. To produce a record as in (1). To establish a relationship between two or more products of the development process; for example, to establish the relationship between a given requirement and the design element that implements that requirement.
traceability	The degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another; for example, the degree to which the requirements and design of a given software component match. See also: consistency. The degree to which each element in a software development product establishes its reason for existing; for example, the degree to which each element in a bubble chart references the requirement that it satisfies.
traceability matrix	A matrix that records the relationship between two or more products of the development process; for example, a matrix that records the relationship between the requirements and the design of a given software component.
trailer	Identification or control information placed at the end of a file or message. Contrast with: header (2).
trailing decision	A loop control that is executed after the loop body. Contrast with: leading decision. See also: UNTIL.
train	To make proficient with specialized instruction and practice. See also: orientation.
training group	The collection of individuals (both managers and staff) who are responsible for coordinating and arranging the training activities for an organization. This group typically prepares and conducts most of the training courses and coordinates use of other training vehicles.
training program	The set of related elements that focus on addressing an organization's training needs. It includes an organization's training plan, training materials, development of training, conduct of training, training facilities, evaluation of training, and maintenance of training records.
training waiver	A written approval exempting an individual from training that has been designated as required for a specific role. The exemption is granted because it has been objectively determined that the individual already possesses the needed skills to perform the role.
transaction	In software engineering, a data element, control element, signal, event, or change of state that causes, triggers, or initiates an action or sequence of actions.
transaction analysis	A software development technique in which the structure of a system is derived from analyzing the transactions that the system is required to process. Syn: transaction-centered design. See also: data structure-centered design; input-processoutput; modular decomposition; object-oriented design; rapid prototyping; stepwise refinement; structured design; transform analysis.
transaction matrix	A matrix that identifies possible requests for database access and relates each request to information categories or elements in the database
transaction-centered design	See: transaction analysis.
transfer	To send data from one place and receive it at another. To relinquish control by one process and assume it at another, either with expectation of return (see call) or without such expectation (see jump).
transform analysis	A software development technique in which the structure of a system is derived from analyzing the flow of data through the system and the transformations that must be performed on the data. Syn: transformation analysis; transform-centered design. See also: data structure-centered design; input-process-output; modular decomposition; object-oriented design; rapid prototyping; stepwise refinement; structured design; transaction analysis.
transform-centered design	See: transform analysis.
transformation analysis	See: transform analysis.
transient error	An error that occurs once, or at unpredictable intervals. See also: intermittent fault; random failure.
translator	A computer program that transforms a sequence of statements expressed in one language into an equivalent sequence of statements expressed in another language. See also: assembler; compiler.
transportability	See: portability.
trap	A conditional jump to an exception or interrupt handling routine, often automatically activated by hardware, with the location from which the jump occurred recorded. To perform the operation in (1).
TRS	Acronym for test readiness review.
TrueType fonts	Fonts that are scalable and are sometimes generated as bitmaps or soft fonts, depending on the capabilities of your printer. TrueType® fonts can be sized to any height, and they print exactly as they appear on the screen.
turnaround time	The elapsed time between the submission of a job to a batch processing system and the return of completed output. See also: port-to-port time; response time; think time.
turnkey	Pertaining to a hardware or software system delivered in a complete, operational state.
two-address instruction	A computer instruction that contains two address fields. For example, an instruction to add the contents of A to the contents of B. Syn: double-operand instruction. Contrast with: one-address instruction; three-address instruction; four-address instruction; zero-address instruction.
two-level address	An indirect address that specifies the storage location containing the address of the desired operand. See also: n-level addressing.
two-level encoding	A microprogramming technique in which different microoperations may be encoded identically into the same field of a microinstruction, and the one that is executed depends upon the value in another field internal or external to the microinstruction. See also: bit steering; residual control. Contrast with: single-level encoding.
two-plus-one address instruction	A computer instruction that contains three address fields, the third containing the address of the instruction to be executed next. For example, an instruction to add the contents of A to the contents of B, then execute the instruction at location C. Contrast with: one-plus-one address instruction; three-plus-one address instruction; four-plus-one address instruction.
type	See: data type.