Multiple Models Overlap

[georgesd]

When, because of project size , one is forced to split a model into multiple projects (separate databases) and there is an overlap between the various projects (models). how to maintain this up to date.
I explain after the split into 2 separate databases we do have:
Lets say one project contains all the data (classes and reverse engineer tables) In that project we do data modelling, mapping etc...
In anopther project we do business and system but as we want to use either classes or tables(entities) we do a XMI export of what we do need initially from data project into business project and all looks well.
Now changes are applied to the data and they impact some of the 'objects' class, table and/or entity and we want to update the business model (maintain the 2 in sync).
If you do a xmi export then import the object resides twice and if a scenario is modified or added the modification is not imported.
If we delete the previously imported objects then we lose all the links (work done).
How to siolve this one??
willing to try anything as long as it works and it is manageable.
thanks in advance for any suggestion.

[thomaskilian]

When, because of project size , one is forced to split a model into multiple projects (separate databases) ...

For sure? What is the background for splitting? Performance? Probably not. So I guess you're looking for a way to manage a large amount of elements. If so, I don't see a reason for splitting an EA repository into many databases. EA has enough ways for structuring large models (in a single database). Or didn't I get your point

[georgesd]

Thomas,
It is performance some diagrams takes up to 15 minutes to open, also to open the model for the first time can take if You have not a pentium 4 with 1 gig ram up to 3 minutes sometimes more.
The server is a very powerfull Unisys server with 8 processing units of 1.5 Gig each.
actually that server is used on average at 40% of its capacity.
so that is what forces us to split the models into 3.
The sql database is arounf 600Mg.
My question is: When one Model uses elements of another model to xmi the first time from that Model is OK, but later when these elements are updated in their owner model to transfer these changes via XMI do not work anymore as it creates a duplicate of each element and if You delete the old one the whole lot goes.
What do You propose to maintain these "copied" elements
Thanks in advance
Have a great weekend in Berlin
Georges

[thomaskilian]

It seems that you don't use the controled package option, do you? If not, right click a package, Package Control/Configure. Having filled the form, you'll notice a red marker next to the package. Using that option will let you share parts between multiple users. I'm not using that since I'm fine with the replication feature. So I can't tell much more, but others can if you have more questions.

Regarding the performance: I'm pretty sure Sparx will fix that problem since it definitely look like a bug in the system.

Have a nice week in South Africa

[georgesd]

Thomas,
Thanks for the info but we did try the control, the main problem is model 1 (own database) export a package containing elements (let say classes) then the XMI produced is imported into model 2 in another database.
The first time around all is perfect but the moment you do it a second time then you create duplicates in model 2, instead of merging the lot and updating the initially imported elements.
That for us is a problem can You help>>
thanks in advance
have a great day in Berlin
Georges

[thomaskilian]

Do you use the package Load/Save (CTL+ALT+L/S)? That works perfectly. You should not use Import/Export (CTL+ALT+I/E). If you use the first variant and have trouble, you should contact Sparx support.