Het vakgebied Software Testen maakt gebruik van een internationaal jargon, waar de International Software Testing Qualifications Board (ISTQB) een rol speelt in het handhaven van een consistente uitleg van de termen en begrippen. We hebben voor u een doorzoekbaar mechanisme gerealiseerd waarmee u niet alleen de woorden kunt vinden, maar ook de definities ervan kunt doorzoeken.
Mocht u een begrip of definitie missen, laat het ons dan weten.
Standard Glossary of Terms used in Software Testing
Er zijn 87 termen in deze lijst die beginnen met de letter S.
See Sofware Process Improvement.
See Systematic Test and Evaluation Process.
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. [After IEEE 610]
An iterative incremental framework for managing projects commonly used with agile software development. See also agile software development.
The capability of the software product to achieve acceptable levels of risk of harm to people, business, software, property or the environment in a specified context of use. [ISO 9126]
The person who records each defect mentioned and any suggestions for process improvement during a review meeting, on a logging form. The scribe should ensure that the logging form is readable and understandable.
A collection of components organized to accomplish a specific function or set of functions. [IEEE 610]
See resource utilization.
A sequence of executable statements within a component.
Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data. [ISO 9126] See also functionality.
The degree of impact that a defect has on the development or operation of a component or system. [After IEEE 610]
Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system. [IEEE 610]
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). [After CMMI]
A representation of summarized performance measurements representing progress towards the implementation of long-term goals. A scorecard provides static measurements of performance over or at the end of a defined interval. See also balanced scorecard, dashboard.
A device, computer program or system used during testing, which behaves or operates like a given system when provided with a set of controlled inputs. [After IEEE 610, DO178b] See also emulator.
The capability of the software product to avoid unexpected effects from modifications in the software. [ISO 9126] See also maintainability.
An entity in a programming language, which is typically the smallest indivisible unit of execution.
safety critical system
A system whose failure or malfunction may result in death or serious injury to people, or loss or severe damage to equipment, or environmental harm.
Testing to determine the safety of a software product.
See smoke test.
The capability of the software product to be upgraded to accommodate increased loads. [After Gerrard]
Testing to determine the scalability of the software product.
See use case testing.
Test execution carried out by following a previously documented sequence of tests.
A programming language in which executable test scripts are written, used by a test execution tool (e.g. a capture/playback tool).
security testing tool
A tool that provides support for testing security characteristics and vulnerabilities.
A tool that supports operational security.
Testing to determine the security of the software product. See also functionality testing.
See maintainability testing.
session-based test management
A method for measuring and managing session-based testing, e.g. exploratory testing.
An approach to testing in which test activities are planned as uninterrupted sessions of test design and execution, often used in conjunction with exploratory testing.
The representation of selected behavioral characteristics of one physical or abstract system by another system. [ISO 2382/1]
site acceptance testing
Acceptance testing by users/customers at their site, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes, normally including hardware as well as software.
A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details. A daily build and smoke test is among industry best practices. See also intake test.
Software Failure Mode and Effect Analysis (SFMEA)
See Failure Mode and Effect Analysis (FMEA).
Software Failure Mode, Effects, and Criticality Analysis (SFMECA)
See Failure Mode, Effects, and Criticality Analysis (FMECA).
Software Fault Tree Analysis (SFTA)
See Fault Tree Analysis (FTA).
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
A program of activities designed to improve the performance and maturity of the organization’s software processes and the results of such a program. [After CMMI]
software product characteristic
See quality attribute.
The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs. [After ISO 9126]
software quality characteristic
See quality attribute.
software test incident
software test incident report
See incident report.
Software Usability Measurement Inventory (SUMI)
A questionnaire-based usability test technique for measuring software quality from the end user’s point of view. [Veenendaal04]
A document that specifies, ideally in a complete, precise and verifiable manner, the requirements, design, behavior, or other characteristics of a component or system, and, often, the procedures for determining whether these provisions have been satisfied. [After IEEE 610]
See black box testing.
See black box test design technique.
specification-based test design technique
See black box test design technique.
An input for which the specification predicts a result.
A model structure wherein attaining the goals of a set of process areas establishes a maturity level; each level builds a foundation for subsequent levels. [CMMI]
See off-the-shelf software.
See compliance testing.
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another. [IEEE 610]
A grid showing the resulting transitions for each state combined with each possible event, showing both valid and invalid transitions.
A transition between two states of a component or system.
state transition testing
A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See also N-switch testing.
The percentage of executable statements that have been exercised by a test suite.
A white box test design technique in which test cases are designed to execute statements.
Analysis of software artifacts, e.g. requirements or code, carried out without execution of these software development artifacts. Static analysis is usually carried out by means of a supporting tool.
static analysis tool
See static analyzer.
A tool that carries out static analysis.
static code analysis
Analysis of source code carried out without execution of that software.
static code analyzer
A tool that carries out static code analysis. The tool checks source code, for certain properties such as conformance to coding standards, quality metrics or data flow anomalies.
Testing of a component or system at specification or implementation level without execution of that software, e.g. reviews or static analysis.
A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing.
An element of configuration management, consisting of the recording and reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of the approved changes. [IEEE 610]
See resource utilization testing.
A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified work loads, or with reduced availability of resources such as access to memory or servers. [After IEEE 610] See also performance testing, load testing.
stress testing tool
A tool that supports stress testing.
Coverage measures based on the internal structure of a component or system.
structural test design technique
See white box test design technique.
See white box testing.
structure-based test design technique
See white box test design technique.
See white-box testing.
The capability of the software product to provide an appropriate set of functions for specified tasks and user objectives. [ISO 9126] See also functionality.
The process of testing to determine the suitability of a software product
The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829]
A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.
system integration testing
Testing the integration of systems and packages; testing interfaces to external organizations (e.g. Electronic Data Interchange, Internet).
system of systems
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.
The process of testing an integrated system to verify that it meets specified requirements. [Hetzel]
Systematic Test and Evaluation Process
A structured testing methodology, also used as a content-based model for improving the testing process. Systematic Test and Evaluation Process (STEP) does not require that improvements occur in a specific order. See also content-based model.