TOPIC: Significance of Acceptance criteria as per Requirements Documentation and Project Scope Statement

Hi, On page 118 of PMBOK 5th edition it mentions acceptance criteria, assumptions and constraints under Requirements Documentation. However, on page 123 it talks in detail about acceptance criteria ,assumptions and constraints under Project Scope Statement. My question is why are these mentioned on two different processes?. Is there a unique significance of acceptance criteria ,assumptions and constraints under Requirements Documentation compared to Project Scope Statement.

Kumar, the voice of the customer drive the requirements for your deliverable at the end of the project. You need to record the discussion with the customer. This recording is your requirements documentation. You will return to these documents often. Also, in situations when the deliverable is different than what the customer expected, you'll have documentation to back you up.

Then you have the internal project management documents that dictate to the project team the scope of work you need to accomplish to customer's requirements. Knowing the requirements will prevent you from "gold-plating" or doing more work than is necessary to accomplish the deliverable.