Collaborative design environment for cooperative Development---Configuration EA+SVN (Fool edition)

Collaborative design environment for cooperative development---configuration EA+SVN

The EA (Enterprisearchitect) is the most powerful case tool. SVN (SubVersion) is the most commonly used version control tool. Together, the two can build an efficient team collaborative design work environment.

The EA itself stores the design in *.eap's private format, but it also supports storing the contents of the design diagram in a repository such as SVN. Use third-party version control tools for versioning and collaborative design purposes.

When you choose SVN as the version of the EA, you need to specify a storage directory on SVN and the EA will store all of its designs in this directory. To achieve the purpose of collaborative design, the EA will store each package as a separate file. That is, only one person can edit the same package in the same time. The following steps are described:

Tools used:

Enterprisearchitect 8.0

Slik-subversion-1.7.8-x64 (SLIK-SUBVERSION-1.7.7-WIN32)

VisualSVN Server2.5.9 (~/bin/svn.exe, can replace slik-subversion in the same name file, the client can not install SVN server)

Tortoise svn1.7.2-x64 (X86)

Note: Version compatibility seems to have a certain impact on EA+SVN's collaborative use, which is the version I tested successfully.

Server Configuration

1, Enterprise Architect 8.0,visualsvn server2.5.9,tortoise Svn 1.7.2 Software Installation simple not to repeat.

2. Build the project version Configuration library on the SVN server (results such as)

3. Check out library to local

4. Version control configuration

5. Add Branch to version control

6. Export with Model branch

7, check the library file Gajah Mada See if the operation is successful

The server-side configuration is complete after the above steps have been submitted to the SVN service after the generated files have been committed.

Client Configuration:

1. Installation of relevant software

2. Checkout the corresponding library files in the server to local

3. Open the EA to create a new empty module (file name, storage address no special requirements)

4. Import the node model

After the import (such as) can be checked out for modification, after the modification is complete, check in again to complete the modification. The client is also configured successfully.

Precautions

• Get into the habit of updating versions from the repository before you start working.
• Develop the habit of "submitting a version in a timely manner after work is over".
• The smaller the checkout the better, the shorter the better. Do not checkout the part that you will not make changes to.
• Tools are just auxiliary, do not neglect to communicate with peers directly under the line.
• For EA+SVN, the design version management operation should be done only in the EA, and not in the local folder directly in the version operation.
• For EA+SVN, the smallest unit of version control is the package, and it is in the form of a file

before the online also read the other version of the majority of the overall introduction of the usage and its benefits, and there is no detailed steps to introduce. In particular, the issue of the version between the various software needs to pay particular attention, you may have a long time environment is because the version of the problem caused by the end of the results you want to lose the candle. This method is actually successful and in operation.

Accumulate from the beginning of sharing (the tool: Http://pan.baidu.com/s/1jG22t4E)

Collaborative design environment for cooperative Development---Configuration EA+SVN (Fool edition)