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

We are proud to announce the release of version 3.1 of our safety modeling tool safeTboxTM. Besides improving safeTbox by fixing some bugs (many thanks to the users that reported issues), in this version, we added the following capabilities:

Modeling capabilities 

Table view

Some times the same attribute of multiple elements have to be changed. Instead of changing them one by one, the new table view lets the user list elements within a diagram within a table, where the attributes can be changed at once. The table view can either be opened for diagram, elements, and packages selected within the project browser or for several selected elements within a diagram. To open the table view, open the smart menu and choose Comfort -> Table View.

Within the table view, the user can filter listed elements by their stereotypes or simply exclude single elements and/or their child elements.

Read more ...

We are releasing a mandatory hotfix that addresses several issues:

• Extended SysML support
• Updated security protocols
• Updated license checking to support different localization settings
• Minor bugs and usability improvements

We are proud to announce the release of version 3.0 of our safety modeling tool safeTbox™. In this version, the following capabilities have been added:

Modeling capabilities 

Hazard and risk assessment (HARA)

In this version, we support hazard and risk assessment according to ISO 26262. This supports the user in the following tasks:

• Functional Hazard Analysis: For selected functions/components, the user can perform a high-level fault analysis with the help of a configurable set of guide words (e.g., Omission, Commission,…). This template allows the user to document the effects of such failures and to determine whether they are safety-critical or not. If they are, the user can also define and associate hazards with them.
• Definition of hazardous events (HE): Given a set of hazards, the user can build hazardous events by defining in which situations these occur. Moreover, the user can also define a hazardous event’s occurrence parameters (e.g., regarding the frequency or the time domain) as well as the expected outcome (e.g., an accident). This implementation also allows the user to define their own scenarios by specifying situation groups (e.g., category Driving Location: highway (over 100 km/h), city (50 km/h),…). The current template makes a clear differentiation between driving and standing situations to simplify the analysis and configuration.
• Definition of safety goals: Having defined the hazardous events, it is then possible to define the severity and the controllability parameters for these HE, for which the system will compute automatically the ASIL. The template allows the user to define safety goals and assumptions related to the assessment of HE.

Read more ...