Modeling collaboratively with Subversion

Subversion (SVN) is a popular version control system that store artifacts centrally and keep track of changes and histories. All Visual Paradigm client products are integrated with Subversion to facilitate collaborative modeling. Your team can use Subversion repository to store project files, keep track of changes and perform modeling concurrently. Branching and Merging of project will be available in the next release.

Teamwork Server, another product of Visual Paradigm, is not required for integrating with Subversion. The integration is supported in the following products (and editions):

Product	Edition
Visual Paradigm for UML	Standard or above
Smart Development Environment	Standard or above
DB Visual ARCHITECT	Java, PHP, .NET and Professional
BP Visual ARCHITECT	Analyst
Agilian	Standard

* The viewer edition of all products support check-out and update Visual Paradigm project from Subversion server.

In this page, we will describe how to work collaboratively using Subversion. Operations such as importing a project into Subversion repository, committing a project to server, and updating a project from server will be covered.

Importing a project to Subversion Server

Developers who take part in the project can add a Visual Paradigm project to the Subversion server. We call this process to import a project to the Subversion server. To import a project to the Subversion server:

Select Tools > Teamwork > Open Teamwork Client... from the main menu.

This shows the Login to the Teamwork Server dialog box.
Select Subversion as Server.

This expands the dialog box to show additional fields for connecting to the Subversion server.

Fill in all the fields to connect to the Subversion Server. You may need to contact the repository administrator for assistance in filling in the information.

Field	Description
User name	The name of user under which to connect
Password	Password for the user
Repository	The path of the Subversion repository
SVN Path	The path of the svn.exe file (The default is pointed to the svn.exe inside $vp-suite-install-dir/bin/vp_windows/svn/bin)

Press the Login button to connect to the server. This shows the Manage Project dialog box, which is for selecting a project file to work with.
Press OK to skip this dialog box. This shows the Teamwork Client dialog box.
Press Import... This shows the Import Project dialog box.
Enter the project name of which to import.

Specify the source of the project to import to the Subversion server.

Option	Description
Currently opened project	The project that is opened in the running application
Create new project	A blank and new Visual Paradigm project
Import existing project	An external project file

To create a remote folder to store the project in server, right-click on a tree node and select New Remote Folder from the pop-up menu.

If Create folder for project is checked, this will create a remote folder, which have the same name as the project file, for storing the project file.
Click OK when done.

Checkout a Project

By importing a project to the server, clients can check that out from the Subversion server to the local machine.

Select Tools > Teamwork > Open Teamwork Client... from the main menu to open the Teamwork Client project dialog box.
Select the project to check out with.
Press Checkout to proceed with checking out the project.

Notice that by checking out a project you get a copy of the teamwork project. In order to work with the project, you need to open it in the application. To open a teamwork project, simply click Open Project, which is next to the Checkout button from the Teamwork Client dialog box.

Committing a Project

Local changes that made on a project can be made available on the project in the server. This can be done by committing the project to the Teamwork Server.

Click on the Commit button from the tool bar.

This shows the Commit Project dialog box.
Enter the description of the change and press OK.

This shows the Commit Model(s) dialog box, which list the changes that will be made to the server copy of the project.

A conflict might be found if someone else’s committed change(s) cause conflict with the change(s) you made. You must resolve all the conflicts to proceed with committing the project. There are two ways of resolving a conflict, Overwrite and Revert. By Overwriting, the server version will be overwritten by the local version for that particular change. By Reverting, the server version will be selected.