Chapter 10. Building a domain-driven specification suite
This chapter covers
- Recognizing good domain models
- Analyzing a ubiquitous language
- Distilling business domains from scenarios
- Recognizing different kinds of business domains
- Organizing a specification suite according to available domains
This is the third chapter in a four-chapter series about managing large specification suites. Chapters 8 and 9 discussed actors and using their abilities and business needs as replacements for the Feature keyword. In this chapter, we’ll analyze what happens when actors have too many scenarios and another level of hierarchy is needed—which usually happens in medium-sized projects.
Figure 10.1 shows a specification suite for the fictional company Activitee of chapters 8–11. We built most of this suite in chapters 8 and 9; the figure presents a slightly expanded version, after the product has grown into a medium-sized project. We’ll talk about the new specifications in section 10.3.
Figure 10.1. Actors in medium-sized projects can have too many abilities, which makes the specification suite more difficult to understand.
