Specifications must be consistent with all other related specifications in the same document, and in all related documents {Sources, Kin and Children}.

GEN.Unambiguous

All specifications must be unambiguous to the Intended Readership, as practiced or implied, for that document.

GEN.Clarity of Purpose

All specification shall result in clarity to the Intended Reader regarding it's purpose or intent.

Note: it is not enough that the statements are unambiguous. They must contain clarity of purpose: why is this here? “Clear enough to test”

GEN.Notes

All manner of comment, notes, suggestion or ideas which are not themselves the actual engineering specification, but merely background, shall be clearly distinguished as such by using italic fonts.

Note: Alternatives: your organization can choose any other method that clearly distinguishes the comments from the specification.

Note: Suggested Devices: italics, ”double quotes”, Note:…, Comment:…., use of footnotes, use of separate commentary pages.

GEN.Brevity

All specification shall be as brief as possible, in order to successfully support their purpose, for the defined Intended Readership.

GEN.Elementary

Specification statements shall be broken up into their most elementary form.

Note: this is so that they each can be unambiguously cross-referenced externally.

Note: an elementary specification can be referred to by its tag (or global tag), and within that, any unique combination of Parameter (for example Meter, Past) and/or Qualified (for example ”[UK, 1999]” ) may be used to refer to or distinguish an elementary idea.

GEN.Unique

Specifications shall only have a single instance in the entire project documentation.

GEN.Glossary

Words starting with a Capital Letter and in bold must be defined, and when you use a defined word, it must use a Capital Letter and be in bold.

Note: Example: This is a True….

True: defined as: …