Terminology Flashcards
Acceptance criteria
The criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.
Acceptance testing
Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers, or other authorized entity to determine whether or not to accept the system.
Accessibility
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.
Actual result
The behavior produced/ observed when a component or system is tested.
Ad hoc reviewing
A review technique carried out by independent reviewers informally, without a structured process.
Alpha testing
Simulated or actual operational testing conducted in the developer’s test environment, by roles outside the development organization.
Anomaly
Any condition that deviates from expectation based on requirement 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.
Audit
An independent examination of a work product, process, or set of processes that is performed by a third party to assess compliance with specifications, standards, contractual agreements, or other criteria.
Availability
The degree to which a component or system is operational and accessible when required for use.
Behavior
The response of a component or system to a set of input values and preconditions.
Beta testing
Simulated or actual operational testing conducted at an external site, by roles outside the development organization.
Black-box test technique
A procedure to drive and/ or select test cases based on an analysis or the specification, either functional or non-functional, of a component or system without reference to its internal structure.
Boundary value
A minimum or maximum value of an ordered equivalence partition.
Boundary value analysis
A black-box test in which test cases are designed based on boundary values.
Burndown chart
A publicly displayed chart that depicts the outstanding effort versus time in an iteration. It shows the status and trend of completing the tasks of the iteration. The X-axis typically represents days in the sprint, while the Y-axis is the remaining effort (usually either in ideal engineering hours or story points).
Checklist-based reviewing
A review technique guided by a list of questions or required attributes.
Check-list based testing
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.
Code coverage
An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g., statement coverage, decision coverage, or condition coverage.
Commercial off-the-shelf (COTS)
A software product that is developed for the general market, i.e., for a large number of customers, and that is delivered to many customers in identical format.
Compatibility
The degree to which a component or system can exchange information with other components or systems.
Complexity
The degree to which a component or system has a design and/ or internal structure that is difficult to understand, maintain, and verify.
Compliance
The capability of the software product to adhere to standards, conventions, or regulations in laws and similar prescriptions.
Component
A minimal part of a system that can be tested in isolation.
Component integration testing
Testing performed to expose defects in the interfaces and interactions between integrated components.
Component specification
A description of a component’s function in terms of its output values for specified input values under specified conditions, and required non-functional behavior (e.g., resource utilization)
Component testing
The testing of individual hardware or software components.
Condition
A logical expression that can be evaluated as true or false.
Configuration
The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.