System Requirements and Configuration

Version controlled packages are packages that have been configured for use with version control software.

To use version control in Enterprise Architect, a third-party source-code control application is required that controls access to and stores revisions of the controlled packages. Enterprise Architect supports the following version control applications:

  • SCC-compatible products; all version control products that provide a client that complies with the Microsoft Common Source Code Control standard, version 1.1 or higher.
     
    The following products are SCC-compatible and are known to successfully integrate with Enterprise Architect:
     

- Accurev

Tested by Sparx

 

- Borland Star Teams

 

Users report success

- ClearCase

 

Users report success

- MS Visual Source Safe

Tested by Sparx

 

- MS TFS-SCC

Tested by Sparx

 

- MKS Source Integrity

Tested by Sparx

 

- Perforce

Tested by Sparx

 

- Serena Dimensions

 

Users report success

- Serena Change Manager

 

Users report success

- Snapshot CM

Tested by Sparx

 

- SourceGear Vault

Tested by Sparx

 

- Source Offsite

Tested by Sparx

 

 
Products that do not appear in the list should still integrate successfully with Enterprise Architect, if there is a client available for that product that complies with the MS SCC API specification.

Configuration

Before using Enterprise Architect's version control facility, your version control software must be installed on each machine on which it is intended to be used.

Typically there are:

  • A server component that manages a version control repository, and
  • Client components on the workstations that Enterprise Architect uses to communicate with the server.

A version control client must be installed on every machine where you run Enterprise Architect and want to access your version control system. Once the version control software has been installed and configured, you must define a Version Control Configuration within Enterprise Architect, to use your installed version control product.

Note:

Sparx Systems strongly urge you not to manipulate version controlled package files outside of Enterprise Architect. It is possible to leave the package files in a state that Enterprise Architect cannot recognize.