List of Figures

Chapter 1. Key benefits

Figure 1.1. Specification by Example helps teams build the right software product, complementing technical practices that ensure that the product is built right.

Figure 1.2. Key factors for the right kind of documentation for agile projects

Chapter 2. Key process patterns

Figure 2.1. The key process patterns of Specification by Example

Figure 2.2. An executable specification automated with Concordion

Figure 2.3. An executable specification automated with FitNesse

Chapter 3. Living documentation

Figure 3.1. Relish builds documentation websites from executable specifications.

Chapter 6. Specifying collaboratively

Figure 6.1. Teams generally fall into four groups depending on when they start working on examples. Those who need more time for analysis and chasing open questions start earlier.

Chapter 7. Illustrating using examples

Figure 7.1. Example of a customer dialog used as a specification for the Talia system

Chapter 11. Evolving a documentation system

Figure 11.1. Living documentation hierarchy organized by functional areas (such as Payments and User Management). Specifications for the current iteration are organized by stories and features. Known issues waiting for more information are also in a separate holding place.