liveBook · Manning

Requirements

As explained in Effective Behavior-Driven Development

A requirement is a statement of a stakeholder need, constraint, or expected system behavior that guides solution development.

A user story is a placeholder for conversation, not the requirement itself. Discovery turns stories into rules and scenarios that describe expected system behavior. section 10.1

Examples make requirements concrete: each describes the system state before a behavior and the outcome expected. A shared, unambiguous understanding helps prevent misunderstandings from becoming implementation mistakes; the examples can later serve as test cases. section 3.4

Keep requirements discovery focused on understanding intended behavior:

  • Explore examples while they reveal new behavior or address concerns the product owner cares about; leave exhaustive combinations for software testing. section 3.4
  • Review after delivery whether there were too few or too many examples, and use that reflection to improve. section 3.4
  • Organize documentation around rules and scenarios, rather than creating one feature file for each user story. section 10.1

Blocklisting

Rules can specify that restricted customers are not offered pay-on-collection, that an email or phone must match the blocklist, and that restrictions apply whether or not the customer is authenticated. section 10.1

Listing 10.1 Structure of the blocklisting feature file (scenario steps omitted for brevity)
Feature: Blocklisting

Rule: Don't offer pay-on-collection for restricted customers
  # Two scenarios merged, because authentication is incidental
  Scenario: Restricted customer is not offered pay-on-collection option

Rule: Customer's email OR phone must match those on blocklist
  Scenario Outline: Decide if customer is restricted

Rule: Restrictions are independent of authentication status
  Scenario: Unauthenticated customer is restricted
  Scenario: Authenticated customer is restricted

Rule: Blocklist is manually configurable
  @manual
  Scenario: Upload replacement blocklist

See how a blocklisting feature file groups scenarios under rules, including a manually configurable blocklist. section 10.1

How Effective Behavior-Driven Development covers it

How deep it goes
Develop requirements through workshop examples, rules, and scenarios, while deferring exhaustive combinations and test coverage to delivery testing.
Examples
Uses restricted-customer blocklisting, pay-on-collection, authentication, and email-or-phone matching to illustrate rules and behavior.
What you can do after
Apply requirements by clarifying expected behavior through examples and documenting rules separately from delivery stories.
How it connects
Links requirements with examples, scenarios, user stories, and software testing while distinguishing their roles.

Also explained in

Compare how 16 books explain requirements →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.