Multiple projects or VOBs?

问题:

I just took over a ClearCase UCM admin position recently, so any input on this post would be great.

We are currently using one VOB with one project. Say the project that we are working on is the software for a Car, CAR X.

Right now, there is one VOB, one component, and one project called 'CAR X' where everyone (maybe 12-15 developers) works on the software for the car.

In the future, we will probably need to make software for a new car, called 'CAR Y' which may be based off of the software that is used for 'CAR X' with modifications. We would like these to be somewhat separate. Should a new VOB be created or just a new component within the current VOB? If a new VOB and project is created, the files could be imported and modified from the new project, correct? Is there a downside to having one component used for each project housed in the same VOB?

This is complicated to explain, so hopefully I was able to get the idea across. If you need me to be more specific or answer any questions, please leave a comment.

Thank You!

回答1:

It depends on the number of vobs you can expect to create over the next few months /years.

I prefer creating multiple components within a (generalically named) vob, rather than limiting a vob to one component (especially when this latter choice cannot be reversed)

You easily can define 100 components within a vob.
Trying to create / manage 100 vobs is almost impossible in term of ressources involved (too many processes)

If you know you only a few of those vobs to create, go ahead.
But my point remains: multiple components per vob is a model you can scale.