Glossar
Search
(clear)
- defect categorySee defect type.
- defect densityThe number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms for that product, e.g. lines-of-code or function points).
- Defect Detection PercentageThe number of defects found by a test phase, divided by the number found by that test phase and any other means afterwards.
- defect managementThe process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact [after IEEE 1044].
- defect management committeeA cross-functional team of stakeholders who manage reported defects from initial detection to ultimate resolution (defect removal, defect deferral, or report cancellation). In some cases, the same team as the configuration control board.
- defect management toolA tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities. See also incident management tool.
- defect maskingAn occurrence in which one defect prevents the detection of another [after IEEE 610].
- defect reportA document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function [after IEEE 829].
- defect taxonomyA system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.
- defect tracking toolSee defect management tool.
- defect triage committeeSee defect management committee.
- defect typeAn element in a taxonomy of defects. Defect taxonomies can be identified with respect to a variety of considerations, including, but not limited to: Phase or development activity in which the defect is created, e.g., a specification error or a coding error, Characterization of defects, e.g.,(...)
- Defekt-TaxonomieSiehe Fehlertaxonomie.
- definition-use pairThe association of a definition of a variable with the subsequent use of that variable. Variable uses include computational (e.g. multiplication) or to direct the execution of a path (“predicate” use).
- Definition-VerwendungspaarDie Verknüpfung einer Definition einer Variablen (im Sinne einer Wertzuweisung) mit einer nachfolgenden Verwendung dieser Variablen in der dynamischen Ausführung. Variablenverwendungen können in Berechnungen sein (z.B. Multiplikation) oder die Ausführung von Pfaden steuern (prädikative Verwendung).
- deliverableAny (work) product that must be delivered to someone other that the (work) product’s author.
- demilitarized zoneA physical or logical subnetwork that contains and exposes an organization’s external-facing services to an untrusted network, commonly the Internet. See also network zone.
- Deming cycleAn iterative four-step problem-solving process, (plan-do-check-act), typically used in process improvement. [After Deming]
- DemingkreisEin iterativer Problemlösungsprozess, der aus vier Phasen besteht (planen, ausführen, überprüfen, umsetzen) und typischerweise in der Prozessverbesserung genutzt wird. [Nach Deming]
- denial of serviceA security attack that is intended to overload the system with requests such that legitimate requests cannot be serviced.
- design-based testingAn approach to testing in which test case are designed based on the architecture and/or detailed design of a component or system (e.g. tests of interfaces between components or systems).
- desk checkingTesting of software or a specification by manual simulation of its execution. See also static testing.
- development testingFormal or informal testing conducted during the implementation of a component or system, usually in the development environment by developers [after IEEE 610]. See also component testing.
- deviationSee incident.
- deviation reportSee incident report.
- Diagnose (IDEAL)Die Phase im IDEAL-Modell, in welcher der derzeitige Stand bestimmt wird (in Relation zum angestrebten Stand). Die Diagnose-Phase enthält die Aktivitäten: derzeitigen und angestrebten Stand beschreiben und Empfehlungen entwickeln. Siehe auch IDEAL.
- diagnosing (IDEAL)The phase within the IDEAL model where it is determined where one is, relative to where one wants to be. The diagnosing phase consists of the activities: characterize current and desired states and develop recommendations. See also IDEAL.
- DienstblockadeEin Sicherheitsangriff mit dem Ziel, das System mit Anfragen so zu überlasten, dass es berechtigte Anfragen nicht mehr bedienen kann.
- dirty testingSee negative testing.
- discount usability testingA test strategy for usability testing that puts emphasis on keeping costs down without compromising too much on the quality of the usability evaluation.