liveBook · Manning

Behavior-driven development

As explained in Build High Value Software Systems

A development practice that specifies and tests software behavior in a form intended to be readable by both technical and non-technical stakeholders.

Behavior-driven development (BDD) expresses software behavior in readable feature files so technical and non-technical stakeholders can review and approve what a feature should do. It aims to reduce business-development misalignment by making intended behavior explicit. section 4.1.2 section 4.1

This approach is most useful when business stakeholders actively help define and review behavior: they can confirm requirements or spot omissions. The tradeoff is extra translation and maintenance; wording changes can break tests, and rules may be duplicated in feature files and code. section 4.1.2

How Build High Value Software Systems covers it

How deep it goes
Defines the stakeholder-facing goal, illustrates a feature file, and weighs maintenance costs without detailing implementation mechanics.
Examples
Shows a subscription purchase scenario covering confirmation, premium-account upgrade, and compliance transaction capture.
What it assumes
Assumes active business-stakeholder participation makes translation and maintenance overhead worthwhile.
What you can do after
Review behavior scenarios with business stakeholders and surface missing requirements before building features.
How it connects
Contrasts BDD with TDD and places it alongside DDD and SDD as approaches that shift the trusted source of truth.

Also explained in

Compare how 8 books explain behavior-driven development →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.