Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Enterprise Architect has been built from the ground up as a team modeling platform, and has extensive support for groups of people working together on the same projects, sharing information, ideas and models. The team support includes features ranging from Baselines, Version Control and a Reusable Asset Service that protect the valuable modeling assets in a team environment, to collaborative tools such as a Discussion Forum, Team Library and Gantt Charts to facilitate people working together. The role-based security system has been designed to encourage collaboration, allowing team members to work together without the fear of interfering with each other’s work.
There is a wide range of deployment options that will suit any team development environment, allowing people to work centrally or remotely in highly distributed environments. Corporate policy and standards can also be built into the models with the use of Workflow Scripts. A free 'Lite' version of Enterprise Architect is available for team members who simply want to view the models, and high quality corporate documentation can be generated in a wide number of formats to communicate with people outside the modeling platform.
Making project data available in a distributed environment
Enterprise Architect offers a diverse set of functionality designed specifically for sharing projects in team-based and distributed development environments; for example: Cloud-based solutions, network deployment of model repositories, replication and XMI Import/Export.
Applying security to the model
User Security is a means of improving collaborative design and development by preventing concurrent editing, and limiting the possibility of inadvertent model changes by users not designated as model authors.
Using an internal discussion forum
The Discussions facility provides several mechanisms to support your development team community in discussing specific elements in the model as a component of each element or, more generally, the development and progress of the model across the project.
Building company policy and project development guidelines into the project
You can create workflow scripts that provide a robust approach to applying company policy and strengthening project development guidelines, by validating against the policy and procedures within the model itself.
Standardizing and re-using project data
You can import and export Reference data (including Glossary and Issue information) from .XML files of another iteration of the same model, or of a different model.