Informaciones emergentes

A black box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters. See also combinatorial testing, nwise Testing, orthogonal array testing.

Testing performed by people who are not co-located with the project team and are not fellow employees.

The process of developing and implementing an operational profile. See also operational profile.

The representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their probabilities of occurrence. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments.

Testing the attributes of a component or system that do not relate to Functionality, e.g. reliability, efficiency, usability, maintainability and portability.

The average time between consecutive failures of a component or system. See Also: mean time to repair, mean time to Failure

The percentage of defects that are removed in the same phase of the software lifecycle in which they were introduced.

(1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. See also Capability maturity Model Integration, Test Maturity Model integration. (2) The capability of the software product to avoid Failure as a result of defects in the software. [ISO 9126] See also reliability.

Modification of a software product after delivery to correct defects, to improve Performance or other attributes, or to adapt the product to a modified environment. [IEEE 1219]

The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment. [ISO 9126]