testing, statement. (NIST) Testing to satisfy the criterion that each statement in a program be executed at
least once during program testing. Syn: statement coverage. Contrast with testing, branch; testing, path; branch
coverage; condition coverage; decision coverage; multiple condition coverage; path coverage.
testing, storage. This is a determination of whether or not certain processing conditions use more storage
[memory] than estimated.
testing, stress. (IEEE) Testing conducted to evaluate a system or component at or beyond the limits of its
specified requirements. Syn: testing, boundary value.
testing, structural. (1) (IEEE) Testing that takes into account the internal mechanism [structure] of a system or
component. Types include branch testing, path testing, statement testing. (2) Testing to insure each program
statement is made to execute during testing and that each program statement performs its intended function.
Contrast with functional testing. Syn: white-box testing, glass-box testing, logic driven testing.
testing, system. (IEEE) The process of testing an integrated hardware and software system to verify that the
system meets its specified requirements. Such testing may be conducted in both the development environment
and the target environment.
testing, unit. (1) (NIST) Testing of a module for typographic, syntactic, and logical errors, for correct
implementation of its design, and for satisfaction of its requirements. (2) (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. Syn: component testing.
testing, usability. Tests designed to evaluate the machine/user interface. Are the communication device(s)
designed in a manner such that the information is displayed in a understandable fashion enabling the operator to
correctly interact with the system?
testing, volume. Testing designed to challenge a system’s ability to manage the maximum amount of data over
a period of time. This type of testing also evaluates a system’s ability to handle overload situations in an orderly
fashion.
traceability matrix. (IEEE) A matrix that records the relationship between two or more products; e.g., a matrix
that records the relationship between the requirements and the design of a given software component. See:
traceability, traceability analysis.
usability. (IEEE) The ease with which a user can learn to operate, prepare inputs for, and interpret outputs of a
system or component.
validation. (1) (FDA) Establishing documented evidence which provides a high degree of assurance that a
specific process will consistently produce a product meeting its predetermined specifications and quality
attributes. Contrast with data validation.
