Enteprise Repository Management

[ajaxx]

This is general question that I'm sure some of you have faced.  My organization is transitioning from one product line to new product line.  We are designing models around the product we are building but we realize that many of the existing components will be part of the overall picture until its all transitioned.

This has resulted in our organization going through some growing pains as we use EA.

We started off by having an EAP that contained the models for a single project.  Collaboration broke down and we ended up moving to the enterprise edition of EA.

Works much better but over time more project roots got added to the repository and its turning into a management mess.  If two root projects are in the repository and each has an object model that contains objects with similar names (consider what happens when a product forks/branches) then it creates problems in our repository.  People end up trying to build new models only to find two "types" with the same name and not knowing which is which.

So now I've kicked everyone out of the main repository and have asked them to work on their own projects in EAP files again and to import their work up to the main repository only after they've finalized their designs.

I'd like to know how others have managed environments with multiple projects and overlap and how you've made EA effective in those environments.

[thomaskilian]

Have you tried searching this forum before? There are a lot of threads dealing with that.