Validating before delivery

Structured acceptance testing ensures solutions are fit for purpose and ready for deployment

An acceptance testing specification is a formal document that defines the test plan, test cases, and pass/fail criteria used to verify that a system meets end-user requirements and business needs.

Using the URS and FDS

The primary inputs for the test cases are the User Requirement Specification (URS) and the Functional Design Specification (FDS)

Detailed Test Cases

For each function, a specific test case is written which includes a clear objective and a step-by-step procedure for the user to follow

Clear Pass/Fail Criteria

A “Pass” means the system behaved exactly as per the Expected Result and any deviation or error is documented as a “Fail”

Ensuring Systems Meet Requirements

Final Proof

Confirmation that the delivered system meets the business requirements

End-Users

Power of approval in the hands of the people who will actually use the system

Objective Basis

Replaces vague feelings with a checklist of evidence which prevents disputes