Introducing Teamwork Server
When several team members need to work on the same project, version control is always a major concern. The time and effort spent on merging the works of each team member is very expensive, and is very risky that the previous works may be overwritten by the new changes.
Visual Paradigm's Teamwork Server automates these complex development processes, although its concept is very simple:
- The administrator creates accounts for team members.
- The administrator creates projects, and assigns selected members to the project. The read/update project permission is granted to members individually.
- The member logs in to the teamwork server.
- The member checks out (download) a project from the server and opens it on the client side.
- The member modifies the project locally, and then commit the changes to the server.
- The server will compare the local project with the server project, and begin the two-phase checkin process.
- The first phase checks whether conflicts are found. A conflict is the modification of a model/view element that is also modified by other team members. If no conflict is found, the server proceeds to the second phase. Otherwise the teamwork client will notify the member of the conflicts, and ask him/her to select the conflict resolve method before proceeding to the second phase.
- In the second phase, a new revision of the project is created by merging the changes made by the member with the latest project copy on the server. The new project is downloaded from the server to the client, and is reopened so that the member can work on the latest project.
The following resources may help you learn more about the topic discussed in this page.
|Chapter 1. Introducing Teamwork Server||Table of Contents||2. System requirements|