4.4. Development Environment

TM’s philosophy is to handle complexity by subdividing a transform project into a number of transforms. Transforms are of two types; independent transforms are executed whenever the transform project runs whereas dependent transforms are executed only if called by another transform. The transform project describes mapping between a source and target model (or group of models), and each transform describes the mapping starting at a source and target element (e.g. XML entity or RDBMS table).

Wizards assist users in virtually all key aspects of transform design and creation, database lookup etc. A comprehensive, context -sensitive Online Help is available to assist whenever required.

The design tool GUI displays all aspects of the source and target models using simple icons showing such things as primary key, root elements, relationships, strings, XPaths, mandatory elements, cardinalities, and what has been mapped.

Transforms are created principally using a drag and drop paradigm and are displayed as a powerful humanly readable mapping syntax that can be understood by both programmers and domain specialists.

Transform statements are displayed in a high level syntax which abstracts away the differences between the different data formats. Database models, for example, appear using the same paradigm as XML or Java. This high-level abstraction provides significant benefit to the user and is easily understood by a developer or domain expert. Transform statements are generally declarative, but may include coding patterns such as IF THEN ELSE, CASE etc., and transforms can be organised such that one transform can call another.

User-Defined Java functions can be developed internally in the Transformation Manager Tool suite or externally in a client’s preferred Java integrated development environment (IDE).

Transforms are easily maintained as model or transform changes are required and the high-level syntax ensures changes can easily be introduced by users who may not be familiar with the original transform design. If a model change occurs, as is very often the case, a new version of a model can be loaded, and the transform statements that are no long valid are automatically detected. Users need only make the required incremental changes.

---

GO TO: TRANSFORMATION MANAGER HOME        TRANSFORMATION FEATURES

---