Enterprise Architect

User Guide Series	

Deployment Scenarios

	
Author:	
 Sparx Systems	

Date:	
  4/10/2018	

Version:	
 1.0	

	CREATED WITH	

	

Table of Contents

Deployment Scenarios	3
Multi Site	4
Head Office with external contractors	5
Multiple sites via Cloud	6
Outsourced teams	7
Amazon	9
Azure	10
Single Site	11
Client Exchange 	14

Deployment Scenarios

To accommodate the range of organizational structures in which Enterprise Architect is used - from large multi-site organizations through to single site developer groups - there are a range of deployment options available.  

Options

This table identifies a number of core deployment scenarios grouped as Multi-site, Single site and Client Exchange.

Multi-site

Options for multiple sites include:
•	Multiple sites with a Cloud connection
Head Office with external contractors working on customer sites
Project input interaction
Small intercontinental teams
Outsource teams
Amazon/Azure
Multi Site

	

Single site

Single site options include:
•	On-site Cloud Connectivity
One building with a large user base on a LAN
Small team using a file based repository
Single Site

	

Client Exchange

There are a number of options for distributing your model to your client base. This exchange can involve a variety of in-house or external clients, from stakeholders down to developers, or testers. The use of these client exchange tools can range from reviewing the model design process, through to using the model in the implementation and testing of the product.

The Client Exchange options include:
•	WebEA
Joomla!
Web reports
EA Lite
Client Exchange

	

Multi Site

With multi-site connectivity there are numerous scenarios. Some of the common patterns in use include:
•	Multiple sites with a Cloud connection
Head Office with external contractors working on customer sites
Small intercontinental teams (standards Development)
Outsourced teams
Amazon/Azure connections 

Scenarios

Given the numerous scenarios for multi-site connectivity this table outlines some key options.

Deployment	Link	

Head Office with external contractors working on customer sites

Head Office with external contractors

	

Multiple Sites with Cloud Connection

Multiple sites via Cloud

	

Outsourced teams

Outsourced teams

	

Amazon connections

Amazon

	

Azure Virtual Machine

Azure

	

Head Office with external contractors

The Sparx Systems Cloud Service provides a platform for intranet style HTTP/S connection to your internally hosted DBMS repositories, which can also be extended to external HTTPS access to allow for off-site usage, by simply allowing port access via the firewall.
Advantage:
•	Off-site direct access to the repository ensures that everyone has immediate access to the latest information

Multiple sites via Cloud

Using the Sparx Systems Cloud service you have an HTTPS connection to your repository internally, which can be extended to external connections for branch offices or outsource vendors. 

This can be via simple HTTPS connection (via firewall), or using a more dedicated VPN style connection.

Advantages:
•	Off-site direct access to the repository ensures everyone has immediate access to the latest information

Outsourced teams

A common scenario for using the Pro Cloud server, where IT developers work with an outsourced team for code production, is represented in this Deployment diagram. The Central Office relies upon workers who either work remotely or provide services from one or more consultancies located in other countries. Some individuals and organizations exchange data through a secure connection across the Internet, others connect via a Virtual Private Network on a WAN.
The Pro Cloud Server unlocks the models that were traditionally only accessed by staff in the Central Office via an Enterprise Architect Client, to anyone with a Web Browser, an Internet connection and the permission to access the content. 

Central Office

The System Architects, in the Central office, design the detailed high level model architecture and data structures ready to be used by the outsource developers as a basis for starting the code development.  

Outsourced Code developers

The outsourced code developers are working with the architectural model and requirements via a Cloud connection to the model repository. Using security the Central office administrator has this group restricted to only viewing the design, but permits them to work with updating the code and performing visual execution of the code being developed.  

Test Analysts

Test Analysts working with test design and test automation tools use WebEA to view the requirements, business rules, and test cases in these models through the Web Browser.   

Out of Office workers

Out-of-office workers can use WebEA to view and follow discussions, view Kanban diagrams and, if configured to do so, update Requirements notes and Issues.   

Amazon

The Sparx Systems Cloud service and the Pro Cloud server can be easily deployed on a 3rd party web service such as the Amazon Web Service (AWS).

A common set-up scenario on the AWS is to use an EC2 server to host both the Pro Cloud server (or just the Cloud service) and the DBMS.

Notes:
•	The Sparx Systems Cloud server ports are configurable and can be set to different port numbers to those shown in the illustration
•	Simple ping testing of the workstation connection requires that ICMP is enabled on the EC2
The EC2 server has internal firewalling that must be set up to allow access to the Cloud service port(s)  

Azure

The Sparx Systems Cloud service and the Pro Cloud server can be easily deployed on a 3rd party web service such as the Microsoft's Azure web service.

A common set-up scenario on the Azure web service is to use an Azure 'Virtual Machine' server to host both the Sparx Systems Cloud service (or the Pro Cloud server) and the DBMS.

Notes:
•	The Sparx Systems Cloud server ports are configurable and can be set to different port numbers to those shown in the illustration
•	Simple ping testing of the workstation connection requires that ICMP is enabled on the Virtual Machine
The Virtual Machine server has internal firewalling that must be set to allow access to the Cloud service port(s).  

Single Site

For an organization that uses Enterprise Architect across a standard Local Area Network (LAN) there are options available, as described here: 

Single site scenarios

On-site Cloud access

The Sparx Systems Cloud service provides a platform for intranet style HTTP/S connection to your internally hosted DBMS repositories.

Advantages:
•	Supports DBMS repositories
•	Leaner network data throughput
Simple connection - ODBC/OLE DB drivers are not required on each workstation
•	HTTP ports can be secured to remain within the local Network
•	Allows for optional off-site connectivity

When using the Cloud service you have a choice of using a Firebird or a DBMS repository. A DBMS repository is preferred for a large user-base. For a smaller user base you can use a file based Firebird repository, which can be a good starter for a small but expanding organization.

One building with a large user base on a LAN

For medium sized organizations you need to use a DBMS repository.
When using multi-user accessible repositories with the core users working in one building, you can opt to use direct workstation-based ODBC connections to the repositories on the DBMS server.

Advantages:
•	No limitation on repository size

Limitations:
•	Restricted to a low Network latency LAN connection
Requires ODBC /OLE DB drivers be configured on each workstation.

Small team using a file based repository

File based repositories can give you quick access to create a simple mock-up model, or they can be used for small teams of fewer than 5 users for creating models in a team-based scenario. 

For interactive usage a .eap file is commonly stored on a file server accessible to the team.

Advantages:
•	Very simple set up
Supports Replication

Limitations:
•	Supports only small groups of concurrent users
There is a limit to the size of repository

Client Exchange 

Exchanging and Publishing content 

Enterprise Architect provides a range of options for interacting with the client/stakeholder base as well as publishing designs for review and for implementation.
Feature	Description	
WebEA
 	Sparx System's WebEA is a web-based interface to Enterprise Architect's models, through which users can review and comment on a model in real time. Being web-based, it operates on a range of mobile devices or on a remote work station, without any need to install Enterprise Architect.
Benefits:
•	Can be used on any machine that has a web browser
Content is dynamic, providing a real time view of the model
Provides a very simple access to model details
Provides optional update to texts such as Discussions, Element Notes and test results
Supports searching the model
No publishing process required

Publish Joomla Articles
 	Enterprise Architect provides a facility for publishing model content as HTML Articles in a local Joomla! installation.

Benefits:
•	Allows the HTML model to be searched
Web discussion can be added

Shortfalls:
•	Content is static after publishing
Requires manual publishing of content
Discussion comments are external and not posted back in the model

Web Reports
 	You can also make your model available to others in a read-only format by generating an HTML report on the model, which can be published on the web with read-only access. This is the simplest reporting in HTML format.

Benefits
•	Simplest cost effective web based publishing

Shortfalls
•	Does not support searches on the model
Does not support adding comments
•	Requires manual Publishing of content
Content is static after publishing

EA Lite
 	Enterprise Architect Lite is a free, read-only edition of Enterprise Architect that can be used by clients and stakeholders for reviewing the project. 
Benefits:
•	Provides a real time view of the model
Allows clients to pass feedback using Element Discussion and Team Library
Does not require a publishing process

Shortfalls:
•	Users need to be familiar with the Enterprise Architect user interface and menu system to access model details
This requires a fixed installation on a workstation (Windows, Linux or Mac)