Version Control

Enterprise Architect supports version control of your projects, by allowing you to place your model packages under version control.  You can place any individual packages, view nodes or model root nodes under version control.

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.

Guide:

Topic

Detail

See Also

Introduction

Version Control provides numerous key facilities:

  • Saving a history of changes to Enterprise Architect packages
  • The ability to retrieve previous revisions of packages
  • Propagating model updates between team members
  • Coordinating sharing of packages between team members

Introduction

Product Setup

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

Setting Up a Version Control Environment

Configuring Enterprise Architect

Once the version control software has been installed and configured, to use your installed version control product you must first define a Version Control Configuration within Enterprise Architect

Version Control Setup

Using Version Control

Version control activities include such things as;

  • Controlling packages
  • Checking out packages for editing
  • Checking in modifications to packages
  • Retrieving previous revisions of controlled packages

Using Version Control

Notes:

  • 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
  • Database replication should not be combined with version controlled packages
  • If the packages under version control contain any alternative images and those images are subject to frequent change, you can set the Export alternate images option on the Options dialog to export the images to the version control repository when you check in the packages; if the images are not subject to frequent change, do not select this option and instead use Export / Import Reference Data to manage alternative images