Information Technology Reference
In-Depth Information
Requirements-based testing:
An approach to testing in which test cases are
designed based on test objectives and test conditions derived from requirements
(e.g., tests that exercise specific functions or probe nonfunctional attributes such as
reliability or usability).
Requirements management tool:
A tool that supports the recording of require-
ments, requirements attributes (e.g., priority, knowledge responsible) and annota-
tion, and facilitates traceability through layers of requirements and requirements
change management. Some requirements management tools also provide facili-
ties for static analysis, such as consistency checking and violations to predefined
requirements rules.
Requirements phase:
The period of time in the software life cycle during which
the requirements for a software product are defined and documented. [IEEE 610]
Resource utilization:
The capability of the software product to use appropriate amounts
and types of resources; for example, the amounts of main and secondary memory used
by the program and the sizes of required temporary or overflow files, when the software
performs its function under stated conditions. [ISO 9126] See also
efficiency
.
Resource utilization testing:
The process of testing to determine the resource-
utilization of a software product. See also
efficiency testing
.
Result:
The consequence/outcome of the execution of a test. It includes outputs to
screens, changes to data, reports, and communication messages sent out. See also
actual result, expected result.
Resumption criteria:
The testing activities that must be repeated when testing is
restarted after a suspension. [IEEE 829]
Retesting:
Testing that runs test cases that failed the last time they were run, in
order to verify the success of corrective actions.
Review:
An evaluation of a product or project status to ascertain discrepancies from
planned results and to recommend improvements. Examples include management
review, informal review, technical review, inspection, and walkthrough. [IEEE 1028]
Reviewer:
The person involved in the review that identifies and describes anoma-
lies in the product or project under review. Reviewers can be chosen to represent
different viewpoints and roles in the review process.
Review tool:
A tool that provides support to the review process. Typical features
include review planning and tracking support, communication support, collabora-
tive reviews, and a repository for collecting and reporting of metrics.
Risk:
A factor that could result in future negative consequences; usually expressed
as impact and likelihood.
Risk analysis:
The process of assessing identified risks to estimate their impact and
probability of occurrence (likelihood).
Risk-based testing:
Testing oriented towards exploring and providing information
about product risks.
Risk control:
The process through which decisions are reached and protective
measures are implemented for reducing risks to, or maintaining risks within, speci-
fied levels.
