Import from Astah SysML (astah* System Safety) (astah* SysML)

Overview

You can import the project files (.asml file) created by Astah SysML into Astah.

How to Import

  1. Select [File]-[Import]-[Astah SysML Project (.asml) …], or [File]-[Open].

select_import_menu
  1. In the Open dialog, select the project and click [Open]. If you are on Windows, change the [Files of type] to enable you to choose the Astah SysML files (.asml) first.

open_import_file
  1. Selected project will be imported into Astah.

  • If there are any problems or information with the import result, they will be displayed.

  • Problems and information may be displayed across multiple lines, and each with the following levels of status.

    • INFO: This indicates that the Model Element was imported but some of its properties were changed or lost.

    • WARNING: This indicates that the Model Element was not imported.

    • ERROR: This indicates that the project import completely failed.

Attention

General Precautions

There are some restrictions you should know before you load Astah SysML diagrams.
At the import, some Model Elements will be automatically comforted to fit in Astah’s specification.
This is because Astah and Astah SysML implement different versions of SysML.
(Astah complies with SysML ver1.5 and Astah SysML does ver1.3.)
  • This version has the following restrictions.

  • Mini Icons that are not supported by Astah will not be imported.

  • The following are affected by improved conformance to the specification.

  • Primitive types are mapped to primitive value types in SysML profile.

  • Same Stereotype cannot be applied to the same Model Element twice.

  • If Model Elements have duplicate names, they will be renamed to be unique.

  • For better conformance to the specification, Stereotypes and Tagged Values are treated as follows.

  • Stereotypes will be mapped to the corresponding Predefined Stereotypes.

  • If there is no corresponding Predefined Stereotype, it will be mapped to a Simplified Stereotype.

  • Tagged Values are defined by the Stereotype in the Profile.

  • Tagged Values are defined by the first Simplified Stereotype that are applied to each Model Element.

  • For Model Elements that do not have any Simplified Stereotype applied, Tagged Values are ignored.

Requirement Diagram

  • The following are affected by improved conformance to the specification.

  • TestCases cannot have an ID attribute.

Block Definition Diagram

  • This version has the following restrictions.

  • Required and Provided Interfaces that are combined in a “channeled ball-and-socket” notation will be imported separately.

  • The following are affected by improved conformance to the specification.

  • If the Type of Port connected to by Realization or Usage Dependency is <<Unspecified>>, appropriate Type will be set.

  • Association cannot be connected to Unit or QuantityKind.

  • Generalization cannot be connected between Interfaces and other Classifiers.

  • Interfaces cannot have an Active attribute.

  • Generalization cannot have a name attribute.

  • Multi-dimensional Multiplicity is not supported.

Internal Block Diagram

  • This version has the following restrictions.

  • Required and Provided Interfaces that are combined in a “channeled ball-and-socket” notation will be imported separately.

  • The following are affected by improved conformance to the specification.

  • If the Type of Part or External Part is <<UnknownType>>, the appropriate Type will be set.

  • Part or External Part whose Type is Actor will not be imported.

  • If the Type of Port connected to by Realization or Usage Dependency is <<Unspecified>>, appropriate Type will be set.

  • Interfaces cannot have an Active attribute.

Parametric Diagram

  • The following are affected by improved conformance to the specification.

  • Value Properties owned by the Constraint Block will be imported as Constraint Parameters.

  • If Value Property has multiple Diagram Elements, only one of them will be imported.

UseCase Diagrams

  • This version has the following restrictions.

  • UseCase Description will not be imported.

  • The following are affected by improved conformance to the specification.

  • Actors cannot have Attributes and Operations.

Activity Diagram

  • This version has the following restrictions.

  • Diagram Element of Connector will be simplified to Action.

  • ObjectNodes and ActivityParameterNodes cannot have State attributes.

  • Stereotypes cannot be applied to ObjectNodes.

  • The following are affected by improved conformance to the specification.

  • Diagram Element of Process will be simplified to Action.

  • Flow Final Node cannot have InputPin or OutputPins.

  • SendSignalAction cannot have OutputPin.

  • AcceptEventActions and AcceptTimeEventActions cannot have InputPins.

  • ObjectNodes cannot have Effect, Exception, or Stream attributes.

  • ObjectFlows cannot be connected except between ObjectNodes, OutputPins, InputPins, and ActivityParameterNodes.

  • Unit and QuantityKind cannot be referenced as Represent of Partition.

Statemachine Diagram

  • The following are affected by improved conformance to the specification.

  • SubmachineState cannot own StubState.

  • Submachine states that have no submachine are imported as states.

Sequence Diagram

  • The following are affected by improved conformance to the specification.

  • CombinedFragment (assert) cannot have multiple Operands.

  • Messages cannot have Guards, Return Value Variables, or Return Value attributes.

  • Unit and QuantityKind cannot be referenced as Lifeline Type.