Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Change Management

Model Management

As users contribute new content and change existing content, a repository will become a valuable data store of organizational information assets. It is imperative that this asset is protected and changes are managed and controlled including being able to revert models back to previous versions or states. Enterprise Architect has a number of sophisticated tools to ensure the information is protected, including full integration with all the leading Version Control Systems, Baselines that are snapshots of your model that can be taken at important milestones, and Auditing that can track the finest changes to a model. A Project Transfer function helps you to make backups of models without involving information technology personnel. There are also Model Validation and Project Integrity Checkers to ensure the repository is maintained with a clean bill of health, and a powerful role based Security System to ensure users can collaborate easily and sections of the model can be locked to users or groups.




See also


Baseline create snapshots of model content, a changed model can then be compared to the snapshot and changes can be reverted to the baseline content if required.

  • Baselines are created at the package level providing snapshots of an entire package including elements, features and diagrams  and optionally also the packages it contains.
  • As a model is altered the changed package can be compared with a baseline, including visual diagram changes and if required the current model can be reverted to the content stored in the baseline.
  • Baselines require no setup and provide an easy way for business and technical users to  restore models to previous states at any level of granularity.

Version Control

Version Control allows model content to be versioned allowing check-out and check-in of packages to facilitate keeping track of different versions of parts of the model and allowing rollback to prior versions.

  • Coordinate sharing of Packages between users, with either read-only access or update access, ensuring that work on different areas of the model is coordinated and synchronous rather than conflicting
  • Allow check-out and check-in of packages to and from working storage including users working offline.
  • Save and retrieve a history of changes to Packages

To use Version Control in Enterprise Architect, you require a third-party source-code control application such as:

  • Subversion
  • CVS
  • MS Team Foundation Server (TFS), or
  • Any other Version Control product that complies with the Microsoft Common Source Code Control standard
Version Control


Auditing records changes to the content in a repository and provides a powerful visualization view that can be used to drill down into changes from the package level down to changes to element features.

  • Auditing is typically used by librarians and administrators to investigate who made a change to the model and the date and time it was changed.
  • It can be used to locate problems in model development or for contractual reasons where third parties have been given access to manage model content and the source of a change needs to be identified.
  • Auditing can be enabled and disabled at any time and the audit logs can be saved and reload as needed.
Tracking Changes

Project Data Transfer

Enterprise Architect enables you to transfer project data between project data repositories either for:

  • Sections of the project (XMI and CSV) or
  • The whole project, row by row, table by table (in the Corporate, Unified and Ultimate Editions of Enterprise Architect)
Model Exchange

Learn more