Simultaneously work with other users and dynamically see their modifications.
All changes on the models and representations are automatically propagated across all users’ views.
Don’t waste your time resolving conflicts generated by concurrent updates.
Only the necessary objects are automatically locked and released. On-demand locks can also be created.
Your models and their representations always remain accessible.
The data stored in the repository can be exported via a standard file format or open APIs.
Team for Capella provides a fine-grained concurrency management policy:
only the minimum set of elements are locked when modified, and automatically released on saving.
|Implicit locking||Any object being edited is automatically locked. It is notified to other users by a specific icon visible on all the representations where the object is visible. The lock is automatically released once the modifications are saved.|
|Explicit locking||It is possible to explicitly lock objects to avoid their modifications by other users. The lock is released on demand.|
|Instant updating||As soon as a modification on a model element is saved, it is instantly reflected to other users who view the same object. .|
|Local project export||Modeling projects which are installed on your environment can be exported to the remote repository and shared with other team members.|
|Remote project import||Projects installed on the remote repository can be imported into your environment.|
Obeo leverages its expertise in Eclipse technologies to help you integrate Capella
with other tools and extend the workbench for your particular engineering concerns