The business/organizational objectives to be achieved by the project or system.
Brief description of the system and functions it is intended to perform.
Identify sources of information used to develop this document, such as IEEE or project documentation.
Any outstanding issues relative to this project, and in particular acceptance testing.
The person(s) responsible for, and involved in, all aspects of acceptance testing, both during preparation and execution, and their roles. Document names and roles or reference the Work Breakdown Structure, where these persons and associated activities are typically identified. Include customer/system owner, development/test team, and external persons/groups.
The scope (boundaries) of the acceptance test - what is, and what is not (that which someone may otherwise believe is) included in the test.
A detailed schedule - also known as a Work Break down Structure (WBS) - indicating all acceptance testing activities to be performed, and the planned start and end dates for each.
Describe the plans for setting up the test environment.
List of individual tests and objective(s) of each test. Note: At least one Test Case should be prepared for each test identified here.
Document what will be included in the Acceptance Test Report. This report usually closes out the acceptance process.
The process that will be used to apply corrections and re-test those cases which fail. This process should be iterative, until each test case has successfully executed.