Skip to main content Skip to complementary content

Borland Together (via UML 2.x XMI) - Import

Availability-note AWS

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

Bridge Specifications

Vendor Borland
Tool Name Together
Tool Version 6.x to 2006
Tool Web Site http://www.borland.com/us/products/together/
Supported Methodology [Object Modeling] Data Store (Object Model UML Class Diagrams) via UML XMI File
Data Profiling
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection

SPECIFICATIONS
Tool: Borland / Together version 6.x to 2006 via UML XMI File
See http://www.borland.com/us/products/together/
Metadata: [Object Modeling] Data Store (Object Model UML Class Diagrams)
Component: OmgUml2XmiImport.BorlandTogether version 11.2.0

OVERVIEW
Imports an XML file compliant to the Object Management Group (OMG) Unified Modeling Language (UML) 2.x XML Metadata Interchange (XMI) 2.x file format. While the OMG specification is clear on some metadata concepts, some concepts are not fully defined, including:

- Diagram information including objects contained, object placement, color, font and other graphical information.
- Data type information including standard native data type information that may be mapped consistently to the MIR metamodel.

Because of this flexibility, potential non-conformities exist between XMI exported from various design tools which support the 2.x format. Three tools are explicitly supported: Borland Together, IBM Rational Software Architect, and Sparx Enterprise Architect. These tools vary in their support for the specification and the way in which they vary from it, thus it is important to refer to this bridge mapping specs for the specific tool in order to determine what metadata is migrated and to what extent.

REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at https://www.metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html

SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6

THIRD-PARTY TOOL SPECIFIC INFORMATION

BORLAND TOGETHER

Generating a supported OMG 2.x XMI file:

1. Open the project with the model to export in Borland Together
2. Right-click on the Project in the Project Browser
3. Select 'Export Model to XMI'

Summary of Known limitations:

Diagramming information is not imported.

IBM RATIONAL SOFTWARE ARCHITECT (RSA)

Generating a supported OMG 2.x XMI file:

1. Open the model to export in IBM RSA
2. Go to the 'File' menu and select 'Export'
3. Select 'Other' > 'UML 2.1 XMI Interchange Model'
4. Browse to the model you wish to export and select it
5. Specify a file to export to

Summary of Known limitations:

1. Diagramming information is not exported to XMI and thus not imported
2. User defined properties (UDPs) are not exported to XMI and thus not imported

SPARX ENTERPRISE ARCHITECT

Generating a supported OMG 2.x XMI file:

1. Open the project with the model to export in Sparx EA
2. Right-click on the Project in the Project Browser
3. Select 'Export Model to XMI'
4. Select 'XMI 2.1'

Summary of Known limitations:

Diagramming information is not exported to XMI and thus not imported.

VISUAL PARADIGM FOR UML

Generating a supported OMG 2.x UML XMI file:

1. Open the project with the model to export in the tool
2. Go to the File menu and select Export -> XMI
3. Inside the 'Export XMI' dialog box be sure to select the following items (in the 'XMI Version' section):
- 'XMI 2.1'
- 'Export to for UML2'
- 'Export Data Type to: UML Primitive Type'
- 'Export ... to Interface'
- 'Export Interface Realization'

Summary of Known limitations:

Diagramming information is not exported to XMI and thus not imported.


Bridge Parameters

Parameter Name Description Type Values Default Scope
File Imports an XML file compliant to the Object Management Group (OMG) Unified Modeling Language (UML) XML Metadata Interchange (XMI) file format. Imports versions of the UML 2.1 metamodel and XMI 2.1 format. FILE
*.xml
*.xmi
*.uml
*.uml2
  Mandatory
Top Package The metamodel requires that all model elements (Classes, Associations...) belong to a package. Whenever any element is not explicitly associated to a package it is stored in a special package. This option specifies the name of that package. If there is a single top level package by that name in the model, package is considered optional so that it will not appear in the destination model if the destination tool does not require all objects to be in the package. STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Borland Together (via UML 2.x XMI)"
Metamodel
OmgUml2Xmi
Mapping Comments
     
Association uml:Association  
Aggregation   True if one of the AssociationRoles has aggregation set to composite.
Description packagedElement / ownedComment / body Enterprise Architect contains a description in model extension.
AssociationRole uml:Property  
Multiplicity ownedEnd / lowerValue ownedEnd / upperValue or ownedAttribute / lowerValue ownedAttribute / upperValue  
Ordered ownedEnd.isOrdered or ownedAttribute.isOrdered  
Attribute uml:Property  
CppDerived ownedAttribute.isDerived  
CppScope ownedAttribute.visibility  
CppStatic ownedAttribute.isStatic  
Description ownedAttribute / ownedComment.body / body Enterprise Architect contains a description in model extension.
InitialValue ownedAttribute \ defaultValue.value  
Name ownedAttribute.name  
Position   Order in the XMI file
BaseType uml:PrimitiveType (ownedAttribute / type or ownedOperation / type) Attribute, Operation
DataType   See datatype conversion array
Name type.href Enterprise Architect contains a type name in model extension.
Class uml:Class  
CppAbstract packagedElement.isAbstract  
Description packagedElement / ownedComment.body / body Enterprise Architect contains a description in model extension.
Name packagedElement.name  
DerivedType uml:PrimitiveType (ownedAttribute / type or ownedOperation / type) Attribute, Operation
DataType   See datatype conversion array
Name type.href Enterprise Architect contains a type name in model extension.
UserDefined   Set to 'true'
DesignPackage uml:Package  
Description packagedElement / ownedComment.body / body Enterprise Architect contains a description in model extension.
Name packagedElement.name  
Generalization uml:Generalization  
Description generalization / ownedComment.body / body Enterprise Architect contains a description in model extension.
GeneralizationRole generalization.general  
Operation uml:Operation  
CppScope ownedOperation.visibility  
CppStatic ownedOperation.isStatic  
Description ownedOperation / ownedComment.body / body Enterprise Architect contains a description in model extension.
Name ownedOperation.name  
Position   Order in the XMI file
PropertyElementTypeScope User Defined Property Tools contain it in model extension.
Scope UDP Class  
PropertyType User Defined Property Tools contain it in model extension.
Name tag Set to the name of the tag
Usage   set to User
PropertyValue User Defined Property Tools contain it in model extension.
Name tag Set to the name of the tag
Value value Value of the tag
StoreModel uml:Model  
Description uml:Model / ownedComment.body / body Enterprise Architect contains a description in model extension.
Name uml:Model.name  

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!