Istqb Glossary Report - Foundation (V3.01) -- Part 6

Front 1

precondition

Back 1

Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.

Front 2

priority

Back 2

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

Front 3

probe effect

Back 3

The effect on the component or system by the measurement instrument when the component or system is being measured, e.g., by a performance testing tool or monitor. For example, performance may be slightly worse when performance testing tools are being used.

Front 4

process

Back 4

A set of interrelated activities, which transform inputs into outputs.

Front 5

process cycle test

Back 5

A black-box test design technique in which test cases are designed to execute business procedures and processes.

Front 6

process improvement

Back 6

A program of activities designed to improve the performance and maturity of the organization's processes, and the result of such a program.

Front 7

product risk

Back 7

A risk directly related to the test object.

Front 8

product-based quality

Back 8

A view of quality, wherein quality is based on a well-defined set of quality attributes. These attributes must be measured in an objective and quantitative way. Differences in the quality of products of the same type can be traced back to the way the specific quality attributes have been implemented.

Front 9

project

Back 9

It is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources.

Front 10

project risk

Back 10

A risk related to management and control of the (test) project, e.g., lack of staffing, strict deadlines, changing requirements, etc.

Front 11

qualification

Back 11

The process of demonstrating the ability to fulfill specified requirements. Note the term"qualified" is used to designate the corresponding status.

Front 12

quality

Back 12

The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.

Front 13

quality assurance

Back 13

Part of quality management focused on providing confidence that quality requirements will be fulfilled.

Front 14

quality attribute

Back 14

A feature or characteristic that affects an item's quality.

Front 15

Rational Unified Process (RUP)

Back 15

A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: inception, elaboration, construction and transition.

Front 16

regression testing

Back 16

Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made. It is performed when the software or its environment is changed.

Front 17

reliability

Back 17

The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of operations.

Front 18

reliability growth model

Back 18

A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in reliability failures.

Front 19

reliability testing

Back 19

Testing to determine the reliability of a software product.

Front 20

requirement

Back 20

A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.

Front 21

requirements management tool

Back 21

A tool that supports the recording of requirements, requirements attributes (e.g., priority,knowledge responsible) and annotation, and facilitates traceability through layers of requirements and requirements change management. Some these tools also provide facilities for static analysis, such as consistency checking and violations to predefined requirements rules.

Front 22

requirements phase

Back 22

The period of time in the software lifecycle during which the requirements for a software product are defined and documented.

Front 23

requirements-based testing

Back 23

An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements, e.g., tests that exercise specific functions or probe nonfunctional attributes such as reliability or usability.

Front 24

result / outcome

Back 24

The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.

Front 25

resumption requirements

Back 25

The defined set of testing activities that must be repeated when testing is re-started after a suspension.

Front 26

review

Back 26

An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, informal review, technical review, inspection, and walkthrough.

Front 27

review tool

Back 27

A tool that provides support to the review process. Typical features include review planning and tracking support, communication support, collaborative reviews and a repository for collecting and reporting of metrics.

Front 28

reviewer

Back 28

The person involved in the review that identifies and describes anomalies in the product or project under review. They can be chosen to represent different viewpoints and roles in the review process.

Front 29

risk

Back 29

A factor that could result in future negative consequences.

Front 30

risk analysis

Back 30

The process of assessing identified project or product risks to determine their level of risk, typically by estimating their impact and probability of occurrence (likelihood).