|
Relying on a SCM tool to manage concurrent accesses is possible, but clearly limited.
This main reason is that the needs for managing model versions (genuine objective of a SCM tool) and concurrent accesses are deeply different:
-
Model versioning: The need is to identify key intermediate baselines (for review, publication, validation, etc.), manage branches allowing maintaining several versions in parallel (development, maintenance, etc.), identity in which version a PCR is fixed, etc. Fragmentation of models should be limited to what has to be versioned.
-
Concurrent accesses: The need is a granularity as fine as possible. From the end user point of view, the locking / unlocking mechanisms have to seamless (i.e. as transparent as possible) so that they do not interfere with their engineering activity. For example, there is often no need for associating each individual model modification to a UCM activity.
Here, fragments are created to manage concurrent accesses and not anymore because their content has to be versioned.
The global idea of Team for Capella Solution is to separate the management of both needs:
-
SCM tools are perfect for managing versions.
-
Team for Capella solution only focuses on managing concurrent accesses.
|