Information Technology Reference
In-Depth Information
only corrections have to be re-tested. However, this is sometimes difficult to
maintain, because the acceptance time slot in many cases is too short because of
time pressure when scheduling backwards from the PfO date, so that some func-
tions to be tested may trail behind for acceptance testing proper right into the
second time slot dedicated to re-testing. However, initial scheduling should respect
this basic differentiation to aim for a minimum of discipline.
3.4.7 Detailed Tasks During Acceptance Testing
The following discussion takes into account, what has been said about responsibil-
ities and conventions so far.
Pre-condition for the kick-off is that the functional scope to be tested is known.
Functional and technical specifications have been approved. A patch cycle has also
been communicated. Now the planning options as displayed in Figs.
3.2
and
3.3
can
be considered.
The pivotal point is the PfA date. Assumed is a duration for acceptance proper of
three calendar weeks (example), that final week of which is reserved for re-tests.
Backwards there is the necessity that the system environment has to be provided not
later than 1 week prior to the beginning of the acceptance process. This buffer is
required since when uploading software and test data technical problems cannot be
excluded. Furthermore the test data to be created have to be known not later than
1 week before system installation. The drafting of test scripts takes time. Figure
3.2
provides 4 weeks for this. This, however, is the minimum required. This initial
phase could be longer.
Up front there is little slack left. Figure
3.3
displays two hypothetical upload
dates for patches. The first week is out of the question since tests have just started
and programming corrections will take up a finite time as well. Since quite often the
PfO date is fixed closely after acceptance it is almost impossible to move re-testing
further into the future.
Bearing this scheduling in mind during the kick-off the following agreements
should be reached:
Fine tuning over time of the allocation of customer resources to test script
writing/test data definition and participation in the acceptance tests proper,
Written requests regarding system and development support by the supplier on
precise dates
Request for the test environment in detail.
The test scripts themselves can be documented according to the template of
Table
3.3
.
There should be at least one further consultation meeting between kick-off and
the PfA date with all parties concerned checking the state of acceptance
preparation—preferably close to the PfA date. This will be the last opportunity to
