software review. (IEEE) An evaluation of software elements to ascertain discrepancies from planned results and
to recommend improvement. This evaluation follows a formal process. Syn: software audit. See: code audit, code
inspection, code review, code walkthrough, design review, specification analysis, static analysis
static analysis. (1) (NBS) Analysis of a program that is performed without executing the program. (2) (IEEE)
The process of evaluating a system or component based on its form, structure, content, documentation. Contrast
with dynamic analysis. See: code audit, code inspection, code review, code walk-through, design review, symbolic
execution.
test. (IEEE) 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.
testability. (IEEE) (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.
test case. (IEEE) Documentation specifying inputs, predicted results, and a set of execution conditions for a test
item. Syn: test case specification. See: test procedure.
test case generator. (IEEE) 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 design. (IEEE) Documentation specifying the details of the test approach for a software feature or
combination of software features and identifying the associated tests. See: testing functional; cause effect
graphing; boundary value analysis; equivalence class partitioning; error guessing; testing, structural; branch
analysis; path analysis; statement coverage; condition coverage; decision coverage; multiple-condition coverage.
test documentation. (IEEE) 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. (IEEE) 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 incident report. (IEEE) A document reporting on any event that occurs during testing that requires further
investigation.
test item. (IEEE) A software item which is the object of testing.
test log. (IEEE) A chronological record of all relevant details about the execution of a test.
test phase. (IEEE) The period of time in the software life cycle in 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. (IEEE) Documentation specifying the scope, approach, resources, and schedule of intended testing
activities. It identifies test items, the features to be tested, the testing tasks, responsibilities, required, resources,
and any risks requiring contingency planning. See: test design, validation protocol.
