SysML v2 Collaborative Modeling Documentation
This guide provides documentation for client-side collaboration on SysML v2 server projects.
Collaborative modeling allows multiple users to work on different parts of the same server project, ensuring efficient teamwork and real-time collaboration. The collaborative modeling documentation explains the principles of working with server projects stored on one of the following servers:
- Teamwork Cloud
- 3DEXPERIENCE platform
Both Teamwork Cloud and the 3DEXPERIENCE platform provide a repository for storing projects and users, allow managing user permissions, and offer the same solutions and user experience for working with server projects. The only differences between the two servers from the modeling tool side are authentication and project versioning described in the respective chapters of the documentation.
Basic concepts
Before you start working with server projects, get acquainted with the following collaborative modeling concepts.
| Concept | Description |
|---|---|
Server project | A project stored either in Teamwork Cloud or on the 3DEXPERIENCE platform. |
User | A person who can log in to Teamwork Cloud or the 3DEXPERIENCE platform and has permissions to access one or more server projects. |
Version | The smallest possible milestone of the project development in Teamwork Cloud. A new project version is created each time a user commits project changes to the server. Versions are labeled by numbers in ascending order starting from 1 (one). |
Iteration | The smallest possible milestone of the project development on the 3DEXPERIENCE platform. A new project iteration is created each time a user commits project changes to the server. Iterations are labeled by numbers in ascending order starting from 0 (zero). |
Revision | A larger project development milestone on the 3DEXPERIENCE platform consisting of one or several iterations. Revisions are labeled by letters from A to Z. |
Branch | A copy of a server project made at a certain point of the project development. Each project branch can be developed independently. |
Trunk | The base branch of a server project that cannot be deleted. Project branches are usually created from the trunk. |
Comment | An optional description of a project version/iteration made during the project commit. |
Tag | A label of a project version/iteration helping to identify it from other project versions/iterations. |
Commit | A process of sending the changes made in the project to the server. Each commit creates a new project version/iteration. |
Author | A user who has committed a particular project version/iteration. |
Update | A process of loading the latest project version/iteration to the modeling tool. |
Category | A concept for grouping projects in a server repository. |
Used project/project usage | A server project used in the project you are working with. It can be a library, profile, or regular project. |