Blog

safeTbox V3.2 Official Release

 

safeTbox stands for Safety Toolbox and it aims at supporting the development of E/E/PE embedded systems with safety critical characteristics. Most of the offered techniques can be used in different domains. However, the tool offers special support for the automotive domain and its associated standard ISO 26262. safeTbox integrates modelling as well as analysis capabilities. Thanks to its integrated approach, it also enables traceability between modelling artefacts.

We hereby would like to welcome you to the release of SafeTBox version 3.2. There are a couple of updates in this version that we hope you will like and enjoy. 

Some of the key highlights include: 

  • Export of HARA artifacts as Excel spreadsheets
  • Introduction of individual set of settings for HARA sheets
  • Extended automation for GSN goals
  • Enhanced the CFT analysis results 

A detailed description of these highlight can be found below.

 

 

Hazard and Risk Assessment - HARA

The HARA can now be exported as an Excel spreadsheet, making it easier to share outside of safeTbox   

 

 

 You can now set individual settings for the HARA sheets and also import and export the settings.

 

 

Other minor changes in HARA

  • Sorting functionality in the sheets have been enhanced

  • Context menus have been reorganized

  • Synchronization for HARA has been reworked for usability purposes

 

Assurance Cases

The modelling automation for Goal Structuring Notation (GSN) goals has been extended by automatically turning goals to public and adding an away goal to the module referencing the given goal, when connecting goals to module elements

 

 

Component Fault Tree Analysis

The CFT analysis results have been enhanced by adding the parent paths of the prime implicants, to provide more detailed analysis results

 

Usability

You can now reproduce the Ports layout between classifiers and instances in both directions. 

 

You can automatically connect the ports at component models and component fault trees (CFTs) by using different strategies.

 

The cloning of realization views allows you to decide for partial and full cloning of interfaces. This helps when you are looking for reusability of your components, either at the model or component-fault-tree level

  

Bug and issues corrections

  • GSN referencing issues

  • Corrected loop detection mechanisms

  • Over-controlling modelling for SysML avoided.

  • HARA ASIL selection