Identify Composite Requirements (Process Notes 3.3)

A composite requirement (also known as a "high-level requirement") does not have its own testable fit criteria, but rather "summarizes" a number of other individually testable requirements. Composite requirements are useful as a way of talking about the combined effect of a number of individually testable requirements. Sometimes a composite requirement is a sign of vagueness or uncertainty.

It is useful to have a composite requirement for each use case. Then you can summarize the requirements at the use case level but you still have connections to each of the testable requirements that compose the particular use case.

When you define a composite requirement, be sure that you have a reason for doing so and that you are not simply taking refuge in generality.