We would like to inform you that the development activities for release 2.0 of safeTbox are ongoing. We expect to release this new version of the tool by the end of NovemberIn this new version, we plan to include some new features, which are intended to make YOU as engineer more effective and efficient during crafting safety-critical software systems.

Press read more to see more detailed descriptions of the new features from the areas Modeling techniques, Fault Tree Analysis, Infrastructure & Usability enhancements being planned for safeTbox release 2.0.

In order to directly start trying out our new model-based safety engineering tool, perform a free registration to obtain access to your personal account in which you will be able to download current and future versions of the tool for free. After registration, you can download the most current install setup of the tool and a fitting trial license being valid for one month. After this period of time has passed you will have to Contact Us to request for an extension of your license. In order to get safeTbox 1.0 running on your machine, Enterprise Architect v12.0+ is required. Don't forget to stop by in the online resources section where the safeTbox user manual as well as an example model can be downloaded to explore the capabilities of safeTbox.

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.