1. 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.
2. Applicability: the situations in which the pattern can be used (and in which it shouldn't be used).
   
3. Discussion: of the topic in general, and how to go about specifying requirements of this type.
   
4. Content: A list of the items of information that a requirement of this type can contain.
5. Template(s): A fill-in-the-blanks starting point for the definition of a requirement.
6. Example(s): One or more real requirement definitions. Sometimes these are a more useful starting point for a requirement than the template.
   
7. Extra requirements: A discussion of all the topics for which you might need to write further requirements.
8. Considerations for development: Suggestions for developers on how to implement this type of requirement.
   
9. Considerations for testing: Suggestions on what to bear in mind when testing requirements of this type.