Glossary
Search
(clear)
- factory acceptance testingAcceptance testing conducted at the site at which the product is developed and performed by employees of the supplier organization, to determine whether or not a component or system satisfies the requirements, normally including hardware as well as software.
- failA test is deemed to fail if its actual result does not match its expected result.
- failover testingTesting by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained (e.g., function availability or response times).(...)
- failureDeviation of the component or system from its expected delivery, service or result [after Fenton].
- failure modeThe physical or functional manifestation of a failure. For example, a system in failure mode may be characterized by slow operation, incorrect outputs, or complete termination of execution [IEEE 610].
- Failure Mode and Effect AnalysisA systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. See also Failure Mode, Effect and Criticality Analysis.
- Failure Mode, Effects, and Criticality AnalysisAn extension of FMEA, as in addition to the basic FMEA, it includes a criticality analysis, which is used to chart the probability of failure modes against the severity of their consequences. The result highlights failure modes with relatively high probability and severity of consequences,(...)
- failure rateThe ratio of the number of failures of a given category to a given unit of measure; e.g. failures per unit of time, failures per number of transactions, failures per number of computer runs [IEEE 610].
- falsch negatives ErgebnisEin result, das einen Fehlerzustand nicht anzeigt, obwohl der Fehlerzustand im Test object enthalten ist.
- falsch positives ErgebnisEin Testergebnis, das einen Fehlerzustand anzeigt, obwohl der Fehlerzustand nicht im Test object enthalten ist.
- false-fail resultSee false-positive result.
- false-negative resultA test result which fails to identify the presence of a defect that is actually present in the test object.
- false-pass resultSee false-negative result.
- false-positive resultA test result in which a defect is reported although no such defect actually exists in the test object.
- faultSee defect.
- fault attackDirected and focused attempt to evaluate a specific quality characteristic of a test object by attempting to force specific failures to occur. Usually focused on reliability or on security. See also negative testing, security attack
- fault densitySee defect density.
- Fault Detection PercentageSee Defect Detection Percentage.
- fault injectionThe process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault injection intended to mimic failures that might occur in the field. See also fault tolerance.
- fault maskingSee defect masking.
- fault seedingThe process of intentionally adding defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and estimating the number of remaining defects. Fault seeding is typically part of development (prerelease) testing and can be performed at(...)
- fault seeding toolA tool for seeding (i.e. intentionally inserting) faults in a component or system.
- fault toleranceThe capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified interface [ISO 9126]. See also reliability, robustness.
- Fault Tree AnalysisA technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose.
- FDPAcronym for Fault Detection Percentage.
- feasible pathA path for which a set of input values and preconditions exists which causes it to be executed.
- FeatureEin Attribut einer Komponente oder eines Systems, spezifiziert oder abgeleitet aus der Anforderungsspezifikation (z.B. Zuverlässigkeit, Gebrauchstauglichkeit oder Entwurfsrestriktionen). [Nach IEEE 1008]
- featureAn attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints) [after IEEE 1008].
- feature-driven developmentAn iterative and incremental software development process driven from a client-valued functionality (feature) perspective. Feature-driven development is mostly used in agile software development. See also agile software development.
- Feature-getriebene EntwicklungEin iterativ inkrementeller Softwareentwicklungsprozess, der mit Blick auf die Funktionalitäten mit Kundenwert (Features) betrieben wird. Feature-getriebene Entwicklung wird meist bei agiler Softwareentwicklung genutzt. Siehe auch agile Softwareentwicklung.