We are delighted to inform you that the 3rd edition of the EA Global Summit 2022 is happening on September 14 & 15 in 2022.

Register now: EA Global Summit 2022

With 1200+ Registrations already, this could be a very good opportunity to meet and collaborate with fellow EA community.
An incredible lineup of speakers is keen to join their expertise, experience, and best practices related to Sparx Systems products including Enterprise Architect, Pro Cloud Server, EA SaaS, and Prolaborate.

Sparx Systems has recently released its latest version of Enterprise Architect 15. Sparx Systems have added various new features in this version.

Here is a guide with list of menus, frequently used by EA practitioners would be very helpful. This ultimate guide focuses highly up on how to access those frequently used options from menu bars along with some shortcuts. Since there are many changes in menus for frequently used options like Package Baseline, Export/Import of XMI, Linked Documents and others.

You can also find the full comparison between Enterprise Architect version 13.5, 14 and 15 in the below link.
Full Comparison between (EA13.5, EA14, EA15) on Frequently used menus in Enterprise Architect

Below table details the commonly used option of Enterprise Architect.

For more details or customization please contact This email address is being protected from spambots. You need JavaScript enabled to view it.

One of the latest features of Sparx Enterprise Architect 15 is the model based add-ins which can be created using JavaScript.  These model based add-ins are defined by a combination of Receptions, Attributes and Operations which can be easily added in a model by just creating with a valid stereotyped classes.

Assuming having basic knowledge with Sparx Traditional add-ins, broadcast events and JavaScript.

Why model based add-ins

• • Accessed by all the users within a model
  • Purely Model specific 
  • No installation, registry entries , distribution or license worries
  • Self-Documenting as everything is modelled and created directly in EA

Prerequisites

• • Signal Reference Library ( Broadcast Events ) -  Defines the entry points to the add-In similar to the com class in the traditional add-ins
  • Referencing relevant signals in the receptions

What is Signal Reference Library

These are Signal elements which contain definitions of all the Enterprise architect broadcast events. Signals that are added to the add-in will receive an event when triggered similar to traditional add-ins. EAExample model contains all the broadcast event signals under the package Example Model.EA 15 Examples.Dynamic Model Based Add-Ins.Broadcast Types

Mandatory Signals or Events for Add-in

• • EA_Connect
  • EA_GetMenuItems
  • EA_MenuClick

All the available events references can be found here https://www.sparxsystems.com/enterprise_architect_user_guide/15.0/automation/broadcastevents.html

To Create an JavaScript Add-In

1. Create a Signal Reference Library referring EAExample model. (Simple way would be just do an XMI export of the Broadcast Types package from EA model and import into your working model).
2. Create a package in the root node for modelling the add-in
   
   
   
   3. Create a class object with stereotype JavascriptAddin ( this stereotyped element can be found in Model Add-Ins tool box as shown below
      
   4. The name of the above defined will be used in the JavaScript code. In our case it will be “Javascript Addin”
   5. Add the signal reference in the created class using the reception.
      • To Access Reception Right-click on the Class element and select the 'Features | Receptions' option. The Features window displays, at the 'Receptions' page.
        
      • Add the required events by clicking the button to the right of the New Receptiontext in the 'Name' column , the dialog will show the available Signals ( it will automatically fetch the parameters details from the object )
        
   • Once selected all the added signals will be displayed in the class object.
     
   6. After adding these events, its time to play with some JavaScript codes.
   7. Please open the behavior window (Develop > Source Code > Behavior) make sure the created class object “Javascript Addin” has been selected. It will show all the added events to which we need to add the code
      
   8. Codes for these events are similar to the traditional add-ins ( please refer the attached model for more details )
   9. Finally make sure the add-in is enabled. To enable the add-in Specialize -> Manage-Addin and please click Load on startup
      
   10. Once the add-in is loaded you can find it in the ribbon
       

   Note:

   • The above referenced model can be downloaded from the http://sparxsystems.in/downloads/Demo Jacascript Add-in SSIN.zip
   • EAExample model contains two example Javascript add-ins by default, you need to just enable it in the manage add-ins for using.

   For more details or customization please contact This email address is being protected from spambots. You need JavaScript enabled to view it.

QuickLinks is one of the most used and useful features in defining domain-specific MDG technology. In addition, the latest version of Sparx Enterprise Architect 14 allows users to define rules for QuickLinker. Each rule has unique features like defined connectors between stereotypes, filtering in classifiers, defining stereotypes connectors between stereotypes and so on. Each rule can be created in the UML profile between the defined stereotypes.

Assuming you’ve good knowledge in Defining Customized MDG Technology, Let’s see in detail about defining QuickLink rules

Methods for defining QuickLink rules are Methods for defining QuickLink rules are

• Meta-Constraint
• Meta-Relationship
• Stereotyped Relationship

Each of the above-mentioned types can be accessed by creating a connector between two defined stereotypes as shown below

Meta-Constraint

Meta-Constraint is used to specify a rule between two defined Stereotypes. The value should be assigned in the tag 'umlRole' on the connector created for meta-constraint.

To create Meta-Constraint

In the below example we are extending\generalizing two stereotypes named Object and Data from BPMN2.0 Activity. Creating a new meta-constraint with classifier filter between the created stereotypes. The created meta-constraint will be used to filter based on the target stereotype when selecting the classifier from the source stereotype.

1. Draw a connector with meta-constraint stereotype between the two defined stereotypes

2. Navigate to the tags tab of the created connector and set one of the constraint values as shown below in the umlRole tag

3. Once saved the defined QuickLink constraint looks like below

After importing the created profile/mdg in the model, when defining classifier for the element with stereotype Object enterprise architect will only show elements with stereotype as Data in the list (refer below)      

 This is the process of defining meta-constraint in QuickLink. Above example illustrates with the constraint value\ umlRole as “classifier”.

For other types of constraint values refer below diagram from SPARX.

Meta-Relationship

Meta-Relationship is used to specify a valid UML Connector between two defined Stereotypes. The name of the UML Connector should be set in the value of tag 'metaclass' on the connector created for Meta-Relationship.

To create Meta- Relationship

In the below example we are extending\generalizing two stereotypes named Application and Function from BPMN2.0 Activity. Creating a new metarelation with generalization connector between the created stereotypes. The created metarelation will be used to create a generalization connector in quick links.

1. Draw a connector with metarelation stereotype between the two defined stereotypes

2. To set the UML connector , Navigate to the tags tab of the created connector and set one of the UML Connector as shown below in the metaclass tag

3. Once saved the defined QuickLink constraint looks like below

After importing the created profile/mdg in the model, the created UML connector will be displayed in the QuickLinker list when we try to create a QuickLink between these stereotyped elements application and function. It can be even defined as self-connector (refer below)

  This is the process of defining meta-relationship in QuickLink.

Stereotyped Relationship

Stereotyped Relationship is used to define a stereotyped connector between the two defined Stereotypes. The name of the stereotyped connector is set in the value of tag 'stereotype' on the connector created for Stereotyped Relationship.

To create Stereotyped Relationship

In the below example we are extending\generalizing two stereotypes named Mobile and Web from BPMN2.0 Activity. Creating a new stereotyped relationship between the created stereotypes. The created stereotyped relationship will be used to connect the target stereotype element with BPMN2.0 sequence flow.

1. Draw a connector with stereotyped relationship stereotype between the two defined stereotypes

2. To set the connector stereotype, Navigate to the tags tab of the created connector and set one of the connector stereotypes in stereotype tag(It can be either a simple or a fully qualified connector stereotype )

3. Once saved the defined QuickLink constraint looks like below

After importing the created profile/mdg in the model, the defined stereotyped connector will be displayed in the QuickLinker list when we try to create a QuickLink between these stereotyped elements (refer below)

This is the process of defining stereotyped-relationship in QuickLink.

Resources

You can download the complete MDG defined model and Generated MDG here for reference.

For more details This email address is being protected from spambots. You need JavaScript enabled to view it.

Sparx Systems Enterprise Architect now allows integration of data from a variety of third-party providers into an Enterprise Architect model. This article explains the configuration and possible ways to integrate Jira with the enterprise architect model.

Jira Integration can be done in two ways

• Creating Virtual links between Enterprise Architect and Jira using Prolaborate
• Importing Data and synchronizing between Jira and Enterprise Architect model using Pro Cloud Server

Creating Virtual links between Enterprise Architect and Jira using Prolaborate

You can now integrate Enterprise Architect with Jira through Prolaborate. Creating a two-way link between Enterprise Architect elements and Atlassian Jira items just got easier through Prolaborate. Prolaborate is a web collaboration platform for Enterprise Architect that makes model sharing simple, efficient and collaborative. Prolaborate lets end-users work on live EA diagrams and model information over an agile collaboration portal. 

Key Features

• Create Live links between Jira Items and Enterprise Architect Objects
• Any Jira item from any of your Projects can be accessed
• View details of Jira items inside Prolaborate
• Visual Cues in diagrams for easy visualization and navigation for the items Linked with JIRA

Refer to this article to learn more about Jira Integration using Prolaborate.

The workflows involved are

1. Configure Jira Account
2. Add Jira Attribute
3. Add Jira Attribute to a Stereotype’s Form
4. Link Jira issues to Enterprise Architect elements
5. Preview JIRA Items
6. View JIRA issue links from Enterprise Architect
7. Manage Integrations
8. Manage Integration Attributes

For detailed documentation refer Enterprise Architect Jira Integration through Prolaborate

Importing and Synchronizing Jira Data using Pro Cloud Server

One of the recent features in Sparx Pro cloud server is the ability to integrate Enterprise Architect model with external software like Jira. Linking and updating between Enterprise Architect items and JIRA items made easier with the pro-cloud server integration.

Key Features

• Import and export of JIRA objects to connected Enterprise Architect model
• Creating a link between JIRA Objects and Enterprise Architect elements

Prerequisite

• Enterprise Architect Corporate, Unified or Ultimate edition v14 or later
• Pro Cloud Server licensed 
• Physical network access to a server hosting the external data
• User credentials to access the external data

Mandatory Details:

• Server name\IP address of Pro cloud Server ( same machine then localhost )
• Port number of Pro cloud Server
• Server name\IP address of JIRA ( base URL )
• Port number of JIRA 80 ( if the protocol is HTTP ) and 443 ( if the protocol is HTTPS )
• Credentials of JIRA account

Configure Pro Cloud Server

The SBPI.exe application is the Integration Bridge between the Pro cloud server and JIRA which is installed by default into pro cloud server installed folder. For each integration with third-party tools like JIRA a data provider must be created in the Pro Cloud Client Configurations.

To Create Integration Bridge

The Integration tab in the Cloud Configuration Client allows the definition and maintenance of Integration Data Provider details.

Step 1: Configure SBPI with Cloud Model:

Open Pro Cloud Config Client -> Integrations (Tab Shown Below)

Click on Save to add the new Integration setting.

Step 2: Create a data provider for JIRA.

                To communicate with an external application (like JIRA) a data provider must be created in the pro-cloud Configuration.

Click on the Add. You will be taken to the Data Provider Page (refer below)

Configure Data Provider:

Configure Pro Cloud Server & Cloud Settings:

Configure Jira Account:

Click on Save to add the new data provider configuration.

Once done with the above configuration as shown in the above image, please make sure Sparx Systems Professional Cloud is restarted under services.

Integrating JIRA and Enterprise Architect

To View JIRA Items in Enterprise Architect

Navigate to Specialize Tab-> Integration (in tool section) JIRA -> select a provider (Created Provider will be displayed) -> JIRA Project -> Filters (favorites in JIRA)

All the items labeled in the Favorite filters will be displayed below.

Any local Enterprise Architect elements that are linked to the JIRA item will be shown as a child of the JIRA item.

Import Jira Items in Enterprise Architect

JIRA items can be directly created in Enterprise architect with the pro-cloud server integration.

To create a new element in the Enterprise Architect model from JIRA:

• Right-click on a JIRA item in the list.

• Select Create Local Element

Click on create, to add the JIRA item in Enterprise Architect. Once created (linked), the element will be displayed under the JIRA Item

To Link Enterprise Architect Element with JIRA Item

An existing element in Enterprise Architect can be linked to an existing item in the JIRA by dragging the local element from the Project Browser and dropping it onto the JIRA Item.

Export Enterprise Architect Elements to JIRA

Pro cloud server integration for JIRA even allows creating new JIRA items from existing elements in the Enterprise Architect. Create Items must be enabled in the integration provider

1. Select the local Enterprise Architect element (in the Project Browser).
2. Browse the external provider and select the required destination location.
3. In the External Data Menu, select 'Create Linked Item'.

Synchronize changes from Jira in Enterprise Architect

If any of the JIRA item has been modified since the items created or linked in enterprise architect an indicator will be displayed on top of the item's icon.  Right-click on the linked Enterprise Architect element and select the 'Pull - Update Local Element with External Data' option. (Any existing changes in the Enterprise Architect element will be overwritten with JIRA data)

Update Jira with changes from Enterprise Architect

If any of the local element has been modified since the items created or linked is an indicator will be displayed on top of the item's icon.  Right-click on the linked Enterprise Architect element and select the 'Push - Update External Item with Local Data’. (Any existing changes in the JIRA Object will be overwritten with Enterprise Architect data)

For more details please contact This email address is being protected from spambots. You need JavaScript enabled to view it.