half of all requirements errors are related to domain, and then asserts that
the vast majority of requirements processes do not explicitly address domain
issues. This is one of several ways in which Correctness by Construction differs
from other requirements elicitation, specification, and verification methods.