Glossary all terms 3.1 / Glossary all terms 3.1: B

Власник перекладу встановив такі правила доступу, що ви не можете переглядати чужі варіанти перекладів тут.
Оригінал англійською Переклад українською

balanced scorecard
See Also: corporate dashboard, scorecard
A strategic tool for measuring whether the operational activities of a company are aligned with its objectives in
terms of business vision and strategy.

#1

baseline
Ref: After IEEE 610
A specification or software product that has been formally reviewed or agreed upon, that thereafter serves as
the basis for further development, and that can be changed only through a formal change control process.

#2

basic block
A sequence of one or more consecutive executable statements containing no branches. Note: A node in a
control flow graph represents a basic block.

#3

basis test set
A set of test cases derived from the internal structure of a component or specification to ensure that 100% of a
specified coverage criterion will be achieved.

#4

behavior
The response of a component or system to a set of input values and preconditions.

#5

benchmark test
Ref: After IEEE 610
(1) A standard against which measurements or comparisons can be made. (2) A test that is used to compare
components or systems to each other or to a standard as in (1).

#6

best practice
beta testing

#7

big-bang testing
Ref: After IEEE 610 See Also: integration testing
An integration testing approach in which software elements, hardware elements, or both are combined all at
once into a component or an overall system, rather than in stages.

#8

black-box test design technique
black-box testing

#9

blocked test case
A test case that cannot be executed because the preconditions for its execution are not fulfilled.

#10

botnet
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.

#11

bottom-up testing
See Also: integration testing
An incremental approach to integration testing where the lowest level components are tested first, and then
used to facilitate the testing of higher level components. This process is repeated until the component at the top
of the hierarchy is tested.

#12

boundary value
boundary value analysis

#13

boundary value coverage
The percentage of boundary values that have been exercised by a test suite

#14

branch

#15

branch coverage
The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both
100% decision coverage and 100% statement coverage.

#16

branch testing

#17

buffer
Ref: IEEE 610
A device or storage area used to store data temporarily for differences in rates of data flow, time or occurrence
of events, or amounts of data that can be handled by the devices or processes involved in the transfer or use of
the data.

#18

buffer overflow
See Also: buffer
A memory access failure due to the attempt by a process to store data beyond the boundaries of a fixed length
buffer, resulting in overwriting of adjacent memory areas or the raising of an overflow exception.

#19

build verification test (BVT)
See Also: regression testing, smoke test
A set of automated tests which validates the integrity of each new build and verifies its key/core functionality,
stability and testability. It is an industry practice when a high frequency of build releases occurs (e.g., Agile
projects) and it is run on every new build before the build is released for further testing.

#20

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).

#21

business process-based testing
An approach to testing in which test cases are designed based on descriptions and/or knowledge of business
processes.

#22

Хвилинку...