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: Add-ins

Add-ins

MDG Integration for Microsoft Office – BPMN Visualizer

BPMN Visualizer is a powerful tool that makes it easy to import BPMN contents from Microsoft Visio into Enterprise Architect using MDG Integration for Microsoft Office. The BPMN Visualizer has a user-friendly interface that simplifies the import process.

Key features in MDG Integration for Microsoft Office – BPMN Visualizer

  • It allows the user to import Visio BPMN shapes and connectors, along with their corresponding property values into Enterprise Architect.
  • We can also Import Non-BPMN Shapes from Visio document by mapping the defined EA BPMN Types and Stereotypes. Otherwise, it will be ignored.
  • It supports .vsd and .vsdx files.

Introducing the Interface

  1. Select the Microsoft Visio Document that contain the BPMN information that needs to be imported.
  2. Choose the profile that has been defined for the selected Visio document. If you don’t have a profile, click on ‘Create New’ option to Create a new profile

  3. Select Import to create the BPMN Information into model elements in Enterprise Architect.
Import Visio Interface

Figure.1 Import Visio Interface

Profile Mapping

Users can easily and adaptably map Visio documents to EA models using profiles. This makes it more effective.

To create a new profile, Specialize -> BPMN Visualizer -> Profile Manager -> Create New

Create new profile

Figure.2 Create New Profile

Profile Information: 

Profile Name The name of the profile
Description A brief description of the profile 
File Name Visio document path 
Only Show Unmapped Objects This option is used to display Unmapped Objects Separately. 
Checked – It only display the unidentified objects for mapping. 
Unchecked – It will display all objects from the Visio
GroupBy Type This option is used to group based on shape type. If the option is checked, it maps the same definition for all similar types 
Skip Unmapped Objects while Importing Used to skip the dialog that displays unidentified shapes while importing.  
Checked – Unidentified shapes will be ignored while importing. 
Unchecked – Unmapped objects window will get pop’s up to map the objects while importing. Refer here

Unmapped objects during import: 

It is used to map unidentified shapes like non-BPMN from a selected Visio document into EA BPMN element types and stereotypes. 

Mapping the Unmapped Shapes from Visio

Figure.3 Mapping the Unmapped Shapes from Visio

Table information in Profile Mapping 

Visio Shape Type Denotes the type of shapes present in the Visio Document 
Shape Name Displays the name of each shape from the document 
Object Type Display the EA BPMN element types that will be created in the EA Models. This column can also be modified via dropdown menu 
StereotypeDisplay the EA BPMN stereotypes that will be created in the EA Models. This column can also be modified via dropdown menu
Page Name Displays the name of the page where each shape is located within the Visio document 

By following the above simple steps, the user can import the Visio BPMN stencils and their relationships into Enterprise Architect with the help of profile mapping as displayed below.

Import Visio BPMN Stencils as EA Artifacts

Figure.4 Import Visio BPMN Stencils as EA Artifacts

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.

Add-insSparx Systems Enterprise Architect

MDG Integration for Microsoft Office – Excel Importer

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 to have a live demo about the new EA 16 features and capabilities.

Add-insSparx Systems Enterprise Architect 16

MDG Integration for Microsoft Office – Word Importer

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 to have a live demo about the new EA 16 features and capabilities.

Add-insSparx Systems Enterprise Architect

Recalibrate Connectors Information using MDG Integration – Excel Importer

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.

Connector InformationSourceInformationTargetInformationConstraints
AliasSource_Access,Target_Access,Pre-Condition
NameSource_Aggregation,Target_Aggregation,Post-Condition
NotesSource_Alias,Target_Alias,
SourceSource_AllowDuplicates,Target_AllowDuplicates,
SourceGUIDSource_Changeable,Target_Changeable,
StereotypeSource_Constraints,Target_Constraints,
StyleSource_Containment,Target_Containment,
TargetSource_Derived,Target_Derived,
TargetGUIDSource_DerivedUnion,Target_DerivedUnion,
GUIDSource_MemberType,Target_MemberType,
Tagged valuesSource_Multiplicity,Target_Multiplicity,
Source_Navigability,Target_Navigability,
Source_Ordered,Target_Ordered,
Source_Owned, Source_Role,Target_Owned, Target_Role,
Source_RoleType,Target_RoleType,
Source_Scope,Target_Scope,
Source_Stereotype,Target_Stereotype,
Source_QualifiersTarget_Qualifiers

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 to have a live demo about the new EA 16 features and capabilities.

Add-insSparx Systems Enterprise Architect 16

SysML Requirements Editor in Sparx Enterprise Architect 16

  • 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 to have a live demo about the new EA 16 features and capabilities.