The concept of using boilerplates for writing statements of requirement is quite simple:
choose an appropriate predefined template, and fill in the gaps.
Each statement of requirement then becomes a generic boilerplate
plus the specific values of selected attributes.
The <user> shall be able to <capability>
at a maximum rate of at least <quantity> times per <time unit>.
<user> = order entry clerk
<capability> = raise an invoice
<quantity> = 10
<time unit> = hour
"The order entry clerk shall be able to raise an invoice
at a maximum rate of at least 10 times per hour."
Using this approach, an organisation can gradually refine a repertoire of ways of expressing
all the kinds of requirement it needs. By encouraging engineers always to choose from the repertoire,
a uniformity of style can be achieved in the organisation.