A stable, change-controlled ↑configuration of ↑work products.
The CPRE Glossary
The basis for successful RE is a common understanding of the terms used. The CPRE Glossary covers the core terms of Requirements Engineering—it is the central reference work across all CPRE modules and levels! The RE@Agile Glossary supplements the CPRE Glossary with terms for Requirements Engineering in an agile environment.
The glossaries are also available in various languages for download.
The CPRE Glossary: An overview of the most important Requirements Engineering terms
Please note that the definitions of terms in the glossaries are deliberately in English only in order to exclude any ambiguities or scope for interpretation that may result from translations.
No matching results found.
Reset filter
B
Reset filter
-
Backlog
-
BaselineNote:
Baselines serve for ↑release planning and release definition as well as for project management purposes such as effort estimation.
-
Behavior
The way in which a ↑system reacts to stimuli, changes its state and produces observable results.
Note:Stimuli may be events or changes of conditions. Their origin may be external or system-internal.
-
Behavior model
A ↑model describing the ↑behavior of a ↑system , e.g., by a ↑state machine.
-
Branch
A line of ↑configurations or ↑work product ↑versions that forks away from the main line (or from another branch) at some point in time.
Note:A branch is created by making a copy of some configuration or work product version and making this copy the root of the branch. A branch may be merged with the main line or with another branch at some later point in time.
-
Bug
-
Burndown chart
A diagram plotting the work items that remain to accomplish on a time scale.
-
Business requirement
A ↑requirement stating a business ↑goal , objective or need of an organization.
Note:Business requirements typically state those business goals, objectives and needs that shall be achieved by employing a ↑system or a collection of systems.