Migration Issues for Revolve

Chapter 1: Introduction

To understand the architecture of the products within the whole MERANT Revolve Transformation Product Suite, please see the chapter Understanding the Revolve Transformation Product Suite in your Revolve Enterprise Edition Getting Started. This explains which features are contained within which product, and how this affects your use of the different products and options, if at all.

This book is intended to help users of:

Product differences that do not require you to make any changes are not, in general, mentioned in this book; these include new features of the product which do not have any specific migration considerations.

You should read the Getting Started book for the product or products you plan to use before reading this or any other documentation provided with this product. The Getting Started book provides an overview of the new features of the product. You should also read the ReadMe help file, which lists any problems that have been found with this release of the Transformation Product Suite.

The rest of this chapter briefly describes how the approach to analyzing an application with this product differs from the approach used with your previous product. The remaining chapters are reference chapters where you can look up particular features and find outline advice on migrating them. The chapters are organized into migration issues that affect Revolve and migration issues that affect Revolve Enterprise Edition.

1.1 Overview

The Revolve Transformation Product Suite enables you to analyze your legacy application to discover its structure; the files it uses; how and where data items are used; and many other details. The results of this analysis are stored in a database, which you can interrogate through many different tools to produce diagrams, reports, and so on, to help you understand the application.

In addition tools are provided that enable you to manage the maintenance of the application - whether as an individual programmer or as leader of a team - by applying rules you define to recognize, categorize and document items that need to be changed for source updates to be complete and consistent.

Several add-on solutions for use with Revolve Enterprise Edition are separately available. They add features for specific purposes:

• AssetMiner helps you identify parts of an application to separate out into modules for use by other applications.

• EuroSmart helps you update an application so that it handles the common European currency, the Euro.

1.2 One Project, Multiple Solutions

As in previous application transformation products from MERANT, all your work with the Revolve Transformation Product Suite is project-based. The first thing you do when you start to analyze an application is to set up a project for the application, in which all information relating to the application is stored.

With previous application transformation products, if you wanted to transform the same application using two or more products, you had to install two separate products, and in each one create a project and project directory. You completed one transformation before starting the next. With the Revolve Transformation Product Suite, you only create one project, regardless of how many transformations you are planning. This is true whether you only use the transformation facilities in Revolve Enterprise Edition, or whether you also use the specific features of AssetMiner and EuroSmart. The same goes for the metering of code. You only meter the code once, in Revolve Enterprise Edition.

If you are part-way through a program of multiple transformations, we recommend that you complete the program using your existing implementations of MERANT transformation products.

Migration Issues for Revolve