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 proud to announce the release of version 2.0 of our safety modeling tool safeTbox™. In this version, the following capabilities have been added: 

Modeling capabilities 

Goal Structuring Notation (GSN)

Create structured and modular safety arguments with the well-known GSN modeling technique. You can use it to create process-related argumentation, such as safety cases, as well as product-specific arguments, such as safety concepts. Moreover, you can easily create references/traces to other model constructs (e.g., UML/SysML blocks, components, ports, fault trees, …). Traceability is supported in an efficient manner by a customizable auto-completion user interface suggesting elements based on the current word written.

Read more ...

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 ...

We are happy to announce that safeTbox version 1.0 is available from now on for all registered users of this website. With this initial version of our safety modeling tool, you will have the possibility to integrate failure model specifications into existing system design models in the general purpose modeling tool Enterprise Architect by Sparx Systems. These system design models can either be created with the SysML 1.4 profile extension of Enterprise Architect or with our own architecture modeling profile having plenty of usability features supporting the efficient creation of models. Regarding SysML, we primarily support the integration of blocks and component fault tree analysis (CFT). This enables you to define complex failure behavior in a modular and compositional way being formally connected to your system design models. Based on these models, qualitative and quantitative failure analyses can be performed.