liveBook · Manning

Chapter 3: What is an Example?

What you will learn in chapter 3 of Effective Behavior-Driven Development

Introduces the chapter’s questions about whether examples can specify a story and how many examples are needed, while previewing the topics to come.

After this chapter you will be able to

What it builds on

Section by section

Introduction

Introduces the chapter’s questions about whether examples can specify a story and how many examples are needed, while previewing the topics to come.

3.1 How hard is concrete?

This section explains how to make an example concrete enough to illustrate system behavior unambiguously.

Key terms: context, action, outcome, rule, concrete example, unambiguous, intention revealing concepts, concrete examples, unwanted side-effects, contradictions

3.2 Is all that concrete essential?

The section explains how to keep examples focused on the behavior they illustrate, while using workshops and optional AI assistance to develop them.

Key terms: example, single rule, concrete data, context, requirements workshop, concrete examples, formulate, scenario, facilitator, AI agent

3.3 Do we need more examples?

The section uses an address-change rule to show why an example at a boundary can catch an implementation mistake, while acknowledging that two examples cannot catch every mistake.

Key terms: waiting for pickup state, address change, concrete examples, waiting for pickup, <, <=

3.4 Why stop now?

This section explains why requirements workshops should gather enough examples to clarify desired behavior without turning into exhaustive test-design sessions.

Key terms: discovery phase, requirements workshop, examples, desired behavior, software testing, good coverage, facilitator, product owner, right number of examples, retrospectives

3.5 Rules vs. examples

This section explains why a software specification needs both explicit rules and illustrative examples, and how rule coverage—not an example count—determines whether a story is specified.

Key terms: rules, examples, Specification by Example, user story, acceptance criteria, example mapping, story

3.6 My example illustrates multiple rules!

This section explains how to keep examples focused on one rule even when they depend on other rules, and where focused examples fit alongside other documentation.

Key terms: rule, example, focus, utilize, order state, valid address, requirements workshops, examples, rules, concrete data

3.7 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 2: Structured Conversation Chapter 4: Who does what and when →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.