S
p
a
r
x
S
y
s
t
e
m
s
I
n
d
i
a

Contacts

No 58A, New No 73,
Thirumangalam Road,
Villivakkam,
Chennai-600 049

info@sparxsystems.in

Category: Sparx Systems Enterprise Architect

Features in Sparx Enterprise ArchitectSparx Systems Enterprise Architect 16

Simplified way to connect with DBMS repositories

Sparx Systems Enterprise Architect 16 introduces a New “Native Connection” method to both 32 and 64-bit versions in addition to the existing connection methods that require separate ODBC or OLEDB drivers to be installed.

Enterprise Architect 16 makes the simplest and recommended way to establish connections with existing and new repositories like:

  • Firebird
  • MariaDB
  • MySQL
  • Oracle
  • PostgreSQL
  • SQL Server

Native Connection does not require the need for installation of drivers for individual DBMS and DSN definitions.

Enter the details of the database in the Native Connection window and connect Enterprise Architect to it.

    Access: Start Page > Open Project | Server Connection

Start Page > Manage Projects > Connect to Server (on drop-down arrow, Select Native Connection)

Sparx India

How do we connect to the Repositories using Native Connection in Enterprise Architect 16?

  1. Click on the radio button for the type of DBMS you are connecting to.
  2. Give the name of the connection in the description field.
  3. Enter the database details as required.
  4. Click on test to check whether the connection is successful or not.
  5. If the connection is successful, OK button will be enabled. Click on it to connect with the EA repository.

Further Information 

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

Sparx Systems Enterprise ArchitectSparx Systems Enterprise Architect 16

Grid Style Diagram in Enterprise Architect 16

  • Enterprise Architect has always allowed modelers to customize the appearance and position of elements in diagrams, and the New Grid Style Diagram option allows you to manage and organize diagrams by sorting diagram elements into cells within a grid.
  • Build a Spreadsheet, Dashboard, and even a home page for your model with the Grid Style diagram.
  • In Enterprise Architect 16, the Grid functionality integrates with a New Scripting API to reference elements by the provided grid position.

Key Points:

  • Holds element in each grid cell
  • Configurable in rows, columns, and cell size
  • Manages medium to a large set of information
  • Row and Column headers refer to the grid position
  • Element position can be referred by grid position
  • Automatically updates and process elements in the grid using Scriptlet.

How to enable Grid Style in Enterprise Architect 16?

In the Diagram Properties tab, select the ‘Enable’ option for Grid Style from the drop-down list under the section ‘Appearance’.

Figure 1 Enable Grid Style

This action turns on the ‘grid-style’ setting and opens the ‘Grid- Style Properties’ dialog, where you can specify settings such as the number of columns and the height and width of cells.

Figure 2 Grid- Style Properties dialog

Figure 3 Grid Style Diagram

Once the Grid-Style is enabled for a diagram, the option ‘Grid’ appears in the context menu which offers a number of commands specific to it. They are:

  • Show Grid Lines
  • Show Grid Headers
  • Edit Grid
  • Compact Grid

Grid style Contect menu in EA 16

Figure 4 Grid Style – Context Menu

Altering the Grid Cells Using Scriptlets

Scriptlet Artifacts can be used to run JavaScript code to access elements in a grid-style diagram and set the appearance of those elements like to set the font and background color, or to alter the text that is displayed.

Each Scriptlet has access to three global objects in addition to the standard automation environment. They are:

  • theDiagram – an automation Diagram interface to the diagram on which the Scriptlet resides
  • theElement – an automation Element interface to the Scriptlet artifact itself
  • theInstance – an automation DiagramObject interface to the Scriptlet artifact itself

Further Information

Please Contact us or write an email to info@sparxsystems.in to talk to our EA Expert to understand more about new interesting capabilities in Sparx Systems Enterprise Architect 16.

Sparx Systems Enterprise Architect 16

Auto Name and Counters using Stereotypes in Enterprise Architect 16

  •  Dealing with complex and large sets of requirements can be a tedious process. Sparx Enterprise Architect allows you to set up your own naming and numbering conventions for elements of the same type which ease the process.
  • Auto Names and Counters can be used to assign a sequential number to element types & stereotypes.

What’s New in Auto Name and Counters in Enterprise Architect 16?

  • Auto-naming has been expanded to target specific element types as well as stereotypes.
  • Distinguish between elements based on both element type and stereotype.

How do we use it in EA 16?

1.In Enterprise Architect 16, find Auto Names and Counter in Ribbon: Settings > Reference Data > Settings > Auto Names and Counters.

Enterprise Architect Version 16 Pictures

2. New Feature – Stereotype is included in Auto Names and Counters in Sparx Enterprise Architect 16

Sterotype is included in autonames and counters

 

3.Select the Type as “Requirement” (Element type) or the type you need.

 

4.By selecting Stereotype – Configure Perspectives as All and Profile as EAREQ. Check the Business requirements and select OK.

 

Autonaming using stereotype

 

Stereotype as requirements

 

5.Now, enter the Prefix as BUSREQ and Counter as 001 in Alias Section and check the Apply on creation Save & Option

Auto Name Counters

6.Enable the option to show Alias and Name in the diagram

a.Check the “Use Alias if Available” option in diagram properties.

b.In Preferences > Behaviour enable both Alias and Name in the Alias Usage section.

Alias & Images Part 2

7.Now, create a Business Requirement from the Requirements toolbox.

Create a Business Requirement.

 

Please Contact us or write an email to info@sparxsystems.in to talk to our EA Expert to understand more about new interesting capabilities in Sparx Systems Enterprise Architect 16.

Features in Sparx Enterprise ArchitectSparx Systems Enterprise Architect 16

Monitor Real-time Diagram Updates in Enterprise Architect 16.

Auto Refresh Diagrams

  • Sparx Systems Enterprise Architect provides the New Auto Refresh feature that allows you to collaborate on diagrams with your team in real-time. This results in improved support for multiple people offering feedback on the same diagram simultaneously.
  • It lets your team monitor the changes immediately after enabling the Auto-Refresh option on your diagram with a time interval.
  • One can design his own dynamic and distributed real-time modeling environment by combining Review, Chat, Discussion, and/or Journal.
  • The Feature is explicitly available in Enterprise Architect version 16.0 and later.

Auto Refresh Reload Diagrams in EA 16

Figure 1: Auto Refresh Context Menu

Access:

  • Right-clicking on the diagram background –> Collaborate –> Auto Refresh
  • In Ribbon, select the Layout –> Auto Refresh –> Auto Refresh

Context Menu Options :

Option Action
Disabled For all diagrams, this is the default setting. Any user can update the diagram, but there is a risk of updating’ collisions’. You’ll get a warning notice and a prompt to refresh the diagram if another user saves their changes.
7 Set the refresh interval to 7 seconds and enable automatic refresh mode for the current diagram.
15 Set the refresh interval to 15 seconds and enable automatic refresh mode for the current diagram.
30 Set the refresh interval to 30 seconds and enable automatic refresh mode for the current diagram.
60 Set the refresh interval to 60 seconds and enable automatic refresh mode for the current diagram.
Pause & Edit Allows the current user to edit the diagram by pausing the automatic refresh of the diagram and releasing the lock on the diagram for the current user.
Resume Saves any outstanding changes to the diagram and reapplies the lock, which prevents any additional modifications to the diagram and resumes the diagram’s automatic refreshing.

Auto Reload Changed Diagrams

  • Sparx Systems Enterprise Architect’s New Auto Reload functionality ensures that the diagram you are working on is the most recent version.
  • One can reload any diagrams that are open while others make modifications by enabling this functionality in Enterprise Architect.
  • It allows one to rapidly communicate with other individuals at work and ensures that the graphical reports EA provides are up to date.

Access: Layout –> Diagram –> Options –> Auto Reload Changed Diagrams

Further Information

Please Contact Us or write an email to info@sparxsystems.in to arrange a detailed demo session of Sparx Systems Enterprise Architect.

Sparx Systems Enterprise ArchitectSparx Systems Enterprise Architect 16

Latest & Greatest of Sparx Enterprise Architect 16

Sparx Systems – released a new version of their application, Enterprise Architect Version 16  has undergone significant changes, plenty of enhancements, and an array of new features is made available to the users which will fulfill their expectations.

Here’s a gist of the new features that will entice users to upgrade their Enterprise Architect to the newest edition.

1. Enterprise Architect 64-Bit

Sparx Enterprise Architect has been considerably modified and is now available in two versions: A new 64-bit version and a legacy 32-bit version. Many improvements are included in the new 64-bit version which allows you to work with significantly larger data sets, reports, files, and repositories. A simple, fast, and scalable solution that can handle even the most complex task.

The Key Benefits are

  • Leverage 64-bit OS features and capabilities.
  • Access larger amounts of memory.
  • Process data more effectively compared to 32-bit.
  • Support larger report generation tasks.
  • Support larger XMI import/export operations.
  • Larger diagrams can be exported and saved.
  • Larger simulations can be built and run.
  • Build and search large Code Miner databases.

2. Support for New Standard File Based Repositories

As a scalable modeling platform, Enterprise Architect provides a range of development options to accommodate a variety of modern enterprises. In consideration of the same, Sparx Systems has extended its support for new standard file-based repositories which are built on SQLite database engine in the latest version of Enterprise Architect.

Enterprise Architect Project (QEA Files) – The basic personal file-based version

Enterprise Architect Shared Project (QEAX Files) – Support shared files with small workgroups

The key benefits of these repository types are

  • Out-of-box EA repository.
  • Lightweight & Serverless.
  • Basic replication is supported for offline development.

Easy migration of existing EAP/EAPX files to QEA/QEAX files which will be compatible with the 64-bit version of Enterprise Architect. To continue using existing EAP/EAPX files, use the 32-bit version of Enterprise Architect.

3. Grid Style Diagram

Enterprise Architect has always supported modelers to customize Element’s appearance and position in diagrams. With the New Grid Style Diagram option, you can build a Spreadsheet, Dashboard, and home page for your model. In Enterprise Architect 16, the Grid functionality integrates with a New Scripting API to reference elements by the provided grid position.

Categorize diagram into cells:

  • Holds element in each grid cell.
  • Configurable in rows, columns, and cell size.
  • Manages medium to a large set of information.
  • Row and Column headers refer to the grid position.
  • Element position can be referred to by grid position.
  • Automatically updates and process elements in the grid using Scriptlet.

Grid style diagram in Enterprise Architect 16

4. Collaboration – Team-Based Approach to Modeling

Enterprise Architect provides a suite of new and expanded Collaboration tools to support a rich, cooperative team-based approach to modeling. Collaborate tools have been restructured into the following new windows

  • ‘Chat & Mail’: Chat, Mail, Diary, Recent.
  • ‘Discuss & Review’: Journal, Discuss, Review.
  • ‘Discuss & Review History’: Journals, Discussions, Reviews.

In Enterprise Architect 16, using the Collaborative tools the users can

  • Chat in real-time.
  • Share small files and images through Chat, Journals, and Discussion.

Save discussions by recording them

  • Provide and manage Review feedback.
  • Record ad-hoc ideas in an Element Journal daily.

To know more about the collaboration features in the Sparx Systems Architecture Platform tool suite, please visit https://prolaborate.sparxsystems.com/ or contact us to book a live customized demo.

Collaboration - Team based approach

5. Simplified way of connecting to DBMS repositories

Sparx Systems Enterprise Architect 16 introduces a New “Native Connection” method to both 32-bit and 64-bit versions in addition to the existing connection methods that require separate ODBC or OLEDB drivers to be installed. It is the simplest and recommended way to establish connections with existing and new repositories. Native Connection does not require the need for installation of drivers for individual DBMS and DSN definitions. Enter the details of the database in the Native Connection window and connect Enterprise Architect to it.

Connecting to DBMS Repositories

6. Scriptlet

The New Scriptlet element is a JavaScript-based powerhouse that allows you to access the underlying diagram and element API. Scriptlets run whenever the diagram containing them is loaded/reloaded before the diagram is displayed or they can run manually on demand. Insert the Scriptlet on any diagram and edit the JavaScript as required. Multiple Scriptlets can be used on a single diagram and the same Scriptlet can be used on multiple diagrams. If a diagram has many Scriptlets, the Z-order of the Scriptlets on the diagram determines the order in which they are executed.

  • Change the appearance of elements, names, and tagged values.
  • Updates to dynamic properties can be automated.
  • Create your spreadsheets with the new Grid Style diagrams and Scriptlets.
  • Update the Grid style diagrams using new cell references (A:1, A:2, etc.,) API.
  • Dynamically colour code elements based on your rules.
  • Validate model elements in a diagram.

.

7. Custom Documents

Custom Documents feature is enhanced in the latest Enterprise Architect 16 to provide an even more attractive solution for creating highly customizable reports. Mix and match your graphics, logos, regulations, and text with content sections developed dynamically from the model. Start with a provided template, your base document, or a blank page, and then drag and drop content from the Project Browser where it is needed.

  • Ability to choose and use a template when creating a new document.
  • More information on how to set up the sections
  • Improved content list, which now includes the element and template for each dynamic section.
  • Numerous improvements and usability improvements have been made
  • Custom Document elements can now be created via Diagram Toolbox

For any assistance in regards to customizing documentation templates in your model, please contact us or email us @ info@sparxsystems.in

8. Support for New Modeling Language – FACE Profile

Using Enterprise Architect 16, the FACE Profile for UAF 1.0 allows users to model the Open Group’s Future Airborne Capability Environment (FACE) data architecture and components. It allows FACE components to be represented in the context of broader UAF system architectures to identify interactions between FACE and other architecture components. FACE Profile is available in the Unified and Ultimate Editions of Enterprise Architect and a separate UPDM license is required for other editions to avail it.

Support for New Modelling Language

9. Native XEA file exchange format

Native XEA file is a new fast and convenient alternative to the XMI and XML formats for large data sharing. The XEA format makes model archiving and the export and import of Enterprise Architect repositories easier. A Native XEA file exported by Enterprise Architect version 16.0 or later cannot be imported by the earlier versions of Enterprise Architect.

Native XEA File Exchange format

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

Features in Sparx Enterprise ArchitectSparx Systems Enterprise Architect

Images Assets and Custom Diagrams in EA 15

Using images to add relevance to any architecture diagram is a very common practice. Enterprise Architect has always supported modellers to set ‘Alternate Image’ or ‘Default Image’ for elements to create such diagrams.  However the users have always sought for an ability to manage a set of image assets in a catalogue and reuse it across multiple diagrams.

The New approach in EA 15 to manage and reuse images in diagrams is a significant enhancement. The ‘Image Asset’ element lets users create a model item to store an image. These items can then be used to apply overlays on other model elements.

Image Assets

The Image Asset images can be used as alternative images in place of the standard UML notation for elements on diagrams. They can also be used in documentation by inserting hyperlinks to the Image Asset element. When a report is generated, the hyperlinked Image Asset element is rendered using its ‘owned image’

To create an image asset, Select the ‘Artifacts’ section in toolbox | select ‘Image Asset’ | click on the diagram, or Drag an ‘Image Asset’ Artifact from the toolbox onto a diagram.

Image Assets as Catalogue

Figure 1 Image Assets Catalogue

Custom Diagram

The new ‘Custom Diagram’ option in EA 15 allows users to create a highly customizable, graphic-rich diagram that is on-par with any modern drawing tools.  Custom Diagram enables the most options to use the Image Assets.

Using Image Assets

The Image Assets from the repository can be used to perform the following actions

  • Set as Icon – As an icon of an Existing Element
  • Set as Alternate Image – As an alternate Image on an existing element
  • Add as element with Icon
  • Add as element with Image
  • Add as link

Options to Use Image Assets

Figure 2 Options to Use Image Assets

Set As Icon

Use Image Asset to  set it as an icon for an existing element or a new element (This is my favourite!).  In the previous versions, users must rely on shapescripts to achieve such visualization.

Set Image as Icon

Figure 3 Set Image as Icon

Set as Alternate Image

You can also use the Image Asset to set it as an alternate image for an existing element or create a new element with the image as alternate image.

Figure 4 Set Image as Alternate Image

Updating Image Asset

There are two key benefits in using the ‘Image Assets’

  1. Ability to drag and drop from project browser to apply image as an icon or alternate image
  2. Ability to update the image asset and also cascade the change across all diagrams where the image asset is used

You can ascertain the impact of modifying a Image Asset by using ‘Find In All Diagrams’ (Element Usage, similar to any other element usage)

Image Assets Usage

Figure 5 Image Asset – Usage

Summary

Using the new enhanced ‘Custom Diagram’ and ‘Image Asset’ of EA 15, I’ve created a deployment diagram (below) which was in-par with a graphic rich diagram created using any drawing tool, at the same time retaining the benefits of a modelling repository.

Prolaborate Architecture Diagram

Figure 6 Prolaborate Architecture Diagram created using EA 15 Image Assets

Further Information

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

EA AutomationSparx Systems Enterprise Architect

How to create model based JavaScript Add-ins using Enterprise Architect 15

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 easy added in a model by just creating with a valid stereotyped classes.

Assuming you have a basic knowledge in Sparx Traditional add-ins, broadcast events and JavaScript.

Why model based add-ins

  • Accessed by all the users with in 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. 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 event references examples 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

  1. Create a class object with stereotype JavascriptAddin ( this stereotyped element can be found in Model Add-Ins tool box as shown below

  1. The name of the above defined will be used in the JavaScript code. In our case it will be “Javascript Addin”
  2. 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.

  1. After adding these events, it time to play with some JavaScript codes.
  2. 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

  1. Codes for these events are similar to the traditional add-ins ( please refer the attached model for more details )
  1. Finally make sure the add-in is enabled. To enable the add-in Specialize -> Manage-Addin and please click Load on startup

  1. Once the add-in is loaded you can find it in the ribbon

Note:

For more details or customization please contact info@sparxsystems.in

Integrations

Enterprise Architect Jira Integration

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 

Pro Cloud ServerSparx Systems Enterprise Architect

Enterprise Architect Pro Cloud Server

Overview:

Sparx Systems Pro Cloud Server opens entire enterprise to modelling efforts, enabling stake holders to have secure access for discussion and review.

Role of Pro Cloud Server:

In simple term Pro Cloud server enables security to the entire enterprise model then allows users to access it via Web EA and integrate with third party collaborative platform.

  • Create with Enterprise Architect
  • Host with Pro Cloud Server
  • Review, Comment & Share via Web EA

The above-mentioned pointers fulfil the life cycle and necessity of using an enterprise tool like Sparx Enterprise Architect.

Requirements:

Key Store

With the power of the Sparx Systems Key Store has been built into the Pro Cloud Server. This allows added flexibility to check out a key across a HTTP connection from anywhere in the world.

The Key Store has also been updated to handle our new editions of Enterprise Architect including the Professional and Unified (Newly introduced in 2018) Edition.

Advantages:

Row Level Security/Visibility Levels

Control visibility in the Project Browser. Both Oracle and SQL Server (latest versions) can now be used to support Row Level Security in cloud-based models. This means that models may be securely partitioned so that only privileged modelers or staff can access specific areas of the model, while other modelers, customers and clients may only see a smaller prescribed section.

Row Level Security is implemented at the database level and effectively limits the information a user of Enterprise Architect can access, even if the user writes ad hoc custom queries. Because the restrictions are tightly integrated into the database, even using custom SQL does not allow the users to view the restricted level information.

Row Level Security is enabled by running some additional configuration scripts on the database and setting up multiple logon accounts that the Cloud Server will use to partition the model. Depending on the logon credentials used to access a model (at the cloud level, not the user level) the amount of information available will vary.

On the client side, admin users can set security/visibility levels on package hierarchies to effectively hide content from non-privileged users.

Enterprise Architect On Cloud

One of the most interesting integration points supported by the new cloud-based Integrator is a connector for other Enterprise Architect Cloud Based projects. This immediately opens up the possibility of partitioning Enterprise Modeling assets across multiple models and providing cross references and linkages between models that allows modelers to develop new scenarios and projects that reference core and related elements and information from multiple existing models.

Integrate Data From External Providers

Pro Cloud Server allows data integration from various external providers. Among various external providers the below mentioned are some the highly preferred by Sparx Enterprise Architect Users.

  • Application Lifecycle Management (formerly HP Quality Center)
  • Jazz (Rational DOORS Next Generation)
  • Jira & Confluence
  • Team Foundation Server
  • Wrike
  • ServiceNow
  • Autodesk
  • Bugzilla
  • SharePoint
  • Dropbox and
  • Other Enterprise Architect models

Expand your model’s horizons. Harness information and data in external tools, making Enterprise Architect a highly effective information hub.

The Pro Cloud Server family of Apps now includes a new modular integration capability that is tightly connected with Enterprise Architect 14. The Integration modules are built into the Pro Cloud Server and Enterprise Architect access is being sold as an optional add-on that seamlessly connects into the Cloud Server via Enterprise Architect 14 clients. A variety of integration modules are planned, and some are scheduled for release including JIRA, TFS, WRIKE, Drop Box and ServiceNow integrations offer support for linking Enterprise Architect elements to objects and elements within external systems.

A new “View” window lets the modeler connect to an integration target and retrieve lists of elements and objects based on built in queries.

Some capabilities include:

  • Link an Enterprise Architect element to an integration object
  • View external element properties
  • View and in some cases add to, external object discussions
  • Export links to WebEA URL’s that correspond to the current model
  • Open external tools in a web browser at relevant bookmarks
  • Import elements
  • Export elements

Included in the list of integrations is an integration capability with another Enterprise Architect project. This allows modelers, teams and organizations to view common information in a model and reference it from another Enterprise Architect model. For example, you can now store organizational structure, deployment maps, requirement sets or other independent sets of information, in separate models and cross link new models to existing external content. You can even post discussions and make comments on the external Enterprise Architect elements where appropriate.

Refer the link below to configure integration

http://sparxsystems.com/enterprise_architect_user_guide/14.0/model_repository/integrate_external_provider_data.html

Features in Sparx Enterprise ArchitectSparx Systems Enterprise Architect

Import Glossary using EA MDG Office for Excel Importer

Glossary can be used to store a list of terms and their definitions. The terms can be grouped into any number of user defined categories such as business, technical, domain specific grouping such as medical, scientific, or aviation. The power of having the terms defined in the model is realized when modelers write description in model elements as these will be linked automatically to terms defined in the Project Glossary. For more details on glossary refer here.

The MDG Office for Excel Importer allows users to import contents from Excel workbooks into Enterprise Architect. This includes importing spreadsheet data as UML Elements, Connectors, Attributes and Operations and also as Glossaries.

To import glossary into EA from Excel Workbook:

  • Create new or open existing eap file.
  • Right click Extension -> Microsoft Office -> Profile Manager for Excel.
    • It will list all the predefined profiles and user defined profiles.
    • Select “Add New -> Object Profile”. ( refer below screen )
      Sparx India
  • Create an Import profile with a sample Excel Workbook, which doesn’t contain the type information. ( refer the attached excel file )
  • The sample document doesn’t contain the Element Type Information; hence “My Data has Element Type Information” is unselected.
  • In Element Type – choose “Glossary” available under EA Features Group
  • In Stereotype – Glossary does not support any stereotype so just skip it.

Sparx India

  • In Property Mapping section map the information in Excel to EA metadata as mentioned in the below image

Sparx India

Glossary Mappings:

Map the exact excel columns to Glossary Term, Glossary Type, and Glossary Meaning by selecting the  “More Properties’ from EA Element Property combo box

Sparx India

Using this “Additional Properties” form, map each columns in excel to the specific EA property.

  • Review the Profile definitions and select ‘Create’, to create the Profile.

Sparx India

To Import Glossary Worksheet Into EA :

  • Choose Extension -> Microsoft Office -> Import Excel Document
  • Select the Excel Workbook and the respective Worksheet that needs to be imported and also the appropriate profile created for glossary import(defined in the previous section)

Sparx India

  • Add Diagram for Each package: Not Applicable for glossary import
  • Enable Synchronization: If enabled, Unique GUID values of the glossary are written in the back up document for later sync with Enterprise Architect. For Glossary, no GUID values are created, it only updated by its term field.
  • Configure Hierarchy: Not Applicable for glossary import
  • Select Preview, to preview the content to import.

Sparx India

  • Select Import,to start importing glossary into the selected EA Model.

Sparx India

         Once the import is done

  • Go to PROJECT->Glossary,to see the imported terms for the project.It is Project Specific properties.

Sparx India

Download the Sample Excel and Model eap file here.

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