Glossary

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.

(IEEE) 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 process of analyzing a software item to detect the differences between existing and required conditions, i.e. bugs, and to evaluate the features of the software items. (also see: Dynamic Analysis, Static Analysis, Software Engineering)

(IEEE) The process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies specified requirements or to identify differences between expected and actual results.

Process by which adjustments to, and regulation of, individual systems are demonstrated as within the required tolerances, system components are demonstrated as delivering the required capacity or duty, the functions of the system are demonstrated as delivering the required capacity of duty, the functions of the system are demonstrated to be as specified and appropriate.

(CMC-BWG) A determination as to whether routine monitoring, characterization testing, in process monitoring, stability testing, or no testing is conducted as a part of the overall control strategy.

Cross-sectional area for testing or measuring the airflow velocity, usually set up in air supply ducts or downstream of final filters or air diffusers in an installation.

Logical and ordered timing of testing activities in relation to the other deliverables of a project.

(IEEE) testing conducted to evaluate the compliance of a system or component with specified functional requirements and corresponding predicted results.

(IEEE) Testing that ignores the internal mechanism or structure of a system or component and focuses on the outputs generated in response to selected inputs and execution conditions.

(IEEE) An orderly progression of testing in which software elements, hardware elements, or both are combined and tested, to evaluate their interactions, until the entire system has been integrated.

(IEEE) Testing conducted to evaluate whether systems or components pass data and control correctly to one another.

(IEEE) Rerunning test cases which a program has previously executed correctly in order to detect errors spawned by changes or corrections made during software development and maintenance.

Testing to insure each program statement is made to execute during testing and that each program statement performs its intended function.Synonymous: White-Box Testing, Glass-Box Testing, Logic Driven Testing.

(IEEE) Testing that takes into account the internal mechanism (structure0 of a system or component. Types include branch testing, path testing, statement testing.

(IEEE) Testing conducted to verify the implementation of the design for one software element; e.g., a unit or module; or a collection of software elements. Synonymous: Component Testing

(NIST) Testing of a module for typographic, syntactic, and logical errors, for correct implementation of its design, and for satisfaction of its requirements.