Formal acceptance testing is conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. Such testing is designed to determine whether the system meet the requirements specified in the contract or by the user. Client user acceptance is a phase within the overall development life cycle of a system. Client acceptance testing usually occurs during the implementation phase, but planning and preparation should begin in the design phase, and run concurrently (design/code/implementation). Acceptance tests relate to the functionality of the system as stated in the requirements specification, and functional test cases must be selected to satisfy the agreed acceptance criteria. These tests cover areas such as performance, security, reliability, load/stress testing, volume testing, human computer interaction tests, configuration testing, compatibility testing, documentation, and human procedures. Client acceptance tests should be a strictly controlled process. The breadth, depth and complexity covering planning and initiation of alternative approaches to skills or knowledge applications across a broad range of technical and/or management requirements, evaluation and coordination would be characteristic. Assessment must ensure: The demonstration of competency may also require self-directed application of knowledge and skills, with substantial depth in some areas where judgement is required in planning and selecting appropriate equipment, services and techniques for self and others. Applications involve participation in development of strategic initiatives as well as personal responsibility and autonomy in performing complex technical operations or organising others. It may include participation in teams including teams concerned with planning and evaluation functions. Group or team coordination may also be involved. The person will need to ensure that: System operates in the manner expected Supporting material such as procedures and forms is accurate and suitable for the purpose intended There are no gaps in functionality Individual elements and the overall system provide the desired result or functionality Unit and suite user documentation is available and accurate User-accepted code is copied correctly to the live area. Version numbers are correct and the code is operational |