Modelling migrating multiple legacy data sources

[Robert Sheridan]

I have had a search here and in the community site and have not found anything on this.

We need to specifiy the migration of legacy data from various sources to a new consolidated data structure and would like to do this in EA rather than a spreadsheet.

My idea is that once we have loaded the physical schemas for the legacy and new databases we use intermediary class operations to document the transformations needed to convert a legacy attribute to the new attribute.  Does anyone have any suggestions for alternative ways of doing this?

Ta

[Geert Bellekens]

You could use association with "link to element feature" to relate the different attributes.

Geert

[Robert Sheridan]

Thanks Geert.  We are looking at using the behaviour and code attributes of an operation to document transformations (typically mapping lookup values which are different in the various systems) so that will work well as we can link from a specific element to a specific operation in the class doing the data transformations.  

For information:  We are looking at having a class for each attribute in the target system which will need a data transformation and then an operation within the class for each source (legacy) system.

[Paolo F Cantoni]

[size=18]...[/size] 

For information:  We are looking at having a class for each attribute in the target system which will need a data transformation and then an operation within the class for each source (legacy) system.

Hi Robert,

Over twenty years ago I came to the same conclusion as you:  That features (attributes, operations) should also be first class citizens of models and they they should be able to participate directly in relationships with other first class citizens.

As Geert points out, the "Link to Element Feature" functionality is a good method to indicate such linkages at higher levels of abstraction/aggregation; but below that you need the detail you've alluded to.

Paolo