6 What is formulation?
This chapter covers
- The importance of unambiguous documentation
- Some popular documentation formats amenable to automation
- An introduction to Gherkin
- The benefits of living documentation
- A taxonomy of scenario granularity and purpose
Formulation is the process of turning a shared understanding of how a system should behave into a business readable specification. On one level this is a trivial activity, since formulation usually produces specifications that are very close to natural language. However, like BDD itself, formulation, while simple, is not easy.
In this chapter we’re going to look at formulation from a high level. We’ll discuss the business language that should be used to document the shared understanding reached during a requirements workshop and some of the different formats that documentation might take. Gherkin is the most common format, so we’ll present a brief overview, with more details to come later in later chapters.
Although automation of formulated scenarios is not covered until part 3, it’s important to establish motivation for the effort required to write scenarios in a format that is conducive to automation. To do that, we need to explain what living documentation is, and the huge benefits that it delivers.