+---+
       | T |
       +---+

TECHNICAL REQUIREMENTS TESTING

See non-functional requirements testing.

TERMINATION OF THE APPLICATION

Although this alternative is unpalatable, it is
probably going to occur fairly often.  The
non-compliant software application will be shut down,
and whatever it was doing will have to be done manually
for an indefinite period until it can be repaired or
replaced.

This strategy may require hiring a significant number
of clerical or administrative employees, or using
temporary contractors.  Obviously this solution will be
expensive and will degrade a number of services which
are now automated but which might have to be done
manually.

TEST AUTOMATION

The use of software to control the execution of tests,
the comparison of actual outcomes to predicted
outcomes, the setting up of test preconditions, and
other test control and test reporting functions.(BCS)

TEST BED

1. A test environment containing the hardware,
isntrumentation tools, simulators and other support
software necessary for testing a system or system
component.

2. The repertoire of test cases necessary for testing a
system or system component.  (IEEE 729-1983)

TEST CASE

A specific set of test data and associated procedures
developed for a particular objective, such as to
exercise a particular program path or to verify
compliance with a specific requirment.  (IEEE 729-1983)

A set of inputs, execution preconditions, and expected
outcomes developed for a particular objective, such as
to exercise a particular program path or to verify
compliance with a specific requirement.  After
[IEEE,do178b]

TEST CASE DESIGN TECHNIQUE

A method used to derive or select test cases.(BCS)

TEST CASE SUITE

A collection of one or more test cases for the software
under test.(BCS)

TEST COMPARATOR

A test tool that compares the actual outputs produced
by the software under test with the expected outputs
for that test case.(BCS)

TEST COMPLETION CRITERION

A criterion for determining when planned testing is
complete, defined in terms of a test measurement
technique.(BCS)

TEST COVERAGE

See coverage.

TEST DATES

These are dates useful to an organization to determine
if a system element performs correctly.  Examples could
include:

* December 31, 1999 Last day before the year 2000
(rollover event)

* January 1, 2000 First day affecting all systems that
were programmed to handle only the years 1900 to1999.
First date with a "00" abbreviated year.  First month
beginning on a weekend date.

* February 29, 2000 First leap day after the rollover

A more exhaustive list of test dates is included in the
IEEE P2000.2 Year 2000 Test Methods document.
(IEEE)

TEST DRIVER

A program or test tool used to execute software against
a test case suite.(BCS)

TEST ENVIRONMENT

A description of the hardware and software environment
in which the tests will be run, and any other software
with which the software under test interacts when under
test including stubs and test drivers.(BCS)

TEST EXECUTION

The processing of a test case suite by the software
under test, producing an outcome.(BCS)

TEST EXECUTION TECHNIQUE

The method used to perform the actual test execution,
e.g. manual, capture/playback tool, etc.(BCS)

TEST GENERATOR

A program that generates test cases in accordance to a
specified strategy or heuristic.  After [Beizer].

TEST HARNESS

A testing tool that comprises a test driver and a test
comparator.(BCS)

TEST MEASUREMENT TECHNIQUE

A method used to measure test coverage items.(BCS)

TEST OUTCOME

See outcome.

TEST PLAN

A record of the test planning process detailing the
degree of tester indedendence, the test environment,
the test case design techniques and test measurement
techniques to be used, and the rationale for their
choice.(BCS)

A document prescribing the approach to be taken for
intended testing activities.The plan typically
identifies the items to be tested, the testing to be
performed, test schedules, personnel requirements,
reporting requirements, evaluation criteria, and any
risks requiring contingency planning.  (IEEE 729-1983)


TEST PROCEDURE

A document providing detailed instructions for the
execution of one or more test cases.(BCS)

TEST RECORDS

For each test, an unambiguous record of the identities
and versions of the component under test, the test
specification, and actual outcome.(BCS)

TEST SCRIPT

Commonly used to refer to the automated test procedure
used with a test harness.(BCS)

TEST SPECIFICATION

For each test case, the coverage item, the initial
state of the software under test, the input, and the
predicted outcome.(BCS)

TEST TARGET

A set of test completion criteria.

TESTING

The process of exercising software to verify that it
satisfies specified requirements and to detect errors.
After [do178b]

THREAD TESTING

A variation of top-down testing where the progressive
integration of components follows the implementation of
subsets of the requirements, as opposed to the
integration of components by successively lower
levels.(BCS)

TOP-DOWN TESTING

An approach to integration testing where the component
at the top of the component hierarchy is tested first,
with lower level components being simulated by stubs.
Tested components are then used to test lower level
components.  The process is repeated until the lowest
level components have been tested.(BCS)

TIME ZONES

The Greenwich meridian (0 degrees) extends through the
center of the initial zone, a nd the zones to the east
are numbered from 1 to 12 with the prefix "minus"
indicating the number of hours to be subtracted to
obtain Greenwich Time.  Each zone extends 7.5 degrees
on either side of its central meridian.

Westward zones are similarly numbered, but prefixed
"plus" showing the number of hours that must be added
to get Greenwich Time.  Although these zones apply
generally to sea areas, the Standard Time maintained in
many countries does not coincide with zone time.

A graphical representation of the zones is shown on the
Standard Time Zone Chart of the World published by the
Defense Mapping Agency, Attn: PR, 8613 Lee Highway,
Fairfax, VA 22031-2137.  The U.S. and possessions are
divided into 8 Standard Time zones, as set forth by the
Uniform Time Act of 1966, which also provides for the
use of Daylight Saving Time therein.  Each zone is
approximately 15 degrees of longitude in width.  All
places in each zone use, instead of their own local
time, the time counted from the transit of the "mean
sun" across the Standard Time meridian that passes near
the middle of that zone.

These time zones are designated as Atlantic, Eastern,
Central, Mountain, Pacific, Yukon, Alaska-Hawaii, and
Bering (Samoa), and the time in these zones is
basically reckoned from the 60th, 75th, 90th, 105th,
120th, 135th, 150th, and 165th meridians west o f
Greenwich.  The line wanders to conform to local
geographical regions.  The time in the various zones is
earlier than Greenwich Time by 4, 5, 6, 7, 8, 9, 10,
and 11 hours respectively.  (FW)


TRIAGE

noun

1. A process for sorting injured people into groups
based on their need for or likely benefit from
immediate medical treatment.  Triage is used on the
battlefield, at disaster sites, and in hospital
emergency rooms when limited medical resources must
located.

2. A system used to allocate a scarce commodity, such
as food, only to those capable of deriving the greatest
benefit from it.

[French, from trier, to sort, from Old French.] (AH)

Sorting into order of urgency, as with battlefield
casualties.  (W)