| Prev | Next |
The Modeling Team
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. Features in team support include Baselines, Version Control and a Reusable Asset Service, which protect the valuable modeling assets in a team environment, plus tools such as a Discussion Forum, Library window and Gantt Charts to facilitate collaboration between project members. The role-based security system has also been designed to encourage collaboration, allowing team members to work together confident that there will be no conflicts in accessing or changing model data.
A choice of deployment options will support 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 offers team members 'view only' access to their models, yet also allow them to generate high quality corporate documentation in a wide number of formats to communicate with people outside the modeling platform.
Overview
Facility |
Description |
|---|---|
|
Team Development 
|
Set up a collaborative modeling environment, taking advantage of security, workflow and shared reference data, as discussed in the rest of this topic. |
|
Formal Model Reviews 
|
A simple yet effective mechanism for capturing, in real time, reviews of a section of the model in line with a particular event. Typically, a Project Manager or coordinator will create a Review element specifically to discuss one or more elements for a project phase or other category of review, over a defined period. |
|
Project Management 
|
Explore some of the ways you can manage your project and team within Enterprise Architect. |
|
Project Resources 
|
Track and manage the people and resources in your project. |
|
Glossary 
|
Define a common vocabulary between your different teams, ensuring common understanding. |
|
Task Allocation 
|
Assign and Track team tasks in a Gantt View. |
|
Personal Tasks 
|
Record and manage your personal tasks within the project. |
|
Model Mail 
|
Use Model Mail in the Chat & Mail window to securely communicate with your team via an internal email system embedded within the model. |
|
Project Calendar 
|
Track the deployment of resources, time-frames for tasks, and upcoming project events such as meetings and milestones, in a calendar format. |
|
Use Case Estimation 
|
Form an estimate of the complexity of a system and an indication of the effort required to implement the model. |
|
Library Window
|
Provides access to a team-based library of documents to record and discuss the development and progress of the project. |
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 Native/XMI Import/Export.
Applying Security to the Model
User Security is a means of improving collaborative design and development by preventing concurrent editing and 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, generally in discussing the development and progress of the model across the project, or specifically in discussing individual elements in the model, the discussions becoming a component of each element.
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 the work 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.