Glossar

AJAX progress indicator
Search (clear)
  • Acceptance 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.
  • A test is deemed to fail if its actual result does not match its expected result.
  • Testing 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).(...)
  • Deviation of the component or system from its expected delivery, service or result [after Fenton].
  • The 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].
  • A 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.
  • An 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,(...)
  • The 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].
  • Ein Ergebnis, das einen Fehlerzustand nicht anzeigt, obwohl der Fehlerzustand im Testobjekt enthalten ist.
  • Ein Testergebnis, das einen Fehlerzustand anzeigt, obwohl der Fehlerzustand nicht im Testobjekt enthalten ist.
  • See false-positive result.
  • A test result which fails to identify the presence of a defect that is actually present in the test object.
  • See false-negative result.
  • A test result in which a defect is reported although no such defect actually exists in the test object.
  • See defect.
  • Directed 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
  • See defect density.
  • See Defect Detection Percentage.
  • The 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.
  • See defect masking.
  • The 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(...)
  • A tool for seeding (i.e. intentionally inserting) faults in a component or system.
  • The 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.
  • A 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.
  • Acronym for Fault Detection Percentage.
  • A path for which a set of input values and preconditions exists which causes it to be executed.
  • Ein Attribut einer Komponente oder eines Systems, spezifiziert oder abgeleitet aus der Anforderungsspezifikation (z.B. Zuverlässigkeit, Gebrauchstauglichkeit oder Entwurfsrestriktionen). [Nach IEEE 1008]
  • An attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints) [after IEEE 1008].
  • An 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.
  • Ein 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.
Cookie Consent with Real Cookie Banner