Referencing from one project to another.

[Mr Dude]

We use EA by connecting to a SQL-server. Recently I added a project by creating a new database (this project is concerned with centralized logging and needs to be able to log for all our applications) For this reason, it was removed from one already existing project and moved to a new one (using XML export and import)

Our emphasis on EA-use lies in the UML-modeling/requirements capturing and documentation. I realized quickly that I would like to have references from the old project to the new. Actors and use cases and requirements from the old model would need to be available in the old and the new model, but only maintained in the new model.

Can I do this in our current structure? I've read about solutions that create a 'superproject' (one database presumably) containing all projects, but I'm reluctant as I don't know how much time this would take or what steps are necessary to do this.

Anyone any tips?

[«Midnight»]

I doubt you can find a 'seamless' solution that will work in real time and satisfy all your needs, at least not with the present state of the product.

Perhaps you could work on a near real time solution, as long as you don't expect to ripple changes in your use cases through the model too often. Check into controlled packages; you'll find what you need in the EA help file. This might be a way to 'snapshot' the current state of some elements when necessary, and to apply those to your 'foreground' project as updates.

HTH, David

[Eve]

Controlled packages are the best way to do this.

Perhaps you could write a small automation client to:

• Connect to your old model
• Export the controlled package
• Connect to your new model
• Import the controlled package.

You could then run this nightly, hourly or whatever period is best for you.

[Dermot]

You might also look at using a Base Model for the comparing with original data (using Project | Manage Baselines).  You can also have a look at other options like this in the Deployment & Requirements Whitepapers available from:
http://www.sparxsystems.com.au/resources/whitepapers/index.html

[Mr Dude]

That enough to get me going. I need to start studying and run this by my peers and stuff. Thanks for the input.

[«Midnight»]

Once you get a feel for this, take the time to search the forum for more hints. There have been many threads over the past few years that might be relevant.

This could involve some hours of time, but I think you will learn enough - even if only what not to try - that your time investment will be worthwhile.

David

PS: Simon's idea about using baselines sounds interesting. [Wish I'd thought of it!] Take some time to read up on this, and perhaps the auditing feature as well (though that might be less relevant to your specific requirement).