A requirement pattern contains nine sections:
- Basic details:
- Manifestation, to enable different variants of the same pattern to be distinguished.
- Owning domain.
- Related patterns, if any.
- Anticipated frequency—the number of requirements of this type in a typical system.
- Pattern classifications.
- Pattern author.
- Applicability: the situations in which the pattern can be used (and in which it shouldn't be used).
- Discussion: of the topic in general, and how to go about specifying requirements of this type.
- Content: A list of the items of information that a requirement of this type can contain.
- Template(s): A fill-in-the-blanks starting point for the definition of a requirement.
- Example(s): One or more real requirement definitions. Sometimes these are a more useful starting point for a requirement than the template.
- Extra requirements: A discussion of all the topics for which you might need to write further requirements.
- Considerations for development: Suggestions for developers on how to implement this type of requirement.
- Considerations for testing: Suggestions on what to bear in mind when testing requirements of this type.