Information Technology Reference
In-Depth Information
Fig. 7.5 Preparation
check list
Preparational Phase
empty system
new software version
identification of customizing variables
dump from source system
allocation of tasks
consultation
time schedule
7.2.3 Separate Milestone
After a preparation phase (see below) the test system is built as an empty basic
configuration without data upload. Before the first data can be loaded a customer
specific structure has to be set up. The relevant customising consists of a technical
and a business related part. Interfaces have to be regarded separately taking into
account the partner systems to be included. Other separate subjects are the treat-
ment of error codes as well as the layout of log files.
Before the start or during acceptance testing but not later than after the data
upload customising should undergo separate acceptance tests. After acceptance the
transfer to the production environment can be carried out.
7.2.3.1 Preparation Phase
In this phase representatives of computer operation, development and end users
come together under the guidance of the acceptance coordination. A checklist like
in Fig.
7.5
is established.
Early enough before the PfT date the main tasks will be allocated to the
responsible persons with fixed target dates. Basically, the following will be decided
upon:
Sizing of the test system including all necessary access rights for acceptance
testers; its logical address
Final status of the new software version with all components required (GUI,
functions, interfaces)
Identification of customising variables
Origin of data dump for first upload: source system (see below).
The customising variables are separated into technical and business related ones.
At this point it is important that the contents of these variables are finalised. To do
this, it is sometimes necessary to address different business units, for example
finance for financial company codes. For this again the responsible persons for
acquiring this information should be named.
