Too many releases will result in extra work and delay the Acceptance Test

Too many releases will result in extra work and delay

This preview shows page 43 - 46 out of 96 pages.

Too many releases will result in extra work and delay the Acceptance Test schedule, bringing into question the overall quality of the delivered system. Where there is an
Image of page 43
The Acceptance Testing Kit – Part 2 31 external system supplier, the consequences of this should be determined by the contractual conditions. The Acceptance Test Manager and the Project Manager, with advice from the Service Provider Project Manager if required, will determine the degree and extent of retesting necessary. ‘Patching’ The System While a “quick fix” may seem like a good idea at the time, don’t rush into any process of making software or system “patches”. It can often result in undocumented changes together with problems reconciling subsequent system releases with any patches and can lead to loss of control of the system and the status of the Test Environment. The Acceptance Test Manager can authorise patches, but only after considering all the options and preferably, allowing for the ability to reverse any changes. Remember to keep accurate documentation! Suspending or Cancelling Testing Where problems exist that inhibit the continuation of effective Testing, the Acceptance Test Manager (under advice from the Project Manager) may suspend Acceptance Testing until the relevant problem or problems are resolved. If no resolution is possible in the immediate future, there may be grounds for cancelling any further testing. The criteria for suspending or cancelling Acceptance Testing should be documented in the Acceptance Test Plan and in the Contract.
Image of page 44
The Acceptance Testing Kit – Part 2 32 Phase 4 Closure Formal Acceptance Once all Acceptance Criteria have been met, the Acceptance Test Manager is in a position to recommend formal acceptance of the system. Upon this recommendation to the Project Manager, the Project Sponsor or Project Steering Committee will formally accept the system. Acceptance is possible even if there are still specific (yet minor) outstanding problems, providing agreement has been reached on problem resolution following system implementation. The system may be accepted with the qualification that these non-critical items will be corrected to an agreed schedule under Warranty or Contract variation. In this way, acceptance can be achieved without unnecessary delay for minor items of non-compliance. The decision to allow a “qualified acceptance” and the items deemed “minor” is the prerogative of the Acceptance Test and Project Manager, and the Manager of the Business Unit that owns the system. Ideally, there should not be undue delay from completion of Acceptance Testing to system implementation. However, this may depend on overall Project and implementation planning. Test Records Management and Retention As far as is practicable, all test records should be retained at least for the duration of the Warranty period. Ideally the electronic components can be archived to off-line media.
Image of page 45
Image of page 46

You've reached the end of your free preview.

Want to read all 96 pages?

  • Fall '18
  • acceptance testing, Acceptance Test Manager

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture