Centralized repository in DBMS or SVN

Question

I am working on setting up a centralized repository to store enterprise architect (from sparx systems) generated artifacts for the team of 6-8 people to use. Initially thoug

Answer 1

Currently I am looking at the same issue and I found these to be helpful:

Deployment of Enterprise Architect http://www.sparxsystems.com/downloads/whitepapers/EA_Deployment.pdf

Version Control Best Practices for Enterprise Architect http://www.sparxsystems.com/WhitePapers/Version_Control.pdf

[Update]

Our team decided the Version Control route, after months of consideration and testing for our scenario.

Each Enterprise Architect project needs its own database. That means if you have 5 projects, you need 5 databases, one for each team. Scale that to 50 projects or systems, we have 50 databases to work with, manage, etc.

Our approach was:

• Each project has its own folder inside Version Control;
• Reusable Asset Service (RAS) for sharing architecture models;
• Security is done with version control teams;
• Models are shared using import/export (remember to turn on image export!)

What needs to be improved:

We would like the contractors to be able to access these models using the "cloud", but there are security concerns that we need to address first.