I have the following dilema.
We are a team of around 10 developers concurrently working on a project. My task is to set up the best repository structure to cater
our needs. I have read the IBM's Team Colaboration Guide but haven't found any decisive (or final) answers.
My use case goes as follows:
The software is divided into 5 different entites. For repository we use Team Foundation Server 2012; Using Rhapsody 8.0.2
My proposal is as follows:
Model organization by domains
>Every domain (i.e.: security, I/O, measurement...) is a standalone rpy.>
>Project is another rpy that has several components that include packages as reference from the domain rpys.
> |-> SECURITY
> |->*.cmp; *.sbs
> |->security.sbs (REF) //added to model from SECURITY Domain and part of the Bootloader_CMP
I wonder what are the best practices used? I also wonder if my proposal is too complicated and there is a better solution?
What I do now already is that I will use packages as the smallest unit on version control.
Thanks for reply and best regards