Version Control Usage

There are four basic ways in which the version control facility might be used:

Use

Description

Single Shared model

Users share an Enterprise Architect model, stored in a central .EAP file or DBMS repository. This configuration enables you to view changes to other users' packages without explicitly having to check them out, but by simply refreshing your view of the model.

  • Version control regulates access to packages, and maintains package revision history.

Multiple Private models

An Enterprise Architect model is created by a single user who configures it for version control. The model file is then distributed to other users, with each user storing their own private copy of the model.

  • Users update their model's packages through version control
  • Version control regulates access to packages, and maintains package revision history
  • Other users' new packages are retrieved using the Get Package menu option.

Shared packages

Individual users create separate Enterprise Architect models but share one or more packages.

  • Users share packages through version control.

Standard packages

A company might have a standard set of packages which are broadly shared (on a read-only basis).

  • Individual users retrieve packages with the Get Package menu option.

For a discussion of how each of these arrangements might be used, see the Version Control Best Practices for Enterprise Architect white paper.