Term: “requirements phase”. It is the time period in the software lifecycle during which the requirements of a software product are defined and documented. [IEEE 610]
Search Results for:
Efficiency
Term: “efficiency”. It is the capacity of a software product to provide an appropriate performance in relation to the amount of resources it uses under determined conditions. [ISO 9126].
Software quality
Term: “software quality”. It is the whole of functionality and features of a product related with its capacity to satisfy implicit or explicit needs. [ISO 9126]
Basic block
Term: “basic block”. It is a sequence of one or more consecutive executable statements without branches. Note: a node in a control flow graph is a basic block.
Dynamic analysis
En Inglés: “dynamic analysis”. It is the behavior assessment process, for example, of the storage performance or use of CPU of a component or system during its execution [IEEE 610].
Failure Mode and Effect Analysis (FMEA)
Ter: “Failure Mode and Effect Analysis (FMEA)”. It is a systematic method for the identification and analysis of risks, determining possible failure modes to avoid them.
Data flow analysis
Term: “data flow analysis”. It is a kind of static analysis based on the definition and use of the variables.
Boundary value
Term: “boundary value”. It is the input or output value in the boundary of an equivalence partition or at the minimum incremental distance at any side of the border, such as the minimum or maximum value of a range.
Boundary value analysis
Term: “boundary value analysis”. It is the black-box test design technique in which the test cases are developed based on boundary values. Also look up Boundary value.