Re-using Models (Core Solutions and Affiliates)

[MissKu]

Hello,

We developing a Model in EA for Core Solution which will be further used and developed in affliliate companies. The Core Solution will be the only, but each company affiliate will customize it more or less.

Could you please share your best practices how to organise this better:

Core Solution in 1 Project, then each affiliate will create a copy and continue development in the Copy Project.

Can we refer somehow to diagrams from the Core Solutions not exactly copying them to New Project?
We would like to keep this as Core Solution might be further developed so to avoid extra work.

Your comments are very welcome!

[Exart]

What do you mean as Core Solution? Is it a structure of packages (Model Template) or something like pattern? Or maybe you would like to create a standard template of model...
In my opinion you should keep in mind that every single project is usually treated as specific project.

[qwerty]

No easy solution for that. One way (I'd recommend) is to have a central repository for each department containing the "common" and the "individual" model. You start with a copy (import strip guid) for each "individual" model from the "common" one. You can use VC (or what I recommend: locking) to secure changes to each model. There must be a central group which deals only with the "common" model. Merging is tough since you must know how guids behave when you merge common->individual and or individual->common.

Good luck!

q.