Find a term
Understand the metrics, models, and methods behind modern engineering. Clear definitions, practical examples, and a closer look at what the numbers actually mean.
Terms beginning with B
82 termsBlended AI rate
Blended AI rate is an average rate combining models, token classes, or pricing tiers. It gives teams a way to name, measure, or reason about an economic property of an AI workload without treating raw usage as proof of value.
Token costs and AI ROIBLEU score
BLEU score is a defined lens for examining AI system behavior with a stated task, evidence, and interpretation rule.
Evaluations and benchmarksBlocked time
Blocked time is the elapsed duration during which a work item is unable to make its next meaningful transition because an explicit obstacle prevents progress. It is a part of waiting time, not active implementation time.
Flow and capacity planningBlocked work
Blocked work is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningBlocker
Blocker is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningBlocker aging
Blocker aging is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningBlocking reason
A blocking reason is the classified cause attached to work that cannot proceed. Common classes include dependency, decision, environment, capacity, defect, and approval, but the useful taxonomy depends on the workflow.
Flow and capacity planningBlue-green deployment
Blue-green deployment is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBlue-green routing
Blue-green routing is a model-routing or gateway concept used to manage traffic selection for AI requests. It describes a distinct decision, control, interface, or observation point between an application and one or more model providers.
Model routing and gatewaysBoolean parameter
A function argument whose true or false value selects behavior or a mode.
Code quality and technical debtBootstrap confidence interval
Bootstrap confidence interval is a defined lens for examining AI system behavior with a stated task, evidence, and interpretation rule.
Evaluations and benchmarksBootstrap resampling
Bootstrap resampling is a statistical or measurement concept used to describe, compare, or interpret engineering data. Its meaning depends on the unit of analysis, data-generating process, and question being asked.
Measurement and experimentationBOS token
BOS token is a language-model concept about instruction design and control. It names a mechanism, representation, prompting pattern, decoding control, or context behavior that can change how an AI system processes input and produces output.
LLM fundamentalsBottleneck
A bottleneck is a workflow stage or capability whose effective capacity limits the rate at which the whole system can complete work. It is identified through sustained evidence of constrained flow, not simply because a stage feels busy.
Flow and capacity planningBoundary value analysis
Boundary value analysis is a software testing or test-design practice used to gather evidence about a defined risk, behavior, boundary, or operating condition. It makes the question under test explicit, identifies the inputs and observations that matter, and gives a team a repeatable basis for deciding whether the result is acceptable.
Code quality and technical debtBox plot
Box plot is a statistical or measurement concept used to describe, compare, or interpret engineering data. Its meaning depends on the unit of analysis, data-generating process, and question being asked.
Measurement and experimentationBranch by abstraction
Branch by abstraction is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.
Code quality and technical debtBranch coverage
Branch coverage is a software testing or test-design practice used to gather evidence about a defined risk, behavior, boundary, or operating condition. It makes the question under test explicit, identifies the inputs and observations that matter, and gives a team a repeatable basis for deciding whether the result is acceptable.
Code quality and technical debtBranch lifetime
Branch lifetime is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBranch protection
Branch protection rules define merge conditions for important branches, such as required reviews, status checks, or restrictions on direct pushes.
Code reviewBreaking change
Breaking change is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.
Code quality and technical debtBreaking change rate
The proportion of public interface changes that require consumers to modify or redeploy.
Code quality and technical debtBudget policy
Budget policy is a model-routing or gateway concept used to manage policy enforcement for AI requests. It describes a distinct decision, control, interface, or observation point between an application and one or more model providers.
Model routing and gatewaysBuild artifact
Build artifact is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBuild debt
Build debt is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.
Code quality and technical debtBuild failure rate
Build failure rate is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBuild feedback time
Build feedback time is the elapsed time between a software change entering a build or validation workflow and the point when useful build or test feedback is available to the team. It includes execution and queueing time when the boundary includes both.
Developer productivityBuild provenance
Build provenance is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsBuild queue time
Build queue time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBuild reproducibility
Build reproducibility is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsBurn-rate alert
Burn-rate alert is detection of how quickly a service consumes error budget relative to its SLO window.
Reliability and observabilityBus factor
The minimum number of people whose loss would put a project or critical area at serious operational risk.
Code quality and technical debt