Rules on Requirement grammar

Grammar rules examine the grammar of a requirement.

Subordinate clauses

Requirements are checked for subclauses. The reason is clarity. Subclauses should be rewritten as new sentences when possible. The exception is temporal and conditional subclauses.

  • The Temporal rule checks for temporal subclauses in requirements. Temporal sub-clauses begin with: "after", "as", "as soon as", "as long as", "before", "directly", "immediately", "the moment", "once", "since", "until", "when", "whenever", or "while". Requirements will most likely need temporal subclauses to work properly.
  • The Conditional rule checks for conditional subclauses in requirements. Conditional sub-clauses begin with: "unless", "in case", "in the event that", "on condition that", "provided that", or "as long as". Requirements will most likely need conditional subclauses to work properly..
  • The Relative rule checks for relative subclauses in requirements. Relative sub-clauses begin with: "who", "which", "that", "what", "whoever" or "whatever".
  • The Reason or cause rule checks for subclauses of reason or cause in requirements. Sub-clauses of reason or cause begin with: "because", "inasmuch as", "since", "as", or "for".
  • The Purpose rule checks for subclauses of purpose in requirements. Sub-clauses of purpose begin with: "so that", "in order to", "so as to", "for the purpose of", or "to".
  • The Concessive rule checks for concessive subclauses in requirements. Concessive sub-clauses begin with: "though", "although", "even if", "while", "whereas", or "as".
  • The Comparison rule checks for comparison subclauses in requirements. Comparison sub-clauses begin with: "as", "like", "the way", "as if", or "as though".

Conjunctions

Conjunctions join sentences, clauses, phrases, or words. Conjunctions may suggest that a requirement is actually several requirements. This is known as requirement amalgamation.

  • The and rule checks for the word "and" in requirements.
  • The or rule checks for the word "or" in requirements.
  • The but rule checks for the word "but" in requirements.
  • The nor rule checks for the word "nor" in requirements.
  • The for rule checks for the word "for" in requirements.
  • The so rule checks for the word "so" in requirements.
  • The either...or rule checks for the words "either" and "or" in requirements.
  • The neither...nor rule checks for the words "neither" and "nor" in requirements.
  • The both...and rule checks for the words "both" and "and" in requirements.
  • The not only...but rule checks for the words "not only" and "but" in requirements.
  • The partly...partly rule checks for the word "partly" in requirements.
  • The yet rule checks for the word "yet" in requirements.

Grammar

  • The Nominalizations rule checks for nominalizations in requirements. Nominalization is the process of transforming a verb or adjective into a noun. The noun "Specification" is a nominalization of the verb "specify". The noun "requirement" is a nominalization of the verb "require". Too much nominalization can make a text abstract.
  • The Passive voice rule checks for usage of the passive voice in requirements. The passive voice often omits the Actor and directs the attention to the action and its receiver.
  • The Adjectives rule checks for the usage of adjectives in requirements. Adjectives are often wide open for interpretation and should be avoided as much as possible. There are exceptions to the rule.
  • The Adverb rule checks for the usage of adverbs in requirements. Adverbs are often worse than adjectives when it comes to clarity. There are exceptions to the rules.

Related Topics

Requirement rules

Rules on Requirement Structure

Rules on using pronouns in Requirements

Rules on expressions of inexact quantity in Requirements

Rules on special characters and expressions in Requirements

Contents