next up previous contents
Next: Pre-delivery tests Up: No Title Previous: Contents

Introduction

This document assumes that there are three distinct phases in the lifecycle of any software in use at ING:

The development phase will normally include the following phases of the ESA software life cycle (see ESA Software Engineering Standards):

The ESA transfer phase will normally include

The ESA operations and maintenance phase will normally include:

It is the delivery phase and the formal acceptance of software systems delivered to ING that this document addresses in detail.

The objectives for ING staff during the delivery phase are to ensure that the product is usable, with reference to the user requirements for the project, by ensuring that the software has the required funtionality and is in working order; and to ensure that the maintenance phase is likely be cost-effective. It is not possible to ensure that the maintenance phase will be cost-effective a priori, but it is possible to ensure that the design and implementation of the software are of a standard which is considered maintainable and to ensure that the software system is adequately documented.

This approach to the delivery of new software systems to ING and their acceptance applies equally to internal and external development programmes. To ensure a degree of impartiality in the case of internal development programmes, staff other than those responsible for the development of the software products will be allocated the task of acceptance testing.


next up previous contents
Next: Pre-delivery tests Up: No Title Previous: Contents


Fri May 23 10:19:54 BST 1997