You can import models you created using Astah SysML into Astah System Safety (ver7.0 and later). This allows you to transfer your data from Astah SysML to Astah System Safety to use the advanced functionalities of Astah System Safety’s such as Cameo XMI import/export and much more! ※ Data transfer is available only one way. You cannot transfer the data back from Astah System Safety to Astah SysML.
Import Astah SysML files
Go to [File] – [import] – [Astah SysML Project (.asml)]
Choose the .asml file you want to import
If some models are changed or not imported completely due to the restrictions below, you will get a window explaining the details about them. Please read them through and click [OK] to complete the import. If you did not see this window, that means loading the .asml file completed successfully.
This indicates that the model was imported but some of its properties were changed or lost.
This indicates that the model was not imported.
This indicates that the project import completely failed.
You can also load from [File] – [Open] menu
You can also load the Astah SysML files directly from [File] – [Open] menu.
If you are on Windows, change the [Files of type] to enable you to choose the Astah SysML files (.asml) first.
Notes & Restrictions
There are some restrictions you should know before you load Astah SysML diagrams. At the import, some models will be automatically comforted to fit in Astah System Safety’s specification. This is because Astah System Safety and Astah SysML implement different versions of SysML. (Astah System Safety complies with SysML ver1.5 and Astah SysML does ver1.3.)
So here’re the descriptions of what will happen at the import.
Block Definition Diagram & Internal Block Diagram
The “ball-and-socket” connections between a Provided Interface and a Required Interface will be detached
A type will be automatically set for Ports that are connected to Realization or Usage Dependency if it was unspecified
Units and QuantityKinds will be imported without associations
Generalization between Interfaces and other Classifiers will not be imported
Interfaces will be imported without Active attribute
Generalizations will be imported without names
Multi-dimensional Multiplicity will not be imported. Only one dimension will be imported.
A type will be automatically set for Parts/External Parts if it was unspecified
Parts/External Parts will not be imported if its type was Actor
Value Properties owned by Constraint Blocks will be imported as Constraint Parameters
Only one presentation of Value Properties will be imported even though it was represented in other places
TestCases will be imported without ID.
UseCase Descriptions will not be imported.
Actors will be imported without Attributes/Operations
Processes will be imported as a simple action
Object Nodes will be imported without State, Effect, Exception and Stream
Connector and Process will be converted to Action
ActivityParameterNodes will be imported without State
Flow Final Node will be imported without InputPin and OutputPins
SendSignalAction will be imported without OutputPins
AcceptEventActions and AcceptTimeEventActions will be imported without InputPins
ObjectFlows will not be imported if there were created between models other than ObjectNodes, OutputPins, InputPins, and ActivityParameterNodes
Partitions will lose its Represent if it was Units or QuantityKinds
Submachine States will be imported without SubState
Submachine Sates without submachine will be imported as State
CombinedFragment (assert) will be imported with only a single top operand if it had plural operands
Messages will be imported without Guards, Return Value Variables and Return Value attributes
Lifelines will lose its type if it was Units or QuantityKinds
If there are stereotypes with the same name in one model, only one of them will be imported
At the import, stereotypes will be mapped with ones that match with from the predefined stereotypes
Stereotypes will be mapped to the corresponding Predefined Stereotypes.
If there is no corresponding Predefined Stereotype, it will be mapped to a Simplified Stereotype.
TaggedValues will be imported based on the stereotype that the model has and also when the stereotype matches with one in the predefined stereotypes in the Profile.
If the model has plural stereotypes, it will be imported based on the top-listed one
TaggedValues will not be imported if the model has no stereotypes or there is no match with predefined stereotypes.
Unsupported mini icons will not be imported.
Primitive types will be mapped to primitive value types in SysML profile.
If Model Elements have duplicate names, they will be renamed to be unique.