A matrix describing the participation by various roles in completing tasks or deliverables for a project or
process. It is especially useful in clarifying roles and responsibilities. RACI is an acronym derived from the four
key responsibilities most typically used: Responsible, Accountable, Consulted, and Informed.
A black-box test design technique where test cases are selected, possibly using a pseudo-random generation algorithm, to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performance.
Rational Unified Process (RUP)
reactive test strategy
A test strategy whereby the test team waits to design and implement tests until the software is received, reacting to the actual system under test.
Testing that dynamically responds to the system under test and test results being obtained. Typically reactive
testing has a reduced planning cycle and the design and implementation test phases are not carried out until
the test object is received.
The exploration of a target area aiming to gain information that can be useful for an attack.
Ref: ISO 9126 See Also: reliability
The capability of the software product to re-establish a specified level of performance and
recover the data
directly affected in case of failure.
See Also: reliability testing
Synonyms: recovery testing
Testing to determine the recoverability of a software product.
regression-averse test strategy
A test strategy whereby the test team applies various techniques to manage the risk of regression such as functional and/or non-functional regression test automation at one or more levels.
Testing using various techniques to manage the risk of regression, e.g., by designing re-usable testware and by extensive automation of testing at one or more test levels.
Ref: After IEEE 829
Synonyms: item transmittal report , test item transmittal report
A document identifying test items, their configuration, current status and other delivery information delivered by development to testing, and possibly other stakeholders, at the start of a test execution phase.
reliability growth model
Ref: ISO 9126 See Also: portability
The capability of the software product to be used in place of another specified software product for the same purpose in the same environment.
requirements management tool
Ref: After ISO 9126 See Also: efficiency
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.
resource utilization testing
See Also: efficiency testing
Synonyms: storage testing
The process of testing to determine the resource-utilization of a software product.
The criteria used to restart all or a portion of the testing activities that were suspended previously.
Synonyms: post-project meeting
A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.
A document describing the approach, resources and schedule of intended review activities. It identifies, amongst others: documents and code to be reviewed, review types to be used, participants, as well as entry and exit criteria to be applied in case of formal reviews, and the rationale for their choice. It is a record of the review planning process.
The process of identifying risks using techniques such as brainstorming, checklists and failure history.
The damage that will be caused if the risk becomes an actual outcome or event.
Synonyms: risk category
A set of risks grouped by one or more common factors such as a quality attribute, cause, location, or potential effect of risk. A specific set of product risk types is related to the type of testing that can mitigate (control) that risk type. For example, the risk of user interactions being misunderstood can be mitigated by usability testing.
root cause analysis
An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of defect recurrence will be minimized.