Acceptance * 

System acceptance testing is the means by which the supplier demonstrates to the user that all the system requirements, as embodied in the agreed Functional specification, have been met. The tests are carried out by the supplier and are witnessed by the user.

Testing will in most cases be carried out in two stages, before delivery on the suppliers premises and after installation on the users site. Testing may be further sub-divided if a phased sequence of delivery and system build is planned.

Conditions which are to be satisfied  before the start of acceptance testing should be stated in the User Requirements Specification and included in the Test Plan. It is suggested that such conditions should include some assurance that all designated hardware and software is available and has been tested to the suppliers satisfaction and that all post-installation documentation is available.

Subject to the terms of the contract, satisfactory completion of the acceptance tests will lead to:

•      Formal acceptance of the system
•      Payment by the user
•      Handover of all the deliverables
•      Start of the warranty period
•      Start of any support and maintenance agreements.

The user should set out his requirements for system testing in the User Requirements Specification. Information on how these requirements are to be met should be included in the Functional Specification. It is particularly important that the supplier should produce an overall test philosophy and test plan at an early stage in the contract negotiations, and that these should be agreed by the user.

The Test Plan details the testing activities and the organisation of those activities which are to be used to establish that the system satisfies the contractual statement of requirements. The remaining test documentation should be produced by the supplier during the development of the system, with all documents being agreed by both parties.

It is the suppliers responsibility to produce the test documentation, which should include:

•      Test philosophy
•      Test Plan
•      Test Specifications
•      Test logs
•      Test summary
•      Commissioning report
•      Certificate of acceptance

* All acknowledgements to the Institution of Electrical Engineers and the Guidelines for the documentation of computer software for real time and interactive systems. 2nd edition 1990.