¤ Revise implementation strategy
An implementation strategy was chosen in the EM stage and revised in the BAA stage and again in the BSD phase of the design stage. A review is now undertaken to revise the strategy to take account of decisions made in the BSD phase and to deal with the transition between one implementation area and another.
ð Updates deliverable D3.7.5 Implementation Strategy.
¤ Identify interface data:
- Identify input to the implementation area -
Identify the data required as input to the implementation area from existing systems. The output from this subtask is a list of the fields in the interfaces.
Every field in the implementation area must be put into a category to reflect its expected status at the time of implementation. If implementation is being phased, fields that are implemented in some locations but not in others must be considered.
Categories of fields
Every field in the implementation area fits into one of the following categories:
* Input directly by human resources from data external to existing systems
* Derived from data in systems to be replaced by the project
* Already present on the databases from a system implemented from the ADM
* Already present on the databases from previously implemented phases of this system
* Data necessary to enter the system
- Identify input to existing systems
Identify the data required as input to existing systems from the implementation area. Every item established (created, updated or deleted) in the area must be considered for its impact on existing systems and must be described on the interface field list.
ð Updates deliverable D4.22.2 Module Specification.
¤ Design implementation algorithms
For each field in the interface field input, an implementation algorithm from which the field can be derived must be designed.
¤ Design bridging procedures
This subtask involves designing procedures to cause the bridging to happen. Every field in the implementation area required in bridging has been identified previously, so it is now necessary to ascertain the frequency of bridging from one system to another. This, together with the data, will indicate the types of procedure required. For each bridging procedure, produce the full range of design documentation required and incorporate all the relevant implementation algorithms. All procedures designed in this stage must be developed with standard Application Development Methodology (ADM) techniques and must be included within the scope of the project and the specification.
ð Updates deliverable D4.1.1 Procedure Definition.
¤ Design conversion procedures
This subtask is concerned with designing procedures to enable existing data (held in files or databases that are to be replaced by the new system) to be converted into a form suitable for loading into the new databases. These procedures may include unique load programs to achieve the population of the new databases from each source. Every field in the implementation area for which conversion is required has been identified previously, and the algorithms required will have been defined. Many of the algorithms will also be common to the bridging procedures.
ð Updates deliverable D4.1.1 Procedure Definition.
¤ Design operational control procedures
Design procedures to create manage the load libraries of executable modules for the testing environment - operational control procedures.
ð Updates deliverable D4.1.1 Procedure Definition.
Previous : This is the first Sub-Activity of Activity A4.13
Activity Overview : A4.13
Stage Overview : Design Stage
Overview : Table of Contents