Team Collaboration
Design application collaboratively with VP Teamwork Server, Subversion, Perforce and CVS.
Concurrent modeling with Subversion server
Subversion is a popular source code and files repository. It is open source, and is a free repository. The integration of Subversion 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 Subversion server, modify project and then commit changes to Subversion 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 Subversion server. After all, you will commit the changes to Subversion server after back to the office. The following movie demonstrates how to checkout project, commit changes to server and update changes from server.
Commit partial changes to server
- Commit part of local modification to Subversion
- Commit diagram
- Commit some shapes
- Commit some model elements
View and compare old revision with Subversion server
Subversion keeps all histories of changes of diagrams and model elements. With Subversion 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. The following movie demonstrates how to open old revisions and use the revision history function to compare changes between revisions in diagram base and model element base.
- Browsing change histories (old revisions)
User's Guide
Detect and resolve conflicts with Subversion 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). The following movie demonstrates how to resolve a conflict in Visual Paradigm for UML Teamwork Client.
- Resolving conflicts
User's Guide
Project baseline with branching and tagging with Subversion 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. The following movie demonstrates how to create a tag (release) revision and branch.
