Requirements Document

  When one is developed or provided, such a document is a specification of the way in which the system is to perform with as little commitment as possible to how this performance is to be accomplished. Behavior, information input/output, and information organization are stressed in terms precise enough so that:

-

the customer and the company understand what is intended;

-

the customer agrees to what is promised;

-

the implementer understands what should be achieved by the code;

-

the tester has a precise statement of what must be validated;

-

the maintainer has a recognized base of correctness to which to refer.