Team Collaboration

Design application collaboratively with VP Teamwork Server, Subversion, Perforce and CVS.
Concurrent modeling with CVS server

Concurrent Versions System (CVS) is a popular source code and files repository. CVS has a long history, and is an open source and free repository. The integration of CVS allows all team members to view and edit the same project, or even same diagram simultaneously. Visual Paradigm for UML employ local workspace concept for collaborative modeling. The normal usage is to checkout project from CVS server, then modify project and commit changes to CVS Server. Thanks to the concept of local workspace, you may bring your notebook to customer's office, and start working with the project without connecting to the CVS Server. After all, you will commit the changes to CVS Server when you back to the office.
Commit partial changes to server

- Commit part of local modification to CVS
- Commit diagram
- Commit some shapes
- Commit some model elements
View and compare old revision with CVS server

CVS keeps all histories of changes of diagrams and model elements. With CVS you can review and compare change histories of specific diagram and model element visually with the "Revision History" function. You can also export and open full project of old revisions.
- Browsing change histories (old revisions)
User's Guide
Detect and resolve conflicts with CVS server

Visual Paradigm for UML helps merge changes from different team members during commit or update. Let's say when two or more team members have modified the same model element, and performed commit or update one after the other, the merge engine will detect that there is a conflict occurred, and prompt to resolve the conflict. Conflicts can be resolved by overwrite (keep local change) or revert (keep server change).
- Resolving conflicts
User's Guide
Project baseline with branching and tagging with CVS server

Business process improvement and software development is a continuous process. There are several milestone and release points throughout the process. In Visual Paradigm for UML you may create a baseline for milestone or release, by creating tag of project - a frozen revision of project. You may compare changes of business process, static design, behavioral design and database design between releases with few mouse clicks. Sometimes, your team may need to examine risky idea on the model, or to carry out long term development tasks, and want to isolate the work from stable trunk, branch is what you need. There is a branch feature for creating an isolated revision of project. Your team can keep modifying the branch and merge the branch to trunk after the development is completed and tested.


