Great software starts with a meaningful description of its users and intent. Exploring requirements with Specification by Example is a collection of hand-picked chapters selected from three novel and insightful books. We hope they'll give you a glimpse at how to write clear specifications in a collaborative, purpose-driven way.

In Exploring requirements with Specification by Example you'll get an overlook of key process patterns essential for using a specification by example approach. Next, you'll go on a whirlwind tour of behavior-driven development and how to implement the basics into your pipeline. Finally, you'll learn how to pick great scenario outlines to use in your documentation. Altogether, you'll have the right frame of mind for writing specifications that improve the quality and usefulness of your software!

What is Specification by Example?

The clearest way to communicate a software specification is to provide examples of how it should work. Specification by Example is a collaborative method for specifying requirements and tests by collecting and documenting use cases. The method brings four great benefits to your team: it produces living, reliable documentation anyone can read; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it lets everyone know that the end product is built exactly for its purpose!

This powerful technique is fully documented in Specification by Example by Gojko Adzic.