System Transformation

Home    Site Map
About Tactical Strategy Group

Organizational Transformation    IT Architecture Transformation
Contingency Planning / Risk Management    Transformation Solutions

This task is an extension of process analysis, but at the next level of detail. The procedure action diagram is the lowest level of procedural specification and key design object from which systems are generated. The main objective within this task is to aid the specification analyst by capturing and importing program specifications into the target CASE environment.

The primary steps within this task focus on selective importation of business rules at the procedural level based on all prior analysis that lead to this point in the redevelopment cycle. The last step of this task however, deviates from this approach using an alternative import facility.

Certain tools automate importation of entire modules into CASE tools. This is a physical import that is to be used only where there are no business or data architecture modifications. Execute the last step only if dictated by a given scenario and where no architectural changes are planned. This step is mutually-exclusive with the other steps in this task.

Specific objectives for this task include:

· Mapping and importing reusable procedures into target procedure action diagrams

· Avoiding the recreation of complex procedures from scratch

· Finalizing procedure action diagrams for the target application

The entrance criteria for the program specification task are listed below.

· Specific scenario to drive either a bottom-up and/or top-down functional integration effort

· Completion of the function hierarchy analysis of the functional assessment

· Completion of the function dependency analysis of the functional assessment

· Completion of code stabilization & re-aggregation tasks based on the scenario driving this effort

· Completion of top-down process hierarchy and process dependency diagrams

· Completion of the general system architecture assessment system level and system/sub-system data flow diagrams (DFD)

· Completion of the dialog analysis and presentation tasks

· Completion of stabilization, data name rationalization, remodularization or other Positioning tasks as dictated by scenario and system condition

· Population of LTM repository model as updated through the process action analysis task

The personnel and skill requirements necessary to meet the program specification task objectives are identified below.

· Redevelopment Expert

- Expertise in capturing, consolidating and importing current business logic into formal representation

· Current Systems Expert

- Knowledge of existing system technical environment

- Knowledge of the functionality of current system

· Target System Functional Expert

- Knowledge of target functional requirements

· Function Modeling Expert

- Expertise in bottom-up and/or top-down process models

· Repository Administrator

- Ability to access and update LTM repository

The system components and related inputs required to initiate and complete the program specification task are listed below.

· Completed Functional Mapping Form 004

· Completed Functional assessment Form 005 - system level functional reusability factors

· Transformation process mapping Form 031 for integrated target system completed in process hierarchy/dependency analysis task

· Completed Screen and report analysis Form 032

· Current systems components - particularly source code

· Process hierarchy and process dependency diagrams representing integrated target system

· All prior data, process and dialog flow diagrams and models completed to this point based on scenario driving this effort

· Legacy transition meta-model (LTM) populated with all system objects and relationships between processes and related physical components in entrance criteria tasks

Technologies supporting the program specification task include design import facility, I-CASE modeling, open systems repository and program editor tools. These tools are used to represent information as required by this task.

This tool facilitates representation of current system flows in dialog flow format. While representation may be derived from physical implementation, it could provide a working starting point for an analyst. Features include:

· Imports multiple physical objects into design workstation

· Program logic tracing and capture

· Logic importation into annotation format

· Annotation load into design workstation

A second set of tools function in a "black box" mode to load entire programs into a design workstation. While feasible and addressed in the last step of this task, use of this type of design import facility is only recommended in cases where no architecture change is envisioned. Features include:

· Supports automated importation of entire COBOL programs into design workstation

· Should only be used where no architecture change is planned

I-CASE analysis workstations provide a mechanism for specifying current and target process action diagrams. While automated input facility is not available in all formats for this type of model, captured rules may be respecified in this format through techniques in this task.

· Analysis workstation: bottom-up/top-down procedure action diagramming

A repository provides an important, yet optional, capability to link business areas, systems and components using the legacy transition meta-model. In this task, repository is used to trace the flow of current processes as input to bottom-up process hierarchy modeling effort.

· Supports manual code analysis and logic path tracing.

· Should display program logic in graphical representations driven by data usage and logic path analysis.

The program specification task is comprised of the following task steps: