Requirements Specification

A requirements specification, in the broadest sense, is an agreement between the customers and the organization regarding what must be built to satisfy user needs.This kind of term is often used to encapsulate various types of requirements documents and specification documents - and, to be sure, that is fine as long as everyone is clear on what is and what is not contained within the term. The bottom-line is that you have to determine if there is an operational reason to make a distinction. In other words, if you will respond differently to something that is a "specification" than you would to sometihng that is a "requirement" and furthermore if that differing response is warranted, then you should use two terms.

Thanks for your time!