Version Control and "Migrations" To Continuum

[ccampise]

Hi All-

We're looking to create an Enterprise Continuum (or Repository) in EA.

Ideally we'd like to be able to use artifacts/components from the Repository in our models and then migrate any additions/changes back to the Continuum/Repository (or something that gives us similar functionality).  

The architects work in a centralized environment using the same SQL Server repository, with multiple architects doing different projects simultaneously (but rarely using the same components at the same time).

I first thought version control (via SVN) would give us this functionality, similar to a software development team working on code simultaneously (i.e: check out development code branch locally, make changes, check them in, integrate those development changes back into the production repository/while resolving any conflicts).  But after reading the best practices document (http://www.sparxsystems.com/WhitePapers/Version_Control.pdf) it doesn't seem I'd be able to quite do things in this fashion.

Does anyone have any advice/guidance on this?

Maybe I'm just having a difficult time wrapping my head around the version control features.  

[qwerty]

Setup a central RDBMS as repository and turn on EA security with the option Require User Lock to Edit. Additionally you can setup a script to create a nightly backup which you can put under version control. For me (and my customers) this was the best configuration (for most cases). There might be reasons for different settings ans it is not an easy task. A good config management will take a couple of cycles.

q.