The IQ application will be briefly unavailable on Sunday, March 31st, starting at 10:00am ET. Access will be restored as quickly as possible.
Browse Prior Art Database

System For Automatically Mapping Model Changes

IP.com Disclosure Number: IPCOM000032355D
Original Publication Date: 2004-Nov-02
Included in the Prior Art Database: 2004-Nov-02
Document File: 2 page(s) / 75K

Publishing Venue



System for automatically collecting model changes, and building a list of mapping commands for these changes that will apply to an existing map and target model. Additionally, these mapping commands will apply the same rules previously followed. This enables the user to edit their model, and any mapping changes will automatically be applied without affecting the existing map and target models.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

System For Automatically Mapping Model Changes

When developing an application it is common to have the need to transform data from one set of model objects to a completely different set of model objects (e.g., Java object model to relational database). This is often done by "mapping" the objects from the first model to the objects in the second model. Many tools exist that create these mappings between different metadata models and some of them may also allow additional custom transformations. Prior art has shown that a set of "target" model objects can be generated by executing mapping commands that are based on default metamodel mapping rules. As models are changed over the design lifecycle, the existing maps must react to these changes. Previous solutions to this problem included manual edit of these maps and manual modification or creation of the target models as required. This is a poor solution because it relies on the user making many manual changes to "complete" the map and it introduces the possibility of user error. To avoid these manual changes, another solution was to replace the entire target model by "re-executing" the previous mapping commands which would then generate an entirely new set of target model objects. This solution would fail to duplicate any changes that were made outside the scope of the mapping tools. Thus the user would loose changes that were made outside of the mapping tools. Also, re-executing the mapping commands will not apply user specific transformation rules to any new models introduced.

There are two main ideas:

1) Applying the mapping commands required to map the changed model.

2) Using previously applied mapping rules with the new mapping commands

In the diagram below, target model A has been created from the mapping commands based on the source model A. These mappings already follow default domain specific meta-model rules to create the targe...