Specification by Example is a software development practice in which requirements are defined as concrete examples with inputs and expected outcomes rather than abstract descriptions, and those examples are used both as automated acceptance tests and as living documentation that stays current. It became widely known through consultant Gojko Adzic's 2011 book of the same name, which distilled the practices of many teams.
It emphasizes a collaborative process in which business stakeholders, developers, and testers create the examples together, and it is closely tied to BDD, ATDD, and techniques such as Example Mapping. Because examples are treated as executable specifications, it is used as a way to reduce ambiguity in requirements.