Loading content
BDD encourages the definition of software behavior in natural language, contributing to better communication and understanding. The use of tests that are understandable to both domain experts and technical staff improves quality and reduces misunderstandings.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What you need to understand to reason about a domain.
Behavior-Driven Development (BDD) combines business examples, shared language, and automated tests to develop a system's observable behavior.
Dan North coined the term Behavior-Driven Development in 2006 as an evolution of test-driven development and agile conversations. BDD aligns technical tests more closely with user behavior and business rules; Cucumber popularized readable examples.
Work in a loop: the team describes an example in plain language, clarifies its meaning, automates the steps, and implements only the required behavior. The executable proof stays connected to the business statement and is maintained together when things change.
The description focuses on what a user or another system can observe.
A concrete case makes the rule and expectation understandable.
Business and technical participants discuss the same behavior.
Automated scenarios repeatedly check the agreed statement.
BDD helps with business-critical rules and misunderstandings between roles. Scenarios should express behavior; excessive technical or UI detail makes them brittle and costly.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.