Overview of Team Collaboration Support
| Team collaboration development on CVS, SVN, Perforce and ClearCase had been discontinued starting from Visual Paradigm version 13.0 |
Visual Paradigm supports collaborative and concurrent modeling, and versioning of works in the following ways:
- Visual Paradigm Teamwork Server (A native product developed by Visual Paradigm)
- SVN
- CVS
- Perforce
- ClearCase
In this page, we will have an overview on how administrator and team members can work together with Visual Paradigm’s team collaborative features, and to clarify some of the major concepts in collaborative modeling.
When your team is composed of people with different roles and authorities, you may want to have control over their actions in the modeling tool, to prevent them from making undesired changes. For example, while it is reasonable for a software architect to build class models, it is not reasonable for him to restructure any model developed, through the refactor feature. With VP Server, administrator is allowed configure the access rights of features for members or member groups. For example, by turning off the “
When Visual Paradigm release a new new version, it comes with many new and enhanced features. In order for a project file created in an old version to work smoothly in new version, it has to undergo a conversion process, which involve the checking and patching of project data. The conversion process is a one-off procedure done when you first open the project in new version. It may take a while to complete. So you can imagine if you are working as a team and your team have many, many projects, conversion can be a fairly daunting task.
It is often that you have quite a number of models being reused across projects. Duplicating those models across projects would lead to a management nightmare in which you will need to update all those models on all projects when you need to make changes on it. By creating reference projects in 