15.1. Importing Models from External SysML Tools

The import process for each supported tool is described in the section about that tool. Each section lists the prerequisites for that particular tool. Before you import System/Function Models, make sure that your installation meets these prerequisites.

To import a SysML model, in medini analyze, you navigate in the model browser to a project package that supports system design, then launch the import wizard for the type of model you want to import. During import, medini analyze stores the metadata needed to later perform an update of the imported model.

For most importers, not all model elements are imported into medini analyze. For example, if a stereotype is missing or changed in a concept in the original model, medini analyze does not import it. To see what concepts can be imported, see Concepts Supported During Import.

Imported models are labeled with a decorator in the Model Browser, for example, "[Rhapsody]" for IBM Rational Rhapsody.

After you have imported a model, you can extend it with safety-related information, just as you would for a SysML model you created directly in medini analyze. There is no difference in the usage of an imported model and a model created in medini analyze. Note that additions and changes to an imported model are kept during an update.

15.1.1. Concepts Supported During Import

The following table lists only the concepts that are supported in the medini analyze integration, by tool. The last column lists the corresponding SysML concept in medini analyze. Note that any concepts not listed in the table are not imported. You can download a PDF of the table.

Table 15.1: Supported Concepts in medini analyze

IBM RhapsodyCameo (MagicDraw)Enterprise ArchitectSCADE ArchitectAnsys SAMmedini analyze
  • Package

  • UseCase

  • Package

  • UseCase

PackagePackage
  • Package

  • Import

SysMLPackage
  • Activity_D

  • Block

Block
  • Class

  • Block

  • Component

Block (Definition)Part DefinitionSysMLBlock
ProjectProjectModelProjectProjectSysMLModel
InterfaceBlock1InterfaceBlock1InterfaceBlock1--PortDefinitionSysMLPortDefinition
PartPartPart
  • Block (unique)

  • Block (replica)

PartSysMLPart
ValueType2ValueType2ValueType2--VALUE TYPESysMLAttributeDefinition
Block15
  • Block15

  • Signal16

Block15--ItemDefinitionSysMLItemDefinition
FlowProperty, FlowProperties3FlowProperty, FlowProperties3FlowProperty3--ItemSysMLItemUsage or SysMLAttributeUsage
Enum4Enum4Enum4--EnumerationDefinitionSysMLEnumerationDefinition
Enum Literal5Enum Literal5Enum Literal5--EnumerationSysMLEnumerationUsage
--------SysMLAttributeDefinitionSysMLValueType
ValueProperty6ValueProperty6ValueProperty6--AttributeSysMLValueProperty
  • FlowPort7

  • ProxyPort7

  • Standard Port7,9

  • FlowPort7

  • ProxyPort7

  • Standard Port7,9

Port/FlowPort7,8FlowPortPortSysMLPortUsage
  • Connector

  • Flow

  • Connector

  • Flow

  • Connector

  • Information Flow

  • Connector

  • Flow

  • Connector

  • Interface

SysMLConnector
ActivityDiagramActivityDiagramActivity (Top-Level)Activity (Diagram)--SysMLActivity
ActionActionAction (kind: Atomic)----SysMLAction
SendActionSendActionAction (kind: SendSignal)----SysMLAction (Stereotype "SendAction")
AcceptEventActionAcceptEventActionAction (kind: AcceptEvent)----SysMLAction (Stereotype "AcceptEventAction")
CallBehaviorCallBehaviorAction (kind: CallBehavior)----SysMLAction (Stereotype "CallBehavior")
CallOperationCallOperationAction (kind: CallOperation)----SysMLAction (Stereotype "CallOperation")
ObjectNodeObjectNodeObject, CentralBufferNode----SysMLObjectNode
TransitionTransitionObjectFlow, ControlFlow----SysMLActivityEdge
DefaultTransitionDefaultTransition------SysMLInitialNode + SysMLActivityEdge
----ActivityInitial----SysMLInitialNode
----
  • ActionPin

  • ObjectNode

  • ActivityParameter

----SysMLPin
InterruptibleRegionInterruptibleRegion------SysMLStructuredActivity (Stereotype "InterruptibleRegion")
----
  • Activity (Nested)

  • InterruptibleActivityRegion

  • ExpansionRegion

  • ExceptionHandler

  • ActivityPartition

----SysMLStructuredActivity
SwimLaneSwimLane------SysMLStructuredActivity (Stereotype "SwimLane")
  • ActivityFinal

  • FlowFinal

  • ActivityFinal

  • FlowFinal

  • ActivityFinal

  • FlowFinal

----SysMLFinalNode
  • DecisionNode

  • MergeNode

  • DecisionNode

  • MergeNode

  • Decision

  • MergeNode

----SysMLDecisionMerge
  • JoinConnector

  • Fork

  • JoinConnector

  • Fork

Synchronization----SysMLForkJoin
Allocation10Allocation10------SysMLAbstraction (Stereotype "allocate")
--
  • Dependency

  • Usage14

Dependency--DependencySysMLDependency
Operation11--------SysMLActivity (Stereotype "function")
Requirement11--------SysMLAbstraction (Stereotype "requirement")
Satisfaction11--------SysMLAbstraction (Stereotype "allocate")
Imported as screenshots11BDD, IBD, and Activity diagrams are imported12Imported as screenshots13IBD diagrams, imported as read-onlyDiagrams are imported as read-onlyDIAGRAMS

  1. Import only to SysMLv2 concept

  2. SysMLv2 concept, corresponds to ValueType in SysML 1.x

  3. Import only to SysMLv2 concepts, when using SysML Profile

  4. SysMLv2 concept, corresponds to Enum in SysML 1.x

  5. SysMLv2 concept, corresponds to Literals in SysML 1.x

  6. SysMLv2 concept, corresponds to ValueProperty in SysML 1.x

  7. SysMLv2 concept, corresponds to Port in SysML 1.x

  8. Import can be customized

  9. Import can be disabled

  10. Allocations to other Dependencies are not imported

  11. Experimental feature

  12. The imported diagrams are read-only and show only elements that are imported

  13. Import is optional. See also Importing Diagrams from Enterprise Architect

  14. A Usage is translated into a SysMLDependency with stereotype "uses"

  15. A Block that is used to type a Flow Property is translated into a SysMLItemDefinition

  16. A Signal that is used to type a Port is translated into a SysMLPortDefinition containing one instance of the SysMLItemDefinition

15.1.2. About the Import of SysML Diagrams

How the import of model diagrams is handled in medini analyze depends on the third-party tool from which you are importing.

Cameo/MagicDraw and SCADE Architect Diagrams

Diagrams imported from Cameo/MagicDraw and SCADE Architect are imported as read-only native medini analyze diagrams.

You can navigate read-only diagrams in medini analyze. You can also make a copy of the diagram and edit it in medini analyze.

The import does not include elements that are not supported by medini analyze, so the imported diagram does not look exactly like the original. For more information about which elements are supported during import, see Concepts Supported During Import.

Rhapsody and EA Diagrams

Diagrams imported from Rhapsody or EA are imported as screenshots.

A screenshot of the diagram is added as JPG or SVG files. The screenshot contains all the elements of the original diagram, but you cannot edit the file or navigate it. You can use it as a guide for creating a new diagram in medini analyze. Note that importing the diagram as a screenshot is optional.

For more details about importing diagrams from EA, see Importing Diagrams from Enterprise Architect.