Glossary of software testing terms

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

abnormal end

Ref: After ISO 24765

Source: ISTQB

The unintended termination of the execution of a component or system prior to completion.
A/B testing

Ref: After ISO 29119-11

Source: ISTQB

A statistical testing approach to determine which of two systems or components performs better.
abuse case

See also: use case

Source: ISTQB

A use case in which some actors with malicious intent are causing harm to the system or to other actors.
Acceptance

Source: IREB

The process of assessing whether a ↑system satisfies all its ↑requirements.
acceptance criteria

Ref: ISO 24765

Source: ISTQB

The criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.
Acceptance criteria

Source: IREB

In agile: Criteria that the implementation of a ↑user story must satisfy in order to be accepted by the ↑stakeholders.
Acceptance test

Source: IREB

A test that assesses whether a ↑system satisfies its ↑requirements.
acceptance test-driven development (ATDD)

Source: ISTQB

A collaborative approach to development in which the team and customers are using the customers own domain language to understand their requirements, which forms the basis for testing a component or system.
acceptance testing

See also: Benutzerabnahmetest

Source: ISTQB

A test level that focuses on determining whether to accept the system.
accessibility

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use.
accountability

Ref: After ISO 25010

Source: ISTQB

The degree to which the actions of an entity can be traced uniquely to that entity.
account harvesting

Source: ISTQB

The process of obtaining user account information based on trial and error with the intention of using that information in a security attack.
Activity

Source: IREB

An action or a set of actions that a person or group performs to accomplish a ↑task.
Activity diagram

Source: IREB

A diagram type in ↑UML which models the flow of actions in some part of a ↑system, including ↑data flows and areas of responsibility where necessary.
Activity model

Source: IREB

A ↑model of the flow of actions in some part of a ↑system.
Actor

Source: IREB

A person in some ↑role, a ↑system or a technical device in the context of a subject under consideration that interacts with that subject.
actual result

Source: ISTQB

The behavior produced/observed when a component or system is tested.
adaptability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be adapted for different or evolving hardware, software or other operational or usage environments.
ad hoc review

Ref: After ISO 20246

Source: ISTQB

A review technique performed informally without a structured process.
adversarial example

Ref: ISO 29119-11

Source: ISTQB

An input to an ML model created by applying small perturbations to a working example that results in the model outputting an incorrect result with high confidence.
adversarial testing

Ref: After ISO 29119-11

Source: ISTQB

A test technique based on the attempted creation and execution of adversarial examples to identify defects in an ML model.
Agile

Source: IREB

In general: (a) Able to move quickly and easily. (b) Quick, smart, and clever. 2. In software development: A development approach which builds a product ↑incrementally by dividing work into ↑iterations of fixed duration (↑timeboxes).
Agile Manifesto

Source: ISTQB

A statement on the values that underpin Agile software development. The values are: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan.
Agile software development

Source: ISTQB

A group of software development methodologies based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.
agile testing quadrants

Source: ISTQB

A classification model of test types/levels in four quadrants, relating them to two dimensions of test goals: supporting the team vs. critiquing the product, and technology-facing vs. business-facing.
alpha testing

See also: Beta.Test

Source: ISTQB

A type of acceptance testing performed in the developer's test environment by roles outside the development organization.
Ambiguity

Source: IREB

The contrary of →unambiguity
analytical test strategy

Source: ISTQB

A test strategy whereby the test team analyzes the test basis to identify the test conditions to cover.
analyzability

Ref: After ISO 25010

Source: ISTQB

The degree to which an assessment can be made for a component or system of either the impact of one or more intended changes, the diagnosis of deficiencies or causes of failures, or the identification of parts to be modified.
anomaly

Ref: ISO 24765

Source: ISTQB

Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc., 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.
anti-malware

See also: malware

Source: ISTQB

Software that is used to detect and inhibit malware.
anti-pattern

Source: ISTQB

Repeated action, process, structure or reusable solution that initially appears to be beneficial and is commonly used but is ineffective and/or counterproductive in practice.
API testing

Source: ISTQB

Testing performed by submitting requests to the test object using its application programming interface.
Application domain

Source: IREB

Those parts of the real world that are relevant for determining the ↑context of a ↑system.
application programming interface (API)

Ref: Nach ISO 29119-1

See also: Gebrauchstauglichkeit

Source: ISTQB

A type of interface in which the components or systems involved exchange information in a defined formal structure.
appropriateness recognizability

Ref: After ISO 25010

Source: ISTQB

The degree to which users can recognize whether a component or system is appropriate for their needs.
Artifact

Source: IREB

Synonym for ↑work product.
Association

Source: IREB

In UML: A relationship between two ↑classes in a ↑UML ↑class model.
atomic condition

Source: ISTQB

A condition that does not contain logical operators.
attacker

See also: hacker

Source: ISTQB

A person or process that attempts to access data, functions or other restricted areas of the system without authorization, potentially with malicious intent.
attack vector

Source: ISTQB

A path or means by which an attacker can gain access to a system for malicious purposes.
Attribute

Source: IREB

A characteristic property of an ↑entity or an ↑object.
(auch: Erfüllung)

Source: IREB

Compliance* The adherence of a ↑work product to ↑standards, conventions, regulations, laws, or similar prescriptions.
audio testing

Source: ISTQB

Testing to determine if the game music and sound effects will engage the user in the game and enhance the game play.
audit

Ref: After ISO 24765

Source: ISTQB

An independent examination of a work product or process performed by a third party to assess whether it complies with specifications, standards, contractual agreements, or other criteria.
authentication

See also: authorization

Source: ISTQB

A procedure determining whether a person or a process is, in fact, who or what it is declared to be.
authenticity

Ref: ISO 25010

Source: ISTQB

The degree to which the identity of a subject or resource can be proved to be the one claimed.
authorization

See also: authentication

Source: ISTQB

Permission given to a user or process to access resources.
automation code defect density

See also: defect density

Source: ISTQB

Defect density of a component of the test automation code.
automotive safety integrity level (ASIL)

Ref: ISO 26262

See also: safety integrity level

Source: ISTQB

One of four levels that specify the item's or element's necessary requirements of ISO 26262 and safety measures to avoid an unreasonable residual risk.
automotive SPICE (ASPICE)

Ref: ISO 33002

Source: ISTQB

A process reference model and an associated process assessment model in the automotive industry.
availability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system is operational and accessible when required for use.
Backlog

Source: IREB

Product backlog, → sprint backlog
back-to-back testing

Ref: Spillner

Source: ISTQB

Testing to compare two or more variants of a test item or a simulation model of the same test item by executing the same test cases on all variants and comparing the results.
Baseline

Source: IREB

A stable, change-controlled ↑configuration of ↑work products.
Behavior*

Source: IREB

The way in which a ↑system reacts to stimuli, changes its state and produces observable results.
behavior-driven development (BDD)

Source: ISTQB

A collaborative approach to development in which the team is focusing on delivering expected behavior of a component or system for the customer, which forms the basis for testing.
Behavior model*

Source: IREB

A ↑model describing the ↑behavior of a ↑system, e.g., by a ↑state machine.
Benutzungsschnittstelle.

Source: ISTQB

GUI testing
Berührung erkennen können.

Source: ISTQB

proximity-based testing
beta testing

Source: ISTQB

A type of acceptance testing performed at an external site to the developer's test environment by roles outside the development organization.
black-box test technique

Source: ISTQB

A test technique based on an analysis of the specification of a component or system.
botnet

Source: ISTQB

A network of compromised computers, called bots or robots, which is controlled by a third party and used to transmit malware or spam, or to launch attacks.
boundary value

Source: ISTQB

A minimum or maximum value of an ordered equivalence partition.
boundary value analysis

See also: Grenzwert

Source: ISTQB

A black-box test technique in which test cases are designed based on boundary values.
branch

Source: ISTQB

A transfer of control from a decision point.
Branch

Source: IREB

A line of ↑configurations or ↑work product ↑versions that forks away from the main line (or from another branch) at some point in time.
Breitband-Delphi-Verfahrens, bei der das Team einen Stapel an Karten mit vorgegebenen Werten für die Schätzung verwendet.

Ref: Mountain Goat Software

Source: ISTQB

planning poker
bug hunting

Source: ISTQB

An approach to testing in which gamification and awards for defects found are used as a motivator.
build verification test (BVT)

Source: ISTQB

An automated test that validates the integrity of each new build and verifies its key/core functionality, stability, and testability.
Burndown chart

Source: IREB

A diagram plotting the work items that remain to accomplish on a time scale.
Business requirement

Source: IREB

A ↑requirement stating a business ↑goal, objective or need of an organization.
Capability Maturity Model Integration (CMMI)

Ref: CMMI

Source: ISTQB

A framework that describes the key elements of an effective product development and maintenance process. The Capability Maturity Model Integration covers best-practices for planning, engineering and managing product development and maintenance.
capacity

Ref: After ISO 25010

Source: ISTQB

The degree to which the maximum limits of a component or system parameter meet requirements.
capacity testing

Source: ISTQB

Testing to evaluate the capacity of a system.
capture/playback

Source: ISTQB

A test automation approach in which inputs to the test object are recorded during manual testing to generate automated test scripts that can be executed later.
Cardinality

Source: IREB

In modeling: The minimum and maximum number of ↑objects in a relationship. In mathematics: The number of elements in a set.
cause-effect diagram

Ref: After Juran

Source: ISTQB

A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or potential defect or failure are organized in categories and subcategories in a horizontal tree-structure, with the (potential) defect or failure as the root node.
cause-effect graph

Source: ISTQB

A graphical representation of logical relationships between inputs (causes) and their associated outputs (effects).
cause-effect graphing

Source: ISTQB

A black-box test technique in which test cases are designed from cause-effect graphs.
certification

Source: ISTQB

The process of confirming that a component, system or person complies with specified requirements.
Change control board

Abbreviation: CCB

Source: IREB

A committee of ↑customer and ↑supplier representatives that decides on ↑change requests.
Change management

Source: IREB

A controlled way to effect or deny a requested change of a ↑work product.
change-related testing

Source: ISTQB

A type of testing initiated by modification to a component or system.
Change request

Source: IREB

In RE: A well-argued request for changing one or more ↑baselined ↑requirements.
checklist-based review

Ref: ISO 20246

Source: ISTQB

A review technique guided by a list of questions or required attributes.
checklist-based testing

Source: ISTQB

An experience-based test technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.
Class

Source: IREB

A representation of a set of ↑objects of the same kind by describing the structure of the objects, the ways they can be manipulated and how they behave.
Class diagram

Source: IREB

A diagrammatic representation of a ↑class model.
classification tree

See also: Klassifikationsbaumverfahren

Source: ISTQB

A tree diagram representing test data domains of a test object.
classification tree technique

Ref: Grochtmann

See also: kombinatorisches Testen

Source: ISTQB

A black-box test technique in which test cases are designed using a classification tree.
Class model

Source: IREB

A model consisting of a set of ↑classes and relationships between them.
CLI testing

Source: ISTQB

Testing performed by submitting commands to the software under test using a dedicated command-line interface.
closed-loop-system

Ref: Bakshi

Source: ISTQB

A system in which the controlling action or input is dependent on the output or changes in output.
code injection

See also: malware scanning, SQL injection

Source: ISTQB

A type of security attack performed by inserting malicious code at an interface into an application to exploit poor handling of untrusted data.
coding standard

Ref: ISO 24765

Source: ISTQB

A standard that describes the characteristics of a design or a design description of data or program components.
coexistence

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can perform its required functions while sharing an environment and resources with other components or systems without a negative impact on any of them.
combinatorial testing

See also: pairwise testing, classification tree technique

Source: ISTQB

A black-box test technique in which test cases are designed to exercise specific combinations of values of several parameters
command-line interface (CLI)

Source: ISTQB

A type of interface in which the information is passed in form of command lines.
commercial off-the-shelf (COTS)

Source: ISTQB

A type of product developed in an identical format for a large number of customers in the general market.
Commonality

Source: IREB

The parts of a ↑product line that are shared by all its members.
Completeness* (of requirements)

Source: IREB

1. For a single ↑requirement: The degree to which the specification of a requirement is self-contained. 2. For a ↑work product covering multiple requirements: The degree to which the work product contains all known requirements that are relevant in the scope of this work product.
complexity

See also: cyclomatic complexity

Source: ISTQB

The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.
compliance

Ref: IREB Glossary

Source: ISTQB

Adherence of a work product to standards, conventions or regulations in laws and similar prescriptions.
compliance testing

Source: ISTQB

Testing to determine the compliance of the component or system.
component

Source: ISTQB

A part of a system that can be tested in isolation.
Component

Source: IREB

In general: A delimitable part of a ↑system. In software architecture: An encapsulated set of coherent ↑objects or ↑classes that jointly achieve some purpose. In testing: A part of a ↑system that can be tested in isolation.
component integration testing

Source: ISTQB

Testing in which the test items are interfaces and interactions between integrated components.
component testing

Source: ISTQB

A test level that focuses on individual hardware or software components.
Composition (in a technical context)

Source: IREB

An ↑item that is composed of a set of items; forming a whole-part relationship. The act of composing a whole from a set of parts.
computer forensics

Source: ISTQB

The practice of determining how a security attack has succeeded and assessing the damage caused.
concurrency

Source: ISTQB

The simultaneous execution of multiple independent threads by a component or system.
concurrency testing

Source: ISTQB

Testing to evaluate if a component or system involving concurrency behaves as specified.
condition coverage

Source: ISTQB

The coverage of condition outcomes.
condition testing

Source: ISTQB

A white-box test technique in which test cases are designed to exercise outcomes of atomic conditions.
confidence interval

Source: ISTQB

In managing project risks, the period of time within which a contingency action must be implemented in order to be effective in reducing the impact of the risk.
confidentiality

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system ensures that data are accessible only to those authorized to have access.
Configuration

Source: IREB

A consistent set of logically coherent ↑items. The items are individually identifiable ↑work products or parts of work products in at most one ↑version per item.
configuration item

Ref: ISO 24765

Source: ISTQB

An aggregation of work products that is designated for configuration management and treated as a single entity in the configuration management process.
confirmation testing

Source: ISTQB

A type of change-related testing performed after fixing a defect to confirm that a failure caused by that defect does not reoccur.
Conformity*

Source: IREB

The degree to which a ↑work product conforms to regulations given in some ↑standard.
connectivity

Ref: After ISO 2382

Source: ISTQB

The degree to which a component or system can connect to other components or systems.
Consistency* (of requirements)

Source: IREB

The degree to which a set of ↑requirements is free of contradicting statements.
Constraint*(in RE)

Source: IREB

A ↑requirement that limits the solution space beyond what is necessary for meeting the given ↑functional requirements and ↑quality requirements.
consultative test strategy

Source: ISTQB

A test strategy whereby the test team relies on the input of one or more key stakeholders to determine the details of the strategy.
Context

Source: IREB

In general: The network of thoughts and meanings needed for understanding phenomena or utterances. Especially in RE: The part of a ↑system’s environment being relevant for understanding the system and its ↑requirements.
Context boundary

Source: IREB

The boundary between the ↑context of a ↑system and those parts of the ↑application domain that are irrelevant for the ↑system and its ↑requirements.
Context diagram

Source: IREB

A diagrammatic representation of a ↑context model. In ↑Structured Analysis, the context diagram is the root of the ↑dataflow diagram hierarchy.
Context model

Source: IREB

A ↑model describing a ↑system in its ↑context.
context of use

Ref: ISO 9241-11

Source: ISTQB

Users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a software product is used.
continuous integration

Source: ISTQB

An automated software development procedure that merges, integrates and tests all changes as soon as they are committed.
continuous testing

Source: ISTQB

An approach that involves a process of testing early, testing often, test everywhere, and automate to obtain feedback on the business risks associated with a software release candidate as rapidly as possible.
contractual acceptance testing

Source: ISTQB

A type of acceptance testing performed to verify whether a system satisfies its contractual requirements.
control chart

Source: ISTQB

A statistical process control tool used to monitor a process and determine whether it is statistically controlled. It graphically depicts the average value and the upper and lower control limits (the highest and lowest values) of a process.
control flow

Ref: After ISO 29119-4

Source: ISTQB

The sequence in which operations are performed by a business process, component or system.
Control flow

Source: IREB

The order in which a set of actions is executed.
control flow analysis

Source: ISTQB

A type of static analysis based on a representation of unique paths for executing a component or system.
control flow testing

Source: ISTQB

A white-box test technique in which test cases are designed based on control flows.
convergence metric

Source: ISTQB

A metric that shows progress toward a defined criterion, e.g., convergence of the total number of tests executed to the total number of tests planned for execution.
Correctness

Source: IREB

The degree to which the information contained in a ↑work product is provably true.
cost of quality

Source: ISTQB

The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure costs.
coverage

Ref: After ISO 29119-1

Source: ISTQB

The degree to which specified coverage items have been determined or have been exercised by a test suite expressed as a percentage.
coverage criteria

See also: coverage item

Source: ISTQB

The criteria to define the coverage items required to reach a test objective.
coverage item

Ref: After ISO 29119-1

Source: ISTQB

An attribute or combination of attributes derived from one or more test conditions by using a test technique.
Critical Testing Processes (CTP)

Ref: CTP

See also: content-based model

Source: ISTQB

A content-based model for test process improvement built around twelve critical processes. These include highly visible processes, by which peers and management judge competence and mission-critical processes in which performance affects the company's profits and reputation.
cross-browser compatibility

Source: ISTQB

The degree to which a website or web application can function across different browsers and degrade gracefully when browser features are absent or lacking.
cross-site scripting (XSS)

Ref: NIST.IR.7298

Source: ISTQB

A vulnerability that allows attackers to inject malicious code into an otherwise benign website.
crowd testing

Source: ISTQB

An approach to testing in which testing is distributed to a large group of testers.
Customer*

Source: IREB

A person or organization who receives a ↑system, a ↑product or a ↑service.
Customer requirements specification

Source: IREB

A coarse description of the required capabilities of a ↑system from the ↑customer’s perspective.
custom tool

Source: ISTQB

A software tool developed specifically for a set of users or customers.
cyclomatic complexity

Ref: After McCabe

Source: ISTQB

The maximum number of linear, independent paths through a program.
dashboard

See also: corporate dashboard, scorecard

Source: ISTQB

A representation of dynamic measurements of operational performance for some organization or activity, using metrics represented via metaphors such as visual dials, counters, and other devices resembling those on the dashboard of an automobile, so that the effects of events or activities can be easily understood and related to operational goals.
data-driven testing

Source: ISTQB

A scripting technique that uses data files to contain the test data and expected results needed to execute the test scripts.
Data flow

Source: IREB

A sequence of data items flowing from a producer to a consumer.
data flow analysis

Source: ISTQB

A type of static analysis based on the lifecycle of variables.
Data flow diagram

Abbreviation: DFD

Source: IREB

A diagrammatic representation of a ↑data flow model.
Data flow model

Source: IREB

A model that describes the ↑functionality of a ↑system by ↑activities, data stores and ↑data flows.
data obfuscation

Source: ISTQB

Data transformation that makes it difficult for a human to recognize the original data.
data privacy

Source: ISTQB

The protection of personally identifiable information or otherwise sensitive information from undesired disclosure.
debugging

Source: ISTQB

The process of finding, analyzing and removing the causes of failures in a component or system.
decision

Ref: After ISO 29119-1

Source: ISTQB

A type of statement in which a choice between two or more possible outcomes controls which set of actions will result.
decision coverage

Source: ISTQB

The coverage of decision outcomes.
Decision table

Source: IREB

A tabular representation of a complex decision, specifying which actions to perform for the possible combinations of condition values.
decision table testing

See also: Entscheidungstabelle

Source: ISTQB

A black-box test technique in which test cases are designed to exercise the combinations of conditions and the resulting actions shown in a decision table.
decision testing

Source: ISTQB

A white-box test technique in which test cases are designed to execute decision outcomes.
defect

Ref: After ISO 24765

Source: ISTQB

An imperfection or deficiency in a work product where it does not meet its requirements or specifications.
Defect*

Source: IREB

An imperfection or deficiency in a ↑work product that impairs its intended use.
defect-based test technique

See also: Fehlertaxonomie

Source: ISTQB

A test technique in which test cases are developed from what is known about a specific defect type.
defect density

Ref: After ISO 24765

Source: ISTQB

The number of defects per unit size of a work product.
Defect Detection Percentage (DDP)

See also: escaped defect

Source: ISTQB

The number of defects found by a test level, divided by the number found by that test level and any other means afterwards.
defect management

Source: ISTQB

The process of recognizing, recording, classifying, investigating, resolving and disposing of defects.
defect management committee

Source: ISTQB

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
defect report

Source: ISTQB

Documentation of the occurrence, nature, and status of a defect.
defect taxonomy

Source: ISTQB

A list of categories designed to identify and classify defects.
definition-use pair

Source: ISTQB

The association of a definition of a variable with the subsequent use of that variable.
demilitarized zone (DMZ)

See also: network zone

Source: ISTQB

A physical or logical subnetwork that contains and exposes an organization's external-facing services to an untrusted network, commonly the Internet.
denial of service (DoS)

Source: ISTQB

A security attack that is intended to overload the system with requests such that legitimate requests cannot be serviced.
der Testteilnehmer zu verstehen.

Source: ISTQB

think aloud usability testing
Design

Source: IREB

1. A plan or drawing produced to show how something will look, function or be structured before it is made. 2. The activity of creating a design. 3. A decorative pattern [This meaning does not apply in the software engineering ↑domain].

Note: 1. In software product development, we distinguish between creative design which shapes the look and feel of the product, i.e., its perceivable form, function and quality, and technical design (also called software design) which determines the inner structure of the product, in particular the software architecture. 2. The creative design of products is also called product design. 3. The creative design of digital solutions is called digital design.
device-based testing

Source: ISTQB

A type of testing in which test suites are executed on physical or virtual devices.
Document template

Source: IREB

A template providing a predefined skeleton structure for a document. (→ requirements template)
Domain

Source: IREB

A range of relevant things (for some given matter); for example, an ↑application domain.
Domain model

Source: IREB

A ↑model describing phenomena in an ↑application domain.

Note: 1. In RE, domain models are created with the intention to understand the ↑application domain in which a planned ↑system will be situated. 2. Static domain models specify (business) objects and their relationships in a ↑domain of interest. 3. Domain story models specify visual stories about how actors interact with devices, artifacts, and other items in a ↑domain.
Domain requirement

Source: IREB

A ↑domain property in the ↑context of a ↑system that is required to hold.
driver

Source: ISTQB

A temporary component or tool that replaces another component and controls or calls a test item in isolation.
dynamic analysis

Ref: After ISO 24765

Source: ISTQB

The process of evaluating a component or system based on its behavior during execution.
dynamic testing

Ref: After ISO 29119-1

See also: statischer Test

Source: ISTQB

Testing that involves the execution of the test item.
effectiveness

Ref: ISO 9241

See also: efficiency

Source: ISTQB

The extent to which correct and complete goals are achieved.
Effectiveness

Source: IREB

The degree to which an ↑item produces the intended results.
efficiency

Ref: IREB Glossary

Source: ISTQB

The degree to which resources are expended in relation to results achieved.
Efficiency

Source: IREB

The degree to which resources are expended in relation to results achieved.
Elaboration (of requirements)

Source: IREB

An umbrella term for requirements ↑elicitation, ↑negotiation and ↑validation.
Elicitation (of requirements)

Source: IREB

→ Requirements elicitation
emulator

See also: simulator

Source: ISTQB

Software used during testing that mimics the behavior of hardware.
encryption

Source: ISTQB

The process of encoding information so that only authorized parties can retrieve the original information, usually by means of a specific decryption key or process.
end-to-end testing

Source: ISTQB

A type of testing in which business processes are tested from start to finish under production-like circumstances.
endurance testing

Source: ISTQB

Testing to determine the stability of a system under a significant load over a significant period of time within the system's operational context.
End user

Source: IREB

→ User
Entity

Source: IREB

In general: Anything which is perceivable or conceivable (→ item). In entity-relationship-modeling: an individual ↑item which has an identity and does not depend on another item (→ object).
Entity-relationship diagram

Abbreviation: ERD

Source: IREB

A diagrammatic representation of an ↑entity-relationship model.
Entity-relationship model

Abbreviation: ER Model

Source: IREB

A ↑model of data that are relevant for a ↑system or of the data of an ↑application domain, consisting of a set of entity types that are each characterized by ↑attributes and linked by relationships.
entry criteria

Ref: Gilb and Graham

See also: exit criteria

Source: ISTQB

The set of conditions for officially starting a defined task.
environment model

Ref: Wallentowitz

Source: ISTQB

An abstraction of the real environment of a component or system including other components, processes, and environment conditions, in a real-time simulation.
epic

Ref: Agile Alliance

Source: ISTQB

A large user story that cannot be delivered as defined within a single iteration or is large enough that it can be split into smaller user stories.
Epic

Source: IREB

In agile development: An abstract description of a ↑stakeholder need which is larger than what can be implemented in a single ↑iteration.
error

Ref: ISO 24765

Source: ISTQB

A human action that produces an incorrect result.
Error

Source: IREB

A human action that produces an incorrect result. A discrepancy between an observed ↑behavior or result and the specified behavior or result.
error guessing

Ref: ISO 29119-1

Source: ISTQB

A test technique in which tests are derived on the basis of the tester's knowledge of past failures, or
escaped defect

Source: ISTQB

A defect that was not detected by a testing activity that is supposed to find that defect.
ethical hacker

Source: ISTQB

A security tester using hacker techniques.
European Foundation for Quality Management excellence model (EFQM)

Source: ISTQB

A non-prescriptive framework for an organization's quality management system based on five 'Enabling' criteria and four 'Results' criteria.
Evolutionary prototype

Source: IREB

A pilot system forming the core of a ↑system to be developed.
exhaustive testing

Source: ISTQB

A test approach in which the test suite comprises all combinations of input values and preconditions.
exit criteria

Ref: After Gilb and Graham

Source: ISTQB

The set of conditions for officially completing a defined task.
expected result

Ref: After ISO 29119-1

Source: ISTQB

The observable predicted behavior of a test item under specified conditions based on its test basis.
experience-based testing

Source: ISTQB

Testing based on the tester's experience, knowledge and intuition.
experience-based test technique

Source: ISTQB

A test technique only based on the tester's experience, knowledge and intuition.
expert usability review

See also: informal review

Source: ISTQB

An informal usability review in which the reviewers are experts. Experts can be usability experts or subject matter experts, or both.
Exploratory prototype

Source: IREB

A throwaway ↑prototype used to create shared understanding, clarify ↑requirements or validate requirements.
exploratory testing

Ref: After ISO 29119-1

Source: ISTQB

An approach to testing whereby the testers dynamically design and execute tests based on their knowledge, exploration of the test item and the results of previous tests.
failed

See also: bestanden

Source: ISTQB

The status of a test result in which the actual result does not match the expected result.
failover

Source: ISTQB

The backup operational mode in which the functions of a system that becomes unavailable are assumed by a secondary system.
failure

Ref: After ISO 24765

Source: ISTQB

An event in which a component or system does not perform a required function within specified limits.
failure mode

Ref: ISO 24765

Source: ISTQB

The physical or functional manifestation of a failure.
Failure Mode and Effect Analysis (FMEA)

See also: Failure Mode, Effect and Criticality Analysis

Source: ISTQB

A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence.
failure rate

Ref: ISO 24765

Source: ISTQB

The ratio of the number of failures of a given category to a given unit of measure.
false-negative result

Source: ISTQB

A test result which fails to identify the presence of a defect that is actually present in the test object.
false-positive result

Source: ISTQB

A test result in which a defect is reported although no such defect actually exists in the test object.
fault injection

Source: ISTQB

The process of intentionally adding a defect to a component or system to determine whether it can detect and possibly recover from it.
fault seeding

Ref: After ISO 24765

See also: Zuverlässigkeit, Robustheit

Source: ISTQB

The process of intentionally adding defects to a component or system to monitor the rate of detection and removal, and to estimate the number of defects remaining.
fault tolerance

Ref: After ISO 25010

See also: Zuverlässigkeit, Robustheit

Source: ISTQB

The degree to which a component or system operates as intended despite the presence of hardware or software faults.
Fault tolerance

Source: IREB

The capability of a ↑system to operate as intended despite the presence of (hardware or software) ↑faults.
Fault Tree Analysis (FTA)

Source: ISTQB

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.
Feasibility (of a requirement)

Source: IREB

The degree to which a ↑requirement for a ↑system can be implemented under existing ↑constraints.
Feature

Source: IREB

A distinguishing characteristic of a ↑system that provides value for ↑stakeholders.
Feature diagram

Source: IREB

A diagrammatic representation of a ↑feature model.
feature-driven development

See also: Agile software development

Source: ISTQB

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.
Feature model

Source: IREB

A ↑model describing the variable features of a ↑product line, including their relationships and dependencies.
field testing

Source: ISTQB

A type of testing conducted to evaluate the system behavior under productive connectivity conditions in the field.
finding

Source: ISTQB

A result of an evaluation that identifies some important issue, problem, or opportunity.
firewall

Source: ISTQB

A component or set of components that controls incoming and outgoing network traffic based on predetermined security rules.
follow-up test case

Source: ISTQB

A test case generated by applying a metamorphic relation to a source test case during metamorphic
formal review

Ref: ISO 20246

Source: ISTQB

A type of review that follows a defined process with a formally documented output.
formative evaluation

See also: summative evaluation

Source: ISTQB

A type of evaluation designed and used to improve the quality of a component or system, especially when it is still being designed.
Form template

Source: IREB

A template providing a form with predefined fields to be filled-in. (→ requirements template)
functional appropriateness

Ref: ISO 25010

Source: ISTQB

The degree to which the functions facilitate the accomplishment of specified tasks and objectives.
functional completeness

Ref: ISO 25010

Source: ISTQB

The degree to which the set of functions covers all the specified tasks and user objectives.
functional correctness

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system provides the correct results with the needed degree of precision.
Functionality*

Source: IREB

The capabilities of a ↑system as stated by its ↑functional requirements.
Functional requirement

Source: IREB

A ↑requirement concerning a result or ↑behavior that shall be provided by a function of a ↑system.
functional safety

Ref: ISO 26262

Source: ISTQB

The absence of unreasonable risk due to hazards caused by malfunctioning behavior of Electric/Electronic(E/E) - Systems.
functional suitability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system provides functions that meet stated and implied needs when used under specified conditions.
functional testing

Ref: After ISO 24765

Source: ISTQB

Testing performed to evaluate if a component or system satisfies functional requirements.
fuzz testing

Source: ISTQB

A software testing technique used to discover security vulnerabilities by inputting massive amounts of random data, called fuzz, to the component or system.
generic test automation architecture

Source: ISTQB

Representation of the layers, components, and interfaces of a test automation architecture, allowing for a structured and modular approach to implement test automation.
Glossary

Source: IREB

A collection of definitions of terms that are relevant in some ↑domain.
Goal*

Source: IREB

A desired state of affairs (that a ↑stakeholder wants to achieve).
Goal model*

Source: IREB

A ↑model representing a set ↑goals, sub-goals and the relationships between them.
graphical user interface (GUI)

Source: ISTQB

A type of interface that allows users to interact with a component or system through graphical icons and visual indicators.
hacker

See also: attacker

Source: ISTQB

A person or organization who is actively involved in security attacks, usually with malicious intent.
hardware in the loop (HiL)

Ref: Automotive SPICE

Source: ISTQB

Dynamic testing performed using real hardware with integrated software in a simulated environment.
hashing

Source: ISTQB

Transformation of a variable length string of characters into a usually shorter fixed-length value or key. Hashed values, or hashes, are commonly used in table or database lookups. Cryptographic hash functions are used to secure data.
heuristic

Source: ISTQB

A generally recognized rule of thumb that helps to achieve a goal.
heuristic evaluation

Source: ISTQB

An evaluation of a work product that uses a heuristic.
high-level test case

See also: low-level test case

Source: ISTQB

A test case with abstract preconditions, input data, expected results, postconditions, and actions (where applicable).
Homonym

Source: IREB

A term looking identical to another term but having a different meaning.
human-centered design

Ref: ISO 9241-210

Source: ISTQB

An approach to design that aims to make software products more usable by focusing on the use of the software products and applying human factors, ergonomics, and usability knowledge and techniques.
hyperlink

Source: ISTQB

A pointer within a web page that leads to other web pages.
hyperlink test tool

Source: ISTQB

A tool used to check that no broken hyperlinks are present on a website.
IDEAL

Source: ISTQB

An organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. The IDEAL model is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning.
impact analysis

Ref: After ISO 24765

Source: ISTQB

The identification of all work products affected by a change, including an estimate of the resources needed to accomplish the change.
incremental development model

Ref: After PMBOK

Source: ISTQB

A type of software development lifecycle model in which the component or system is developed through a series of increments.
Increment* (in software development)

Source: IREB

An addition to a ↑system under development that extends, enhances or refactors (↑refactoring) the existing parts of the system.
independence of testing

Ref: After DO-178C

Source: ISTQB

Separation of responsibilities, which encourages the accomplishment of objective testing.
independent test lab (ITL)

Source: ISTQB

An organization responsible to test and certify that the software, hardware, firmware, platform, and operating system follow all the jurisdictional rules for each location where the product will be used.
informal review

Source: ISTQB

A type of review that does not follow a defined process and has no formally documented output.
information assurance

Ref: NIST.IR.7298

Source: ISTQB

Measures that protect and defend information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. These measures include providing for restoration of information systems by incorporating protection, detection, and reaction capabilities.
input data testing

Source: ISTQB

A test level that focuses on the quality of the data used for training and prediction by ML models.
insider threat

Source: ISTQB

A security threat originating from within the organization, often by an authorized system user.
insourced testing

Source: ISTQB

Testing performed by people who are co-located with the project team but are not fellow employees.
inspection

Ref: After ISO 20246

Source: ISTQB

A type of formal review to identify issues in a work product, which provides measurement to improve the review process and the software development process.
Inspection*

Source: IREB

A formal ↑review of a ↑work product by a group of experts according to given criteria, following a defined procedure.
installability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be successfully installed and/or uninstalled in a specified environment.
integration testing

See also: Komponentenintegrationstest, Systemintegrationstest

Source: ISTQB

A test level that focuses on interactions between components or systems.
integrity

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system allows only authorized access and modification to a component, a system or data.
interface testing

Ref: After ISO 24765

Source: ISTQB

A type of integration testing performed to determine whether components or systems pass data and
interoperability

Ref: After ISO 25010

Source: ISTQB

The degree to which two or more components or systems can exchange information and use the information that has been exchanged.
intrusion detection system (IDS)

See also: malware scanning

Source: ISTQB

A system which monitors activities on the 7 layers of the OSI model from network to application level, to detect violations of the security policy.
Item

Source: IREB

Anything which is perceivable or conceivable.
Iteration*

Source: IREB

In general: The repetition of something, for example, a procedure, a process or a piece of program code. In agile development: A ↑timeboxed unit of work in which a development team implements an ↑increment to the ↑system under development.
iterative development model

Source: ISTQB

A type of software development lifecycle model in which the component or system is developed through a series of repeated cycles.
keyword-driven testing

See also: datengetriebenes Testen

Source: ISTQB

A scripting technique in which test scripts contain high-level keywords and supporting files that contain low-level scripts that implement those keywords.
Kind of requirement

Source: IREB

A classification of requirements according to their kind into ↑system requirements (consisting of ↑functional requirements, ↑quality requirements and ↑constraints), project requirements, and process requirements.

Note: 1. RE is primarily concerned with system requirements. 2. Quality requirements and constraints are also called ↑non-functional requirements.
Language

Source: IREB

A structured set of signs for expressing and communicating information.
learnability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be used by specified users to achieve specified goals of learning with satisfaction and freedom from risk in a specified context of use.
level of intrusion

Source: ISTQB

The level to which a test object is modified by adjusting it for testability.
level test plan

See also: test plan

Source: ISTQB

A test plan that typically addresses one test level.
linear scripting

Source: ISTQB

A simple scripting technique without any control structure in the test scripts.
load generation

See also: load testing

Source: ISTQB

The process of simulating a defined set of activities at a specified load to be submitted to a component or system.
load generator

See also: Lasttest

Source: ISTQB

A tool that generates a load for a system under test.
load management

Source: ISTQB

The control and execution of load generation, and performance monitoring and reporting of the component or system.
load profile

Source: ISTQB

Documentation defining a designated number of virtual users who process a defined set of transactions in a specified time period that a component or system being tested may experience in production.
load testing

Ref: After ISO 29119-1

See also: performance testing, stress testing

Source: ISTQB

A type of performance testing conducted to evaluate the behavior of a component or system under varying loads, usually between anticipated conditions of low, typical, and peak usage.
low-level test case

See also: high-level test case

Source: ISTQB

A test case with concrete values for preconditions, input data, expected results, postconditions, and a detailed description of actions (where applicable).
maintainability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be modified by the intended maintainers.
Maintainability

Source: IREB

The ease with which a ↑system can be modified by the intended maintainers.
maintenance

Ref: After ISO 24765

Source: ISTQB

The process of modifying a component or system after delivery to correct defects, improve quality characteristics, or adapt to a changed environment.
maintenance testing

Source: ISTQB

Testing the changes to an operational system or the impact of a changed environment to an operational system.
malware

Source: ISTQB

Software that is intended to harm a system or its components.
malware scanning

See also: intrusion detection system

Source: ISTQB

Static analysis aiming to detect and remove malicious code received at an interface.
management review

Ref: After ISO 24765, IEEE 1028

Source: ISTQB

A systematic evaluation of software acquisition, supply, development, operation, or maintenance process, performed by or on behalf of management that monitors progress, determines the status of plans and schedules, confirms requirements and their system allocation, or evaluates the effectiveness of management approaches to achieve fitness for purpose.
manufacturing-based quality

Ref: After Garvin

See also: product-based quality, transcendent-based quality, user-based quality, value-based quality

Source: ISTQB

A view of quality measured by the degree that a product or service conforms to its intended design and requirements based on the process used.
master test plan

See also: test plan

Source: ISTQB

A test plan that is used to coordinate multiple test levels or test types.
math testing

Source: ISTQB

Testing to determine the correctness of the pay table implementation, the random number generator
maturity

Ref: ISO 25010

Source: ISTQB

(1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The degree to which a component or system meets needs for reliability under normal operation.
maturity model

Source: ISTQB

A structured collection of elements that describe certain aspects of maturity in an organization, and aid in the definition and understanding of an organization's processes.
MBT model

Source: ISTQB

Any model used in model-based testing.
mean time between failures (MTBF)

See also: mean time to repair, mean time to failure

Source: ISTQB

The average time between consecutive failures of a component or system.
mean time to failure (MTTF)

See also: mean time between failures

Source: ISTQB

The average time from the start of operation to a failure for a component or system.
mean time to repair (MTTR)

Source: ISTQB

The average time a component or system will take to recover from a failure.
measurement

Ref: After ISO 24765

Source: ISTQB

The process of assigning a number or category to an entity to describe an attribute of that entity.
memory leak

Source: ISTQB

A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it.
metamorphic relation (MR)

Ref: ISO 29119-11

Source: ISTQB

A description of how a change in the test inputs from the source test case to the follow-up test case affects a change in the expected outputs from the source test case to the follow-up test case.
metamorphic testing (MT)

Source: ISTQB

A test technique in which the inputs and expected results are extrapolated from a passing test case using a metamorphic relation.
Method

Source: IREB

The systematic application of a ↑technique (or a set of techniques) to achieve an objective or create a ↑work product.
methodical test strategy

Source: ISTQB

A test strategy whereby the test team uses a pre-determined set of test conditions such as a quality standard, a checklist, or a collection of generalized, logical test conditions which may relate to a particular domain, application or type of testing.
Methodology

Source: IREB

The systematic study of ↑methods in a particular field, in particular, how to select, apply or evaluate methods systematically in a given situation. A set of ↑methods being applied in some combination.
method table

Ref: ISO 26262

Source: ISTQB

A table containing different test approaches, testing techniques and test types that are required depending on the Automotive Safety Integrity Level (ASIL) and on the context of the test object.
metric

Ref: ISO 14598

Source: ISTQB

A measurement scale and the method used for measurement.
ML functional performance

Source: ISTQB

The degree to which an ML model meets ML functional performance criteria.
ML functional performance criteria

Source: ISTQB

Criteria based on ML functional performance metrics used as a basis for model evaluation, tuning and testing.
ML functional performance metrics

Source: ISTQB

A set of measures that relate to the functional correctness of an ML system.
ML model

Source: ISTQB

An implementation of machine learning (ML) that generates a prediction, classification or recommendation based on input data.
ML model testing

Source: ISTQB

A test level that focuses on the ability of an ML model to meet required ML functional performance criteria and non-functional criteria.
Mock-up* (of a digital system)

Source: IREB

A medium-fidelity ↑prototype that demonstrates characteristics of a user interface without implementing any real ↑functionality.
Model

Source: IREB

An abstract representation of an existing part of reality or a part of reality to be created.

Note: 1. The notion of reality includes any conceivable set of elements, phenomena, or concepts, including other models. 2. Models are always built for specific purposes in a specific context. 3. With respect to a model, the modeled part of reality is called the original. 4. In RE, ↑requirements can be specified with models.
model-based testing (MBT)

Source: ISTQB

Testing based on or involving models.
model-based test strategy

Source: ISTQB

A test strategy whereby the test team derives testware from models.
model coverage

Source: ISTQB

The coverage of model elements.
Modeling language

Source: IREB

A ↑language for expressing ↑models of a certain kind. May be textual, graphic, symbolic or some combination thereof.
model in the loop (MiL)

Ref: Automotive SPICE

Source: ISTQB

Dynamic testing performed using a simulation model of the system in a simulated environment.
moderator

Source: ISTQB

(1) The person responsible for running review meetings. (2) The person who performs a usability test session.
modifiability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be modified without degrading its quality.
Modifiability

Source: IREB

The degree to which a ↑work product or ↑system can be modified without degrading its ↑quality.
modified condition/decision coverage (MC/DC)

Source: ISTQB

The coverage of all outcomes of the atomic conditions that independently affect the overall decision outcome.
modified condition/decision testing

Source: ISTQB

A white-box test technique in which test cases are designed to exercise outcomes of atomic conditions that independently affect a decision outcome.
modularity

Ref: After ISO 25010

Source: ISTQB

The degree to which a system is composed of discrete components such that a change to one component has minimal impact on other components.
monitoring tool

Ref: ISO 24765

Source: ISTQB

A software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyzes the behavior of the component or system.
multiplayer testing

Source: ISTQB

Testing to determine if many players can simultaneously interact with the casino game world, with computer-controlled opponents, game servers, and with each other, as expected according to the game design.
multiple condition coverage

Source: ISTQB

The coverage of all possible combinations of all single condition outcomes within one statement.
multiple condition testing

Source: ISTQB

A white-box test technique in which test cases are designed to exercise outcome combinations of atomic conditions.
Multiplicity

Source: IREB

→ Cardinality
Myers-Briggs Type Indicator (MBTI)

Source: ISTQB

An indicator of psychological preference representing the different personalities and communication styles of people.
Native prototype

Source: IREB

A high-fidelity ↑prototype that implements critical parts of a ↑system to an extent that ↑stakeholders can use the prototype to see whether the prototyped part of the system will work and behave as expected.
Necessity*(of a requirement)

Source: IREB

The degree to which an individual ↑requirement is a necessary part of the ↑requirements specification of a ↑system.
negative testing

Source: ISTQB

Testing a component or system in a way for which it was not intended to be used.
neighborhood integration testing

Source: ISTQB

A type of integration testing in which all of the nodes that connect to a given node are the basis for the integration testing.
network zone

Source: ISTQB

A sub-network with a defined level of trust. For example, the Internet or a public zone would be considered to be untrusted.
neuron coverage

Source: ISTQB

The coverage of activated neurons in the neural network for a set of tests.
Non-functional requirement

Source: IREB

A ↑quality requirement or a ↑constraint.
non-functional testing

Source: ISTQB

Testing performed to evaluate that a component or system complies with non-functional requirements.
non-repudiation

Ref: After ISO 25010

Source: ISTQB

The degree to which actions or events can be proven to have taken place, so that the actions or events cannot be repudiated later.
N-switch coverage

Ref: Chow

Source: ISTQB

The coverage of sequences of N+1 transitions.
Object

Source: IREB

1. In general: Anything which is perceivable or conceivable (→ item). 2. In software engineering: an individual ↑item which has an identity, is characterized by the values of its ↑attributes and does not depend on another item (→ entity).
Object diagram

Source: IREB

A diagrammatic representation of an ↑object model.
Object model

Source: IREB

A ↑model describing a set of ↑objects and relationships between them.
offline MBT

Source: ISTQB

Model-based test approach whereby test cases are generated into a repository for future execution.
online MBT

Source: ISTQB

Model-based test approach whereby test cases are generated and executed simultaneously.
open–loop-system

Ref: Bakshi

Source: ISTQB

A system in which controlling action or input is independent of the output or changes in output.
open-source tool

Source: ISTQB

A software tool that is available to all potential users in source code form, usually via the internet. Its users are permitted, usually under license, to study, change, improve and, at times, to distribute the software.
operability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system has attributes that make it easy to operate and control.
operational acceptance testing

Source: ISTQB

A type of acceptance testing performed to determine if operations and/or systems administration staff can accept a system.
operational profile

Source: ISTQB

An actual or predicted pattern of use of the component or system.
operational profiling

See also: operational profile

Source: ISTQB

The process of developing and implementing an operational profile.
outsourced testing

Source: ISTQB

Testing performed by people who are not co-located with the project team and are not fellow employees.
pair testing

Source: ISTQB

An approach in which two team members simultaneously collaborate on testing a work product.
pairwise integration testing

Source: ISTQB

A type of integration testing that targets pairs of components that work together as shown in a call graph.
pairwise testing

Ref: After ISO 29119-4

Source: ISTQB

A black-box test technique in which test cases are designed to exercise pairs of parameter-value pairs
par sheet testing

Source: ISTQB

Testing to determine that the game returns the correct mathematical results to the screen, to the players'accounts, and to the casino account.
passed

See also: fehlgeschlagen

Source: ISTQB

The status of a test result in which the actual result matches the expected result.
pass/fail criteria

Ref: After ISO 29119-1

Source: ISTQB

Decision rules used to determine whether a test item has passed or failed.
password cracking

Ref: after NIST.IR.7298

Source: ISTQB

A security attack recovering secret passwords stored in a computer system or transmitted over a network.
path

Source: ISTQB

A sequence of consecutive edges in a directed graph.
path testing

Source: ISTQB

A white-box test technique in which test cases are designed to execute paths in a control flow graph.
peer review

Ref: After ISO 20246

Source: ISTQB

A review performed by others with the same abilities to create the work product.
penetration testing

Source: ISTQB

A testing technique aiming to exploit security vulnerabilities (known or unknown) to gain unauthorized access.
performance efficiency

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system uses time, resources and capacity when accomplishing its designated functions.
performance indicator

Ref: After ISO 33001

Source: ISTQB

A metric that supports the judgment of process performance.
Performance requirement

Source: IREB

A ↑requirement describing a performance characteristic (timing, speed, volume, capacity, throughput, ...).
performance testing

Source: ISTQB

Testing to determine the performance efficiency of a component or system.
performance testing tool

Source: ISTQB

A test tool that generates load for a designated test item and that measures and records its performance during test execution.
Persona

Source: IREB

A fictitious character representing a group of ↑users with similar needs, values and habits who are expected to use a ↑system in a similar way.
perspective-based reading

Source: ISTQB

A review technique in which a work product is evaluated from the perspective of different stakeholders with the purpose to derive other work products.
pharming

Source: ISTQB

A security attack intended to redirect a website's traffic to a fraudulent website without the user's knowledge or consent.
phase containment

Source: ISTQB

The percentage of defects that are removed in the same phase of the software lifecycle in which they were introduced.
phishing

Source: ISTQB

An attempt to acquire personal or sensitive information by masquerading as a trustworthy entity in an electronic communication.
Phrase template

Source: IREB

A template for the syntactic structure of a phrase that expresses an individual ↑requirement or a ↑user story in ↑natural language. (→ requirements template)
player perspective testing

Source: ISTQB

Testing done by testers from a player's perspective to validate player satisfaction.
pointer

Ref: ISO 24765

Source: ISTQB

A data item that specifies the location of another data item.
portability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be transferred from one hardware, software or other operational or usage environment to another.
Portability

Source: IREB

The ease with which a ↑system can be transferred to another platform while preserving its characteristics.
postcondition

Source: ISTQB

The expected state of a test item and its environment at the end of test case execution.
post-release testing

Source: ISTQB

A type of testing to ensure that the release is performed correctly and the application can be deployed.
Practice

Source: IREB

A proven way of how to carry out certain types of ↑tasks or ↑activities.
precondition

Source: ISTQB

The required state of a test item and its environment prior to test case execution.
Prioritization

Source: IREB

The process of assigning priorities to a set of ↑items.
priority

Source: ISTQB

The level of (business) importance assigned to an item, e.g., defect.
Priority

Source: IREB

The level of importance assigned to an ↑item, e.g., a ↑requirement or a ↑defect, according to certain criteria.
PRISMA

Source: ISTQB

A systematic approach to risk-based testing that employs product risk identification and analysis to create a product risk matrix based on likelihood and impact. Term is derived from Product RISk MAnagement.
Problem

Source: IREB

A difficulty, open question or undesirable condition that needs investigation, consideration, or solution.
Process

Source: IREB

A set of interrelated ↑activities performed in a given order to process information or materials.
process assessment

Ref: after ISO 15504

Source: ISTQB

A disciplined evaluation of an organization's software processes against a reference model.
process-driven scripting

Source: ISTQB

A scripting technique where scripts are structured into scenarios which represent use cases of the software under test. The scripts can be parameterized with test data.
process model

Source: ISTQB

A framework in which processes of the same nature are classified into an overall model.
Process model*

Source: IREB

A ↑model describing a ↑process or a set of related processes.
Process pattern

Source: IREB

An abstract, reusable ↑model of a ↑process which can be used to configure and instantiate a concrete process for a given situation and ↑context.
Product backlog

Source: IREB

An ordered, typically prioritized collection of work items that a development team has to work on when developing or evolving a ↑system.
product-based quality

Ref: After Garvin

Source: ISTQB

A view of quality measured by the degree that well-defined quality characteristics are met.
Product*(in the context of software)

Source: IREB

A software-based ↑system or a ↑service provided by a system which is developed and marketed by a ↑supplier and used by ↑customers.
Product line

Source: IREB

A jointly managed set of systems (provided as products or services) that share a common core and have a configurable set of ↑variants for satisfying needs of particular ↑customers or market segments.
Product owner

Source: IREB

A person responsible for a ↑product in terms of ↑functionality, value and ↑risk.
product risk

See also: risk

Source: ISTQB

A risk impacting the quality of a product.
project risk

See also: risk

Source: ISTQB

A risk that impacts project success.
Prototype

Source: IREB

1. In manufacturing: A piece which is built prior to the start of mass production. 2. In software and systems engineering: A preliminary, partial realization of certain characteristics of a ↑system. 3. In design: A preliminary, partial instance of a design solution.

Note: 1. In RE, prototypes are used as a means for requirements ↑elicitation (see ↑specification by example) and ↑validation. 2. Prototypes in RE can be classified (a) with respect to their degree of fidelity into ↑native prototypes, ↑mock-ups and ↑wireframes; (b) with respect to their purpose into ↑exploratory prototypes and ↑evolutionary prototypes.
Prototyping

Source: IREB

A ↑process that involves the creation and evaluation of ↑prototypes.
pseudo-oracle

Ref: ISO 29119-11

Source: ISTQB

An independently derived variant of the test item used to generate results, which are compared with the results of the original test item based on the same test inputs.
quality

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system satisfies the stated and implied needs of its various stakeholders.
Quality

Source: IREB

1. In general: The degree to which a set of inherent characteristics of an item fulfills ↑requirements. 2. In systems and software engineering: The degree to which a ↑system satisfies stated and implied needs of its ↑stakeholders.
quality assurance (QA)

Ref: After ISO 24765

See also: quality management

Source: ISTQB

Activities focused on providing confidence that quality requirements will be fulfilled.
quality characteristic

Ref: ISO 24765

Source: ISTQB

A category of quality attributes that bears on work product quality.
quality control (QC)

Ref: after ISO 24765

See also: testing

Source: ISTQB

A set of activities designed to evaluate the quality of a component or system.
quality function deployment (QFD)

Ref: ISO 24765

Source: ISTQB

A facilitated workshop technique that helps determine critical characteristics for new product development.
quality management

Ref: After ISO 24765

Source: ISTQB

The process of establishing and directing a quality policy, quality objectives, quality planning, quality control, quality assurance, and quality improvement for an organization.
Quality requirement

Source: IREB

A ↑requirement that pertains to a quality concern that is not covered by ↑functional requirements.
quality risk

See also: quality characteristic, product risk

Source: ISTQB

A product risk related to a quality characteristic.
RACI matrix

Source: ISTQB

A matrix describing the participation by various roles in completing tasks or deliverables for a project or process. It is especially useful in clarifying roles and responsibilities. RACI is an acronym derived from the four key responsibilities most typically used: Responsible, Accountable, Consulted, and Informed.
ramp-down

Source: ISTQB

A technique for decreasing the load on a system in a measurable and controlled way.
ramp-up

Source: ISTQB

A technique for increasing the load on a system in a measurable and controlled way.
random testing

Source: ISTQB

A black-box test technique in which test cases are designed by generating random independent inputs to match an operational profile.
reactive testing

Source: ISTQB

Testing that dynamically responds to the behavior of the test object and to test results being obtained.
reactive test strategy

Source: ISTQB

A test strategy whereby the test team waits to design and implement tests until the software is received, reacting to the actual system under test.
reconnaissance

Source: ISTQB

The exploration of a target area aiming to gain information that can be useful for an attack.
recoverability

Ref: After ISO 25010

See also: Zuverlässigkeit

Source: ISTQB

The degree to which a component or system can recover the data directly affected by an interruption or a failure and re-establish the desired state of the component or system.
Redundancy

Source: IREB

Multiple occurrence of the same information or resource.
Refactoring

Source: IREB

The improvement of the internal ↑quality of source code, particularly the structure of the code, without changing its observable behavior.
regression-averse test strategy

Source: ISTQB

A test strategy whereby the test team applies various techniques to manage the risk of regression such as functional and/or non-functional regression test automation at one or more levels.
regression testing

Source: ISTQB

A type of change-related testing to detect whether defects have been introduced or uncovered in unchanged areas of the software.
regulatory acceptance testing

Source: ISTQB

A type of acceptance testing performed to verify whether a system conforms to relevant laws, policies and regulations.
Release

Source: IREB

A ↑configuration that has been released for installation and use by ↑customers.
reliability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system performs specified functions under specified conditions for a specified period of time.
Reliability*

Source: IREB

The degree to which a ↑system performs specified functions under specified conditions for a specified period of time.
reliability growth model

Source: ISTQB

A model that shows the growth in reliability over time of a component or system as a result of the defect removal.
remote test lab

Source: ISTQB

A facility that provides remote access to a test environment.
replaceability

Ref: After ISO 25010

See also: Übertragbarkeit

Source: ISTQB

The degree to which a component or system can replace another specified component or system for the same purpose in the same environment.
requirement

Ref: ISO 24765

Source: ISTQB

A provision that contains criteria to be fulfilled.
Requirement

Source: IREB

1. A need perceived by a ↑stakeholder. 2. A capability or property that a ↑system shall have. 3. A documented representation of a need, capability or property.
Requirements analysis

Source: IREB

1. Analysis of elicited ↑requirements in order to understand and document them. 2. Synonym for ↑Requirements Engineering.
requirements-based testing

Source: ISTQB

An approach to testing in which test cases are designed based on requirements.
Requirements baseline

Source: IREB

A ↑baseline for a set of ↑requirements.
Requirements branching

Source: IREB

Branch
Requirements configuration

Source: IREB

Configuration
Requirements conflict

Source: IREB

1. A situation where two or more ↑requirements cannot be satisfied together. 2. A situation where two or more ↑stakeholders disagree about certain ↑requirements.
Requirements document

Source: IREB

A document consisting of a ↑requirements specification.
Requirements elicitation

Source: IREB

The process of seeking, capturing and consolidating ↑requirements from available ↑sources, potentially including the re-construction or creation of requirements.
Requirements Engineer

Source: IREB

A person who – in collaboration with ↑stakeholders – elicits, documents, validates, and manages ↑requirements.
Requirements Engineering

Abbreviation: RE

Source: IREB

The systematic and disciplined approach to the ↑specification and management of ↑requirements with the goal of understanding the ↑stakeholders’ desires and needs and minimizing the risk of delivering a ↑system that does not meet these desires and needs.
Requirements management

Source: IREB

The process of managing existing ↑requirements and requirements-related ↑work products, including the storing, changing and tracing of requirements (↑traceability).
Requirements model

Source: IREB

A ↑model that has been created with the purpose of specifying ↑requirements.
Requirements negotiation

Source: IREB

A ↑process where ↑stakeholders are working toward reaching an agreement to resolve ↑requirements conflicts.
Requirements source

Source: IREB

The source from which a ↑requirement has been derived.
Requirements specification

Source: IREB

A systematically represented collection of ↑requirements, typically for a ↑system, that satisfies given criteria.

Note: 1. In some situations we distinguish between a ↑customer requirements specification (typically written by the ↑customer) and a ↑system requirements specification or ↑software requirements specification (written by the supplier). 2. Requirements specification may also denote the ↑process of specifying (↑eliciting, documenting and ↑validating) requirements.
Requirements template

Source: IREB

A template for specifying ↑requirements.
resource utilization

Ref: After ISO 25010

Source: ISTQB

The degree to which the amounts and types of resources used by a component or system, when performing its functions, meet requirements.
retrospective

Ref: After SAFe

Source: ISTQB

A regular event in which team members discuss results, review their practices, and identify ways to improve.
reusability

Ref: After ISO 25010

Source: ISTQB

The degree to which a work product can be used in more than one system, or in building other work products.
review

Source: ISTQB

A type of static testing in which a work product or process is evaluated by one or more individuals to detect defects or to provide improvements.
Review

Source: IREB

An evaluation of a ↑work product by an individual or a group in order to find problems or suggest improvements.
reviewer

Ref: After ISO 20246

Source: ISTQB

A participant in a review who identifies issues in the work product.
risk

Source: ISTQB

A factor that could result in future negative consequences.
Risk*

Source: IREB

A possible event that threatens the success of an endeavor.
risk analysis

Source: ISTQB

The overall process of risk identification and risk assessment.
risk assessment

See also: Produktrisiko, Projektrisiko, Risiko, Schadensausmaß des Risikos, Risikostufe, Eintrittswahrscheinlichkeit des Risikos

Source: ISTQB

The process to examine identified risks and determine the risk level.
risk-based testing

Ref: After ISO 29119-1

Source: ISTQB

Testing in which the management, selection, prioritization, and use of testing activities and resources are based on corresponding risk types and risk levels.
risk identification

Ref: ISO 31000

Source: ISTQB

The process of finding, recognizing and describing risks.
risk impact

Source: ISTQB

The damage that will be caused if the risk becomes an actual outcome or event.
risk level

Source: ISTQB

The qualitative or quantitative measure of a risk defined by impact and likelihood.
risk likelihood

Source: ISTQB

The probability that a risk will become an actual outcome or event.
risk management

Ref: After ISO 24765

Source: ISTQB

The process for handling risks.
risk mitigation

Source: ISTQB

The process through which decisions are reached and protective measures are implemented for reducing or maintaining risks to specified levels.
Role

Source: IREB

1. A part played by a person in a given context. 2. In ↑UML ↑class models: The parts played by the linked ↑objects in an ↑association.
role-based review

Source: ISTQB

A review technique in which a work product is evaluated from the perspective of different stakeholders.
root cause

Ref: CMMI

Source: ISTQB

A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.
root cause analysis

Source: ISTQB

An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of defect recurrence will be minimized.
Safety

Source: IREB

The capability of a ↑system to achieve an acceptable level of probability that the system, under defined conditions, will not reach a state in which human life, health, property, or the environment is endangered.
safety integrity level (SIL)

Ref: After IEC 61508

See also: automotive safety integrity level

Source: ISTQB

The level of risk reduction provided by a safety function, related to the frequency and severity of perceived hazards.
salting

See also: hashing

Source: ISTQB

A cryptographic technique that adds random data (salt) to the user data prior to hashing.
scalability

Ref: After Gerrard

Source: ISTQB

The degree to which a component or system can be adjusted for changing capacity.
scalability testing

Source: ISTQB

Testing to determine the scalability of the software product.
Scenario

Source: IREB

1. In general: A description of a potential sequence of events that lead to a desired (or unwanted) result. 2. In RE: An ordered sequence of interactions between partners, in particular between a ↑system and external ↑actors. May be a concrete sequence (instance scenario) or a set of potential sequences (type scenario, ↑use case).
scenario-based review

Source: ISTQB

A review technique in which a work product is evaluated to determine its ability to address specific scenarios.
Scope* (of a system development)

Source: IREB

The range of things that can be shaped and designed when developing a ↑system.
scribe

Ref: After ISO 24765

Source: ISTQB

A person who records information at a review meeting.
scripted testing

Source: ISTQB

Testing (manual or automated) that follows a test script.
script kiddie

See also: hacker

Source: ISTQB

A person who executes security attacks that have been created by other hackers rather than creating one's own attacks.
Scrum

Source: IREB

A popular ↑process framework for ↑agile development of a ↑system.
security

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system protects its data and resources against unauthorized access or use and secures unobstructed access and use for its legitimate users.
Security

Source: IREB

The degree to which a ↑system protects its data and resources against unauthorized access or use and secures unobstructed access and use for its legitimate ↑users.
security attack

Ref: after NIST.IR.7298

Source: ISTQB

An attempt to gain unauthorized access to a component or system, resources, information, or an attempt to compromise system integrity.
security audit

Source: ISTQB

An audit evaluating an organization's security processes and infrastructure.
security policy

Source: ISTQB

A high-level document describing the principles, approach and major objectives of the organization regarding security.
security procedure

Source: ISTQB

A set of steps required to implement the security policy and the steps to be taken in response to a security incident.
security risk

Source: ISTQB

A quality risk related to security.
security testing

Source: ISTQB

Testing to determine the security of the software product.
security vulnerability

Source: ISTQB

A weakness in the system that could allow for a successful security attack.
seine Messung verursacht wird.

Source: ISTQB

probe effect
Semantics

Source: IREB

The meaning of a sign or a set of signs in a ↑language.
Semi-formal

Source: IREB

Something which is formal to some extent, but not completely.
Sequence diagram

Source: IREB

A diagram type in ↑UML which models the interactions between a selected set of ↑objects and/or ↑actors in the sequential order in which those interactions occur.
sequential development model

Source: ISTQB

A type of software development lifecycle model in which a complete system is developed in a linear way of several discrete and successive phases with no overlap between them.
Service

Source: IREB

The provision of some ↑functionality to a human or a ↑system by a provider (a system, organization, group or individual) that delivers value to the receiver.
service virtualization

Source: ISTQB

A technique to enable virtual delivery of services which are deployed, accessed and managed remotely.
session-based testing

Source: ISTQB

An approach in which test activities are planned as test sessions.
session-based test management (SBTM)

Source: ISTQB

A method for measuring and managing session-based testing.
severity

Ref: Nach IEEE 610

Source: ISTQB

The degree of impact that a defect has on the development or operation of a component or system.
short-circuiting

Source: ISTQB

A programming language/interpreter technique for evaluating compound conditions in which a condition on one side of a logical operator may not be evaluated if the condition on the other side is sufficient to determine the final outcome.
sign change coverage

Source: ISTQB

The coverage of neurons activated with both positive and negative activation values in a neural network for a set of tests.
sign-sign coverage

Ref: After ISO 29119-11

Source: ISTQB

The coverage achieved if by changing the sign of each neuron it can be shown to individually cause one neuron in the next layer to change sign while all other neurons in the next layer do not change sign for a set of tests.
simulator

Ref: After ISO 24765

See also: emulator

Source: ISTQB

A component or system used during testing which behaves or operates like a given component or system.
S.M.A.R.T. goal methodology (SMART)

Source: ISTQB

A methodology whereby objectives are defined very specifically rather than generically. SMART is an acronym derived from the attributes of the objective to be defined: Specific, Measurable, Attainable, Relevant and Timely.
smoke test

Source: ISTQB

A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.
social engineering

Ref: NIST.IR.7298

Source: ISTQB

An attempt to trick someone into revealing information (e.g., a password) that can be used to attack systems or networks.
software development lifecycle (SDLC)

Source: ISTQB

The activities performed at each stage in software development, and how they relate to one another logically and chronologically.
software in the loop (SiL)

Ref: Automotive SPICE

Source: ISTQB

Dynamic testing performed using real software in a simulated environment or with experimental hardware.
software lifecycle

Source: ISTQB

The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The software lifecycle typically includes a concept phase, requirements phase, design phase, implementation phase, test phase, installation and checkout phase, operation and maintenance phase, and sometimes, retirement phase. Note these phases may overlap or be performed iteratively.
software process improvement (SPI)

Ref: After CMMI

Source: ISTQB

A program of activities designed to improve the performance and maturity of the organization's software processes and the results of such a program.
software qualification test

Ref: Automotive SPICE

Source: ISTQB

Testing performed on completed, integrated software to provide evidence for compliance with software requirements.
Software requirements specification*

Abbreviation: SRS

Source: IREB

A ↑requirements specification pertaining to a software ↑system.
Software Usability Measurement Inventory (SUMI)

Ref: Kirakowski93

Source: ISTQB

A questionnaire-based usability testing tool that measures and benchmarks user experience.
Source(of a requirement)

Source: IREB

→ Requirements source
source test case

Source: ISTQB

A test case that passed and is used as the basis of follow-up test cases in metamorphic testing.
Specification

Source: IREB

1. As a work product: A systematically represented description of the properties of an ↑item (a ↑system, a device, etc.) that satisfies given criteria. 2. As a process: the process of specifying (↑eliciting, documenting and ↑validating) the properties of an ↑item.
Specification by example

Source: IREB

A ↑technique that specifies test cases and ↑requirements for a ↑system by providing examples of how the system should behave.
specification by example (SBE)

See also: acceptance test-driven development

Source: ISTQB

A development technique in which the specification is defined by examples.
Specification language

Source: IREB

An artificial ↑language that has been created for expressing ↑specifications.
Spike

Source: IREB

In agile development: A task aimed at gaining insight or gathering information, rather than at producing a ↑product ↑increment.
spike testing

Source: ISTQB

Testing to determine the ability of a system to recover from sudden bursts of peak loads and return to a steady state.
Sprache Natural language

Source: IREB

A ↑language that people use for speaking and writing in everyday life.
Sprint*

Source: IREB

An ↑iteration in ↑agile development, particularly when using ↑Scrum.
Sprint backlog

Source: IREB

A set of ↑product backlog items that have been selected to be implemented in the current ↑sprint.
SQL injection

Source: ISTQB

A type of code injection in the structured query language (SQL).
Stakeholder

Source: IREB

A person or organization who influences a ↑system’s ↑requirements or who is impacted by that system.
Stakeholder requirement

Source: IREB

A ↑requirement expressing a ↑stakeholder desire or need.
standard

Ref: After CMMI

Source: ISTQB

Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., ISO/IEC standards, IEEE standards, and organizational standards).
Standard

Source: IREB

A formal, possibly mandatory set of regulations for how to interpret, develop, manufacture, or execute something.
standard-compliant test strategy

Source: ISTQB

A test strategy whereby the test team follows a standard. Standards followed may be valid e.g., for a country (legislation standards), a business domain (domain standards), or internally (organizational standards).
Statechart

Source: IREB

A ↑state machine having states that are hierarchically and/or orthogonally decomposed.
State machine*

Source: IREB

A ↑model describing the behavior of a ↑system by a finite set of states and state transitions. State transitions are triggered by events and can in turn trigger actions and new events.
State machine diagram*

Source: IREB

A diagrammatic representation of a ↑state machine.
statement

Source: ISTQB

An entity in a programming language, which is typically the smallest indivisible unit of execution.
statement coverage

Source: ISTQB

The coverage of executable statements.
statement testing

Source: ISTQB

A white-box test technique in which test cases are designed to execute statements.
State-transition diagram

Source: IREB

→ State machine diagram
state transition testing

Source: ISTQB

A black-box test technique in which test cases are designed to exercise elements of a state transition model.
static analysis

Ref: After ISO 24765

Source: ISTQB

The process of evaluating a component or system without executing it, based on its form, structure, content, or documentation.
static testing

See also: dynamic testing

Source: ISTQB

Testing that does not involve the execution of a test item.
Steering committee

Source: IREB

A committee that supervises a project.
Storyboard

Source: IREB

A series of sketches or pictures that visualize the execution of a ↑scenario.
Story (in an RE context)

Source: IREB

→ User story
Story map

Source: IREB

A two-dimensional arrangement of ↑user stories.
stress testing

Ref: ISO 24765

See also: Performanztest, Lasttest

Source: ISTQB

A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced availability of resources such as access to memory or servers.
structural coverage

Source: ISTQB

Coverage measures based on the internal structure of a component or system.
Structured Analysis

Source: IREB

An approach for specifying the ↑functionality of a system based on a hierarchy of ↑data flow diagrams. Data flows as well as persistent data are defined in a data dictionary. A ↑context diagram models the sources of incoming and the destinations of outgoing ↑data flows.
structured scripting

Source: ISTQB

A scripting technique that builds and utilizes a library of reusable (parts of) scripts.
stub

Ref: After ISO 24765

Source: ISTQB

A skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component.
summative evaluation

See also: formative evaluation, testing

Source: ISTQB

A type of evaluation designed and used to gather conclusions about the quality of a component or system, especially when a substantial part of it has completed design.
Supplier

Source: IREB

A person or organization who delivers a ↑product or ↑service to a ↑customer.
Synonym*

Source: IREB

A word having the same meaning as another word.
Syntax*

Source: IREB

The rules for constructing structured signs in a ↑language.
System*

Important: {{important_data}

Source: IREB

1. In general: A principle for ordering and structuring. 2. In engineering: A coherent, delimitable set of elements that – by coordinated action – achieve some purpose.

Note: 1. A system may comprise other systems or ↑components as sub-systems. 2. The purposes achieved by a system may be delivered by deploying the system at the place(s) where it is used, selling/providing the system as a ↑product to its ↑users, having providers who offer the system’s capabilities as ↑services to users. 3. Systems containing both software and physical ↑components are called cyber- physical systems. 4. Systems spanning software, hardware, people and organizational aspects are called socio-technical systems.
Systematic Test and Evaluation Process (STEP)

See also: inhaltsbasiertes Modell

Source: ISTQB

A structured testing methodology also used as a content-based model for improving the testing process. It does not require that improvements occur in a specific order.
System boundary*

Source: IREB

The boundary between a ↑system and its surrounding ↑context.

Note: 1. The system boundary delimits the system as it shall be after its implementation and deployment. 2. At the system boundary, the external interfaces between the ↑system and its ↑context have to be defined. 3. The system boundary frequently coincides with the ↑scope of a ↑system (which denotes the range of things that can be shaped and designed). However, this is not always the case: there may be components within the system boundary that have to be re-used as they are (i.e., cannot be shaped nor designed), while in the system context there may be things that can be re-designed when the system is developed (which means that they are in scope).
System context

Source: IREB

The part of a ↑system’s environment that is relevant for the definition as well as the understanding of the ↑requirements of a ↑system to be developed.
Systemen austauschen kann, und/oder ihre geforderten Funktionen bei einer gemeinsamen Benutzung einer Hardware- oder Softwareumgebung ausführen kann.

Ref: After ISO 25010

Source: ISTQB

compatibility
system hardening

Source: ISTQB

The step-by-step process of reducing the security vulnerabilities of a system by applying a security policy and different layers of protection.
system integration testing

Source: ISTQB

A test level that focuses on interactions between systems.
system of systems

Source: ISTQB

Multiple heterogeneous, distributed systems that are embedded in networks at multiple levels and in multiple interconnected domains, addressing large-scale inter-disciplinary common problems and purposes, usually without a common management structure.
system qualification test

Ref: Automotive SPICE

Source: ISTQB

Testing performed on the completed, integrated system of software components, hardware components, and mechanics to provide evidence for compliance with system requirements and that the complete system is ready for delivery.
System requirement*

Source: IREB

A ↑requirement pertaining to a ↑system.
System requirements specification*

Abbreviation: SyRS

Source: IREB

A ↑requirements specification pertaining to a ↑system.
system testing

Source: ISTQB

A test level that focuses on verifying that a system as a whole meets specified requirements.
system throughput

Ref: After ISO 24765

Source: ISTQB

The amount of data passing through a component or system in a given time period.
system under test (SUT)

Source: ISTQB

A type of test object that is a system.
System Usability Scale (SUS)

Source: ISTQB

A simple, ten-item attitude scale giving a global view of subjective assessments of usability.
Task

Source: IREB

A coherent chunk of work to be done.
technical review

Source: ISTQB

A formal review by technical experts that examine the quality of a work product and identify discrepancies from specifications and standards.
Technique

Source: IREB

A documented set of coherent actions for accomplishing a ↑task or achieving an objective.
test

Ref: IEEE 829

Source: ISTQB

A set of one or more test cases.
testability

Ref: After ISO 25010

Source: ISTQB

The degree to which test conditions can be established for a component or system, and tests can be performed to determine whether those test conditions have been met.
test adaptation layer

Source: ISTQB

The layer in a test automation architecture which provides the necessary code to adapt test scripts on an abstract level to the various components, configuration or interfaces of the SUT.
test analysis

Source: ISTQB

The activity that identifies test conditions by analyzing the test basis.
test approach

Source: ISTQB

The implementation of the test strategy for a specific project.
test architect

Source: ISTQB

(1) A person who provides guidance and strategic direction for a test organization and for its relationship with other disciplines. (2) A person who defines the way testing is structured for a given system, including topics such as test tools and test data management.
test automation

Source: ISTQB

The use of software to perform or support test activities.
test automation architecture

Source: ISTQB

An instantiation of the generic test automation architecture to define the architecture of a test automation solution, i.e., its layers, components, services and interfaces.
test automation engineer

Source: ISTQB

A person who is responsible for the design, implementation and maintenance of a test automation architecture as well as the technical evolution of the resulting test automation solution.
test automation framework

Source: ISTQB

A tool that provides an environment for test automation. It usually includes a test harness and test libraries.
test automation manager

Source: ISTQB

A person who is responsible for the planning and supervision of the development and evolution of a test automation solution.
test automation solution

Source: ISTQB

A realization/implementation of a test automation architecture, i.e., a combination of components implementing a specific test automation assignment. The components may include commercial off-the-shelf test tools, test automation frameworks, as well as test hardware.
test automation strategy

Source: ISTQB

A high-level plan to achieve long-term objectives of test automation under given boundary conditions.
test basis

Ref: After TMap

Source: ISTQB

The body of knowledge used as the basis for test analysis and design.
test case

Source: ISTQB

A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.
test charter

Source: ISTQB

Documentation of the goal or objective for a test session.
test closure

See also: Testprozess

Source: ISTQB

During the test closure phase of a test process data is collected from completed activities to consolidate experience, testware, facts and numbers. The test closure phase consists of finalizing and archiving the testware and evaluating the test process, including preparation of a test evaluation report.
test completion

Source: ISTQB

The activity that makes testware available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders.
test completion report

Source: ISTQB

A type of test report produced at completion milestones that provides an evaluation of the corresponding test items against exit criteria.
test condition

Ref: After ISO 29119-1

Source: ISTQB

A testable aspect of a component or system identified as a basis for testing.
test control

See also: Testmanagement

Source: ISTQB

The activity that develops and applies corrective actions to get a test project on track when it deviates from what was planned.
test cycle

Source: ISTQB

An instance of the test process against a single identifiable version of the test object.
test data

Source: ISTQB

Data needed for test execution.
test data preparation

Source: ISTQB

The activity to select data from existing databases or create, generate, manipulate and edit data for testing.
test definition layer

Source: ISTQB

The layer in a generic test automation architecture which supports test implementation by supporting the definition of test suites and/or test cases, e.g., by offering templates or guidelines.
test design

Source: ISTQB

The activity that derives and specifies test cases from test conditions.
test director

See also: test manager

Source: ISTQB

A senior manager who manages test managers.
test-driven development (TDD)

Source: ISTQB

A software development technique in which the test cases are developed, and often automated, and then the software is developed incrementally to pass those test cases.
Testentwurfsverfahren zum ersten Mal systematisch angewendet wird.

Source: ISTQB

test case explosion
test environment

Ref: ISO 24765

Source: ISTQB

An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
tester

Source: ISTQB

A person who performs testing.
test estimation

Source: ISTQB

An approximation related to various aspects of testing.
test execution

Source: ISTQB

The activity that runs a test on a component or system producing actual results.
test execution automation

Source: ISTQB

The use of software, e.g., capture/playback tools, to control the execution of tests, the comparison of actual results to expected results, the setting up of test preconditions, and other test control and reporting functions.
test execution layer

Source: ISTQB

The layer in a generic test automation architecture which supports the execution of test suites and/or test cases.
test execution schedule

Source: ISTQB

A schedule for the execution of test suites within a test cycle.
test execution tool

Source: ISTQB

A test tool that executes tests against a designated test item and evaluates the outcomes against expected results and postconditions.
test-first approach

See also: test-driven development

Source: ISTQB

An approach to software development in which the test cases are designed and implemented before the associated component or system is developed.
test generation layer

Source: ISTQB

The layer in a generic test automation architecture which supports manual or automated design of test suites and/or test cases.
test harness

Source: ISTQB

A collection of stubs and drivers needed to execute a test suite
test hook

Source: ISTQB

A customized software interface that enables automated testing of a test object.
test implementation

Source: ISTQB

The activity that prepares the testware needed for test execution based on test analysis and design.
test improvement plan

Ref: After CMMI

Source: ISTQB

A plan for achieving organizational test process improvement objectives based on a thorough understanding of the current strengths and weaknesses of the organization's test processes and test process assets.
test infrastructure

Source: ISTQB

The organizational artifacts needed to perform testing, consisting of test environments, test tools, office environment and procedures.
testing

Source: ISTQB

The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of a component or system and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
test item

See also: test object

Source: ISTQB

A part of a test object used in the test process.
test leader

See also: test manager

Source: ISTQB

On large projects, the person who reports to the test manager and is responsible for project management of a particular test level or a particular set of testing activities.
test level

Ref: ISO 29119-1

Source: ISTQB

A specific instantiation of a test process.
test log

Ref: ISO 24765

Source: ISTQB

A chronological record of relevant details about the execution of tests.
test logging

Source: ISTQB

The activity of creating a test log.
test management

Ref: ISO 29119-1

Source: ISTQB

The planning, scheduling, estimating, monitoring, reporting, control and completion of test activities.
test management tool

Source: ISTQB

A tool that supports test management.
test manager

Source: ISTQB

The person responsible for project management of testing activities, resources, and evaluation of a test object.
Test Maturity Model integration (TMMi)

Source: ISTQB

A five-level staged framework for test process improvement, related to the Capability Maturity Model Integration (CMMI), that describes the key elements of an effective test process.
test mission

See also: test policy

Source: ISTQB

The purpose of testing for an organization, often documented as part of the test policy.
test model

Source: ISTQB

A model describing testware that is used for testing a component or a system under test.
test monitoring

Source: ISTQB

The activity that checks the status of testing activities, identifies any variances from planned or expected, and reports status to stakeholders.
test object

Source: ISTQB

The work product to be tested.
test objective

Source: ISTQB

The reason or purpose of testing.
test oracle

Ref: After Adrion

Source: ISTQB

A source to determine an expected result to compare with the actual result of the system under test.
Testorakel, und die Organisation des Testteams.

Source: ISTQB

process-compliant test strategy
test plan

Ref: After ISO 29119-1

Source: ISTQB

Documentation describing the test objectives to be achieved and the means and the schedule for achieving them, organized to coordinate testing activities.
test planning

Source: ISTQB

The activity of establishing or updating a test plan.
Test Point Analysis (TPA)

Ref: TMap

Source: ISTQB

A formula based test estimation method based on function point analysis.
test policy

Source: ISTQB

A high-level document describing the principles, approach and major objectives of the organization regarding testing.
test procedure

Ref: ISO 29119-1

Source: ISTQB

A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post execution.
test process

Source: ISTQB

The set of interrelated activities comprising of test planning, test monitoring and control, test analysis, test design, test implementation, test execution, and test completion.
test process group (TPG)

Ref: After CMMI

Source: ISTQB

A collection of specialists who facilitate the definition, maintenance, and improvement of the test processes used by an organization.
test process improvement

Ref: After CMMI

Source: ISTQB

A program of activities undertaken to improve the performance and maturity of the organization's test processes.
test process improvement manifesto

Ref: Veenendaal08

Source: ISTQB

A statement that echoes the Agile manifesto, and defines values for improving the test process.
test process improver

Source: ISTQB

A person implementing improvements in the test process based on a test improvement plan.
test progress report

Source: ISTQB

A type of test report produced at regular intervals about the progress of test activities against a baseline, risks, and alternatives requiring a decision.
test pyramid

Source: ISTQB

A graphical model representing the relationship of the amount of testing per level, with more at the bottom than at the top.
test report

Source: ISTQB

Documentation summarizing test activities and results.
test reporting

See also: Testprozess

Source: ISTQB

Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders.
test result

Source: ISTQB

The consequence/outcome of the execution of a test.
test run

Source: ISTQB

The execution of a test suite on a specific version of the test object.
test schedule

Source: ISTQB

A list of activities, tasks or events of the test process, identifying their intended start and finish dates and/or times, and interdependencies.
test script

Source: ISTQB

A sequence of instructions for the execution of a test.
test selection criteria

Source: ISTQB

The criteria used to guide the generation of test cases or to select test cases in order to limit the size of a test.
test session

Source: ISTQB

An uninterrupted period of time spent in executing tests.
test specification

Ref: After ISO 29119-1

Source: ISTQB

The complete documentation of the test design, test cases, and test scripts for a specific test item.
test strategy

Source: ISTQB

Documentation aligned with the test policy that describes the generic requirements for testing and details how to perform testing within an organization.
test suite

Source: ISTQB

A set of test scripts or test procedures to be executed in a specific test run.
test technique

Source: ISTQB

A procedure used to define test conditions, design test cases, and specify test data.
test type

Ref: After TMap

Source: ISTQB

A group of test activities based on specific test objectives aimed at specific characteristics of a component or system.
testware

Ref: After ISO 29119-1

Source: ISTQB

Work products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing.
Theme

Source: IREB

In agile development: A collection of related ↑user stories.
think time

Source: ISTQB

The amount of time required by a user to determine and execute the next action in a sequence of actions.
threshold coverage

Source: ISTQB

The coverage of neurons exceeding a threshold activation value in a neural network for a set of tests.
time behavior

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can perform its required functions within required response times, processing times and throughput rates.
Timebox

Source: IREB

A fixed, non-extendable amount of time for completing a set of ↑tasks.
Tool* (in software engineering)

Source: IREB

A (software) ↑system that helps develop, operate and maintain systems.
Total Quality Management (TQM)

Ref: After ISO 24765

Source: ISTQB

An organization-wide management approach to quality based on employee participation to achieve long-term success through customer satisfaction.
tour

Source: ISTQB

A set of exploratory tests organized around a special focus.
TPI Next

Source: ISTQB

A continuous business-driven framework for test process improvement that describes the key elements of an effective and efficient test process.
traceability

Ref: After ISO 19506

Source: ISTQB

The degree to which a relationship can be established between two or more work products.
Traceability*

Source: IREB

1. In general: The ability to establish explicit relationships between related ↑work products or ↑items within work products. 2. In RE: The ability to trace a ↑requirement (a) back to its origins, (b) forward to its implementation in design and code and its associated tests, (c) to requirements it depends on (and vice-versa).
traceability matrix

Source: ISTQB

A two-dimensional table, which correlates two entities (e.g., requirements and test cases). The table allows tracing back and forth the links of one entity to the other, thus enabling the determination of coverage achieved and the assessment of impact of proposed changes.
transcendent-based quality

Ref: After Garvin

See also: manufacturing-based quality, product-based quality, user-based quality, value-based quality

Source: ISTQB

A view of quality based on the perception and feeling of individuals.
UML*

Source: IREB

Abbreviation for Unified Modeling Language, a standardized language for modeling problems or solutions.
Unambiguity (of requirements)

Source: IREB

The degree to which a ↑requirement is expressed such that it cannot be understood differently by different people.
Understandability*

Source: IREB

The degree to which an ↑item is comprehensible to its intended users.
unit test framework

Ref: Graham

Source: ISTQB

A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also provides other support for the developer, such as debugging capabilities.
usability

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system can be used by specified users to achieve specified goals in a specified context of use.
Usability

Source: IREB

The degree to which a ↑system can be used by specified ↑users to achieve specified ↑goals in a specified context of use.
usability evaluation

See also: formative evaluation, summative evaluation

Source: ISTQB

A process through which information about the usability of a system is gathered in order to improve the system (known as formative evaluation) or to assess the merit or worth of a system (known as summative evaluation).
usability lab

Source: ISTQB

A test facility in which unintrusive observation of participant reactions and responses to software takes place.
usability requirement

Source: ISTQB

A requirement on the usability of a component or system.
usability testing

Ref: After ISO 25010

Source: ISTQB

Testing to evaluate the degree to which the system can be used by specified users with effectiveness, efficiency and satisfaction in a specified context of use.
usability test participant

Source: ISTQB

A representative user who solves typical tasks in a usability test.
usability test script

See also: Testablaufspezifikation

Source: ISTQB

A document specifying a sequence of actions for the execution of a usability test. It is used by the moderator to keep track of briefing and pre-session interview questions, usability test tasks, and post-session interview questions.
usability test session

Source: ISTQB

A test session in usability testing in which a usability test participant is executing tests, moderated by a moderator and observed by a number of observers.
usability test task

Source: ISTQB

A usability test execution activity specified by the moderator that needs to be accomplished by a usability test participant within a given period of time.
Use case*

Source: IREB

A set of possible interactions between external ↑actors and a ↑system that provide a benefit for the actor(s) involved.
Use case diagram*

Source: IREB

A diagram type in ↑UML that models the ↑actors and the ↑use cases of a ↑system.
Use case model

Source: IREB

A ↑model consisting of a set of ↑use cases, typically together with a ↑use case diagram.
use case testing

Source: ISTQB

A black-box test technique in which test cases are designed to exercise use case behaviors.
User

Source: IREB

A person who uses the ↑functionality provided by a ↑system.
user acceptance testing (UAT)

See also: acceptance testing

Source: ISTQB

A type of acceptance testing performed to determine if intended users accept the system.
user-agent based testing

Source: ISTQB

A type of testing in which a test client is used to switch the user agent string and identify itself as a different client while executing test suites.
user-based quality

Ref: after Garvin

See also: manufacturing-based quality, product-based quality, transcendent-based quality, value-based quality

Source: ISTQB

A view of quality measured by the degree that the needs, wants, and desires of a user are met.
user error protection

Ref: After ISO 25010

Source: ISTQB

The degree to which a component or system protects users against making errors.
user experience

Ref: ISO 9241-210

Source: ISTQB

A person's perceptions and responses resulting from the use or anticipated use of a software product.
user interface

Source: ISTQB

All components of a system that provide information and controls for the user to accomplish specific tasks with the system.
user interface guideline

Source: ISTQB

A low-level, specific rule or recommendation for user interface design that leaves little room for interpretation so designers implement it similarly. It is often used to ensure consistency in the appearance and behavior of the user interface of the systems produced by an organization.
User requirement

Source: IREB

A ↑requirement expressing a ↑user need.
user story

Source: ISTQB

A user or business requirement consisting of one sentence expressed in the everyday or business language which is capturing the functionality a user needs, the reason behind it, any non-functional criteria, and also including acceptance criteria.
User story*

Source: IREB

A description of a need from a ↑user’s perspective together with the expected benefit when this need is satisfied.

Note: 1. User stories are typically written in ↑natural language using a ↑phrase template and are accompanied by ↑acceptance criteria. 2. In ↑agile development, user stories are the main means for communicating needs between a ↑product owner and the development team.
user story testing

Source: ISTQB

A black-box test technique in which test cases are designed based on user stories to verify their correct implementation.
user survey

Source: ISTQB

A usability evaluation whereby a representative sample of users are asked to report subjective evaluation into a questionnaire based on their experience in using a component or system.
validation

Ref: ISO 9000

Source: ISTQB

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.
Validation*

Source: IREB

The ↑process of confirming that an ↑item (a ↑system, a ↑work product or a part thereof) matches its ↑stakeholders’ needs.
value-based quality

Ref: After Garvin

See also: manufacturing-based quality, product-based quality, transcendent-based quality, user-based quality

Source: ISTQB

A view of quality measured by the ratio of the cost to the value received from a product or service.
value change coverage

Source: ISTQB

The coverage of neurons activated where their activation values differ by more than a change amount in the neural network for a set of tests.
Variability

Source: IREB

1. The degree to which a ↑system can be changed or customized. 2. In product lines: The ↑features that can differ among the members of the ↑product line.
Variant

Source: IREB

One of the possible forms that an ↑item (e.g., a ↑requirement) may have.
Variation point

Source: IREB

A point in a ↑product line where an element of the product line (typically a variable or a ↑feature) can be chosen from a set of ↑variants.
Verifiability* (of requirements)

Source: IREB

The degree to which the fulfillment of a ↑requirement by an implemented ↑system can be verified.
verification

Ref: ISO 9000

Source: ISTQB

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
Verification

Source: IREB

The process of confirming that an ↑item (a system, a work product, or a part thereof) fulfills its ↑specification.
Verifizierung der Übereinstimmung mit spezifizierten Anforderungen.

Source: ISTQB

configuration management
Version*

Source: IREB

An occurrence of an ↑item which exists in multiple, time-ordered occurrences where each occurrence has been created by modifying one of its previous occurrences.
View

Source: IREB

An excerpt from a ↑work product, containing only those parts one is currently interested in.
Viewpoint

Source: IREB

A certain perspective on the ↑requirements of a ↑system.
virtual test environment

Ref: ISO 29119-11

Source: ISTQB

A test environment in which one or more parts are digitally simulated.
virtual user

Source: ISTQB

A simulation of activities performed according to a user operational profile.
Vision*(for a system or product)

Source: IREB

A conceptual imagination of a future ↑system or ↑product, describing its key characteristics and how it will create value for its ↑users.
visual testing

Ref: After ISO 29119-11

Source: ISTQB

Testing that uses image recognition to interact with GUI objects.
V-model

Source: ISTQB

A sequential software development lifecycle model describing a one-for-one relationship between major phases of software development from business requirements specification to delivery, and corresponding test levels from acceptance testing to component testing.
vulnerability scanner

Source: ISTQB

A static analyzer that is used to detect particular security vulnerabilities in the code.
walkthrough

Ref: After ISO 20246

See also: Peer Review

Source: ISTQB

A type of review in which an author leads members of the review through a work product and the members ask questions and make comments about possible issues.
Walkthrough*

Source: IREB

A ↑review in which the author of a ↑work product leads the reviewers systematically through the work product and the reviewers ask questions and make comments about possible issues.
Web Content Accessibility Guidelines (WCAG)

Source: ISTQB

A part of a series of web accessibility guidelines published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C), the main international standards organization for the internet. They consist of a set of guidelines for making content accessible, primarily for people with disabilities.
Website Analysis and Measurement Inventory (WAMMI)

Source: ISTQB

A commercial website analysis service providing a questionnaire for measuring user experience and assessing delivery of business goals online.
white-box testing

Source: ISTQB

Testing based on an analysis of the internal structure of the component or system.
white-box test technique

Source: ISTQB

A test technique only based on the internal structure of a component or system.
Wideband Delphi

Source: ISTQB

An expert-based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.
wild pointer

Source: ISTQB

A pointer that references a location that is out of scope for that pointer or that does not exist.
Wireframe*

Source: IREB

A low-fidelity ↑prototype built with simple materials that primarily serves for discussing and validating requirements, design ideas or user interface concepts.
Work product

Source: IREB

A recorded, intermediate or final result generated in a work ↑process.
XiL test environment (XiL)

Source: ISTQB

A generalized term for dynamic testing in different virtual test environments.
zu verwendende Reviewarten, Teilnehmer, Eingangs- und Endekriterien für formale Reviews und Begründung für deren Auswahl. Der Reviewplan ist ein Ergebnis des Reviewplanungsprozesses.

Source: ISTQB

review plan

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

abnormal end

A/B testing

abuse case

Acceptance

acceptance criteria

Acceptance criteria

Acceptance test

acceptance test-driven development (ATDD)

acceptance testing

accessibility

accountability

account harvesting

Activity

Activity diagram

Activity model

Actor

actual result

adaptability

ad hoc review

adversarial example

adversarial testing

Agile

Agile Manifesto

Agile software development

agile testing quadrants

alpha testing

Ambiguity

analytical test strategy

analyzability

anomaly

anti-malware

anti-pattern

API testing

Application domain

application programming interface (API)

appropriateness recognizability

Artifact

Association

atomic condition

attacker

attack vector

Attribute

(auch: Erfüllung)

audio testing

audit

authentication

authenticity

authorization

automation code defect density

automotive safety integrity level (ASIL)

automotive SPICE (ASPICE)

availability

Backlog

back-to-back testing

Baseline

Behavior*

behavior-driven development (BDD)

Behavior model*

Benutzungsschnittstelle.

Berührung erkennen können.

beta testing

black-box test technique

botnet

boundary value

boundary value analysis

branch

Branch

Breitband-Delphi-Verfahrens, bei der das Team einen Stapel an Karten mit vorgegebenen Werten für die Schätzung verwendet.

bug hunting

build verification test (BVT)

Burndown chart

Business requirement

Capability Maturity Model Integration (CMMI)

capacity

capacity testing

capture/playback

Cardinality

cause-effect diagram

cause-effect graph

cause-effect graphing