Guided by Examples - Software Driven by Requirements
summary
Describes a pipeline: impact mapping → example mapping → executable specifications → code, using BDD to turn concrete examples into working behavior. Uses Behat and Gherkin run against a domain model wired into Symfony, first executing three scenarios that drive implementation of about 9-10 domain classes; scenarios pass, allow refactoring, and expose missing rules. Produces living documentation (Serenity, Concordion) so specs stay the single source of truth and prevent gold‑plating.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:12Requirements are always vague
- 2:05A courier company
- 3:04Uber
- 3:16Product Owner
- 3:54Communication Gap
- 5:11Developer Gap
- 5:42User Story
- 7:33Software Driven by Requirements
- 10:21Impact Mapping
- 11:25Deliveryto
- 13:55Examples
- 16:44Event storming
- 17:14Customer book
- 19:06Specification by example
- 20:19Example mapping
- 24:35Executable specifications
- 26:49Arrange act
- 27:30Domain driven design
- 30:11Context file
- 35:05Domain model
- 37:40Living documentation
related talks
01h 04mDriving Design through Examples
45mBehaviour Driven Development and Behat: Telling Stories Through Code
38mHow Are We Supposed to Know what We Should Create?
45mLet's talk about software behaviour (BDD)
41mWriting better BDD scenarios
57mSetting a Good Example - How to improve your SbE, BDD & ATDD Artefacts
05mWhy Living Documentation is Cool
31mBDD: Behaviour Driven Development