Author
Topic: Developing a meta model and aplying it to an existing project (Read 26528 times)

I am developing a meta model and would like to apply it to an existing model. I would appreciate some advice tegarding the following;

1) How do I apply the meta model to an existing project?2) How can I include existing profiles into the meta model (aka Database Engineering)?3) How do I customise existing profiles (aka Database Engineering)?4) How can I get this done iteratively? I have version 0.5 of the meta model but I strongly suspect that quite a number of elements will be added to the meta model overtime?

Applying any MDG is now simply by adding the appropriate stereotype to the element. This can be done manually or via a script. The latter is nice if you can determine the right set automatically. Else you'd probably need to go the manual way. AFAIK (haven't tried, but remember this from a post) you can drag the right element from the MDG toolbox onto the element to change and it will take its properties.

Applying any MDG is now simply by adding the appropriate stereotype to the element. This can be done manually or via a script. The latter is nice if you can determine the right set automatically. Else you'd probably need to go the manual way. AFAIK (haven't tried, but remember this from a post) you can drag the right element from the MDG toolbox onto the element to change and it will take its properties.

q.

I suspect "here be dragons".

I'm not sure we're necessarily understanding what the OP is asking.

But, assuming it's: "I've created my own MDG and I want to apply it to an existing repository", I suspect q's point about dragging and dropping the new element type over the old element type MANUALLY is the best option as (hopefully) Sparx have (behind the scene) executed the use cases involved.

Trying to do it via scripts (especially if you're not familiar with EA's internals) could e a recipe for disaster. Making sure "all the i's are crossed and t's dotted" is not trivial. It's not rocket science, but not trivial.

We are evolving multiple MDGs into one while the repository is "in flight" and it's doable, but there's a lot of "balls to keep in the air". We have nearly 80,000 items so, manual is not possible.

But, assuming it's: "I've created my own MDG and I want to apply it to an existing repository", I suspect q's point about dragging and dropping the new element type over the old element type MANUALLY is the best option as (hopefully) Sparx have (behind the scene) executed the use cases involved.

Trying to do it via scripts (especially if you're not familiar with EA's internals) could e a recipe for disaster. Making sure "all the i's are crossed and t's dotted" is not trivial. It's not rocket science, but not trivial.

We are evolving multiple MDGs into one while the repository is "in flight" and it's doable, but there's a lot of "balls to keep in the air". We have nearly 80,000 items so, manual is not possible.

Paolo

- There is an EA meta model- The meta model has not been exported to an MDG because it is not complete, I will rather include changes to existing profiles- Points 1, 2, and 3 on my OP refer to the creation of the meta model- Point 4 applies to applying an evolving meta model, possibly using an MDG, to an exisitng "in flight" repository. Doing this manually is not very realistic becuase of the number of elements in the repository

Somehow I sense this is not as straight forward as it may sound. The help in the above link reads:

Quote

In the Project Browser, locate the Package with the <<profile>> Stereotype and open its child diagram.

If you do not have an existing <<profile>> Package, use the 'MDG Technology Builder' option in the Model Wizard to create a new technology, then open the diagram from the newly created <<profile>> Package.

But I, of course, cannot see a 'MDG Technology Builder' on my Model Wizard. What am I missing here?