“Without requirements, there is no way to validate a program design; that is, no way to logically connect the program to the customer’s desires.”
— Benjamin L. Kovitz
If human communication and human memory were perfect, we may not need deliberation and documentation of requirements. Alas, neither is close to true. It is the iterative exercise of modeling requirements, and then documenting them that enables shared understanding to be affirmed, and then shared with those who use requirements to guide design, construction and quality assurance. Requirements are the link between concept and product, and an important standard for measuring solution success.