Reusable Asset Service (RAS) in Sparx Enterprise Architect

• Sparx Enterprise Architect supports the Reusable Asset Service feature, which offers a straightforward and practical method for modelers to share or download reusable model structures, information, as well as corporate directives and standards.
• Distributed teams can access the shared repository as it will be connected to Pro Cloud Server.
• The RAS gives distributed teams convenient access to a single ‘source of truth’ for shared data, including project milestones, architectural frameworks, and industry standards.

Reusable Assets

Pro Cloud Server repository encompasses a Reusable Asset Storage.

Reusable Assets can consist of:

• Packages containing elements, diagrams and structures (as drawn from any point within the Browser window).
• A variety of text, coding, and graphic file types, such as.qea and.eap files.

Figure :1 Reusable Asset Service

Key-Feature in RAS

Features	Description
Register Assets	The assets that can be created include: ●      Packages – including diagrams and subordinate Packages ●      Baseline Packages ●      Files
Browse Assets	Any user, regardless of password protection, can freely browse and identify the contents of a Package held in a Storage – including displaying the diagrams – without importing the material into a model.
Import Content	Any user with access to the Pro Cloud Server repository and a password (if required), can import an Asset into their repository.
Dependencies	Any dependencies within a stored Package are viewable, providing a quick means to visually see what the Asset requires.
View Diagrams	Any diagrams set in an Asset are logged and can be viewed providing a quick means to check and visually compare the Asset diagrams against updates to diagrams in the current model.
Compare	Where a user that has imported an Asset Package into their model, they can compare their model Package against any version of the Asset Package, to check for and assess any differences between them.
Required Technologies	For a Package Asset that has specific Technologies these are displayed for clarification of what is required on importing the Asset.
Reviews	Reviews and comments can be posted against a Package.

Five simple steps to compare/merge between versions using RAS in Sparx Enterprise Architect :

1. Creating a RAS repository using PCS.
2. Configuring the RAS in the Main Repository and registering the assets in the Main Repository.
3. Import branches to other local repository by configuring the same RAS in that repository.
4. Make some changes in the local repository and register it in RAS configuration.
5. Compare/merge/restore the changes from RAS configuration to Baseline repository.

Further Information

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

The Excel importer in MDG Integration for Microsoft Office is a powerful tool for quickly importing and managing large amounts of data into models. It helps you to save time and reduce errors by automating the process of importing data from an Excel worksheet into Sparx Enterprise Architect. 

Key features in MDG Integration for Microsoft Office – Excel Importer 

• Excel importer is a powerful and flexible tool for importing data from Excel worksheets into Enterprise Architect model elements more efficiently and accurately. 
• It Includes importing worksheet information as UML Elements, Connectors, Attributes, TestScript, Usecase, Glossary, and tagged values to Enterprise Architect.
• It is also possible to import hierarchical data from Microsoft Excel into Enterprise Architect. 

Introducing the Interface

1. Select the Excel document that contains the information to be imported. 
2. Choose the profile that has been defined for the particular document.
3. Optionally set hierarchical composition.
4. Preview the ‘About to be imported’ model content.
5. Import the document to create model elements in Enterprise Architect.

Figure 1. Excel Importer Interface

Profile Mapping

Profiles in MDG Integration for Office give users flexible and simple ways to map the EA models with an Excel worksheet by providing a step-by-step approach. This results in more efficiency and effectiveness. 

Two types of profiles are supported by the Excel Importer

• Object profile – Allows the user to import the Object and its properties into Enterprise Architect Model. 
• Connector profile – Allows the user to import the Connector and its properties to the existing objects in the Enterprise Architect Model.

Figure 2. Excel Profile Mapping

Step 1. Get Started 

Get started wizard is categorized into two sections: 

• Profile Information 
• Settings

Profile Information 

Basic information about the profile – Profile Name, Description, and Excel document path. 

Settings 

If the Element Type Information (Eg: Class, Requirement, etc), is missing from the Excel worksheet then uncheck the ‘My Data has Element Type Information’ checkbox. This will enable the Element Type combo box and stereotype text fields.

• Element Type – The Enterprise Architect element types are listed here. Select a single Element type from the Excel worksheet to import the whole sheet.
• Stereotype – It allows the user to manually enter the stereotype for the object import. 

Step 2. Map Element Type 

It allows users to choose a column name that specifies the element type to be created in Enterprise Architect

Note:  Map Element Type wizard is displayed only if the ‘My Data has Element Type’ Information is checked in the previous (Get started) screen.

Step 3. Map Element Properties 

The Element Information in the Excel is to be mapped to the appropriate EA Element Property by using a drop-down list 

Note: Configure Connectors – This button should be enabled only when a user mapped any of the columns as a “connector” in the EA Element Property. By default, the connector has some pre-selected values to import. We can change the selected values by clicking on the “Configure Connector” button.

More Properties – In the EA Element Property drop-down, we have an option called More Properties.  Selecting ‘More Properties ‘from the drop-down, shows the below properties to map to import into EA.

• Tagged Values 
• Use case
• Glossary
• Attributes
• Methods
• TestScript

Parent Package Mapping – Map the Parent information column to ‘SET_AS_PARENT _PACKAGE_1’ from the EA Element Property drop-down under ‘MULTI-LEVEL HIERARCHY’. 

When ‘SET_AS_PARENT _PACKAGE_1’ is mapped, the ‘Create parent package if not exists’

The option will get enabled and checked by default. We can also change this setting if needed.

1. If a parent exists in the selected sheet, it creates the object under this parent, or
2. If the parent already exists under the selected package in EA, it creates the object under the parent, or
3. It creates the parent as a package in Enterprise Architect and then creates the object under this parent package

Step 4. Review and create

It provides a summary of the mappings defined in the profile as well as a preview of the final model structure corresponding to the sample document. 

By following the four simple steps above, we can easily create a profile. Selecting the Created Profile from the profile dropdown menu is necessary when using the EA Excel Importer. This profile allows the user to import Excel data into EA as Artifacts and connections. It will import as shown below. 

Figure 3. Import Excel Worksheet as EA Artifacts  

Further Information

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

Sparx Enterprise Architect is a powerful modeling platform that helps organizations to create and manage their models. It also provides a range of features such as EA Word Importer, which helps in integrating Microsoft Office documents with the models created using Sparx Enterprise Architect.

Key features in MDG Integration for Microsoft Office – Word Importer

• Word Importer offers a powerful interface for instantly converting Word documents into Enterprise Architect model elements.
• The tool brings Requirements, Use Cases, Glossary, Processes, Classes, Connectors, and other data from Word documents into Enterprise Architect as model elements, Connectors, and Tagged Values.
• It greatly reduces the time and effort involved to translate the information available in requirements documents, use case documents, test plan documents, etc.

Introducing the Interface

Word Importer lets users import Word documents in four simple steps.

1. Select the word document that contains the information to be imported.
2. Choose the profile that has been defined for the particular document.
3. Preview the model contents to be imported.
4. Click Import to create model elements in Enterprise Architect from the selected word document.

 

Figure 1. Word Importer Interface

Word Importer Interface provides a step-by-step approach for mapping items like section tables and delimited name-value pairs from Word Documents to model Enterprise Architect elements and properties through profiles.

Profile Mapping

• Profile mapping helps to map the word document styles and structured information to Enterprise Architect Object & its Properties.
• Profile is reusable for all Word documents which are in similar structures.

Figure 2. Word File Getting Started.

Step 1. Get Started

Get started wizard is categorized into three sections:

• Profile Information
• Element Properties
• Element Definitions Table (Excel-like).

Profile Information

Basic information about the profile – Profile Name, Description, and Word document path.

Element Properties Mapping

It gives users the flexibility to map additional details in Word documents as Element Properties.  The additional details in the Word document are expected to be given as name-value pairs separated by delimiters.  Delimiters symbols can also be provided in the “Delimited by” field.

The delimited name-value pairs could be.

Element Definition table (Excel)

It allows the user to select whether the table information provided in Word Document contains Headers in the first row or Headers in the first column.  The below-mentioned options are available in the Element Definition Table section.

• None
• Excel-like tables with a header in the first row
• Excel-like tables with a header in the first column

Step 2. Map Headings

It allows users to map the document headings to the corresponding Sparx Enterprise Architect Element types.

Step 3. Map Properties

The Map Properties window lists all unique properties identified across the word document. Users can map these identified properties to the corresponding Sparx Enterprise Architect Element properties.

Note: Configure Connectors – This button should be enabled only when a user needs to map any of the columns as a “connector” in the EA Element Property. By default, the connector has some pre-selected values to import when using this button.

More Properties – In the EA Element Property column, we have an option called More Properties. By selecting ‘More Properties ‘from the drop-down, it displays ‘Additional Properties ‘.

In ‘Additional Properties ‘, the Properties drop box contains,

• Tagged Values
• Use case
• Glossary

Step 4. Map Tables

It allows the user to specify how element definitions specified in table format in the Word Document are mapped during the import process.

Step 5.Set Hierarchy

It creates a hierarchical structure in the Project Browser while importing from the Word document that reflects the structure of the model.  This helps to keep documents organized and easily accessible, improve collaboration among stakeholders, and better manage project tasks and issues.

Step 6. Review and create

It provides a summary of the mappings defined in the profile as well as a preview of the final model structure corresponding to the sample document.

 By following six simple steps, EA Word Importer allows us to create a profile successfully.  The Created Profile should be chosen in the EA Word Importer starting interface (refer Figure 1).  Using this Profile, allows the user to create EA Artifacts and their relationships from Word Document as displayed below.

Figure 3. Import Word Document as EA Artifacts using MDG Integration – Word Importer

Further Information

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

Time is a key aspect of the virtual world, and it is also a concern in models that represent the world. Time Aware Modeling is a powerful and expressive technique for defining and visualizing how model changes over time. The technique works by allowing a modeler to clone a package, diagram or element in a model also maintaining traceability to both earlier and later versions of model elements.

Key-Feature Benefits

• Easier to Analyse “As-Is” and “To-Be” model versions.
• Make updates to later versions without changing the ‘As-Is’ diagrams.
• Gain more control over how your entire model developed and that can be tracked.
• Create traceability diagrams that show each phase of the evolution of the elements.

Figure 1: Clone Structure as New Version

New Improvements in Sparx Enterprise Architect v16.1

• Exposed Interface element types are copied with cloned diagrams.
• Fixed error when cloning an element with embedded elements on a diagram enabled with ‘Collapse Embedded Elements’ option
• Traces created using abstraction connectors between cloned elements are showcased as a unique meaning in the traceability window.
• Annotation Elements are now cloneable artifacts.
• Support for Time Aware Modeling Version Structure branching has been included, along with support for Connectors to Connectors.

The basis of time-aware modeling is to clone a Package structure (Packages and diagrams only) as a new version, and then to replace specific portions of the old version with new elements and relationships using either the “Clone as New Version” capability or merely adding new material to the model as needed.

Note: This approach maintains traceability to both earlier and subsequent work while allowing for very selective incremental model adjustment or development.

Figure 2:Traceability Window

Further Information

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

Connectors, which link elements, are commonly described as lines on diagrams showing how the elements relate to one another. In natural languages, the Connectors are verbs that define how the nouns relate to each other if the elements are nouns. Now, we’ll take a closer look at importing the connector information using MDG Integration in Enterprise Architect.

MDG Integration for Microsoft Office – Excel Importer

The Excel Importer tool allows the user to import Excel workbook contents as model elements. It also involves adding/updating UML Elements, Connectors, Attributes, Methods, Test Scripts, Use Cases, Glossary, and Tagged Values to Enterprise Architect.

Profiles are used to define the mapping between the Excel document and the Enterprise Architect model

Two types of profiles are supported by the Excel Importer

• Object profile – Allows the user to import the Object and its properties into Enterprise Architect Model.
• Connector profile – Allows the user to import Connector and its properties to the existing objects in the Enterprise Architect Model.

Recalibrate Connector Information using Connector Profile

The connectors between the model elements are shown in the image below. (Connector Name, Stereotype, Alias, etc.,) needs to be updated for connectors using MDG Integration – Excel Importer.

                              Figure.1  Model Elements with Connectors.

The below image displays the excel sheet with connector information to be updated between the specific model elements. The Connectors largely depend on the source GUID and target GUID since they specify how the elements are related to each other.

Note: Source GUID and Target GUID are mandatory to create and Connector GUID is mandatory to update the Connector.

Figure 2.  Connector informatin in Excel

Mapping Connector Information in Connector Profile

The Connector Information in the excel is to be mapped to the appropriate EA Connector Property by using a drop-down list and select ‘more properties’ options (Connector Source & Target Information)

Figure 3.  Connector Profile Property Mapping.

You can update the below properties for the connectors that are imported into the model.

After importing the Excel using the created Connector profile, the connector Name, Stereotype, and Alias information are updated for its respective connector.

Figure 4.  Updated Connector Information using MDG Integration – Excel Importer.

Further Information  :

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

Sparx Enterprise Architect can be used to capture models that are associated with the ServiceNow tables and other artifacts. The capacity to connect the components of all models to one another is the key strength of Sparx Systems Enterprise Architect, the more time analysts and designers spend in creating attractive, well specified models, the greater the potential future benefit from any further changes to the systems. With Sparx Systems Pro Cloud Server users can easily integrate with ServiceNow to fetch tables into their Cloud model.

ServiceNow

ServiceNow is a ticketing system for customer service that processes and catalogues service requests. You can create queries for incidents, changes, problems, and other services using tools like ServiceNow. ServiceNow has had its roots in ITSM since 2012. With the advent of cloud computing and changing technology, however, it carved out a niche as a cross-departmental platform that operates as an enterprise cloud solution built on top of all other applications. Its method of developing business processes that optimize information extraction distinguishes it as a one-of-a-kind provider in today’s modern cloud space.

Key features of Integrating ServiceNow with Sparx Enterprise architect

• Map Enterprise Architect elements to their ServiceNow counterparts.
• Users can easily create a new Enterprise Architect element linked to a ServiceNow item.
• It provides better customer service while lowering maintenance costs.
• Customization is simple and easy with the help of ServiceNow integration.
• Users can link an existing element in Enterprise Architect to a ServiceNow item or create a new element in Enterprise Architect linked to a ServiceNow item.
• Changes to the Enterprise Architect element can be reflected in the ServiceNow item.
• Users can create a new ServiceNow item that is linked to an Enterprise Architect element.
• Conduct a traceability analysis.

Simple steps for configuring Snow Integration in PCS:

1.  Open Pro Cloud Config Client in Desktop.
2.  Click on the Integrations Tab in the config client window and enable the Integrations button.
3.  Click on Add button to Add the data provider
4.  Check ‘Enabled’ option
5.  Type the name for the provider (For ex: ServiceNow) in the field.
6.  Select ServiceNow in the provider drop down box
7.  In the ‘Server Name/IP’ field, type the server name or IP address that the ServiceNow Plug-in will use to communicate with ServiceNow
8.  In the port field Enter “443”
9.  In User Name field and Password enter the given credentials, (Under provider Server)
10. If needed, select the check box create items and modify items to create elements and modify
11.  Leave the check box ignore SSL Errors
12.  You can ignore other options and once you have finished. Click the “OK” button, which redirects to the Integration tab.
13. The ServiceNow Data Provider will be active, you must bound it to the Db by checking the check box or you can select all checkbox by selecting this option.
14.  Once you have selected, you must restart the PCS by heading to the task manager, click on the services tab and restart “Sparx Systems Professional Cloud”.

Further Information

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

Sparx Enterprise Architect can be used to capture business requirements, develop and manage all subsequent models, algorithms, process flows and workflows, design business data objects, and create other artifacts. 

The capacity to connect the components of all models to one another is the key strength of Sparx system’s Enterprise Architect, the more time analysts and designers spend in creating attractive, well specified models, the greater the potential future benefit from any further changes to the systems. 

Jama Integration with Sparx Enterprise Architect

• Jama Connect is a cutting-edge, team-based system for managing requirements and tests. It helps engineering, and software development teams to keep updated (in real-time) about their requirements and test plans throughout the course of a project.
• Jama integration through Pro cloud server is an amazing feature offered by Sparx Enterprise Architect.
• The seamless integration offers real-time synchronous access to the Enterprise Architect repositories. From any location in the world, users can work on the same model concurrently.

Key highlights of the Sparx Enterprise Architect integration with Jama

• Teams may connect Jama Connect with their ALM, PLM, development, and QA tools using Sparx Enterprise Architect.
• Connect with resources like QATest or Microsoft Project.
• Requirements and test cases between Jama Connect and Sparx Enterprise architect can be seamlessly synchronized between tools.
• Enhance collaboration, visibility, and traceability across your organization.
• Architect teams adopting a Model-Based Systems Engineering (MBSE) methodology can preserve Live Traceability inside Jama Connect while being integrated into another best-of-breed solution.

New Enhancements in Jama Integration with Sparx Enterprise Architect 16

• Enhanced Type and Field Mapping in System Integration.
• Optimized loading time of System Integration Comments tab in Inspector window
• Sync fields to newly created items.
• Improved tooltips for the System Integration windows navigation breadcrumb control.

Quick Jama Integration through PCS in 3-simple steps

• Open “Sparx Systems Pro Cloud Server Configuration Client”. Select the Add button in the Database Managers tab to add a database. Enable the Pro Feature for the database to enable Jama Integration under custom integration. Other third-party applications can also be integrated with the EA Cloud Model.
• Go to the Integration tab and create a Data Providers profile. Set a unique port for SBPI.exe, which is used for Integration feature, and enable Integration Feature.
• Select Add in Data Providers and Enter the required information.

Further Information

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

• The MDG Integration for Microsoft Office enables users to quickly import the data created in Microsoft Word & Excel documents within Sparx Enterprise Architect. 
• Sparx EA Users can easily upgrade existing static documents into rich traceable models with the help of MDG Integration for Microsoft Office.
• Users can automatically associate Sparx Enterprise Architect element properties and tagged values with the appropriate document sections and tables with ease. 
• With the new version of MDG office a key feature for SysML Requirement elements is added. The “SysML Requirements on Excel” feature would be a fantastic addition for System Engineering Users.

Key features in SysML Requirement in MDG office Integration 

• Import & Export a large amount of SysML requirements data from Excel, which avoids manual error.
• With the latest SysML requirement editor, Users can export the mapping data (derived SysML requirements) from their EA model to Excel in a Relationship matrix style, providing a convenient analysis of how the requirements are related to each other within the EA model.
• Users can easily push the contents of SysML Requirements from an Excel document to an EA or vice versa by selecting “SysML Requirement Manager” from the Feature menu.

SysML Requirements in Enterprise Architect

Using the “SysML Requirements on Excel” menu, users can export the data of SysML Requirement elements gathered in the EA Model as Excel documents.

Figure 1   –  SysML Requirements on Excel Feature

• Exported SysML Requirements data/information from Sparx Enterprise Architect contains the Name with its predefined properties id & text in the Requirements sheet.
• In the case of Requirement Matrix sheet, resembles a relationship matrix style contains Derived Requirements (mapped information of specific SysML Requirements).

Figure 2   –  SysML Requirements – Exported Information

Figure 3   –  SysML Requirements – Matrix Information

Further Information

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

In Sparx Enterprise Architect, the tagged values are exported and they are imported into Prolaborate as custom properties. In Prolaborate V4.2, we can import the tagged values xml file which is exported from Sparx EA. Custom colours can be applied for the Enumeration Tagged value.

• Create Tagged Value type from Predefined Types in EA.
  • Refer to the below Link for creating the tagged values: https://sparxsystems.com/enterprise_architect_user_guide/15.2/modeling/predefinedtaggedvaluetypes.html

• Export the Tagged value from Sparx EA
  • Once the tagged values are created, select “Configure > Transfer > Export Reference Data…” in Ribbon.
  • In the “Export Reference Data” window, Check the UML Types a Tagged Value Types and click Export button.

• Import the Tagged value in Prolaborate
  • Under Menu, select the “Modelling Languages”.
  • In the Modelling Languages window, Select the “Custom Properties” (Top Right Corner).
  • Select the “Import Custom Property” option in the Custom Properties window and choose the exported EA tagged value XML file.

• Add the Custom Property to corresponding UML Type element or Technology Type element.
  • Go to Modelling Languages and select the corresponding technology, For example ArchiMate 3.1 and select Default Profile.
  • Select the corresponding Stereotype Name to which the tagged values needs to be updated from the profile list.
  • Next, Add the New Group to the Form Designer (by clicking the ‘+’ icon), then drag and drop the tagged value from the Custom Properties.
  • Next, click save and go to the home page, To check for the default colour that is applied for the tagged value, select the appropriate stereotype (to which the tagged values is assigned) in the Prolaborate Project Browser.

Further Information

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