Question to forum:
What are the good examples of acceptance criteria or setting the cut-offs for testing, as for example:
1. Test case Documents should be ready 2 weeks before testing
2. No changes will be accepted after final release.
3. Changes after this release will be managed as...
Can you suggest such cut-offs of test phases within releases which can be included for test planning. (system, integration and user acceptance test planning)
There seems to be a couple of questions in your one question but I'll give it a go:
You should definitely have deadlines and timelines for locking down the requirements and design of an application. If you don't "lock down" those two things you can get major scope creep and then your cost and timeline goes right out the window.
There should be a cut off for new requirements and major design changes! Then if new requirements or functionality are found that are needed in the current release, they should be handled as a change control which will affect the budget and project schedule accordingly.
When you are short on time you could always go the Risk-Based Testing way and hit the most important components first.
As far as User Acceptance Testing goes you should always use the requirements to base what gets Accepted by the clients.
As far as acceptance cut-offs go - they are determined differently based on 1) you having your own development team, 2) you are the vendor providing testing services or 3) you are the contracting party who has hired a test lab for its testing activities.
Can you please specify in which of the above you fit into ?