System Safety 6.0 (July 29, 2021)

Released: July 29, 2021
Model Version compatibility link: 7

A 40-day Free Trial Available!

Astah System Safety is a new MBSE tool for system engineers and safety engineers providing SysML, GSN, STAMP/STPA, SCDL all in one package.
A 40-day free trial is available before purchase. If you have tried it out already but want to evaluate it again, you can!

Try Now
section divider

Model Interchange with Cameo Systems Modeler

You can now export all the SysML diagrams to XMI that is compatible with Cameo Systems Modeler. Six types of SysML diagrams (Block Definition diagrams, Internal block diagrams, Activity diagrams, Parametric diagrams, Requirement diagrams, and Sequence diagrams) are supported. You can also import the same SysML diagrams from Cameo Systems Modeler to Astah.
Read User Guide

Astah System Safety Cameo Integration
section divider

Sync-Converter to maintain the model consistency

In Astah System Safety, you can convert SysML models to STAMP/STPA models or SCDL models and vice versa.
There is a new option “Sync-Convert” which lets the original model and converted model sync the content. So when you update one model, it will update the other converted model automatically.
This keeps your models stay consistent throughout the project without extra effort.

Astah System Safety Feature Image
section divider

Expanded API support for SysML diagrams

We have made progress in implementing APIs for project management, view-related and common diagram elements. We also supported APIs that include editing of requirement diagrams, state machine diagrams, activity diagrams, block definition diagrams, and internal block diagrams, mainly related to SysML. Please take advantage of the APIs that are now in place, along with the APIs for other models that were already supported.

API Support
section divider

More Improvements & Bug Fixes

[—] Implemented APIs that were not yet supported in general.
[234] Scrolling and other operations in the figure area of the comparison dialog have been improved.
[303] Reduced the risk of accidental overwriting when saving a file with project disambiguation.

Issues resolved in 6.0

[610] Active section split problem when deleting the middle of multi-stage self-message is fixed.
[537] Fixed an issue where an unintentional edit state would occur when trying to select.
[699] Fixed an issue where replacements would not be disabled when searching for models that are not referenced or drawn in the Find view.
[917] Fixed an issue where operations could be set on Reply messages with time constraints set.
[121] Fixed an issue where infinite recursion could occur when comparing projects with swapped parent-child relationships.
[221] Fixed an issue where the location of the project creator’s file is included in the reference string when the hyperlink destination is a root model.
[233] Fixed an issue where “Show All” would not work properly when there are links between topics in a mind map
[241] Fixed an issue where the icons in the plugin list are displayed too small in high resolution environments
[255] Fixed an issue where an exception would occur when using [Set Text Color] from the main menu while a cell in the table is selected.
[275] Issue where models with simple profiles or user-defined profiles are displayed in the search view has been fixed.
[287] Fixed an issue where Ctrl+right dragging while the context menu is displayed in the Diagram Editor would raise an exception.
[309] Fixed an issue where an exception could occur in certain steps in the search view.
[350] Fixed an issue where child topic edges would not be drawn after adding a new topic if the child topic was hidden when opening or closing a topic.

section divider


[769] Internal block diagrams, activity diagrams, parametric diagrams, requirement diagrams, and sequence diagrams in Cameo Systems Modeler models can now be imported.
[915] Internal block diagram and parametric diagram information can now be output in a format that can be imported by Cameo Systems Modeler.
[967] The [Model Correction] – [Check Invalid Models] function can now also detect invalid models in sequence diagrams.
[904] When duplicating a non-diagram, all the subordinate diagrams are opened in the editor, but now they are not.

Issues resolved in 6.0

[554] Fixed an issue where a realization between a port and an interface was generated to a block when the realization was removed from the diagram and the hidden relationship of the interface was displayed.
[714] When a dependency diagram element is connected from a port to a block or interface, the terminating diagram element is deleted along with the dependency diagram element.
[743] Fixed an issue where generalization lines and nested lines in shared notation are not merged properly.
[805] Fixed a problem in which Reply messages are not deleted if they are changed to asynchronous after a synchronous message is replaced.
[806] Fixed an issue in which the start of a Create message in a sequence diagram would not follow the start of the message if the parent lifeline of the interaction use was changed.
[823] Fixed an issue where the value of the argument set for the use of interaction in a sequence diagram would be cleared when copy-pasted.
[860] Fixed an issue where constraint properties would become unusually large vertically when a constraint parameter is created for a constraint property.
[868] Fixed an issue where multiple Reply messages could be created for interaction use or synchronization messages to a frame.
[871] Fixed an issue where a Reply message could be created when the target side of a synchronization Found message was an interaction use.
[878] Fixed a problem where a Reply message was not taken into account when replacing the end of a synchronization message with the source, which could result in an exception in subsequent operations.
[879] Fixed a problem in which an exception would occur and the message could not be replaced if a self-message was created when replacing the end of a vanishing message.
[880] Fixed a problem in which replacing a message with a frame terminated message so that it becomes a self-message would deviate from the execution specification.
[883] Fixed a problem where a dependency could be created on a frame in an internal block diagram.
[896] Fixed an issue where an error would occur if you moved the end of a message that terminated in a non-lifeline to the ancestor lifeline.
[901] Fixed an issue that could cause an error in the merge function
[927] Fixed an issue where a message could not be included when creating a compound fragment or when creating a message within a compound fragment
[929] Fixed an issue where copy-pasting a message with certain conditions would not paste correctly.
[948] Fixed an issue where requirements, test cases, actors, and use cases could be placed on a block definition diagram by adding related elements to the diagram or adding hidden relationships to the diagram.
[954] Fixed an issue where hidden relation lines connected to ports and properties could be redisplayed by adding the related elements to the diagram.
[958] Fixed an issue in which the execution specification would extend abnormally when creating a new message from a lifeline to which a Create message is connected.
[974] Added an item “Add related elements to diagram” to the context menu of blocks
[001] Fixed an issue where an exception could occur when certain key and mouse operations are performed while editing a mind map.
[732] Fixed an issue where the execution specification would shift from the lifeline or the end would shift in self asynchronous messages.

section divider


[254] The contents of SysML blocks and STAMP components can now be synchronized.

section divider


[51] The contents of SysML requests and SCDL requests can now be synchronized.

Issues resolved in 6.0

[39] Fixed a problem that caused an error when copy-pasting two requests between separately launched astah* System Safety.

section divider


[31] The content of SysML requests and GSN Goal can be synchronized.
[06] Drag and drop a SysML requirement onto a blank GSN diagram to create the corresponding Goal.
[965] By dragging and dropping a GSN Goal onto a blank space in a requirement diagram, the corresponding requirement can be created.