Version Control vs. Baselining

[ch@SVDO]

Hello,
i've got problems with understanding the differences between the Version Control feature and the possibility of creating baselines within EA, although i carefully read the corresponding whitepaper .
The baseline functionality is for making snapshots /freezes of packages/models, so far so good. But what`s the matter with Version Control?
Does VC (e.g. via PVCS or Clearcase) only handle the concurrent access of several users to packages/models/.. within the whole EA-Model?
Or may there also be a possibility of developing several versions of one model at a time?

Why:
Our division is modeling the information architecture of our tool suite that currently is in development. On the one hand at specific milestones a snapshot of the whole model (consists of several root packages, one for each tool) should be made and kept somewhere e.g. with a version label.

On the other hand this model, respectively single packages of that model should be further developed, according to the development of our different tools. This may even be possible even in advance of the snapshot.
So is it possible to have two versions of one specific package within a model with the help of Version Control?

Thanks
Charly

[peter.zrnko]

Or may there also be a possibility of developing several versions of one model at a time?

With version controlled package you have also the history of this package and it's possible to view/retrieve old versions in read only format (see Review Package History in the help file). You can have one version in EA project A and another in EA project B.

If you want to work on separate versions of the same package, you can duplicate/branch (outside of EA) the xmi file in the version control repository. But there is no merge support, only compare (compare with the version on disk). I also didn't find any simple way how to compare actual version of a package with it's version in the repository.