Version Control Usage

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

Field

Usage

See also

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 is used to;

  • Archive successive versions of your work to date
  • Maintain package revision history
  • Provide an "undo" facility to recover from unwanted changes or accidental deletions
  • Regulate access to packages

 

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.

Version control is used to;

  • Propagate changes to the model, throughout the team
  • Archive successive versions of your work to date
  • Maintain package revision history
  • Provide an 'undo' facility to recover from unwanted changes or accidental deletions
  • Regulate access to packages

 

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

 

Learn More: