VC on a large project - any suggestions?

[AndyJ]

Hi team,

I'm working on a project that has shared information and distinct information in (currently) two small projects.

To help keep things straight, we've created packages for each sub-project beneath each of the Sparx high-level packages:

For example:

Business Process Model
-->Package A
-->Package B

Requirements Model
-->Package A
-->Package B

We're about to add version control (CVS short-term and SVN long-term) to the mix, and we're wondering if we're making appropriate choices...

In the future (it's possible that we'll have more sub-projects in the mix)

Particularly we're wondering how we'll manage to baseline and maintain Project A and Project B separately, and if checking out one package at a time will be sufficient.

Other than the Sparx white papers (which we have) can anyone recommend practices for managing a set of version controlled projects like this?

Andy

[Geert Bellekens]

Andy,

I would rather go for an approach:
Project A
 - Business Process Model
 - Requirements Model

Project B
 - B...

I think that will be easier to isolate and maintain.

Geert

[AndyJ]

Hey Geert,

That was our first thought, but EA didn't seem to allow it...

Aha! Add new Root Node!

It just goes to show, sometimes with EA you have to look harder.