Chapter 4 Flashcards
defect
A flaw in a component or system that can cause the component or system to fail to perform its required function—for example, an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system
failure
Deviation of the component or system from its expected delivery, service, or result
phase containment
The percentage of defects that are removed in the same phase of the software lifecycle in which they were introduced
priority
The level of (business) importance assigned to an item such as, for example, a defect
root cause
A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed
severity
The degree of impact that a defect has on the development or operation of a component or system
anomaly
Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, and so on or from someone’s perception or experience. Anomalies may be found during, but not limited to, reviewing, testing, analysis, compilation, or use of software products or applicable documentation
error
A human action that produces an incorrect result
incident
Any event occurring that requires investigation
defect management committee
A 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
false-negative result
A test result that fails to identify the presence of a defect that is actually present in the test object
false-positive result
A test result in which a defect is reported although no such defect actually exists in the test object
