In many development scenarios, we often need to reuse, refine, elaborate and transcribe an portion of diagram, known as a design patterns, during the development process or in between development phases. Design pattern can be defined by designing the pattern in a diagram, and saving it as a pattern file. Now, it can be shared across the team easily through the team collaboration support. Users in a team just need a few mouse actions to grab a pattern file created by another member, and reuse on their own design.

To Share a Design Pattern

1. Login to server, checkout and open the teamwork project for managing design patterns.
   
   
   If such as project does not exists, import a new project to the teamwork server, checkout and open it.
2. Design and define the design pattern(s). For information on defining and designing design pattern, refer to: Defining, Configuring and Applying Design Patterns.
   
3. When complete, open the Teamwork Client dialog box by selecting Tools > Teamwork > Open Teamwork Client... from the main menu.
   
4. From the Teamwork Client dialog popped up, select Repository > Synchronize Design Pattern to Server from the menu.
   
5. This displays the Pattern Synchronization dialog box, which displays the patterns that will be committed to server or updated from server. Press OK to confirm.

To Acquire a Design Patterns from Server

The way to acquire design patterns is the same as to commit a pattern. Open the Teamwork Client dialog box and select Repository > Synchronize Design to Server. New pattern files can then be obtained from the server.

After that, user can model with the use of the acquired design patterns.

To Resolve a Conflict

Once a pattern has been redefined and re-committed to server, users who attempt to synchronize pattern to server will encounter a situation that the pattern is said to be conflicted, which appear as red entry(-ies) in the Pattern Synchronization dialog box.

There are three ways of solving a conflict. Commit will replace the server copy with the local one. On contrary, Update will replace the local copy with the server's. Keep both will result in acquiring the server copy yet keeping the local one by renaming and committing it as a new one.

Comments (0)

Subscribe to this comment's feed

Show/Hide comments

Show/Hide comment form

Name

Email

Title

Comment

smaller | bigger

Subscribe via email (Registered users only)

Write the displayed characters

Add Comment