Parallel Running Parallel running is normally conducted after implementation prior to a full cut-over to the new system. However, parallel running may also occur during Acceptance Testing. Parallel running is where an existing system continues to operate as normal, with the new system duplicating the processes and activities. The results of the old and new systems can then be compared. Caution should be taken when planning parallel running as it can place additional and excessive demands on end-users’ time. It may be necessary to consider increased personnel numbers.
The Acceptance Testing Kit – Part 2 39Minor System Deficiency Delays Even minor system modifications, implemented at a late stage of development to overcome deficiencies in the business requirements specification, can cause final delivery of the system to be significantly delayed. Acceptance of the system, subject to any minor modifications being done after the system has been fully implemented, is at the discretion of the Project Manager and Steering Committee. Generally, these issues will be handled under change management or contract variation procedures.
DEPARTMENT ofINFRASTRUCTURE, ENERGY andRESOURCES “Acceptance Testing” The Acceptance Testing Kit Glossary for Projects with an IT Enhancement or Procurement Component A Guide for Project and Acceptance Test ManagersVersion B August 2001 Information Management Branch Corporate Services
The Acceptance Testing Kit – Glossary 1Glossary of Terms Acceptance Criteria Generated by the system end-users and owners to determine if the final outputs of the system are in line with what the Business Unit requires and expects. Acceptance Testing Acceptance Testing is a process undertaken by end-users, operators and maintainers of a system to test a system to ensure it meets business requirements. It is sometimes called User Acceptance Testing (UAT). Acceptance Test Environment The hardware, software, and network environment within which a system will be tested. Acceptance Test Log A log maintained throughout Acceptance Testing by the Acceptance Test Manager and System Administrator to recording significant events and changes to the Test environment and Test data. Acceptance Test Plan A structured document outlining the Acceptance Test approach, the objectives, the activities, the responsibilities, and the detail schedule. Change Management (1)A formal process implemented to manage and minimise the impact of change in an organisation. Change Management (2)A formal process to request a change to a controlled product. This may be a system, a document (such as the System Business Specifications), a test environment, a contract etc. The process includes assessment of the impact and cost, and authorisation, prior to implementation.