defect management tool:A 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 d re-testing of defects and provide reporting facilities.See also incident management tool defect report:A 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 taxonomy:A system of(hierarchical)categories designed to be a useful aid for reproducibly classifying defects. defect tracking tool:See defect management tool ultiplication)or to direct the execution of a path("predicate"use). omputational deliverable:Any (work)product that must be delivered to someone other than the (work) product's author. design-based testing:An to testing in which test csesare architecture andor detailed dsign of a component or system (eg tests of interfaces desk checking:Testing of software or specification by manual simulation of its execution. See also static analysis. development testing:Formal or informal testing conducted during the implementation of a component or system,usually in the development environment by developers.[After IEEE 6101 deviation:See incident. deviation report:See incident report dirty testing:See negative testing. documentation testing:Testing the quality of the documentation,e.g user guide or installation guide. domain:The set from which valid input and/or output values can be selected. dynamic analysis:The process of evaluating behavior.e. g.memory performance,CPU usage,of a system or component during execution.[After IEEE 610] dynamic analysis tool:A tool that provides run-time information on the state of the software code.These tools are most commonly used to identify unassigned pointers,check pointer arithmetic and to monitor the allocation,use and de-allocation of memory and to flag memory leaks. arison of execution to dynamic testing:Testing that involves the execution of the software of a component or system.16 defect management tool: A 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 masking: An occurrence in which one defect prevents the detection of another. [After IEEE 610] defect report: A 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 taxonomy: A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects. defect tracking tool: See defect management tool. definition-use pair: The association of the definition of a variable with the use of that variable. Variable uses include computational (e.g. multiplication) or to direct the execution of a path (“predicate” use). deliverable: Any (work) product that must be delivered to someone other than the (work) product’s author. design-based testing: An approach to testing in which test cases 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 checking: Testing of software or specification by manual simulation of its execution. See also static analysis. development testing: Formal or informal testing conducted during the implementation of a component or system, usually in the development environment by developers. [After IEEE 610] deviation: See incident. deviation report: See incident report. dirty testing: See negative testing. documentation testing: Testing the quality of the documentation, e.g. user guide or installation guide. domain: The set from which valid input and/or output values can be selected. driver: A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. [After TMap] dynamic analysis: The process of evaluating behavior, e.g. memory performance, CPU usage, of a system or component during execution. [After IEEE 610] dynamic analysis tool: A tool that provides run-time information on the state of the software code. These tools are most commonly used to identify unassigned pointers, check pointer arithmetic and to monitor the allocation, use and de-allocation of memory and to flag memory leaks. dynamic comparison: Comparison of actual and expected results, performed while the software is being executed, for example by a test execution tool. dynamic testing: Testing that involves the execution of the software of a component or system