Information Technology Reference
In-Depth Information
Cause-effect graph:
A graphical representation of inputs and/or stimuli (causes)
with their associated outputs (effects), which can be used to design test cases.
Cause-effect graphing:
A black box test design technique in which test cases are
designed from cause-effect graphs. [BS 7925/2]
Cause-effect analysis:
See
cause-effect graphing
.
Cause-effect decision table:
See
decision table
.
Certification:
The process of confirming that a component, system or person com-
plies with its specified requirements (e.g., by passing an exam).
Changeability:
The capability of the software product to enable specified modifi-
cations to be implemented. [ISO 9126] See also
maintainability
.
Change control:
See
configuration control.
Change control board:
See
configuration control board
.
Checker:
See
reviewer
.
Classification tree method:
A black box test design technique in which test cases,
described by means of a classification tree, are designed to execute combinations of
representatives of input and/or output domains.
Code:
Computer instructions and data definitions expressed in a programming lan-
guage or in a form output by an assembler, a compiler, or other translator. [IEEE
610]
Code coverage:
An analysis method that determines which parts of the software
have been executed (covered) by the test suite and which parts have not been exe-
cuted (e.g., statement coverage, decision coverage, condition coverage).
Code-based testing:
See
white box testing
.
Co-existence:
The capability of the software product to co-exist with other inde-
pendent software in a common environment sharing common resources. [ISO
9126] See also
portability.
Commercial off-the-shelf software:
See
off-the-shelf software
.
Compatibility testing:
See
interoperability testing
.
Compiler:
A software tool that translates programs expressed in a high order lan-
guage into their machine language equivalents. [IEEE 610]
Complete testing:
See
exhaustive testing
.
Completion criteria:
See
exit criteria
.
Complexity:
The degree to which a component or system has a design and/or
internal structure that is difficult to understand, maintain, and verify. See also
cyclomatic complexity.
Compliance:
The capability of the software product to adhere to standards, con-
ventions, or regulations in laws and similar prescriptions. [ISO 9126]
Compliance testing:
The process of testing to determine the compliance of the
component or system.
Component:
A minimal software item that can be tested in isolation.
Component integration testing:
Testing performed to expose defects in the inter-
faces and interaction between integrated components.
