liveBook · Manning

Capability

As explained in Effective Behavior-Driven Development

The set of capabilities and behaviors that a software system provides.

A capability is a distinct piece of business functionality a system provides. Its size depends on perspective: developers and testers may focus on a small behavior, while customers may value a larger activity, such as ordering a pizza online. section 10.7

Keep delivery stories separate from lasting descriptions of functionality. Stories help plan small increments; rules and scenarios capture requirements and expected behavior. Organizing documentation around coherent functionality makes it more stable and easier to navigate. 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

The blocklisting example groups scenarios under distinct rules, including payment restrictions, identity matching, and manual configuration. section 10.1

How Effective Behavior-Driven Development covers it

How deep it goes
Defines functionality as business-facing and contrasts fine-grained component rules with multi-behavior stakeholder journeys, without prescribing a fixed feature size.
Examples
Uses blocklisting rules and online pizza ordering journeys to contrast narrow behaviors with larger customer activities.
What you can do after
Evaluate whether to group documentation by stable business functionality or by incremental delivery stories.
How it connects
Connects functionality to user stories, requirements, rules, scenarios, and journey scenarios.

Also explained in

Compare how 9 books explain capability →

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.