liveBook · Manning

Requirements structure

As explained in Spec-Driven Development

Requirements structure is the organization and formalization of requirements statements, including their grammar and behavioral expression.

Requirements structure determines how intent is expressed for implementation. Natural-language user stories and acceptance criteria are approachable, but can leave behavior open to interpretation. Constrained grammars and machine-parseable formats can make decisions and missing details more visible, at the cost of readability or learning effort. section 3.6.1

Choose a structure with its consequences in view:

  • Loose natural language may suit simple changes, but can leave failure paths, state changes, and expected outcomes undecided. section 3.6.1
  • Structured requirements can reduce interpretation, while making authoring and review less approachable. section 3.6.1
Figure 3.6 Taxonomy of specification styles based on structure, location, granularity, and organization

The taxonomy places requirement structure alongside specification location, granularity, and organization. section 3.6.1

How Spec-Driven Development covers it

How deep it goes
Compares natural language, constrained grammars, and machine-parseable formats, but does not prescribe one format.
Examples
Contrasts natural-language user stories and acceptance criteria with EARS, Gherkin, and machine-parseable formats.
What you can do after
Evaluate formats for ambiguity, behavioral detail, readability, and authoring effort.
How it connects
Connects requirements to acceptance criteria, EARS, Gherkin, and verifiability.

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