Informaciones emergentes

Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data. [ISO 9126] See also Functionality.

The capability of the software product to be upgraded to accommodate increased loads. [After Gerrard]

The activities performed at each stage in software development, and how they relate to one another logically and chronologically

Systematic application of procedures and practices to the tasks of identifying, analyzing, prioritizing, and controlling risk.

The importance of a risk as defined by its characteristics impact and likelihood. The level of risk can be used to determine the intensity of Testing to be performed. A risk level can be expressed either qualitatively (e.g. high, medium, low) or quantitatively.

The process through which decisions are reached and protective measures are implemented for reducing risks to, or maintaining risks within, specified levels.

An approach to Testing to reduce the level of product risks and inform stakeholders of their status, starting in the initial stages of a project. It involves the identification of product risks and the use of risk levels to guide the test process.

The process of identifying and subsequently analyzing the identified project or product risk to determine its level of risk, typically by assigning likelihood and impact ratings. See also product risk, project risk, risk, risk impact, risk level, risk likelihood.

The process of assessing identified project or product risks to determine their level of risk, typically by estimating their impact and probability of occurrence (likelihood).

A factor that could result in future negative consequences; usually expressed as impact and likelihood.