Collaboration Features

Sparx Enterprise Architect Collaboration Features

Enterprise Architect supports several collaboration patterns. The best choice depends on team size, connectivity, governance, and whether users need simultaneous editing or controlled package exchange.

Multi-user repository access

A server-based repository allows multiple users to connect to the same model and work concurrently.

Key capabilities include:

• User authentication and permission management
• Model, package, diagram, element, and resource security
• Read-only or locked packages
• User and group permissions
• Version and audit history, where enabled
• Centralized backups and database administration
• Controlled access through VPN, private networks, or secure remote connectivity

Best for: connected teams working from a shared source of truth.

Main concern: the repository needs proper database administration, security, backup, and network planning.

Package control

Package control supports structured team workflows by allowing packages to be managed independently.

Typical capabilities include:

• Check-in/check-out to reduce conflicting edits
• Package ownership and controlled editing
• Exchange of controlled packages between repositories or teams
• Separation of model areas by project, domain, or responsibility

Advantages: clear ownership, controlled changes, and useful separation of work.

Disadvantages: additional process overhead; cross-package relationships, baselines, and merges can become more complicated.

Version-control integration

EA can integrate with systems such as Git, Subversion, and Team Foundation/Azure DevOps-style systems, subject to configured providers.

Advantages

• External change history
• Branching and parallel development
• Review and approval workflows
• Distribution of model packages between teams
• Alignment with software-development configuration management

Disadvantages

• Version control is primarily package/file-oriented rather than seamless database collaboration.
• Binary or structured model files may be difficult to merge.
• Teams must define conventions for package ownership, branching, baselines, and conflict resolution.
• Poorly governed branching can produce divergent or duplicated model content.

Replication and distributed work

EA replication supports separate copies of a model that can be synchronized later. This can help users who work offline or across disconnected locations.

Advantages

• Offline modeling
• Separate working copies for distributed teams
• Synchronization when connectivity is restored

Disadvantages

• Synchronization conflicts
• Duplicate or deleted objects
• Greater operational complexity
• Need for disciplined synchronization procedures
• More demanding backup and recovery practices

For continuously connected teams, a shared server repository is usually simpler than replication.

Model baselines and comparison

Baselines capture a known model state and allow teams to compare or restore model content.

Useful for:

• Design and architecture reviews
• Release milestones
• Impact analysis
• Approval checkpoints
• Recovering from unwanted changes
• Comparing branches or package versions

Baselines complement, but do not replace, database backups or source control.

Pro Cloud Server and remote access

Sparx Pro Cloud Server can provide remote access to EA repositories and support browser-oriented access scenarios, depending on licensing and configuration.

Implementation considerations include:

• Authentication and authorization
• HTTPS and certificates
• Network segmentation
• Performance over high-latency connections
• Licensing and feature availability
• Whether users need the full EA client or only browser access

Recommended collaboration pattern

For most connected enterprise teams:

1. Use a centrally managed SQL repository as the authoring source of truth.
2. Divide the model into logical packages with clear ownership.
3. Use permissions and package controls to protect sensitive or stable areas.
4. Establish baselines for major reviews and releases.
5. Use source control where package-level history or distributed exchange is required.
6. Provide read-only web or generated-document access to stakeholders.
7. Maintain automated backups and a documented recovery process.