Grammar
The following messages deal with grammar issues, both on requirement level and on specification level.
Nominalization of adjective/verb.
Nominalizations are verbs and adjectives that have been converted into nouns, for example output from put out, requirement from require, and failure from fail.
Too much nominalization in a document can make the content sound abstract and difficult to understand. Requirements Specifications often contain several hundred nominalizations. It is not possible to remove them all, and while a requirement text needs to be as clear as possible, a plain text paragraph can afford to contain some nominalizations. Do not convert nominalized nouns back to their original adjective.
Sentence in passive voice.
Sentences can be written in the active or in the passive voice. An example of the passive voice is:
IP-addresses are leased to clients in the network.
Or the active voice:
The DHCP server leases IP-addresses to clients in the network.
The passive voice is considered wordy and weak. Sentences in active voice are generally clearer and more direct than those in passive voice.
Adverb.
An adverb has been found, which is not allowed according to an active rule.
Adverbs are often open for interpretation. Therefore, they are a source of ambiguity and should be avoided in requirements. But there are adverbs that can be used. Adverbs such as "never", "latest" and "daily" can often be used without risk.
Terms that are defined as either Actors, Definitions or Abbreviations are not assigned
issues, even if they are adverbs. This is a work around for difficult requirements. Terms are
always case sensitive. A Definition or Actor can be written on different grammatical forms,
separated by commas, semicolons, vertical bars or slashes. For example: "foot; feet" or "user/users/end-users"
or "issue | issues". Abbreviations can contain one
term only.
Adjective.
An adjective has been found, which is not allowed according to an active rule.
Adjectives are often open for interpretation. Therefore, they are a source of ambiguity and should be avoided in requirements. But there are adjectives that can be used without risk. Adjectives such as "empty" and "last" are seldom problematic to use.
Terms that are defined as either Actors, Definitions or Abbreviations are not assigned
issues, even if they are adjectives. The term "Universal Binary Format" is not assigned an issue if it
is defined. This is a work around for difficult requirements. Terms are always case sensitive. If
the term "Universal Binary Format" is defined in the Definitions chapter, but "Universal binary
format" is used in the requirement, an issue will be generated. Definitions and Actors can be written
on different grammatical forms, separated by commas, semicolons, vertical bars or slashes. For example:
"store, stored, stores" or "foot; feet" or "user/users/end-users" or "issue | issues". Abbreviations
can contain one term only.