Sparx 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 info@sparxsystems.in 

Features in Sparx Systems Enterprise Architect is designed specifically to enhance team-based modeling practice in large organization environments. As a scalable modeling platform, Enterprise Architect provides a range of deployment options to accommodate the variety of modern enterprises.

Choice of Repository

Models can be stored in either a file based repository or a DBMS repository.

• File based Repository
• DBMS

File based Repository

• Enterprise Architect Project / JET 4 Base Projects (*.eapx) – Newly introduced in Enterprise Architect 14.
• Enterprise Architect Project / JET 3.5 (*.eap).
• Enterprise Architect Project / Firebird (*.feap).

In Enterprise Architect 14 Sparx Systems has added support to Jet 4 base projects by introducing *.eapx file. Jet 4 databases support Unicode. Previous versions of Enterprise Architect 14 supported in Jet 3.5 database which doesn’t support Unicode. Also the advantage of using *.eapx file is in some circumstances database corruption would cause a Jet 3.5 model to fail to open in Jet 3.5 code, but Jet 4 code ignores or handles the error.

The benefits of this repository type are:

• Replication of the repository.
• Simple file access across a shared network drive.

The limitations of this repository type to consider are:

• Concurrent access is limited to small groups of users.
• Data corruption can occur if there is a network/power failure while editing.
• There are limitations on the data size supported by the Jet database (less than 30-40 mb is recommended).

DBMS Repository

Using a DBMS repository overcomes the limitations of file-based repositories. Typically, dedicated DBMS servers provide faster response times for a larger user base than the file based repositories. Further, any network errors are handled by the ability of the DBMS server to roll back transaction failure caused by external conditions. DBMS repositories can be accessed from a Cloud service. Although replication is not supported with DBMS repositories, with the Cloud connectivity replication is largely superseded. Enterprise Architect supports the 10 most popular types of DBMS server repositories.

DBMS Products you can use

You can set up your project on a repository in:

• MySQL from v5.
• Microsoft SQL Server from 2005, all editions including Express and Azure.
• Oracle from 9i (all editions).
• Firebird from v2.
• Microsoft Access from 2007.
• PostgreSQL from v8.
• Sybase Adaptive Server Anywhere 8 or 9, or SQL Anywhere 10, 11 or 12.

Drop mail to info@sparxsystems.in for any assistance.

We can execute Enterprise Architect Scripts from an external C# Application. Enterprise Architect supports a flexible and easy to use scripting capability. Enterprise Architect supports three scripting languages JavaScript and Microsoft JScript/VBScript.

Pros

• Hassle-free updates in restricted environments – Not necessary to re-install addins
• Introduce new feature in less time – Create New functionality using Scripts
• Deploy changes to all model users -Scripts are stored in repository
• Scripting is an interesting feature in Sparx Enterprise Architect. This aid us to do many things using Scripts and play with the active models

Cons

• Certain limitations within scripts discussed in the article below.

Assumptions

• The reader has a fairly good understanding of creating an Enterprise Architect Addin or writing an application that can use Enterprise Architect. Refer to below references if you need more information on these
  • To create an Addin from scratch refer this link 
  • Download Skeleton for creating an Add-In using the C# Language from this link

How to invoke Scripts from an External Application

• Create an application and get a handle of Enterprise Architect

select script.ScriptID as SCRIPTID, script.Notes as NOTES, script.ScriptName as SCRIPTNAME, script.Script as SCRIPTGroup from t_script script where script.ScriptAuthor IS NOT NULL

• Execute above Query to get the set of Script information
• Parse the XML Output to get the Script Content based on Script Name and Guid by user selection
• Save this script content in a string and pass as an argument for IncludeScripts method
• Use ScriptControlClass to invoke the Enterprise Architect script.
  Refer below code

ScriptControlClass scriptController = new ScriptControlClass(); scriptController.Language = this.language.name; scriptController.Timeout = -1; scriptController.AddObject(“Repository”, Session.Repository); //Add the actual code. This must be done in a try/catch because a syntax error in the script will result in an exception from AddCode try { //first add the included code string includedCode = IncludeScripts(scriptcontent); //pass script content string //then add the included code to the scriptcontroller scriptController.AddCode(includedCode); } catch (Exception e) { MessageBox.Show(e.Message); }

• Add Reference for ScriptControlClass to invoke Enterprise Architect selected scripts.
• Set AddObject to Active Enterprise Architect repository.
• Replace all the !INC with actual codes in scriptcontent

Limitations

Script should not include any Enterprise Architect specific keywords.

• It should not use “as”
  • Correct Syntax : Var ele;
  • Incorrect Syntax : Var ele as EA.Element;
• Script should not use any static functions like
  • “Session”.Eg.Session.Output,Session.Input,Session.Prompt
• Repository and !INC are the only Enterprise Architect specific keywords supported

Certainly, users could develop an external program to handle scripts inside EA. Please drop your comments below if you have any queries.

Drop mail to info@sparxsystems.in for any assistance.

Enterprise Architect Excel Exporter allows users to export Model information as Excel documents.

Excel Exporter can be used to publish elements, connectors, tagged values, test cases, scenarios and various other model information, into Excel spreadsheets, for easy review and updates by the wider team.

Steps to Export EA Model Information to Excel:

Step 1: Select the EA Model that contains the information to be exported.

Step 2: Create/Choose the Specification for the EA Model to be exported.

Step 3:Create/Choose the Output document to be exported.

Step 4:Select the Worksheet from the output document to be exported.

Step 5:Generate the model elements in Enterprise Architect to Export the document.

Export Excel Profile

To Export data from  EA Model, choose ‘Export to Excel’. The following dialog appears,

Select highlighted icon to create a new profile,

Home Tab

Mandatory Mappings:

• Specify document to Export (Can use existing document or create new Excel document) using two nearby button icon.
• Select the concerned work sheet from the dropdown or create a “New Work Sheet”

Optional Mappings:

• Generate Headers: Select this option to Export properties along with column name.
• Include Synchronization Information: Select this to Export Unique (GUID) information for every Object and Classifiers (Attributes and Methods).
• Include Diagram Elements in Report: Select this and also select the appropriate diagram type’s in Diagram Tab, this will leads to include the element in the export from external Packages that are referenced in a diagram under each package.
• Write Log File: It maintain, every Object Export Status.

Note: User can also export the data through unsaved profiles

Elements Tab

Model Data to be exported: All the properties are selected by default. User can,

• Select/Unselect the properties.
• Defined Tag Properties globally.
• Create Custom Tag using “Add Custom Tag” button.

Types to be chosen for Exporting: All the Object types will be selected by default. User can,

• Arrange the Order of export.
• Select/Unselect the Object Types.

Note: Should select minimum one object type and Object properties to Export.

Stereotype to Export: Specifying stereotype filters the exporting elements.

• All: Exports all the elements under the selected Object from Enterprise Architect.
• Non-Stereotype: Objects without stereotypes are exported.
• Specify Stereotype in CSV Format: User can define multiple stereotypes in CSV Format; the exporting objects must contain these stereotypes.
• Prompt during Export: While starting Export, its pop-up the dialog, that shows all the stereotypes under the selected node from Enterprise Architect.

Attributes Tab

Selecting “Include Attributes” will enable “Export Settings” group.

Must select separate worksheet or choose to export in the Main Worksheet.

Select the attribute properties to export. Users can also define “Custom Tag” to include any additional tagged values defined in the model.

Methods Tab

Selecting “Include Method” will enable “Export Settings” group.

Must select separate worksheet or in Main Worksheet and select minimum one Method property to export. It also loads Global Tag, we can define “Custom Tag” also.

Test Scripts Tab

Selecting “Include TestScript” will enable “Export Settings” group.

Must select separate worksheet or in Main Worksheet and select minimum one TestScript property to export.

Glossary Tab

Selecting “Include Glossary” will enable “Export Settings” group.

Select Worksheet to export Glossary and also select minimum one property to export.

Diagram Type Tab

It is used to export all the objects available in diagram, irrespective of objects available under selected node. We must select “Include Diagram Elements in Report” in Home Tab and also select suitable diagram type to export the objects.

Connector Tab

Context End: Used to define the settings of one end of connector.

• Column Name: The name is connector column name, which will be displayed in the generated Excel document.
• Context End: Select the element type for one end of the connector.
• Delimited By: Exporting the Object Name into the corresponding Connector Column in Excel should be separated by this delimited value.

Other End: Used to define the settings of another end of the connector,

• Type: Select the element type for another end of connector.
• Stereotype: It defines the stereotype for the other end of the connector.it support CSV Format.it filter out the connector to Export.
• Value: It used to search, that which type of the property should match the connectors that needs to be exported.

Connector: Used to define connector settings,

• Direction: Specify direction of the connector.
• Stereotype: It defines connector Stereotypes
• Type: It defines type of Connector

Note: Except Stereotype input, all other inputs are mandatory!!!

Export Process

While selecting Export button, two options will be displayed.

• To Local System: Allows user to export document to the local system.
• To SharePoint: Allows user to export document to the SharePoint folder. For more information regarding SharePoint export, refer “C:\ProgramData\MDG Integration for Microsoft Office\Help Document\UserGuide\index.html”

It gives a pop-up, like

Prompt during Export option, will prompt here, it shows all the object stereotypes available under selected Node from Enterprise Architect

Select Export, to export non-stereotyped Object.

 

Exported Document

• Elements are exported with GUID information.

• Attributes are exported with GUID information and parent object information under “GUID” and “ELEMENT NAME” column, respectively, which is highlighted.

• Methods are exported with GUID information and parent object information under “GUID” and “ELEMENT NAME” column, respectively, which is highlighted.

• TestScripts are exported with Parent object information in “ELEMENT NAME” column, which is highlighted.
  
• Glossary Exported with Term, Type and Meaning column. It is Model defined.
• Connector Column Exported.
• 
• Scenarios are exported with GUID information and parent object information under “GUID” and “ELEMENT NAME” column, respectively, which is highlighted.
• Constraints are exported with Parent object information in “ELEMENT NAME” column, which is highlighted.
• Export profile has
  Description: Want to export Connector Other end Name. It has to filter out the connector ends while exporting,
  • Source and Destination are Usecase type.
  • Connector Type should be “Dependency”.
  • Connector Direction should be “Incoming”.

  Comparing results,

  • “Login” has Incoming Connector from “Create Account” of “Dependency” Type.
  • “View Account Details” has Incoming Connector from “Close Account” of “Dependency” Type.
  • “Close Account” has Incoming Connector from “Delete User” of “Dependency” Type.

  Connector Other End names are exported successfully!

  Above, section Examine Overall Export Process.

 

An introduction to the Zachman Framework

The Zachman Framework is a widely used approach for engineering Enterprise Architecture. This Framework is a simple logical structure that helps in organizing the information infrastructure of an Enterprise.

While conceptually simple, the Zachman Framework provides many benefits in helping technology with business needs. It has become a popular approach in defining Enterprise Architecture because it :

• Is platform neutral
• Is a powerful planning device
• Is both comprehensive and readily understood by non-technical people
• Assists in problem solving
• Helps in documenting enterprise-wide information system architecture

Using this technology in Enterprise Architect, you can employ the Zachman Framework with the associated benefits of a powerful, open-standard modeling system

Using MDG Technology for Zachman Framework

The MDG Technology for Zachman Framework provides a model-based framework for planning, designing and implementing the Architecture for an Enterprise. The starter model provided with the technology acts as a base upon which you can build the Enterprise Architecture. You can create the appropriate diagrams from the extended Enterprise Architect UML diagram set, using Toolbox pages that support every cell of the Zachman classification framework.

This technology also provides model validation and reporting capabilities for strategic project plans.

You can also align cells across the framework (horizontally and vertically) through the Enterprise Architect Relationship Matrix.

You can view a demonstration video of the MDG Technology for Zachman Framework here.

Help topics in sparx systems provide a detailed exploration of the MDG Technology for Zachman Framework tools and features, such as.

• The example Enterprise Architect model for the Zachman Framework
• UML profiles (Toolbox pages) for use within specific Zachman Framework cells
• A diagram interface for the Zachman Framework
• New diagram types specific to the Zachman Framework
• A flexible model starter-structure
• Report generation capabilities for strategic project plans

Note that the MDG Technology for Zachman Framework is integrated with the features of Enterprise Architect.

Getting Started with the MDG Technology for Zachman Framework

Access the MDG Technology for Zachman Framework

1. Create a new Enterprise Architect project file.
2. From the Add Model Wizard select MDG Technology for Zachman Framework.
3. From the Name panel, select the Zachman Framework Model.
4. Click on the OK button.

A new base model for the Zachman Framework is created, displaying the Zachman Interface diagram

Drop mail to info@sparxsystems.in for any assistance

The New Menu option “Specialize” in Enterprise Architect 14 is the modernized version of “Extend” Menu in previous Enterprise Architect versions.

To Access: Specialize Or Right Click on Project Browser | Specialize

The Specialize Menu as the features that Utilize built-in and 3rd party tools to take your model in new and very specific directions. User can extend and specialize the product’s capabilities by using Add-Ins (extensions written in COM that interact with the Enterprise Architect user interface), and by importing XML files from specific technologies, working with them and publishing model information in XMI format back to the technologies.

• Build data models.
• Create XSD message schema from logical models.
• Write and execute scripts.
• Use the new External Data Integration capabilities to link your model with other tools, such as JIRA, DOORS, WRIKE, TFS and others.
• Manage and work with Add-Ins, Technologies and another advanced tool.

Specialize includes three Sections, Tools, Technologies, Add-In’s.

1. Tools
2. Technologies
3. Add-In’s

Tools

Tools helps in developing and managing the models, user can make use of a wide range of tools for code engineering, performing transformations, creating technologies, spell checking the model, customizing features and setting operational options.

Technologies

Technology as an option to Manage the In build technologies and 3^rd party technology which is defined in Enterprise Architect.

Import

Display a menu of options for importing XMI/XML from a variety of formats. ArcGIS, OWL/RDF and EMX are specifically supported, but a wide range of other tools’ XML output can be imported into Enterprise Architect using the Other Tools/Formats menu option.

Publish

Display a menu of options for Publishing (exporting) Enterprise Architect model information in a specific format for consumption by other tools or processes.

Add-In’s

Add-Ins enable you to add functionality to Enterprise Architect. The Enterprise Architect Add-In model builds on the features provided by the Automation Interface to enable you to extend the Enterprise Architect user interface.

Add-Ins enhance the existing functionality of Enterprise Architect through a variety of mechanisms such as Scripts, UML Profiles and the Automation Interface. Once an Add-In is registered, it can be managed using the Add-In Manager.

Overview:

‘Quick link’ feature in Enterprise Architect’s makes connector creation quicker and easier. Though quick linker simplifies the concept of creating connectors between artifacts (or) elements, the process of defining it would really consume a huge amount of time and manual efforts sometimes lead to errors. Though quick linker simplifies the concept of creating connectors between artifacts (or) elements, the process of defining it would really consume a huge amount of time and manual efforts sometimes lead to errors.

To overcome this we have created a custom script. This allows us to generate the quick linker definition quicker & easier than ever before. Please follow the below steps to create your quick linker definition with ease.

Pre-requisite:

• Custom MDG Technology. Please refer to how to define a custom MDG in this link
  https://sparxsystems.in/how-to-define-mdg-technologies-in-enterprise-architect/
• Must have a diagram (Metamodel / Blueprint) with connectors between artifacts which are required as quick links.

Steps to follow:

• Create a diagram group in the scripting section
• Create a J-Script below the newly create diagram group. Copy and Paste the code snippet given below

!INC Local Scripts.EAConstants-JScript

/*

 * This code has been included in the default Diagram Script template.

 * If you wish to modify this template, it is located in the Config\Script Templates

 * directory of your EA install path.

 *

 * Script Name: Generate Quick Linker Definition

 * Author: Nabil Saleem – Sparx Systems India

 * Purpose: Generate the quick linker definition from metamodel and to reuse in MDG definition

 * Date: 12/07/2018

 */

/*

 * Diagram Script main function

 */

function OnDiagramScript(diaID)

{

        // Get a reference to the current diagram

        var currentDiagram as EA.Diagram;

        currentDiagram = Repository.GetCurrentDiagram();

        Session.Output(“//Source Element Type\tSource ST filter\tTarget Element Type\tTarget ST Filter\tDiagram Filter\tNew Element Type\tNew Element ST\tNew Link Type\tNew Link ST\tNew Link Direction\tNew Link Caption\tNew Link & Element Caption\tCreate Link\tCreate Element\tDisallow Self connector\tExclusive to ST Filter + No inherit from metatype\tMenu Group\tComplexity Level\tTarget Must Be Parent\tEmbed element\tPreceeds Separator LEAF\tPreceeds Separator GROUP\tDUMMZ COLUMN”);

        if ( currentDiagram != null )

        {

                       for(var i=0; i<currentDiagram.DiagramLinks.Count; i++)

                       {

                                      var dialinks as EA.DiagramLink;                                

                                      var curCon as EA.Connector;

                                      dialinks = currentDiagram.DiagramLinks.GetAt(i);  

                                      curCon = Repository.GetConnectorByID(dialinks.ConnectorID);

                                      var SourceElem as EA.Element;

                                      SourceElem = Repository.GetElementByID(curCon.ClientID);

                                      var TargetElem as EA.Element;

                                      TargetElem = Repository.GetElementByID(curCon.SupplierID);

                                      var ConcType = “”;

                                      if(curCon.Type==”Realisation”)

                                                     ConcType = “Realization”;

                                      else

                                                     ConcType = curCon.Type;

                                      Session.Output(SourceElem.Type + “\t”+ SourceElem.Stereotype + “\t” + TargetElem.Type + “\t” + TargetElem.Stereotype + “\t” + “\t” + TargetElem.Type + “\t” + TargetElem.Stereotype +  “\t” + ConcType + “\t” + curCon.Stereotype + “\t” + ‘to’ + “\t” + “<Connector Caption>” + “\t” + “<Element Caption>” + “\t” + “TRUE” + “\t” + “TRUE” + “\t” + “FALSE” + “\t” + “TRUE” + “\t” + “\t” +  “0”);

                                      //Session.Output(TargetElem.Type + “\t” + TargetElem.Stereotype + “\t” + SourceElem.Type + “\t”+ SourceElem.Stereotype + “\t” +  “\t” + SourceElem.Type + “\t”+ SourceElem.Stereotype +  “\t” + ConcType + “\t” + curCon.Stereotype + “\t” + ‘from’ + “\t” + “<Connector Caption>” + “\t” + “<Element Caption>” + “\t” + “TRUE” + “\t” + “TRUE” + “\t” + “FALSE” + “\t” + “TRUE” + “\t” + “\t” +  “0”);

                       }

                       Session.Output(“Done”);

        }

        else

        {

                       Session.Prompt( “This script requires a diagram to be visible.”, promptOK)

        }

}

OnDiagramScript();

• Now open the diagram which has the connectors and artifacts
• Right – Click on the diagram. Select Script|New Script from Context Menu.
• Now open the system output screen
• Right – Click on the system output screen. Then click “Copy All to Clipboard”
• Paste the clipboard data into the excel file
• Replace the cell values of “New Link Caption” – Column K & “New Link &amp; Element Caption” – Column L.
• Now save the file as CSV.
• Now copy and paste the CSV data in MDG quick link artifact and generate custom MDG with quick links

Note: This feature is only available in Enterprise Architect 13.5.

Further Information
Please contact us or write an email to info@sparxsystems.in to have a live demo of the new EA 16 features and capabilities.

What’s new in SysML Modeling?

A huge update to the SysML technology making it one of the most compliant and easy-to-use implementations available today.

There have been literally hundreds of changes, modifications, and embellishments to the SysML technology. The result is an implementation that is highly compliant, and a user experience that will both delight and result in great productivity gains.

• All diagrams are by default displayed in frames.
• Revised property windows and toolboxes make working with all properties including, parts, ports, and pins much easier.
• A rich set of patterns for every diagram type provides a starting point and reference model for novices and experts alike.
• Element compartments are now highly configurable and SysML specific.
• Parametric and Simulation have been significantly enhanced – from modeling to configuration to execution of Model Parametric Simulation.

Figure 1 A state machine diagram showing three states and four transitions.

To Access:

Perspective | Systems Engineering | SysML, UAF, UPDM etc.
Model Patterns Window: Dropdown

Conformance Improvements Compared with Enterprise Architect 13

• Classifier behavior has now been added and can be set via the Element Details property tab.
• Behaviors have been updated to correctly display parameters when drawn within a compartment.
• The casing on multiple compartment names conforms with the SysML1.5 specification.
• Bound references can now display the binding path when displayed in a compartment.
• All SysML elements can display the AllocateTo and AllocateFrom compartment.
• UseCase Extends connector can display a condition by adding a constraint to the connector with the type ‘Condition’.
• Ports on an Internal Block / Parametric Diagram can display compartments from their classifying object.
• Port names can now be displayed within the Port if ‘Show Compartments’ is enabled.
• Inherited properties will now display with the caret (^) symbol before the name.

Further Information
Please contact us or write an email to info@sparxsystems.in to have a live demo of the new EA 16 features and capabilities.